AWS MediaConvert looks cheap on its pricing page: $0.0075/output-minute for standard definition video is an attractive headline. But AWS pricing is famously multi-layered — and MediaConvert is no exception. The full cost includes S3 storage for input and output files, data egress charges when you download the result, API calls to trigger jobs, and CloudWatch logs if you're monitoring pipelines.
This guide calculates the full AWS cost stack for common video conversion workflows and compares it against managed conversion APIs. All prices are April 2026 AWS US-East-1 pricing — rates vary by region.
TL;DR — what does AWS MediaConvert actually cost per video?
For a typical 5-minute 1080p video input, transcoded to 720p MP4 output:
| Cost component | Amount | AWS price | Per-conversion cost |
|---|---|---|---|
| MediaConvert processing (5 min HD output) | 5 min | $0.0150/min | $0.075 |
| S3 input storage (500 MB × avg 1 day) | ~0.016 GB-month | $0.023/GB-month | $0.0004 |
| S3 output storage (300 MB × avg 3 days) | ~0.030 GB-month | $0.023/GB-month | $0.0007 |
| S3 PUT/GET requests | ~10 requests | $0.005/1K PUT, $0.0004/1K GET | $0.000054 |
| S3 data egress (300 MB output downloaded) | 0.3 GB | $0.09/GB | $0.027 |
| Total per 5-min HD conversion | ~$0.10–$0.12 |
vs. ChangeThisFile Hobby ($29/10K): $0.0029/conversion — roughly 35× cheaper per conversion at this plan. But AWS scales better at very high volume, and MediaConvert is specifically designed for broadcast-quality video pipelines.
AWS MediaConvert pricing breakdown (April 2026)
MediaConvert processing cost (US-East-1):
| Tier | Resolution | Rate per output-minute |
|---|---|---|
| Basic (SD up to 720p) | ≤720p | $0.0075/min |
| Professional (HD 1080p) | 720p–1080p | $0.0150/min |
| Premium (4K UHD) | 1080p–4K | $0.0300/min |
Cost is based on output duration, not input. If you transcode a 10-minute source to a 10-minute output, you pay for 10 output-minutes. If you create two output renditions (e.g., 1080p + 720p) from the same source, you pay for output-minutes of both renditions.
S3 storage costs (US-East-1):
- Storage: $0.023/GB-month for first 50 TB
- PUT requests: $0.005 per 1,000 requests
- GET requests: $0.0004 per 1,000 requests
- Files don't automatically delete after MediaConvert finishes — you must delete them via lifecycle policy or manual cleanup
Data egress (transfer out of AWS to internet):
- First 100 GB/month: $0.09/GB
- 100 TB–9.999 PB: $0.085/GB
- If your output is delivered via CloudFront CDN: $0.0085–$0.02/GB depending on region and volume (significantly cheaper)
First 15 minutes/month free: AWS MediaConvert includes 15 minutes of SD or HD output per month at no charge — useful for testing, not for production workloads.
Hidden AWS costs that catch teams off-guard
1. Data egress is the silent budget killer. AWS doesn't charge for data transfer into S3 (upload). But transferring output files from S3 to your server or users costs $0.09/GB. A video pipeline producing 1 TB/month of output video faces $90/month in egress charges alone — on top of MediaConvert processing fees.
2. S3 storage accumulates if you don't clean up. MediaConvert doesn't delete input or output files after processing. If your pipeline doesn't implement S3 lifecycle rules, files accumulate indefinitely. A bug that disables your cleanup job can result in hundreds of GB of stored video you're paying for but don't need.
3. Multiple output renditions multiply cost. If you produce a 4K master + 1080p stream + 720p stream + 480p stream from each source video, you pay output-minutes for all four renditions. A 10-minute video that produces 4 renditions = 40 output-minutes of billing vs 10 for a single output. Teams that naively implement multi-bitrate ladders see 3–5× higher-than-expected costs.
4. CloudWatch logging costs. MediaConvert emits job status events to CloudWatch. CloudWatch ingestion is $0.50/GB after the free tier. At high job volume, CloudWatch logging adds $5–$20/month.
5. AWS regions have different rates. MediaConvert pricing varies by AWS region. Processing in EU-West-1 (Ireland) or AP-Southeast-1 (Singapore) is 10–30% more expensive than US-East-1. Teams with compliance requirements that force specific regions pay a premium.
Cheaper architecture for common video workflows
Scenario 1: Mobile app with user video uploads (avg 30s clips)
Volume: 10,000 conversions/month. Avg output: 30s HD.
AWS MediaConvert: 10K × 0.5 min × $0.0150 + egress (50 MB avg × 10K × $0.09/GB) = $75 + $45 = $120/month
ChangeThisFile Startup: $99/month flat for 50K conversions
Savings: $21/month. ChangeThisFile also eliminates S3 management complexity.
Scenario 2: Content platform with 10-minute episodes
Volume: 1,000 conversions/month. Avg output: 10 min HD.
AWS MediaConvert: 1K × 10 min × $0.0150 + egress = $150 + ~$90 = $240/month
CloudConvert PAYG: 1K × 10 min × $0.0048 = $48/month
ChangeThisFile Startup: $99/month (covers 50K conversions)
AWS wins at very high volume but not at 1K conversions/month.
Scenario 3: Broadcast-quality encoding at scale
Volume: 100,000 hours output/month.
AWS MediaConvert: 100K hr × 60 min × $0.0150 = $90,000/month — but reserved pricing and AWS support tiers reduce this significantly. For this use case, AWS is the intended platform and negotiated rates apply.
When AWS MediaConvert is the right choice
AWS MediaConvert wins when:
- Broadcast-quality video requirements — HDR, Dolby Vision, HEVC, AV1 encoding, broadcast spec compliance
- You're already deep in AWS infrastructure — Lambda triggers, S3 events, CloudWatch monitoring, IAM policies already exist. MediaConvert fits naturally into an AWS-native pipeline at near-zero additional ops cost.
- Multi-bitrate adaptive streaming — HLS, MPEG-DASH, CMAF output for video streaming platforms. AWS MediaConvert is designed for this; general conversion APIs are not.
- High-volume video production — at 500,000+ output-minutes/month, AWS reserved pricing and volume discounts change the economics significantly.
- SLA requirements — AWS MediaConvert has enterprise-grade SLAs, regional redundancy, and support tiers that managed conversion APIs don't match.
When a managed conversion API beats AWS MediaConvert
Choose a managed conversion API over AWS MediaConvert when:
- You're not already on AWS (no existing infrastructure advantage)
- You need mixed format types — documents, images, audio, and video in one API
- Video conversion is not your core product — overhead of AWS S3 + IAM + CloudWatch for a supporting feature isn't worth it
- Volume is under 10,000 conversions/month — flat-rate APIs are simpler and often cheaper
- You need simple synchronous conversion (upload file, get result) without S3, lifecycle rules, or event-based triggers
Full cost comparison: AWS MediaConvert vs alternatives
| Use case | AWS MediaConvert (total incl. egress) | ChangeThisFile | CloudConvert PAYG |
|---|---|---|---|
| 1K × 5-min HD conversions/mo | ~$120–$150 | $29 (Hobby) | $24–$48 |
| 10K × 30-sec HD clips/mo | ~$90–$120 | $29 (Hobby) | $24 |
| 100K × 1-min SD conversions/mo | ~$150–$200 | $499 (Scale) | $240 |
| 1K × 10-min HD episodes/mo | ~$240–$290 | $99 (Startup) | $48 |
| Documents (not video) | Not supported | $29–$99 | $48–$240 |
April 2026 US-East-1 pricing estimates. AWS MediaConvert includes estimated S3 egress at $0.09/GB. Verify at aws.amazon.com/mediaconvert/pricing.
AWS MediaConvert is the right tool for broadcast-quality video pipelines at scale, especially for teams already on AWS. For product teams that need video as one of many conversion formats, or who want a simpler billing model without S3 management, managed APIs are cheaper and easier to integrate at moderate volume. ChangeThisFile's free tier handles MP4, MKV, MOV, WebM, AVI, and other video formats alongside documents, images, and audio — one API, one billing model, no S3.