AWS Elemental MediaConvert, compared. Jobs, setup and the move.

MediaConvert is built for teams that live in AWS. Videxo is one HTTP API with an API key: no S3 bucket, IAM role or EventBridge rule to set up before the first job.

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 AWS Elemental MediaConvert. Checked on Nov 5, 2026.

Videxo and AWS Elemental MediaConvert, as their own pages describe them on Nov 5, 2026
Topic	Videxo	AWS Elemental MediaConvert
Before the first job	An API key as a Bearer token. No bucket, role or queue to create.	An IAM service role that gives MediaConvert access to your input files and output locations in S3.
How a job is described	JSON operations, or the ffmpeg command you already run, checked before the job is created.	A job with inputs and output groups, often from a job template and output presets, sent to a queue.
Where outputs go	Stored for your plan’s retention, 7 days to 30 days, with signed download links that last up to an hour.	Written to your S3 bucket.
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.	Job events to Amazon EventBridge, routed from there to SNS, Lambda or other targets.
Streaming formats, live, DRM	Files in, files out. Adaptive streaming (HLS) and a player Soon	HLS, DASH, CMAF and more, with DRM on the Professional tier.
AI assistants (MCP)	An MCP server that checks, runs and waits for jobs with your API key.	No MediaConvert server; AWS’s general MCP server runs AWS CLI commands, MediaConvert’s among them, with your AWS credentials.
Company	BEO TECHNOLOGY sp. z o.o., Poland, in the European Union.	Amazon Web Services, in the AWS Region you choose.

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.
AWS Elemental MediaConvert

Before the first job

An IAM service role that gives MediaConvert access to your input files and output locations in S3.
How a job is described

A job with inputs and output groups, often from a job template and output presets, sent to a queue.
Where outputs go

Written to your S3 bucket.
When a job ends

Job events to Amazon EventBridge, routed from there to SNS, Lambda or other targets.
Streaming formats, live, DRM

HLS, DASH, CMAF and more, with DRM on the Professional tier.
AI assistants (MCP)

No MediaConvert server; AWS’s general MCP server runs AWS CLI commands, MediaConvert’s among them, with your AWS credentials.
Company

Amazon Web Services, in the AWS Region you choose.

AWS Elemental MediaConvert, as its own pages said on Nov 5, 2026: MediaConvert pricing IAM permissions What is MediaConvert EventBridge events AWS API MCP server Supported output formats

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

AWS Elemental MediaConvert concepts and what they are in Videxo
AWS Elemental MediaConvert	Videxo
Job	Job: POST /v1/jobs, or a per-operation endpoint such as POST /v1/transcode
Job template	The JSON body kept in your code
Output preset	A preset (GET /v1/presets), its options overridden per output
Output group and outputs	The `outputs` list, each with a `type` and options
Queue	None to manage: jobs run as your plan’s concurrency allows
S3 input and destination	An https input URL or a one-time upload; outputs with signed download links
EventBridge and SNS	`webhook_url` or your account’s webhook endpoint, signed
IAM role and credentials	One API key as a Bearer token

Honestly

When AWS Elemental MediaConvert fits better. Pick it then.

Your media already sits in S3 and your stack already runs on AWS.
You need broadcast inputs and outputs, HLS, DASH or CMAF packaging, or DRM.

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