AWS MediaConvert vs Self-Hosted FFmpeg: A Cost Breakdown

When building a video transcoding pipeline, the choice between AWS MediaConvert and self-hosted FFmpeg is one of the first big decisions you'll face. Both are powerful — but their cost structures are completely different. At low volumes, managed services are easier and cheaper. Beyond a certain threshold, self-hosting wins decisively.

This article uses real numbers to calculate the break-even point and gives you a clear framework for choosing between the two.

Two Approaches

Let's define the options clearly.

AWS MediaConvert is a fully managed video transcoding service. No server management required — you call an API and MediaConvert handles everything. Scaling is automatic, and operational overhead is minimal.

Self-hosted FFmpeg means running FFmpeg on a VPS or EC2 instance you manage yourself. You're responsible for the infrastructure, but as volume grows your costs stay mostly flat.

The key difference in one line: MediaConvert is pay-per-use; self-hosted FFmpeg is mostly fixed cost. That's the heart of every cost comparison between the two.

AWS MediaConvert Pricing

AWS MediaConvert charges based on the output duration of processed video. Rates vary by region, codec, and resolution.

Representative rates (Professional Tier, Tokyo region):

Example: 100 × 1080p videos per month

Let's say you process 100 videos per month, each averaging 10 minutes in length.

• Output duration: 10 min × 100 videos = 1,000 minutes/month
• 1080p rate: $0.0135/min
• Transcoding cost: 1,000 min × $0.0135 = $13.50/month

Add S3 storage and data transfer for ~100 videos at ~1 GB each:

• S3 storage: ~100 GB × $0.025/GB = $2.50/month
• Data transfer: ~$1–5 depending on destination

Total: roughly $17–21/month

At this scale, MediaConvert is genuinely inexpensive with no operational overhead to worry about.

Submitting a MediaConvert Job via AWS CLI

aws mediaconvert create-job \
  --endpoint-url https://XXXX.mediaconvert.ap-northeast-1.amazonaws.com \
  --role arn:aws:iam::123456789012:role/MediaConvertRole \
  --settings file://job-settings.json

Job settings — including resolution, bitrate, and codec options — are defined in a JSON file and passed via --settings.

Self-Hosted FFmpeg Cost Structure

Running FFmpeg yourself involves several cost components. Let's break them down.

VPS / Server Costs

Video encoding is CPU-intensive. For real-time 1080p encoding, you'll want at least 4 cores. Here's a comparison of popular providers:

For cost-sensitive setups, Hetzner and Vultr are the go-to options. For a full walkthrough of server selection and FFmpeg setup, see FFmpeg VPS Encoding Server Setup.

Storage Costs

You need somewhere to hold files before and after conversion. If you use the VPS's local disk, there's no extra charge — but using object storage adds cost:

• Cloudflare R2: $0.015/GB/month (free egress)
• AWS S3: $0.025/GB/month (data transfer billed separately)

Labor Costs (The Hidden Variable)

Assuming two hours per month of maintenance (patching, log review, incident response):

• At $50/hour: 2 hrs × $50 = $100/month

This is the number most teams forget to include when comparing options.

Monthly Cost Breakdown

Where Is the Break-Even Point?

Self-hosted FFmpeg's fixed-cost model wins once volume is high enough. Using the minimal setup at $65/month as a baseline:

The break-even sits around 400–500 videos (4,000–5,000 minutes) per month. Below that, MediaConvert is cheaper. Above it, self-hosted FFmpeg wins.

One important caveat: these numbers assume labor costs of $50/month (about one hour of maintenance). If maintenance runs $100/month, the break-even shifts up to 800–1,000 videos per month.

When MediaConvert Makes Sense

MediaConvert earns its place in several scenarios.

Low or unpredictable volume. At 100 videos/month, you're paying roughly $17. There's no idle server sitting there costing money while you wait for jobs. If your volume swings from 50 to 500 month to month, pay-per-use is a natural fit.

Limited infrastructure expertise. When your team's strengths lie elsewhere, the operational overhead of running and maintaining servers is a real cost — often harder to quantify but definitely real.

High quality requirements out of the box. MediaConvert supports broadcast-grade codecs (H.264, H.265, AV1) with fine-grained bitrate control. It's production-ready without configuration effort.

When Self-Hosted FFmpeg Makes Sense

The case for self-hosting is equally clear in the right circumstances.

High, steady volume. Once you're past 500 videos/month, the fixed-cost model pays off. At 1,000 videos/month, you could save over $1,000/year compared to MediaConvert — and the gap widens as volume grows.

Custom codecs or specialized processing. If you need filters that MediaConvert doesn't support, custom codec settings, GPU-accelerated encoding (NVENC, QuickSync), or any pipeline that goes beyond standard presets, FFmpeg is your only real option.

Data residency or on-premises requirements. Regulatory constraints — data that can't leave a specific country or facility — rule out cloud services entirely. Self-hosted FFmpeg is the answer here.

Predictable cost at scale. Pay-per-use pricing has no ceiling. Fixed costs make budgeting straightforward and remove the risk of surprise bills during traffic spikes.

Wrapping Up

There's no universal winner between AWS MediaConvert and self-hosted FFmpeg. The right choice depends on your volume and your team's operational capacity.

• Under 500 videos/month (5,000 min) — MediaConvert: cheaper and simpler
• Over 500 videos/month (5,000 min) — Self-hosted FFmpeg: better cost efficiency
• Custom requirements or data residency constraints — FFmpeg, no question

Start by putting real numbers on your current volume and growth trajectory. Once you know where you land relative to the break-even point, the decision becomes straightforward.

For a step-by-step guide to setting up your own FFmpeg encoding server, see FFmpeg VPS Encoding Server Setup.