The best FFmpeg APIs in 2026, compared
Eight ways to run FFmpeg-style video jobs without your own servers. They differ most in what they bill, whether you can send your own FFmpeg command, and whether an AI agent can run jobs. Yes, Xora is one of them; we say where the others are the better choice.
| API | Billing | Entry paid plan | Free plan | Your own FFmpeg command | MCP that runs jobs |
|---|---|---|---|---|---|
| Xora | Machine time + output size (credits) | $15 / mo, 400 credits | 25 credits / mo, no card | Yes, args array, plus recipes | Yes |
| Rendi | Processed GB (input + output) | $25 / mo, 250 GB | 50 GB / mo, card required | Yes, command string | No (docs search) |
| FFmpeg Micro | Input duration (1 token per 10 s) | Pro: $49.99 / mo, 7,000 tokens | 200 tokens at sign-up, no card | Options, no -filter_complex | Yes |
| ffmpeg-api.com | GB-seconds (size × time) | $11 / mo, 500 GB-seconds | Yes, limits not published | Options and a filter_complex string | Yes |
| FFmpegAPI.net | API calls | Premium: 100 calls / mo | A few calls / mo, no card | No, fixed endpoints | Yes |
| Transloadit | GB (input + output) | Lite: $29 / mo, 15 GB | 5 GB / mo, outputs watermarked or trimmed | ffmpeg parameter object | Yes |
| Shotstack | Rendered minutes | $10 for 50 minutes (pay as you go) | 10 credits for 30 days | No, JSON timeline | Yes |
| AWS MediaConvert | Output minutes × multipliers | Pay per use | No free tier listed | No, job settings JSON | No |
Facts from each vendor’s own pricing and docs pages: Rendi checked on 13 October 2026, FFmpeg Micro and ffmpeg-api.com on 9 October 2026, the others on 30 October 2026. Prices change; check the vendor’s page before you decide.
Pick by the shape of your jobs
The meter matters more than the headline price. The same job can be cheap on one and expensive on another.
Large files, light work
Thumbnails, probes, trims and audio from big uploads. Size-based meters (Rendi, Transloadit) and duration-based meters (FFmpeg Micro) charge for the whole file. Xora bills the machine time, and reads only the byte ranges it needs when the storage supports it.
Small files, heavy work
Long filter graphs or slow encodes on short clips. A size-based meter such as Rendi can cost less here, because processing time does not change the bill.
Template video editing
Text, images and clips on a timeline, rendered from JSON. Shotstack is built for this and has templates and an editor.
Broadcast transcoding on AWS
ABR packaging, HDR and Dolby, at volume, inside your AWS account. AWS MediaConvert fits teams that already run on AWS.
The APIs, one by one
Xora
Runs any FFmpeg args array, including -filter_complex and several inputs, plus recipes for common jobs and a probe mode. Bills one credit per minute of machine time plus credits per GB of output; failed, rejected and cancelled jobs cost nothing. Webhooks, an MCP server that runs jobs, and outputs in your own Cloudflare R2 bucket on paid plans. Input limits from 250 MB (Free) to 6 GB (Scale). See pricing.
Rendi
Runs FFmpeg command strings with {{in_1}} placeholders, with webhooks and stored outputs. Bills processed GB, so heavy work on small files is cheap. The free plan needs a card and has a 1-minute limit per command. Xora vs. Rendi.
FFmpeg Micro
Runs FFmpeg options without -filter_complex, outputs MP4 and WebM, and has an MCP server that runs jobs. Bills by the duration of the input video. Xora vs. FFmpeg Micro.
ffmpeg-api.com
Takes input options, output options, maps and a filter_complex string, with async jobs and an MCP server. Bills GB-seconds: file size times processing time. Xora vs. ffmpeg-api.com.
FFmpegAPI.net
Ready-made endpoints such as compress, trim, merge, captions and YouTube download, billed per API call, with an MCP server. Simple when your task is on the list; there is no way to send your own command. Xora vs. FFmpegAPI.net.
Transloadit
A file-processing platform with many “robots”, including video encoding with an ffmpeg parameter object, and an MCP server. Bills GB of input plus output. Strong when you also need uploads, image processing and storage integrations in one service.
Shotstack
A video editing API: describe clips, text and audio on a timeline in JSON, and it renders the video, with webhooks and an MCP server. Bills rendered minutes. Strong for templated marketing and social video; not built for running FFmpeg commands.
AWS MediaConvert
A broadcast-grade transcoder inside AWS, configured with job settings JSON, with S3 outputs and EventBridge events. Bills output minutes with multipliers. Strong for streaming formats at volume. Xora vs. AWS MediaConvert.
Frequently asked questions
What is the best FFmpeg API?
It depends on the job. For your own FFmpeg commands with credits for machine time, Xora. For small files with heavy processing, a per-GB service such as Rendi. For template-based video editing, Shotstack. For broadcast transcoding inside AWS, MediaConvert. For a few ready-made endpoints, FFmpegAPI.net.
Which FFmpeg APIs let me send raw FFmpeg commands?
Xora and Rendi take a full FFmpeg command (Xora as an args array, Rendi as a command string). ffmpeg-api.com takes input options, output options and a filter_complex string. Transloadit takes an ffmpeg parameter object on its video encode robot. FFmpeg Micro takes FFmpeg options but not -filter_complex. FFmpegAPI.net and Shotstack use their own endpoints or JSON formats.
Which FFmpeg APIs have an MCP server that runs jobs?
Xora, FFmpeg Micro, ffmpeg-api.com, FFmpegAPI.net, Transloadit and Shotstack list MCP servers that run jobs or renders. Rendi's MCP server searches its documentation. AWS MediaConvert has no MCP server of its own; agents use the AWS APIs.
How do FFmpeg APIs bill?
Six different ways: by file size (Rendi, Transloadit), by file size times processing time (ffmpeg-api.com), by input duration (FFmpeg Micro), by API call (FFmpegAPI.net), by output minutes (Shotstack, MediaConvert), or by machine time plus output size (Xora). The cheapest one depends on the shape of your jobs.
Try Xora with your own command
Bring the FFmpeg command you already have, run it with one POST, and pay only for the credits your jobs use.