Hosted FFmpeg REST API: 2026 Pricing and Comparison Guide

A developer in 2026 searching for "hosted FFmpeg REST API video transcoding API 2026 pricing docs" wants one thing: send a video and an FFmpeg command to a URL, get the output back, and know exactly what it costs. The market has exploded to nine competing providers across six different pricing models, and the differences between them matter more than the headline rates.

_Gyan, an FFmpeg expert and r/ffmpeg moderator, describes the core audience for these services as "corporate/enterprise who don't want to maintain staff and metal for codec breakages." The category exists because running FFmpeg at production scale is genuinely hard. You need GPU provisioning, queue management, retry logic, and constant FFmpeg maintenance.

Very Good FFmpeg was designed to fix what existing options get wrong. Instead of wrapping FFmpeg in proprietary abstractions and opaque pricing, it gives you raw command control and per-GB billing. No multipliers, no minimums, no surprise bills. The straightforwardness of running FFmpeg locally, but hosted, scaled, and billed fairly.

Key takeaways: what should you know before choosing a hosted FFmpeg REST API?

The 2026 hosted FFmpeg market has nine providers and six different pricing models. Most share one common pain point: opaque pricing that makes forecasting difficult. Here is the landscape at a glance.

Very Good FFmpeg is the only option that combines raw FFmpeg command passthrough with per-GB billing and zero multipliers. Rendi and FetchMedia also support raw FFmpeg but lack GPU acceleration or have other tradeoffs covered below.

What is a hosted FFmpeg REST API for video transcoding?

A hosted FFmpeg REST API lets you send video files and FFmpeg commands to a cloud endpoint instead of running FFmpeg on your own servers. You provide an input URL, the FFmpeg flags you want, and the API returns the output. No server provisioning, no queue management, no FFmpeg build maintenance.

The old approach required installing FFmpeg on a server, downloading video files, running CLI commands, managing parallel jobs, and storing results yourself. A hosted API replaces all of that with a single HTTP request.

Not all video APIs qualify as hosted FFmpeg. Mux, api.video, Bitmovin, AWS MediaConvert, Cloudinary, and Encoding.com all wrap FFmpeg in proprietary presets and templates. You get abstractions, not flags. One developer on Reddit described testing Streamrun and finding that its "API doesn't expose enough destination control" -- a common complaint across platforms that hide FFmpeg behind higher-level interfaces.

The services that let you send exact FFmpeg commands are Very Good FFmpeg, Rendi (raw FFmpeg passthrough), and FetchMedia (any FFmpeg command on autoscaled workers). If you need raw control over codec flags, filter graphs, and complex filterchains, these are the options that deliver it.

How much do hosted FFmpeg REST APIs cost in 2026?

Nine providers use six different pricing models. The headline rates rarely reflect what you actually pay because most apply resolution multipliers, codec multipliers, or other hidden fees.

Here is a detailed pricing comparison across every major provider.

Mux pricing

Mux charges for delivery minutes and storage, not compute. Input is free. Storage costs $0.0024 per minute. Delivery costs $0.0008 per minute watched, with 100,000 free minutes per month. Resolution multipliers: 720p is 1x, 1080p is 1.25x, 4K is 4x. Launch plan: $20/mo for $100 credit. Scale plan: $500/mo for $1,000 credit.

api.video pricing

api.video charges zero for encoding. Hosting is $0.00285 per minute stored. Delivery is $0.0017 per minute delivered. Three team members included. Enterprise adds SAML SSO, audit logs, and isolated storage. Custom domains: 60 EUR/mo.

Bitmovin pricing

Bitmovin charges $0.02 per minute for VOD encoding with 2,000 free minutes per month. Live encoding: $3/hr with 6 free hours. Player: $1.50 per 1,000 impressions. Resolution multipliers: SD 1x, HD 2x, 4K 4x, 8K 120x. Codec multipliers: HEVC 2x. Available on AWS, Azure, and GCP marketplaces.

AWS MediaConvert pricing

