How it works

Create a Source, submit a transcoding Job, and receive webhook notifications.

This guide documents the legacy Jobs API (/jobs). Existing Jobs API integrations remain supported during the transition. For automatic file encoding, see the transcode guides.

Here are the main steps to create a transcode with the legacy Jobs API:

flowchart LR
    hosted(Hosted File)-->source
    local(Local File)-->upload(Upload)-->source(Source)-->job(Transcoding Job)--Notifications-->webhooks(Webhooks)

Create a source

Create a Source from an HTTP or HTTPS URL, a file in your storage, or an upload.

For a file in your storage, provide storage.path and optionally storage.id. Omit the ID when your storage is already the Project default.

We recommend hosting source files in S3 or equivalent cloud storage for reliable access during processing.

See Video upload for the setup steps.

Create a transcode

Use the Source ID to create a Job with your chosen format and encoding settings. When the Job finishes, the video is available in its output storage.

See output paths for file locations, or explore storage, video formats, and transcoder settings.

Chunkify's default temporary storage is for testing. Files are deleted after 24 hours. For production, use your own storage to keep the files you need.

Webhooks and Notifications

Receive a webhook when a Job completes or fails so your application can use the result or handle the error. See Webhooks for setup and verification.

Start Now !

Use the CLI or the Transcodings API to create a transcode.

Chunkify CLI

The easiest and fastest way to get started

Transcodings API reference

See the request fields and SDK examples for creating a transcoding.