AWS MediaConvert Alternative for Developers Who Want Raw FFmpeg

Feature	AWS Elemental MediaConvert	Xora (xora.sh)
Job format	Job settings JSON, presets, job templates	FFmpeg args array, or 9 recipes
Billing model	Per output minute × multipliers (tier, resolution, fps, codec)	Credits: machine time + output size
Example rate	Basic tier: $0.0075 per normalized minute (first 100,000, AWS’s US East (Ohio) example)	$15 / mo for 400 credits on Build
Setup	AWS account, IAM role, S3 buckets, queues	An API key
Inputs	Amazon S3 or HTTP(S) URLs	HTTPS or S3 URLs, or a direct upload
Outputs	Your Amazon S3 bucket	Signed URLs, or your own Cloudflare R2 bucket (paid plans)
Job done	EventBridge events (COMPLETE has the output locations)	Webhook on every terminal state, or polling
Broadcast features	ABR packaging (HLS, DASH), Dolby, HDR10+, Dolby Vision, many codecs	Whatever FFmpeg does with the arguments you send
AI agents	AWS SDKs and APIs	Remote MCP server that runs jobs

MediaConvert facts from aws.amazon.com and docs.aws.amazon.com, checked on 30 October 2026. AWS shows rates by Region and volume tier; check the pricing page for your Region.

What you pay for

MediaConvert bills per minute of output. The rate changes with the tier, resolution, frame rate and codec, and outputs shorter than 10 seconds are billed as 10 seconds. S3 storage and data transfer are billed on their own, and so is a Lambda function or another service that you add to EventBridge to tell your app that a job is done.

Xora bills credits for machine time and output size. The webhook and the signed output URL are part of the job. A thumbnail from a 2 GB video uses about 0.1 credits, because only the part of the file around that frame is read. Failed, rejected and cancelled jobs cost nothing.

The best test is your own jobs: run a few on the Free plan (25 credits, no card), and compare the credits with the MediaConvert pricing page for your Region.

Where the difference is not price

Many video jobs are not transcodes: a thumbnail from a 2 GB upload, a probe to check a file, a GIF preview, the audio track for transcription, a trim, a watermark from a filter graph. With MediaConvert, each of these needs its own job settings, or it is not what MediaConvert is built for. With Xora, each one is one FFmpeg command or a recipe.

There is also the setup. A MediaConvert job needs an IAM role with access to your S3 buckets, input and output buckets, and an EventBridge rule to learn that the job is done. A Xora job needs an API key and a URL.

A job in each

MediaConvert describes the output in its own settings model: output groups, outputs, codec settings and a destination in S3. Xora takes the FFmpeg arguments:

{
  "mode": "ffmpeg",
  "input_files": { "in_1": "https://example.com/master.mov" },
  "output_files": { "out_1": "master_720p.mp4" },
  "ffmpeg": {
    "args": [
      "-i", "{{in_1}}",
      "-vf", "scale=-2:720",
      "-c:v", "libx264", "-crf", "23", "-preset", "medium",
      "-c:a", "aac", "-b:a", "128k",
      "-movflags", "+faststart",
      "{{out_1}}"
    ]
  },
  "webhookUrl": "https://your-app.com/webhooks/xora"
}

Where MediaConvert is strong

Volume tiers for teams that transcode many hours of video each month.
Broadcast and streaming features: ABR packaging for HLS and DASH, Dolby audio, HDR10+ and Dolby Vision, and many professional codecs.
Inside AWS: IAM, S3, EventBridge and CloudWatch work together, and your media does not leave your AWS account.

Choose Xora when you want to run FFmpeg commands as written, when many of your jobs are not plain transcodes, when an AI agent sends the jobs, or when you do not want to set up AWS resources for video. See all options in the best FFmpeg APIs compared, and Xora’s pricing.

Frequently asked questions

Can AWS MediaConvert run FFmpeg commands?

No. MediaConvert jobs are defined with its own job settings in JSON, presets and job templates, through the console, the API, the SDKs or the AWS CLI. To run an FFmpeg command as written, use an FFmpeg API such as Xora or run FFmpeg on your own compute.

How is AWS MediaConvert priced?

Per minute of output, with multipliers for tier, resolution, frame rate, codec and features. In AWS's own US East (Ohio) example, the Basic tier is $0.0075 per normalized minute for the first 100,000, and an HD output at up to 30 fps counts as 2 normalized minutes per minute. Outputs shorter than 10 seconds are billed as 10 seconds. S3 storage and transfer are billed separately.

Which costs less, MediaConvert or Xora?

It depends on the jobs. MediaConvert bills per output minute, and S3 storage, transfer and the services you add for notifications are billed separately. Xora bills credits for machine time and output size, so short jobs such as thumbnails and probes use a small part of a credit, and failed jobs cost nothing. Run a few of your real jobs on the Xora Free plan and compare them with the MediaConvert pricing page for your Region.

How do I know when a MediaConvert job is done?

MediaConvert sends job events to Amazon EventBridge, and the COMPLETE event includes the output locations. You add an EventBridge rule that calls a Lambda function or another target. On Xora, you pass webhookUrl on the job, or poll GET /v1/jobs/{id}.

Xora vs. AWS MediaConvert