AWS MediaConvert uses normalized minute pricing with tiered discounts. Basic tier (AVC only): $0.0075/min for first 100K, down to $0.0038/min above 1M. Professional tier (HEVC, AV1, Dolby): $0.012/min for first 50K, down to $0.0036 above 10M. Resolution, framerate, and codec multipliers compound, making effective rates hard to predict.

Cloudinary pricing

Cloudinary uses monthly credits. Free: 25 credits. Plus: $99/mo for 225 credits. Advanced: $249/mo for 600 credits. Credits cover uploads, transformations, transcoding, and delivery. Credits expire monthly with no rollover.

Encoding.com pricing

Encoding.com uses a subscription model. Free: 1 GB. Pro: $199/mo for 100 GB. Studio: $399 to $1,599/mo for 220 GB to 1.56 TB. Overage: $2/GB (Pro) to $1.60/GB (Studio). Features include API access, watch folders, Aspera high-speed transfer, and broadcast support.

Coconut pricing

Coconut charges per output minute with no resolution or codec multipliers. Audio $0.00325/min, SD $0.0075/min, HD $0.015/min, UHD $0.03/min. Output minutes equal video length times number of output formats. No minimum, no charge for failed jobs, free test plan with no credit card. Operates since 2006. Serves Triller, Sport1, and Sked Social.

Rendi pricing

Rendi charges by total data processed (input plus output size). Free: 50 GB processing, 1-min runtime, 5 GB storage. Pro: $25/mo for 100 GB, 10-min runtime, 50 GB storage. No resolution or codec multipliers. No egress fees. Raw FFmpeg passthrough. Caveats: AMD only, no GPU, no streaming protocol support.

FetchMedia pricing

FetchMedia is a managed FFmpeg infrastructure API launched in 2026. Send input URLs with a full FFmpeg command, and the platform runs on autoscaled Hetzner workers with logging, retries, and webhooks. Optimized for high-volume batch processing. Usage-based pricing with a free tier.

Very Good FFmpeg pricing

Very Good FFmpeg charges per GB processed with no monthly minimum. First 2 GB free. 0-10 GB: $0.50/GB. 10-100 GB: $0.10/GB. 100 GB+: $0.08/GB. No resolution or codec multipliers. No storage or delivery fees. No credit expiry. You pay for the compute your FFmpeg commands actually use.

How to calculate your real transcoding cost

Follow these steps to compare prices across providers accurately.

1. Find your average input file size in GB and video length in minutes.
2. Choose your output codec (H.264, HEVC, AV1) and resolution.
3. Estimate the output file size based on the codec and resolution ratio.
4. For Very Good FFmpeg and Rendi: add input size to output size, then multiply by the tier rate. That is your total cost.
5. For Mux, Bitmovin, and AWS MediaConvert: multiply the base rate by the resolution multiplier, then by the codec multiplier, then add storage and delivery fees.
6. For Coconut: multiply video length by the number of output formats. Apply the per-minute rate for each quality tier.
7. Compare the effective per-job cost across providers. The cheapest base rate almost never wins after multipliers and hidden fees.

What hidden costs should you watch for in video transcoding APIs?

Hidden costs in video transcoding APIs often outweigh the base rate. Understanding them before choosing a platform prevents surprises on the first big bill.

Resolution multipliers

Resolution multipliers are the most common hidden cost. On Mux, a 4K transcode costs 4x the base rate. On Bitmovin, 4K is 4x and 8K is a staggering 120x. On AWS MediaConvert, resolution is one of several compounding multipliers. Very Good FFmpeg, Coconut, and Rendi do not use resolution multipliers. A 4K job costs the same per-GB or per-tier rate as an SD job.

Codec multipliers

Codec multipliers add cost for using modern codecs. Bitmovin charges 2x for HEVC. AWS MediaConvert applies 2x to 4x multipliers for HEVC depending on the profile. AV1 can be even higher. Very Good FFmpeg, Coconut, and Rendi do not charge extra for any codec. H.264, H.265, VP9, and AV1 all bill at the same rate.

Storage and delivery fees

Mux charges ongoing storage per minute of content. api.video charges storage per minute and delivery per minute. These costs grow with your library size and viewership, not just your processing volume. One Reddit user shared that their team spends "a few hundred/month on Coconut," highlighting the real monthly burn for production transcoding. Very Good FFmpeg does not charge storage or delivery fees. Output URLs and webhook delivery are included in the processing price.

