Bitrate vs resolution

Two numbers decide how a video looks, and most people only pay attention to one of them. Resolution is the pixel count: 1920x1080, 3840x2160. Bitrate is how many bits per second the file spends describing those pixels. Resolution sets the size of the canvas. Bitrate decides how much paint you get.

Starve a 4K file of bitrate and it will look worse than a well-fed 1080p one, on the same screen, every time. This is not a marginal effect. It's the single most common reason a video that should look good doesn't.

Why more pixels need more bits

A 4K frame has four times as many pixels as a 1080p frame. Hold the bitrate constant and each pixel gets a quarter of the description it had. The encoder responds the only way it can, by grouping pixels together and describing them as blocks rather than individually.

That's what compression artefacts are. Blocking in dark areas, banding across skies and gradients, smeared texture on skin and hair, and detail that dissolves whenever the camera moves. The frame is still technically 3840 pixels wide. It just doesn't contain 3840 pixels worth of information.

What the numbers actually look like

Situation	Rough working range	What you notice if you go under
1080p, talking head, locked off	8-12 Mbps	Very little. This is an easy scene.
1080p, handheld, moving background	15-25 Mbps	Texture smears during movement.
4K, general delivery	35-50 Mbps	Banding in skies, mushy foliage.
4K, high motion or grain	60-100 Mbps	Blocking that pulses with the motion.
Archival master	Higher, or an intermediate codec	Generational loss on every future edit.

Treat those as starting points rather than rules. The honest answer is that the right bitrate depends on the content, and the way to find it is to encode a difficult thirty seconds and look at it, not to trust a table.

A rule of thumb that holds up

If you have to choose between resolution and bitrate, choose bitrate. A clean 1080p file beats a starved 4K one on any display, because a good scaler upsizing clean pixels produces a better picture than a decoder reconstructing damaged ones.

The exception is upload, where platforms tie their bitrate allocation to the resolution you give them. There, going up in resolution can buy you a bigger budget than you would otherwise qualify for, which is a quirk of how the platforms work rather than anything about the format.

What to do with a file that's already starved

You can't recover information the encoder discarded. What you can do is stop making it worse and clean up what's visible. Compression artefacts respond reasonably well to targeted denoising, and an AI upscaler that has been trained on compressed footage will reconstruct plausible texture where blocking removed it. Crisp does both on-device, and it's worth doing before any re-encode rather than after, since a second compression pass will otherwise preserve the artefacts as if they were detail.

Bitrate questions

Is a bigger file always better?

Up to a point, and then it stops mattering. Past the bitrate a scene actually needs, extra bits describe information the encoder has already captured perfectly well, and you're only making the file harder to store and slower to upload. The point of diminishing returns depends entirely on how difficult the footage is.

Should I export at a higher resolution than I shot?

For upload, often yes, because platforms allocate bitrate by resolution. For archival or local playback, no. You aren't adding real information, and you're making every future operation on the file slower.

What is variable bitrate, and should I use it?

Variable bitrate lets the encoder spend more on difficult scenes and less on easy ones, which is almost always what you want for delivery. Constant bitrate is mainly useful when something downstream needs a predictable data rate.

Why does my footage look worse after editing even though I didn't change anything?

Because exporting re-encodes it. Unless you're stream-copying, the export is a fresh compression pass, and any clip that passes through it loses a little. Keeping an intermediate or high-bitrate master limits how much that accumulates over successive edits.

Download Crisp for Mac Free to try, one-time $19 to remove the watermark. Runs entirely on your Mac.