A Zencoder alternative. Transcoding jobs over HTTP.

If you send Zencoder jobs today, Videxo takes the same shape of request: one input, the outputs you want and a URL to call when they are ready. Here is how the two compare and how your jobs map over.

Get an API key Read the docs

curl "$VIDEXO_API_URL/v1/transcode" \
  -H "Authorization: Bearer $VIDEXO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "input": "https://videxo.io/samples/talk.mp4",
  "preset": "web-720p",
  "filename": "talk-720p.mp4",
  "metadata": {
    "order": "1234"
  }
}'

const response = await fetch(`${process.env.VIDEXO_API_URL}/v1/transcode`, {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.VIDEXO_API_KEY}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    "input": "https://videxo.io/samples/talk.mp4",
    "preset": "web-720p",
    "filename": "talk-720p.mp4",
    "metadata": {
      "order": "1234"
    }
  }),
});
const job = await response.json();

Side by side

Videxo and Zencoder. Checked on Nov 5, 2026.

Videxo and Zencoder, as their own pages describe them on Nov 5, 2026
Topic	Videxo	Zencoder
Before the first job	An API key as a Bearer token. No bucket, role or queue to create.	An API key from the account, sent in the Zencoder-Api-Key header.
How a job is described	JSON operations, or the ffmpeg command you already run, checked before the job is created.	A JSON job: one input and up to 20 outputs with encoding settings.
Where outputs go	Stored for your plan’s retention, 7 days to 30 days, with signed download links that last up to an hour.	Uploaded to your S3, Google Cloud Storage, Azure, FTP or SFTP; without a destination, kept for 24 hours.
When a job ends	A webhook URL per job or endpoints on your account, signed in the Standard Webhooks format and retried for about a day.	Notifications to a URL you set on the job or an output.
Streaming formats, live, DRM	Files in, files out. Adaptive streaming (HLS) and a player Soon	HLS and DASH outputs, with DRM options.
AI assistants (MCP)	An MCP server that checks, runs and waits for jobs with your API key.	None in the Zencoder docs. Brightcove’s MCP server covers Video Cloud accounts, not Zencoder jobs.
Company	BEO TECHNOLOGY sp. z o.o., Poland, in the European Union.	Brightcove; Zencoder is a Brightcove product.

Videxo

Before the first job

An API key as a Bearer token. No bucket, role or queue to create.
How a job is described

JSON operations, or the ffmpeg command you already run, checked before the job is created.
Where outputs go

Stored for your plan’s retention, 7 days to 30 days, with signed download links that last up to an hour.
When a job ends

A webhook URL per job or endpoints on your account, signed in the Standard Webhooks format and retried for about a day.
Streaming formats, live, DRM

Files in, files out. Adaptive streaming (HLS) and a player Soon
AI assistants (MCP)

An MCP server that checks, runs and waits for jobs with your API key.
Company

BEO TECHNOLOGY sp. z o.o., Poland, in the European Union.
Zencoder

Before the first job

An API key from the account, sent in the Zencoder-Api-Key header.
How a job is described

A JSON job: one input and up to 20 outputs with encoding settings.
Where outputs go

Uploaded to your S3, Google Cloud Storage, Azure, FTP or SFTP; without a destination, kept for 24 hours.
When a job ends

Notifications to a URL you set on the job or an output.
Streaming formats, live, DRM

HLS and DASH outputs, with DRM options.
AI assistants (MCP)

None in the Zencoder docs. Brightcove’s MCP server covers Video Cloud accounts, not Zencoder jobs.
Company

Brightcove; Zencoder is a Brightcove product.

Zencoder, as its own pages said on Nov 5, 2026: Zencoder product page Quick start Test jobs and integration mode Output settings File transfers DRM settings Brightcove MCP server HLS streaming DASH streaming

Moving over

What each part is called here. One request per job.

Every job returns the ffmpeg command it ran, so you can compare the output with what you have today, one job at a time.

Every output type and option

Zencoder concepts and what they are in Videxo
Zencoder	Videxo
Job (input and outputs)	Job: `inputs` and a list of `outputs` on POST /v1/jobs
Output settings (video_codec, width, quality)	Output options (`video.codec`, `resize`, `video.crf`) or a preset
Output url (your bucket)	A stored output with a signed download_url; copy it to your bucket
Thumbnails on an output	An `image` output with `times`, or POST /v1/thumbnails
notifications	`webhook_url`, signed in the Standard Webhooks format
Job progress	GET /v1/jobs/{id}: `state` and `progress`
Integration mode	POST /v1/jobs/compile: the ffmpeg command a job would run, without creating it

Honestly

When Zencoder fits better. Pick it then.

You need HLS or DASH packaging or DRM today.
Outputs must land directly in your S3, Google Cloud Storage, Azure, FTP or SFTP.
You already buy other Brightcove products and want one vendor.

Questions, answered.

What are the limits?

On Pay as you go a job runs up to 10 min of ffmpeg with inputs up to 1 GB; on Scale up to 60 min with inputs up to 10 GB. Uploads from apps and browsers go up to 100 MB.

Which ffmpeg and which codecs?

ffmpeg 6.1.1, with H.264, H.265, VP8, VP9 and AV1 video, and AAC, MP3, Opus, FLAC and WAV audio, among others. The command rules list every option, filter and format a command can use.

Can I send my own ffmpeg command?

Yes. POST /v1/jobs takes input URLs, output names and an ffmpeg command that names files by alias. It is checked before the job exists; a refused command answers with a code for each problem and costs nothing.

How long are the files kept?

Outputs stay for your plan’s retention. Each download link is signed and lasts up to one hour; read the job again for a fresh one, or delete the files sooner with DELETE /v1/jobs/{id}/files.

How do I know a webhook came from you?

Each delivery is signed with your account’s secret in the Standard Webhooks format. Verify it with the standardwebhooks library or a few lines of code; the docs show both.

Who runs Videxo?

BEO TECHNOLOGY sp. z o.o., a limited company in Poland, in the European Union. Write to hello@videxo.io.

Run your first job. Free, no card.

Get an API key Read the quickstart