Minimum commitments and credit expiry

Encoding.com requires a $199 per month minimum even if you process less than 100 GB. Cloudinary credits expire monthly and do not roll over. Very Good FFmpeg has no monthly minimum and no credit system. You pay only for what you process each month.

How do resolution and codec multipliers compound your bill?

Multipliers stack. A single 4K HEVC job on Bitmovin can cost 8x the base rate: 4x for resolution and 2x for the codec. On AWS MediaConvert, the same job can cost 8x to 16x depending on the HEVC profile and framerate.

Here is how effective multipliers compare across providers for common scenarios.

Coconut uses one price per quality tier (SD, HD, UHD) with no codec add-ons. Rendi and Very Good FFmpeg use zero multipliers. Only the total bytes processed or output minutes matter.

Hosted FFmpeg API vs self-hosted: which is cheaper in 2026?

The answer depends on your monthly volume and whether you count operational time as a cost.

How to decide

1. Calculate your monthly GB processed.
2. Compare the hosted cost (VGF: $0.50 to $0.08/GB) against a GPU cloud instance ($200 to $800 per month).
3. Factor in operational time: FFmpeg builds, GPU driver updates, queue management, and failed job retries.
4. Factor in utilization: an idle GPU instance burns money. Hosted APIs charge only for what you use.
5. Factor in hidden self-hosted costs: storage, bandwidth, monitoring, and backup infrastructure.

Break-even points

At volumes under 100 GB per month, a hosted API is always cheaper. Self-hosting a GPU instance that runs 10 hours per week still costs the full instance price.

At 100 GB to 1 TB per month, Very Good FFmpeg costs $30 to $100 per month. A self-hosted GPU instance starts at $200 per month before storage and bandwidth.

Above 1 TB per month, Very Good FFmpeg volume discounts apply. Self-hosting wins on raw compute cost only if your GPU utilization stays above 60 percent. Below that, you pay for idle capacity.

One Reddit user in the self-host camp argued you can "get cheap server from lowendtalk, install FFmpeg, setup webgui with Claude AI. Simple as that." The Rendi creator responded: "becomes harder at large scale -- auto scaling, instant availability, maintenance." This captures the core tension. Hosted wins for most teams unless you have a dedicated infrastructure team and near-full GPU utilization.

What sets Very Good FFmpeg apart? The design philosophy behind the API

Very Good FFmpeg is not just another hosted FFmpeg API. It was built to supercede every competitor in both specification and price.

The design philosophy is straightforward. Very Good FFmpeg was designed to provide the straightforwardness and simplicity of "just use FFmpeg" type approaches to video processing, while satisfying the same root requirement that drives teams to hosted solutions in the first place: video processing is compute intensive and requires infrastructure that most teams do not want to maintain.

Every other platform forces you into an abstraction layer. Mux has playback IDs and encoding presets. Bitmovin has encoding profiles and templates. AWS MediaConvert has job templates and normalized minute calculations. Very Good FFmpeg says the FFmpeg command IS the API. If it works in your terminal, it works through the API.

The billing reflects the same philosophy. Per-GB pricing means you pay for the actual compute work, not for arbitrary resolution tiers or codec classifications. A 4K HEVC transcode costs the same per GB as an SD H.264 transcode. No resolution multipliers. No codec multipliers. No storage fees. No delivery fees. No monthly minimum. No credit expiry.

On the hardware side, CPU jobs run on dedicated 16 vCPU, 32 GB DDR5, NVMe instances with 5+ GHz cores. GPU jobs run on Nvidia RTX 4090, RTX 5090, A4000, A5000, RTX 4000, and RTX 2000 hardware. You select the GPU per job. Jobs support up to 6 hours of runtime, 100 requests per second with a $10 pre-paid balance, and unlimited concurrent jobs.

As _Gyan noted, the challenge with raw FFmpeg is that the CLI is "messy FFmpeg flags." Very Good FFmpeg gives you both: a clean REST API with full flag passthrough for when you need exact control.

What matters beyond price for a hosted FFmpeg REST API?

