Mux encoding pricing by quality tier: free on basic, metered above it

If you’re modeling out a Mux bill before committing to it, the line item that catches people off guard usually isn’t storage or delivery — it’s encoding. But the detail most comparisons get wrong, including an earlier version of this post, is that it isn’t a flat charge. Mux encodes for free on its basic quality tier at any volume, and only starts metering once you move up to plus or premium.

So the real question isn’t “what does Mux charge to encode” — it’s whether basic quality is good enough for your catalog, and what happens to the bill if it isn’t.

That’s not a knock on Mux’s engineering. Their transcoding pipeline is solid and their dashboard makes a bill legible in a way a lot of infra doesn’t. It’s a question of billing model fit: does a per-minute-to-encode charge match how your catalog actually grows? For teams building course libraries, internal video archives, or anything fed by user or AI-generated uploads, the answer is often no — and the reason has less to do with Mux specifically than with the shape of a catalog that only ever grows.

Mux encoding is free on the basic quality tier at all volumes, $0.03125/minute for plus-quality 1080p, and $0.046875/minute for premium, per their public pricing at time of writing. Basic uses a reduced encoding ladder aimed at simpler use cases, so the tier you need is decided by your content, not your budget. Above basic, the charge lands at ingest and scales with how much you upload rather than how much gets watched — which is what compounds for a catalog that only grows.

What each quality tier actually costs

Mux’s pricing is built around discrete meters — encoding at ingest, storage, and delivery — each billed per minute of video rather than per byte. Per their public pricing at the time of writing, encoding is free on the basic quality tier at all volumes, which uses a reduced ladder aimed at simpler use cases. Above that, encoding runs $0.03125 per minute for plus-quality 1080p and $0.046875 for premium, charged before the video is stored and before it’s streamed to a single viewer. So the charge this post is about applies once you need more than basic quality — which most production catalogs do.

Quality tier	Encoding, up to 720p	Encoding, 1080p	Ladder
Basic	Free	Free	Reduced, lower target quality
Plus	$0.025/min	$0.03125/min	Full
Premium	$0.0375/min	$0.046875/min	Full, highest target quality

Rates per Mux’s public pricing at time of writing; 2K and 4K cost more, and volume discounts apply above 5,000 minutes a month.

Basic is genuinely free, not a trial allowance — Mux describes it as suited to “simpler video use cases” like social or user-generated content, and positions it for scenarios where “high encoding costs may limit your business model.” Screen-recorded lectures and talking-head footage often survive a reduced ladder fine. High-motion or high-production video generally doesn’t.

Metering in minutes instead of gigabytes isn’t unique to Mux — Cloudflare Stream does the same thing for storage and delivery, which we’ve covered in why Cloudflare Stream doesn’t bill per GB. What makes encoding worth isolating is timing: above basic, it’s charged once at upload, completely independent of whether the video ever gets watched.

The encoding charge doesn’t care whether anyone ever presses play — only that you uploaded the video.

A course module uploaded and never opened costs exactly the same to encode as one streamed ten thousand times.

Why this compounds for a growing catalog

If basic quality works for you, none of what follows applies and you should take the free encoding. Above basic, a catalog that only grows — new creators adding courses, a fleet generating footage, an AI pipeline producing clips — never sees its encoding line item shrink. Every new upload is a fresh charge stacked on every charge that came before it. The bill tracks cumulative upload volume, not active audience size and not storage footprint, and for most growing products cumulative upload volume is a number that only goes up.

That’s a different shape from a bill that tracks usage. If nobody watches an old module this month, a per-GB delivery charge for that video is close to zero. But the encoding charge for putting it there in the first place already happened, months earlier, and doesn’t get any cheaper as the catalog ages or as older content goes cold. Teams that project this out over a year or two of steady uploads are usually the ones who start looking for a different model.

The rehelios model: encoding is free

rehelios turns that specific meter off. Uploading or importing video — transcoding to adaptive HLS, with optional MPEG-DASH and progressive MP4 — costs $0, at any volume. What you pay for is what the video actually consumes once it exists: $0.02 per GB-month stored and $0.005 per GB delivered, with a $1/month minimum. That’s the same shape as Bunny’s pricing, and the deliberate opposite of a per-minute meter — it charges for space and bandwidth, not for the act of encoding.

npx @rehelios/cli import https://storage.example.com/course-042.mp4 \
  --collection col_courses \
  --wait --json

Encoding to HLS happens as part of that call, at no charge. The only bill you’ll see later is for the GB it occupies in storage and the GB actually delivered to viewers. See the full breakdown on the pricing page.

A worked example: encoding 1,000 hours of new content

Take 1,000 hours of new video landing in a catalog over a quarter — 60,000 minutes. Under Mux’s per-minute model, at $0.03125/minute for plus-quality 1080p (per their public pricing at the time of writing), that’s an encoding charge in the neighborhood of $1,875 for that batch alone, before a single minute of storage or delivery is billed. On the premium tier it’s closer to $2,800. On the basic tier it’s nothing — so the first question to ask is whether basic quality is good enough for your catalog. That charge recurs every time another 1,000 hours comes in — it doesn’t taper off as the catalog matures.

Under rehelios’s model, the same 60,000 minutes cost $0 to encode. The bill only starts once that video is sitting in storage and being delivered to viewers, and it’s metered in gigabytes rather than minutes — so a library that’s mostly cold (uploaded, rarely watched) stays cheap. The real difference is the shape of the two bills: one scales with what you upload, the other scales with what you store and serve. We compare this per-minute-vs-per-GB split across providers in more depth in how video hosting API pricing compares by billing model.

Mux isn’t the wrong choice — it’s a billing model choice

None of this is an argument that Mux is a bad product. Their developer experience is mature, their dashboard and debugging tools are well built, and their feature set — thumbnails, live streaming, real-time analytics — covers ground that takes most video infra vendors years to build. Mux even ships an official MCP server for agent workflows, which is more than most providers in the category can say.

The question worth asking before committing isn’t whether Mux is good — for plenty of teams it clearly is — it’s two things in order. First, does basic quality hold up for your content? If yes, encoding is free and this whole line item disappears. If no, does per-minute-to-encode at plus or premium match how your catalog actually grows? Flat upload volume and a small library barely register. Onboarding new creators, ingesting AI-generated video, or anything where the catalog only moves in one direction is worth modeling explicitly before you sign up. See how the two providers stack up in the Mux comparison.

A bill you can predict from the shape of your catalog, rather than one you have to reconstruct from every ingest event against a per-minute meter, tends to be the one that doesn’t surprise you a year in. That’s the real argument for separating the cost of encoding from the cost of everything else — and for checking, before you build on top of either model, which one actually matches how your product grows.