Getting Started with Media Storage
Introduction
Qencode supports saving output files to various destinations. Our goal is to make it as easy as possible for you to manage your video content in Qencode S3, as well as across the top cloud storage platforms like AWS S3, GCP, Azure Blob, DigitalOcean Spaces, and Backblaze B2.
Whether you need to store source files, transcoding outputs, live streaming recordings, or other media assets, this step-by-step guide is designed to get you up and running.
Supported Destinations
- Any S3-compatible storage
- Qencode S3
- AWS S3
- Google Cloud Storage
- DigitalOcean Spaces
- Wasabi
- Cloudflare R3
- Backblaze B2 (also available as an S3 gateway)
- Azure blob
- FTP(s)
- SFTP
- Aspera
General structure of the destination object
The approach to specifying the destination URL depends on the format and output type. For outputs that produce a single file, like mp4, webm, mp3 or thumbnail you should specify the full path including the file name and extension. For outputs containing a set of files or folders with files you specify the path to the folder on your storage where the output should be saved to.
The destination object must include the url param having the following structure:
protocol://host[:port]/bucket/pathProtocols
| s3:// | for any S3-compatible storage (Qencode, AWS, GCS, DigitalOcean, etc.) |
| b2:// | for Backblaze B2 |
| azblob:// | for Azure Blob Storage |
| ftp:// or ftps:// | for any FTP server |
| sftp:// | for any FTP over SSH server |
The host naming convention is defined below for each protocol and storage solution supported. You can optionally specify a port. The default port value is defined by the protocol used.
The list of providers:
- AWS S3
- Qencode S3
- Google Cloud Storage
- DigitalOcean Spaces
- Wasabi
- Cloudflare R3
- Generic S3
- Backblaze B2
- Azure blob
- FTP(s)
- SFTP
- Aspera