Video Transcoding Pricing Compared: AWS, Mux, Coconut, Google, Bitmovin, and Transcodely
An honest comparison of video encoding costs across AWS MediaConvert, Mux, Coconut, Bitmovin, Google Cloud, and Transcodely — with real numbers.
Video transcoding pricing should be simple: you put video in, you get encoded video out, and you pay a predictable amount per minute. In reality, most providers bury the true cost behind multiplier tables, tiered pricing, bundled services, and “contact sales” gates.
This article compares the actual cost of encoding video across six providers: AWS MediaConvert, Mux, Coconut, Google Cloud Transcoder, Bitmovin, and Transcodely. All pricing data is from publicly available rate cards as of March 2026. Where providers do not publish exact rates, we note the estimates and their sources.
Last updated: March 2026. Pricing changes. If you are reading this months after publication, verify current rates on each provider’s website.
Why pricing transparency matters
Before diving into the numbers, it is worth understanding why transcoding pricing is so often confusing.
Video encoding has many variables: codec, resolution, frame rate, HDR, number of outputs, quality settings. Some providers price per minute of input, others per minute of output. Some charge per “normalized minute” (a synthetic unit that adjusts for complexity). Some bundle encoding with delivery and storage, making it impossible to isolate the transcoding cost.
AWS MediaConvert is the most extreme example. Its pricing page lists a base rate per minute, then applies multipliers for codec tier (Basic vs. Professional), codec type, resolution, frame rate, HDR, and output format. The result is over 50 possible multiplier combinations, and calculating the cost of a specific job requires a spreadsheet.
This opacity is not an accident. Complex pricing makes comparison shopping difficult and creates lock-in through confusion. If you cannot easily calculate your bill, you cannot easily compare alternatives.
Provider-by-provider breakdown
AWS MediaConvert
Pricing model: Per minute of output, multiplied by codec tier, resolution, frame rate, and features.
AWS MediaConvert offers two tiers: Basic (limited features, lower cost) and Professional (full feature set). Most production workloads require Professional tier for features like HEVC, HDR, or advanced audio.
Base rates (Professional tier, US East):
| Resolution | H.264 | HEVC | AV1 |
|---|---|---|---|
| SD (480p) | $0.0075/min | $0.0105/min | $0.053-$0.079/min |
| HD (1080p) | $0.015/min | $0.021/min | $0.105-$0.158/min |
| UHD (4K) | $0.030/min | $0.042/min | $0.210-$0.315/min |
The AV1 range reflects AWS’s “accelerated transcoding” multiplier of 7-10.5x, which is required for AV1 encoding. Yes, you read that right: AV1 on AWS costs 7 to 10.5 times the H.264 base rate, depending on quality settings.
Additional multipliers apply for: frame rates above 30fps (2x), HDR (1.4x), audio processing, and caption embedding. These stack multiplicatively.
The “normalized minutes” problem: AWS uses a concept where one minute of output can translate to more than one billed minute depending on the job’s complexity. This makes it difficult to predict costs from your source content alone.
What is included: Encoding only. Storage (S3), delivery (CloudFront), and data transfer are billed separately across other AWS services.
Best for: Teams already deeply invested in the AWS ecosystem who need the broadest feature set and can absorb the pricing complexity.
Mux
Pricing model: Per minute of input for encoding, plus per minute of delivery, plus storage.
Mux positions itself as an all-in-one video platform rather than a standalone transcoding service. Their pricing reflects this bundled approach.
Published rates:
| Component | Rate |
|---|---|
| Encoding | $0.0075/min of input |
| Video delivery (streaming) | $0.025/min of video delivered |
| Storage | $0.007/GB/month |
The encoding rate of $0.0075/min looks competitive at first glance. But Mux charges for delivery on top of encoding, and the delivery rate of $0.025/min is where the real cost accumulates. For a video that is encoded once but watched 1,000 times, the encoding cost is negligible — the delivery cost dominates.
Example: A 10-minute video encoded once and watched 1,000 times:
- Encoding: 10 min x $0.0075 = $0.075
- Delivery: 10 min x 1,000 views x $0.025 = $250.00
- Total: $250.08
This bundled model can make sense if you genuinely need an all-in-one platform and do not want to manage your own CDN. But if you already have a CDN (Cloudflare, Fastly, CloudFront) or want to control your delivery infrastructure, you are paying for something you do not need.
What is included: Encoding, hosting, delivery, player analytics, and a basic video player. No separate codec multipliers.
Best for: Teams that want a fully managed video platform and are comfortable with per-viewer delivery costs.
Coconut
Pricing model: Per minute of output, tiered by resolution.
Coconut offers straightforward per-minute pricing without the multiplier complexity of AWS:
| Resolution | Rate |
|---|---|
| SD (up to 576p) | $0.0075/min |
| HD (up to 1080p) | $0.015/min |
| Full HD (up to 1440p) | $0.020/min |
| UHD (up to 2160p) | $0.030/min |
Strengths of this model: It is simple. You know the resolution, you know the cost. No codec multipliers, no tier confusion.
Limitations: Coconut’s codec and customization options are more limited than the other providers in this comparison. Advanced features like per-title encoding, VMAF-targeted quality, DRM, and multi-codec ladders may require workarounds or may not be available. The simplicity of pricing partly reflects the simplicity of the product.
What is included: Encoding and temporary storage. Output delivery to your own S3/GCS/Azure storage.
Best for: Simple transcoding workloads where you need predictable costs and do not require advanced codec or quality features.
Google Cloud Transcoder
Pricing model: Per minute of output, tiered by resolution.
Google Cloud Transcoder API pricing is clean and tiered:
| Resolution | Rate |
|---|---|
| SD (up to 480p) | $0.015/min |
| HD (up to 1080p) | $0.030/min |
| UHD (up to 4K) | $0.060/min |
These rates are notably higher than most competitors, especially at HD and above. Google’s $0.030/min for 1080p H.264 is double what AWS charges for the same codec and resolution, and three times what Transcodely charges.
What is included: Encoding only. Source and output storage (Cloud Storage) and delivery are billed separately.
Best for: Teams already on Google Cloud Platform who want a managed transcoding API integrated with GCS and want to avoid cross-cloud data transfer. The pricing premium is significant, so it is difficult to recommend purely on cost.
Bitmovin
Pricing model: Per minute of output with codec, resolution, and feature multipliers. Custom enterprise pricing available.
Bitmovin targets enterprise customers and does not always publish transparent self-serve pricing. Based on publicly available data and reported customer rates:
Estimated base rates:
| Feature | Multiplier |
|---|---|
| Base rate (H.264, 1080p) | ~$0.0206/min |
| HEVC | 2x base |
| VP9 | 2x base |
| AV1 | 4x base |
| 4K resolution | 4x base |
| 8K resolution | 120x base |
The multipliers stack. A 4K HEVC encode would be approximately: $0.0206 x 4 (4K) x 2 (HEVC) = $0.165/min. An 8K AV1 encode: $0.0206 x 120 (8K) x 4 (AV1) = $9.89/min.
That 8K AV1 number is not a typo. Bitmovin’s 8K multiplier of 120x pushes costs to nearly $10 per minute of output.
What is included: Encoding, with an excellent encoder (Bitmovin’s proprietary encoder is genuinely good). Player SDK is a separate product. Analytics is a separate product. No storage or delivery included.
Best for: Enterprise customers with complex encoding requirements, willingness to negotiate custom pricing, and budget for premium tooling.
Transcodely
Pricing model: Per minute of output, by resolution and codec. No tiers, no normalized minutes.
| Resolution | H.264 | HEVC | VP9 | AV1 |
|---|---|---|---|---|
| 480p | EUR 0.005 | EUR 0.008 | EUR 0.008 | EUR 0.020 |
| 720p | EUR 0.008 | EUR 0.012 | EUR 0.012 | EUR 0.030 |
| 1080p | EUR 0.010 | EUR 0.015 | EUR 0.015 | EUR 0.040 |
| 4K | EUR 0.020 | EUR 0.030 | EUR 0.030 | EUR 0.080 |
Feature add-ons:
- Per-title encoding (content-adaptive bitrate): 1.5x
- DRM (Widevine, FairPlay, PlayReady): 1.25x
- HDR passthrough/tone mapping: 1.4x
- Dolby Atmos audio: 1.15x
What is included at no extra cost:
- Audio track encoding (all tracks in the source)
- Thumbnail generation
- HLS and DASH manifest generation
- CMAF packaging (shared fMP4 segments)
- Subtitle passthrough
- Failed job retries (you are not charged for jobs that fail)
What is not included: Storage and CDN delivery. Transcodely writes output files to your own storage (S3, GCS, Azure, or HTTP endpoint). You manage delivery with your own CDN.
No monthly fees. No minimum commitments. No “contact sales” for pricing. No free tier that expires and traps you into a paid plan. You pay for what you encode, at the rates published above.
Side-by-side cost comparison
Scenario 1: 1,000 minutes/month of 1080p H.264
A small to medium workload — typical for a SaaS product with embedded video, an e-learning platform, or a small media site.
| Provider | Rate | Monthly Cost |
|---|---|---|
| Transcodely | EUR 0.010/min | EUR 10.00 (~$10.80) |
| AWS MediaConvert | $0.015/min | $15.00 |
| Coconut | $0.015/min | $15.00 |
| Mux (encoding only) | $0.0075/min | $7.50 |
| Google Cloud Transcoder | $0.030/min | $30.00 |
| Bitmovin | ~$0.0206/min | ~$20.60 |
At this scale, the differences are modest in absolute terms. Mux appears cheapest, but remember that Mux’s model includes delivery charges that will dominate your bill once viewers start watching. For encoding-only comparison, Transcodely and AWS are the most cost-effective.
Scenario 2: 10,000 minutes/month, multi-codec (H.264 + HEVC + AV1 at 1080p)
A more realistic production workload for a video platform. Each minute of source content produces three output renditions: H.264 for compatibility, HEVC for Apple/smart TV devices, and AV1 for modern browsers.
That is 10,000 min x 3 codecs = 30,000 minutes of output.
| Provider | H.264 (10K min) | HEVC (10K min) | AV1 (10K min) | Total Monthly |
|---|---|---|---|---|
| Transcodely | EUR 100 | EUR 150 | EUR 400 | EUR 650 (~$700) |
| AWS MediaConvert | $150 | $210 | $1,050-$1,575 | $1,410-$1,935 |
| Coconut | $150 | $150* | $150* | $450* |
| Google Cloud | $300 | $300* | $300* | $900* |
| Bitmovin | $206 | $412 | $824 | ~$1,442 |
| Mux | $75** | N/A | N/A | $75** |
* Coconut and Google Cloud Transcoder do not break out per-codec pricing in their published rate cards. These estimates assume the same resolution-based rate applies regardless of codec. Actual costs may differ.
** Mux charges per minute of input, not output, and does not offer granular codec selection in the same way. The encoding cost is lower, but delivery costs ($0.025/min/view) must be factored in.
Key observations:
- AWS AV1 is extremely expensive. The 7-10.5x multiplier makes AV1 encoding on MediaConvert cost more than the combined H.264 + HEVC cost. This effectively penalizes teams for adopting the most efficient codec.
- Transcodely’s AV1 pricing is 2.5-4x cheaper than AWS for the same codec at the same resolution.
- Bitmovin’s multiplier model produces costs comparable to AWS, with the added uncertainty of enterprise negotiation.
- Mux’s model is fundamentally different — the low encoding cost is misleading without accounting for per-view delivery charges.
Scenario 3: Annual cost at 50,000 minutes/month, multi-codec
For a growing platform encoding 50K min/month across H.264 + HEVC + AV1 at 1080p (150K output minutes/month):
| Provider | Monthly | Annual |
|---|---|---|
| Transcodely | ~EUR 3,250 | ~EUR 39,000 (~$42,100) |
| AWS MediaConvert | ~$7,050-$9,675 | ~$84,600-$116,100 |
| Bitmovin | ~$7,210 | ~$86,520 |
| Google Cloud | ~$4,500* | ~$54,000* |
At scale, the cost differences become significant. A team choosing AWS MediaConvert over Transcodely for a multi-codec workload could pay $40,000-$74,000 more per year for the same encoding output.
What is included for free
Not all minutes are created equal. The total cost of transcoding includes more than just the per-minute rate. Here is what each provider includes at no additional charge:
| Feature | Transcodely | AWS | Mux | Coconut | Bitmovin | |
|---|---|---|---|---|---|---|
| Audio tracks | Included | Charged separately | Included | Included | Included | Included |
| Thumbnail generation | Included | Charged separately | Included | Paid add-on | Not available | Paid add-on |
| HLS packaging | Included | Included | Included | Included | Included | Included |
| DASH packaging | Included | Included | N/A | Included | Included | Included |
| CMAF (shared segments) | Included | Included | N/A | Not available | Included | Included |
| Subtitle passthrough | Included | Included | Included | Included | Included | Included |
| Failed job billing | Not charged | Charged | Not charged | Not charged | Charged | Varies |
| Job history retention | Indefinite | 90 days | Indefinite | 30 days | 30 days | Varies |
Two items stand out:
- Failed job billing. Some providers charge you for jobs that fail — meaning a malformed input file or a transient infrastructure error costs you money. Transcodely does not charge for failed jobs.
- Job history retention. As discussed in Why I Built Transcodely, losing historical job data is a real operational problem. Transcodely retains job history indefinitely.
Hidden costs nobody talks about
The per-minute rate is only part of the total cost of ownership. Here are the expenses that pricing pages do not emphasize:
Storage egress fees
If you use AWS MediaConvert, your source files are in S3 and your output files go to S3. Every time a viewer requests a video segment, you pay S3/CloudFront egress fees. These can easily exceed the encoding cost for popular content.
Transcodely is storage-agnostic — you can write outputs to any S3-compatible storage, GCS, Azure, or even Cloudflare R2 (which has zero egress fees). This gives you flexibility to optimize delivery costs independently of encoding costs.
Minimum commitments and reserved pricing
AWS offers reserved pricing for MediaConvert, but it requires a 12-month commitment to a minimum monthly spend. Bitmovin’s enterprise contracts typically include annual minimums. If your volume fluctuates — which it does for most growing platforms — these commitments can lock you into paying for capacity you do not use.
Transcodely has no minimum commitments. You pay for what you encode, month to month.
Support tiers
AWS charges for support plans above the basic tier. Business support starts at $100/month or 10% of your AWS bill (whichever is higher). Enterprise support starts at $15,000/month.
Bitmovin’s support tiers are not publicly priced but are part of enterprise contract negotiation.
With Transcodely, engineering support is included. When you have a question, you talk to engineers who built the platform — not a tiered support organization.
Codec licensing pass-through
If you use HEVC encoding, some providers may require you to handle your own patent licensing arrangements with the HEVC patent pools. This is a real cost and a real legal exposure that is rarely mentioned on pricing pages. Read more about codec licensing in our codec comparison guide.
Multi-output multiplication
Most real workloads produce multiple outputs per source file (different resolutions, codecs, and quality levels for adaptive streaming). A typical ABR ladder might produce 12-18 output renditions per input video. Every rendition is billed separately.
When comparing providers, always calculate the cost for your full output set, not just a single rendition. A provider that looks cheap for a single 1080p H.264 output may be expensive when you factor in your complete codec-and-resolution ladder.
The verdict
Here is how to think about choosing a transcoding provider:
Choose AWS MediaConvert if you are already deeply embedded in AWS, your team is comfortable navigating complex pricing, and your workload is primarily H.264/HEVC (where AWS pricing is competitive). Avoid AWS for AV1-heavy workloads — the 7-10.5x multiplier is punitive.
Choose Mux if you want a fully managed video platform (encoding + delivery + analytics + player) and are comfortable paying per-view delivery charges. Mux is not a transcoding service — it is a video platform. Compare it on that basis.
Choose Coconut if you have simple encoding needs, want predictable pricing, and do not require advanced features like VMAF-targeted quality or DRM.
Choose Google Cloud Transcoder if you are on GCP and want native integration. Be prepared to pay a premium — Google’s rates are among the highest in this comparison.
Choose Bitmovin if you are an enterprise customer with complex encoding requirements and the budget for premium tooling. Their encoder quality is excellent, but you will pay for it, and you will need to negotiate pricing.
Choose Transcodely if you want transparent per-minute pricing, VMAF-targeted quality tiers, a Stripe-like developer experience, and you do not want to negotiate an enterprise contract to get started. Transcodely is built for the 99% of developers who need a transcoding API that just works — sign up, get an API key, and start encoding.
You can explore the full pricing breakdown on our pricing page, read about our codec support in the developer’s codec guide, or see how the API works in our documentation.