Turn one source video into the renditions you actually ship — MP4 files at several resolutions, an HLS adaptive ladder, thumbnails, preview GIFs — written straight into your own S3-compatible bucket. Manage jobs on the Video Transcoding page in my.cubepath.com.
It's the standard pattern for VOD platforms, user-generated content pipelines, course and webinar processing, and any case where you have a stack of source files and need consistent multi-format output without running ffmpeg yourself.
How it works
You create a job: an input (a public URL or an object in your S3 bucket), an output destination (your bucket plus a path prefix), and the list of formats you want. We fetch the source, cut it into segments, encode them in parallel across as many workers as capacity allows, package the results, and upload everything under your prefix.
Because the work is split into segments rather than streamed through one encoder, a long file finishes in a fraction of the wall-clock time it would take on a single machine — and you can watch the segment counter move while it happens.
ImportantYou bring the storage. Input and output both point at any S3-compatible endpoint — CubePath Object Storage, AWS S3, Cloudflare R2, Backblaze B2, Wasabi, MinIO. Your credentials are used only for that job and stored encrypted; we never echo them back and we never keep your media.
The pages
| Page | What it covers |
|---|---|
| Create a job | The source, the destination bucket, the credentials a job runs with, and the two optional fields that save you the most trouble later |
| Outputs | The four output types, their parameters, and exactly which files each one writes |
| Job status | The lifecycle, progress and segments, webhooks, cancelling, and what to do when a job fails |
| Batches and limits | Submitting up to 1000 sources at once, idempotency, and the rate and volume limits you'll meet at scale |
What it doesn't do
- It doesn't store your media. Input and output live in your buckets; there's no "download from CubePath" step.
- It isn't a streaming server. It produces HLS you can stream; serving it, and access control, is your CDN's job. Put a CDN zone in front of the bucket and you have a delivery path.
- It isn't an editor. It transcodes, packages, thumbnails and clips to GIF — it doesn't cut, splice, overlay or colour-grade.
TipThe full API (jobs, batches, status, outputs, cancellation) is documented at api.cubepath.com — it's the right interface once you're processing more than a handful of files.