Qencode
DEVELOPERS
All
All
API Reference
API Reference
Tutorials
Tutorials
Release Notes
Release Notes
Try QencodeSign In
HomeAPI ReferenceTutorialsRelease Notes
On this page
On this page

Getting Started with Third Party Storage

Introduction

General considerations

Qencode supports saving output files to various destinations. You will find a detailed instruction for each supported provider and protocol below. Please also note, the approach to specifying the destination URL depends on the output. 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, like HLS or DASH outputs, you specify the path to the folder on your storage where the output should be saved to.

Supported destinations

  1. Any S3-compatible storage (including but not limited to):
  • Qencode S3
  • AWS S3
  • Google Cloud Storage
  • DigitalOcean Spaces
  • Wasabi
  • Cloudflare R3
  1. Backblaze B2 (also available as an S3 gateway).
  2. Azure blob
  3. FTP(s)
  4. SFTP

General structure of the destination object

The destination object must include the url param having the following structure:

protocol://host[:port]/bucket/path

where protocol can be one of the following:

  • 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: