Getting an MP4 back out of Mux: what static renditions cost

Your asset is in Mux, the playback ID works, and your automation needs the actual file. You enable static renditions, the docs say standard ones are free to generate, and you move on. Then the invoice has a storage line and a delivery line you didn't model.

Mux static renditions cost nothing to prepare when you use the standard type (the highest video rendition, or audio-only), but the file you created is then billed per minute of content, per rendition, per month that it sits there, and every minute you download is billed as a minute streamed at the asset's delivery rate. Advanced static renditions, the resolution-specific ones, add a preparation charge per minute of content that scales with resolution: roughly $0.008 per minute up to 720p and $0.032 per minute at 4K on basic and plus quality, inside the first 5,000 minutes. So "free to generate" is accurate about one of three meters.

These rates are Mux's own published numbers as of late October 2026, read off its pricing page and its static renditions guide. Rate cards move; check the current page before you commit a budget to them.

The four charges between "my file is in Mux" and "my file is on my disk"

Getting a plain MP4 back out of Mux touches up to four separate meters, and no single page totals them for you. Mux stores a master and serves HLS by default, so the download path is something you opt into.

The encode being free is the part everybody quotes. It's also the part that makes Mux look like a transcoder when it's priced like a platform: the free encode is paid for by the meters that run afterward, forever.

What a standard rendition still charges you for after it's generated

A standard static rendition is free to prepare and not free to keep. Static rendition storage is billed per minute of content, per rendition, per month: around $0.00075 per minute up to 720p, $0.001 per minute at 1080p, and $0.0001 per minute for audio-only. That's a second storage line on top of whatever the asset itself costs, because the MP4 is a separate stored object from the master.

Resolution multiplies both storage and delivery off the 720p base. 1080p is 1.25x, 1440p/2K is 2x, 2160p/4K is 4x. A month of 4K renditions is four times the storage line of the same minutes at 720p, before you fetch any of them.

Delivery is the charge that surprises pipeline builders, because a download is not a separate category. Each minute downloaded counts as a minute streamed and is billed at the asset's video quality level delivery rate, which starts at $0.0008 per minute up to 720p after the first 100,000 free delivery minutes each month. Your automation pulling a file is, to the meter, a viewer watching it.

One more detail that catches people who treat Mux as scratch space: basic quality assets carry a minimum storage charge of one month, prorated after that. Upload at 9am, fetch the MP4 at 9:04, delete the asset at 9:05, and you've still bought a month.

Advanced static renditions: per minute, per rendition, per resolution

Advanced static renditions exist because "highest" isn't always what you want. You create them with POST /video/v1/assets/{ASSET_ID}/static-renditions, passing a resolution of highest, audio-only, 2160p, 1440p, 1080p, 720p, 540p, 480p, 360p or 270p, and the output lands at a predictable filename you can construct in a workflow. Requests that would upscale the source are skipped rather than served.

The published preparation rates on basic and plus quality, first 5,000 minutes, are $0.008 per minute up to 720p, $0.010 at 1080p, $0.016 at 1440p and $0.032 at 2160p. Premium quality runs $0.012 / $0.015 / $0.024 / $0.048. Each rendition is billed separately, so asking for 1080p and 480p off the same source bills both, and then stores both.

This is the change that moved MP4 output from a bundled feature to a line item. Mux's own stated reason for unbundling was that about 90% of its customers don't use static renditions, so the cost of generating and storing them was being built into everyone's bill. Fair enough. If you're in the 10% who only ever wanted the file, the unbundling was a price increase.

500 clips a month, fetched once by a robot, never watched by a human

Here's the workload Mux's own documentation never models: a content pipeline that pushes 500 one-minute 1080p clips a month, fetches each one exactly once over HTTP, and hands it to the next step. Nobody presses play.

Two honest readings of that table. First, the delivery charge really is $0: 500 minutes is half a percent of the 100,000 free delivery minutes, so a small pipeline's downloads are genuinely free, and the meters to watch are preparation and storage. Second, the only line that behaves like a subscription is storage, and it compounds. Keep twelve months of clips and the rendition storage alone is $6.00 in month 12 and about $19.50 across the year, on top of $60 of preparation and on top of base asset storage. Switch the same pipeline to 4K and preparation goes to $16.00 a month, $192 a year, with storage at four times the 720p base.

Now the part that decides whether any of this is the right bill. A static rendition hands back the same video in a different container. It does not reframe a 16:9 master to 1080x1920, burn in captions, or stamp a logo. If your 500 clips need any of that, you're paying Mux to store a catalogue you already keep in S3 or R2, and still running FFmpeg somewhere to do the actual work. On a processing API the shape inverts: FFmpeg Micro meters input duration only, 1 token per 10 seconds, per second with no rounding up to the minute, with status checks and downloads free and failed jobs never billed. Those 500 minutes are 3,000 tokens, which is the $19.99 Starter grant plus one $5 top-up, and the meter stops when the job does. There's nothing stored on our side generating a line item next month.

The trim case widens the gap. If those 500 clips are cut from 50 hour-long recordings, Mux has to hold the full 3,000 minutes of source as assets before you can render a rendition of any of it. Billed on input duration per second, a 30-second clip out of a one-hour recording costs 30 seconds. That's the same arithmetic as counting which parts of your editing cost are machine work: you pay for the output you asked for, not for the archive it came from.

When the static rendition is the right call

Mux is priced correctly for what it is. If you need a player, adaptive HLS, a CDN and a catalogue that viewers actually watch, the delivery meter is buying you something real, and enabling a standard static rendition so an occasional user can download the file is a 50-cent decision. Master access is the other documented path, and it gives you a URL to the original master that's valid for 24 hours, which is fine for a one-off export and wrong for a retry queue that might come back tomorrow.

Where it goes sideways is using a streaming platform as a transcoder. You end up renting storage for a duplicate of a file you already own, paying a viewer-shaped delivery rate for robot fetches, and carrying a one-month storage minimum on assets you wanted for four minutes. That's the same mismatch as hitting a host's built-in limits and generating the asset from an API instead, or watermarking every UGC upload inside Make rather than inside a platform that bills you monthly for the result.

FAQ

Are standard static renditions on Mux really free?

Standard static renditions are free to prepare, not free to have. Mux charges static rendition storage per minute of content, per rendition, per month, and bills every minute you download as a streamed minute, so a standard rendition you fetch once still produces two line items.

Do my automation's downloads eat the free delivery minutes?

Downloads draw on the same delivery allowance as playback, because Mux counts a minute downloaded as a minute streamed. With 100,000 free delivery minutes a month, a pipeline fetching 500 one-minute clips uses half a percent of the allowance and pays $0 for delivery, which is why preparation and storage are the lines that actually move a small bill.

If I delete the asset the same day, do I still pay a month of storage?

Basic quality assets carry a minimum storage charge of one month, prorated after that, so deleting an asset hours after you fetch its MP4 does not avoid the storage charge. Treating Mux as temporary working space for a transcode means paying a month of rent per pass.

Which download path is cheapest for a file I only fetch once?

For a single fetch, a standard "highest" rendition is the cheapest of the three paths because its preparation is free and only storage and delivery apply; an advanced rendition adds $0.008 to $0.032 per minute of preparation depending on resolution. Master access avoids rendition storage but produces a URL that expires in 24 hours, so it won't survive a retry the next day.

Am I billed for preparation when a rendition gets skipped as an upscale?

Mux documents that rendition requests which would upscale the source are skipped rather than served, but the pages that document the behavior don't state how skipped preparation is metered, so confirm it against your own usage report before you build a pipeline that requests resolutions blindly. For comparison, FFmpeg Micro never bills a failed job, which is a rule you can budget against rather than a question you have to test.

A rendition storage line that reads $6.00 in month 12 for clips nobody watched is a small number attached to the wrong model: you're renting a catalogue to get a file back. If your pipeline's real job is a reframe, a caption burn or a watermark, as with converting a 4K master to 1080x1920, run that pass where the only meter is the seconds you send in and the download costs nothing. Sign up free and point it at one clip from this week: nothing to install, no server to keep alive, callable from your own code, from n8n, Make and Zapier, or from an AI agent, with a free tier to start.