Price is one factor, but raw FFmpeg support, job timeouts, hardware, rate limits, and developer experience matter just as much.

Raw FFmpeg support

This is the biggest differentiator. Mux, api.video, Bitmovin, AWS MediaConvert, Cloudinary, and Encoding.com do not support raw FFmpeg commands. You work within their presets, templates, or transformation syntax.

Very Good FFmpeg, Rendi, and FetchMedia let you send exact FFmpeg command strings. Same flags, same filter graphs, same complex filterchains. If your command works in FFmpeg on the terminal, it works through the API.

Job runtime limits

AWS Lambda supports a maximum of 15 minutes per invocation. Cloud Run supports up to 60 minutes. Very Good FFmpeg supports jobs up to 6 hours, which covers feature-length films and large batch processing without chunking. Rendi's free tier limits runtime to 1 minute; Pro extends to 10 minutes.

Hardware and GPU support

Very Good FFmpeg offers on-demand Nvidia RTX 4090, RTX 5090, A4000, A5000, RTX 4000, and RTX 2000 GPUs selected per job. Bitmovin supports GPU acceleration for select codecs. Rendi uses AMD processors with no GPU option. Mux, api.video, Cloudinary, and Coconut do not offer selectable GPU instances for raw FFmpeg workloads.

Rate limits and concurrency

Very Good FFmpeg supports 100 requests per second after a $10 pre-paid balance with no limit on concurrent jobs. AWS MediaConvert supports high throughput but requires careful queue management. Most other providers have account-level rate limits that cap throughput.

Developer tooling

Very Good FFmpeg offers official TypeScript and Python SDKs, an MCP server, and a Make.com integration. Jobs stream FFmpeg stderr in real time through the dashboard. Auto-diagnosis analyzes failed FFmpeg output and tells you what went wrong. Command chaining lets you run multiple FFmpeg commands in a single request.

Auth and teams

Very Good FFmpeg supports teams with role-based access control. Create teams, invite members, and assign permissions from the dashboard. Most video APIs offer single-user API keys only.

Which hosted video transcoding API is right for you in 2026?

The right choice depends on your use case. The table below maps common scenarios to the best fit.

New 2026 entrants worth watching: Coconut for predictable per-output pricing, Rendi for simple processing-based billing, and FetchMedia for full command passthrough at scale.

Verdict

The 2026 hosted video API market offers more options than ever, but most still use opaque pricing. Mux uses per-minute delivery with resolution multipliers. Bitmovin uses per-minute encoding with codec multipliers. AWS MediaConvert uses normalized minutes with compounding multipliers. Cloudinary uses credits that expire. Encoding.com requires subscription commitments.

New entrants show the market trending toward simpler models. Coconut offers per-output-minute pricing with no multipliers. Rendi charges per GB with raw command passthrough. FetchMedia provides managed FFmpeg infrastructure at scale.

Very Good FFmpeg is the only option combining everything: raw FFmpeg control, per-GB billing with zero multipliers, no minimum, no storage or delivery fees, and on-demand GPU. Built to be the uncomplicated alternative. Straightforward like running FFmpeg locally, but hosted, scaled, and billed fairly.

Start with Very Good FFmpeg for raw FFmpeg workloads. Use Mux or api.video for video hosting with a built-in player. Use Coconut for predictable per-output pricing. Use Rendi for simple processing without GPU needs. Use Bitmovin or AWS MediaConvert for enterprise broadcast features.

FAQ

What is a hosted FFmpeg REST API?

A hosted FFmpeg REST API is a web service that accepts video files and FFmpeg commands over HTTP, processes them on cloud infrastructure, and returns the output. It removes the need to manage servers or install FFmpeg yourself.

How does Coconut pricing compare to Very Good FFmpeg?

Coconut charges per output minute with tiered rates for audio, SD, HD, and UHD. Very Good FFmpeg charges per GB with no resolution tiers. Coconut has no multipliers but cost scales with output formats. Very Good FFmpeg cost scales with file size. For short videos with many output formats, Coconut may be cheaper. For long videos or complex processing, Very Good FFmpeg often wins.

What is Rendi and how does its pricing work?

Rendi charges by total data processed (input plus output size). No multipliers, no egress fees, raw FFmpeg passthrough. Free tier includes 50 GB of processing.

Does FetchMedia support raw FFmpeg commands?

Yes. FetchMedia accepts any FFmpeg command on autoscaled Hetzner workers. Optimized for high-volume batch processing. Launched in 2026.

How do resolution multipliers affect cost across providers?

Resolution multipliers multiply the base price by a factor based on output resolution. 4K on Mux costs 4x. 8K on Bitmovin costs 120x. Very Good FFmpeg, Coconut, and Rendi do not use resolution multipliers.

What hidden costs do video transcoding APIs have?

Resolution multipliers, codec multipliers, storage fees, delivery fees, minimum commitments, and credit expiry. These can multiply effective rates by 4x to 120x.

Which hosted FFmpeg APIs support GPU acceleration?

Very Good FFmpeg supports on-demand Nvidia RTX and A-series GPUs selected per job. Bitmovin supports GPU for select codecs. Rendi uses AMD with no GPU.

Does Very Good FFmpeg have a free tier?

Yes. First 2 GB free with no credit card required.

Hosted API vs self-hosted FFmpeg: which is better for my volume?

Under 100 GB/mo, hosted is always cheaper. From 100 GB to 1 TB, VGF costs $30 to $100/mo versus $200+ for a GPU instance. Above 1 TB, self-hosting wins only if GPU utilization stays above 60 percent.

What is the cheapest hosted FFmpeg API in 2026?

Very Good FFmpeg is cheapest for most workloads. Per-GB billing with no multipliers. Starts at $0.50/GB with 2 GB free. Drops to $0.08/GB at volume.

Does Mux support raw FFmpeg commands?

No. Mux uses its own API objects with encoding presets. You cannot pass custom FFmpeg flags.

Can I use Very Good FFmpeg for 4K HEVC transcoding?

Yes. Same per-GB rate as any other resolution and codec. No multipliers apply.

How do I calculate my real transcoding cost per job?

Add input size to estimated output size, multiply by per-GB tier rate. For providers with multipliers, multiply base rate by resolution and codec multipliers, then add storage and delivery fees.

Is Rendi better than Very Good FFmpeg?

Rendi is cheaper at low volumes (free 50 GB) and supports raw FFmpeg. But Rendi has AMD only, no GPU, no streaming support, and 10-minute runtime limit. VGF offers GPU on demand, 6-hour runtime, and 100 req/s concurrency.

What new hosted FFmpeg APIs launched or gained traction in 2026?

Coconut (newly relevant for transparent per-output pricing), Rendi (launched 2025, gained traction 2026), and FetchMedia (launched 2026). All signal market shift toward simpler pricing.

References

1. Mux pricing: https://www.mux.com/pricing
2. Mux Video API: https://www.mux.com/video-api
3. api.video pricing: https://api.video/pricing
4. Bitmovin pricing: https://bitmovin.com/pricing
5. AWS MediaConvert pricing: https://aws.amazon.com/mediaconvert/pricing
6. Cloudinary pricing: https://cloudinary.com/pricing
7. Encoding.com pricing: https://www.encoding.com/pricing
8. Coconut pricing: https://coconut.co/pricing
9. Rendi pricing: https://rendi.dev/pricing
10. FetchMedia: https://fetchmedia.io
11. Reddit: Dev builds cloud SaaS around FFmpeg: https://old.reddit.com/r/ffmpeg/comments/1n4ggf5/
12. Reddit: Roast my FFmpeg API SaaS (Rendi): https://old.reddit.com/r/ffmpeg/comments/1n6guet/
13. Reddit: Self-hosted video platform debate: https://old.reddit.com/r/ffmpeg/comments/1n7eune/
14. Reddit: Looking for headless streaming API: https://old.reddit.com/r/ffmpeg/comments/1rr8um0/
15. Reddit: r/ffmpeg app/service sticky: https://old.reddit.com/r/ffmpeg/comments/1tjk08g/
16. Very Good FFmpeg landing: https://verygoodffmpeg.com
17. Very Good FFmpeg docs: https://verygoodffmpeg.com/docs