The complaint
Your export looks perfect on your machine. You upload it. The version that comes back has smeared shadows, blocky movement, and bands across the sky. Nothing you did was wrong, and the reason is that you are not uploading a finished video — you are uploading raw material for someone else's encoder.
Understand four things once and export stops being guesswork.
Container and codec are different
The container is the box: .mp4, .mov, .mkv, .webm. It holds video, audio, subtitles and metadata, and says how they are interleaved. The codec is how the video inside was compressed.
An .mp4 might contain H.264 or H.265 or AV1. That is why "it's an MP4" tells you almost nothing about whether a given player can open it, and why renaming a file extension never fixes anything.
- H.264 / AVC — the safe default. Nearly every device on earth decodes it in hardware. Not the most efficient any more, and worth it anyway for anything you hand to another person.
- H.265 / HEVC — roughly 30–50% smaller than H.264 at similar quality, and what most modern phones record in. Decode support is good but not universal, and its patent licensing is messy enough that some browsers avoid it.
- AV1 — royalty-free and more efficient than H.265. Encoding is slow; hardware decode is common on newer devices, absent on older ones. YouTube serves it to clients that can take it.
- ProRes, DNxHR — intermediate codecs. Every frame stored whole, files enormous, editing instant. For handing to another editor or archiving a master, never for uploading.
Bitrate is the one that decides how it looks
Bitrate is how many bits per second the encoder may spend. Resolution and codec set the ceiling; bitrate sets what you get.
Roughly, for H.264 uploads (check the platform's current guidance — these numbers move):
- 1080p at 25 or 30 fps: about 8–12 Mbps
- 1080p at 50 or 60 fps: about 12–18 Mbps
- 4K at 25 or 30 fps: about 35–45 Mbps
- 4K at 50 or 60 fps: about 53–68 Mbps
Some content eats bits far faster than others. Rain, confetti, foliage in wind, water, film grain, smoke and fast camera moves all produce huge change between frames, and the encoder must describe all of it. A talking head against a plain wall at 8 Mbps looks fine; a rainy street at 8 Mbps turns to porridge.
Two practical consequences:
Upload generously. The platform re-encodes whatever you send, so anything you save with a small file is quality thrown away before their encoder starts. Give it two to three times the delivery bitrate.
Upload at a higher resolution than your target. Platforms allocate bitrate by resolution tier, and the 4K tier gets substantially more bits than the 1080p tier. Exporting a 1080p project upscaled to 2160p before upload is a well-known and genuinely effective way to get a better-looking 1080p stream back, particularly for high-motion content. It feels like a cheat. It works because you are moving your video into a more generously funded bucket.
Frame rate and resolution: match, do not convert
Pick the frame rate of your source and stay on it end to end. Shoot 25, cut on a 25 fps timeline, export 25.
Convert and you get judder, because the editor has to invent or discard frames. Putting 30 fps clips on a 25 fps timeline means five frames a second are dropped or blended, which the eye reads as a stutter on every pan.
Regionally, 25 and 50 fps are standard where mains power is 50 Hz — India, most of Europe and Africa — and 30 and 60 where it is 60 Hz. Matching the local mains frequency also avoids rolling flicker under fluorescent and LED lighting.
Slow motion is the exception: shoot 50 or 60 and place it on a 25 or 30 timeline for honest half-speed with real frames.
Audio, and one number that catches people
Export audio as AAC, 48 kHz, stereo, 192–320 kbps. There is no reason to go lower and little benefit above.
The number that matters is loudness. Platforms normalise: YouTube brings uploads to somewhere around -14 LUFS integrated, and other short-form platforms are in a similar region. Their exact figures change, so treat that as an order of magnitude.
So mastering loud gains you nothing. Crush your mix to -6 LUFS and the platform turns it down by 8 dB: you have destroyed your dynamic range and arrived at the same perceived volume as everyone else. Mix near -14 LUFS and keep true peaks below about -1 dBFS so the encoder has room. Resolve's Fairlight page has a loudness meter; so does any free DAW.
The settings that actually matter, by destination
- YouTube: MP4, H.264, high bitrate, source resolution and frame rate, AAC 48 kHz. Consider the upscale-to-4K trick for high-motion work.
- Instagram, TikTok, Shorts: MP4, H.264, 1080×1920, under the platform's file size and length limits, captions burnt in. These re-encode hard, so send the best file the app will accept.
- A client, or another editor: ProRes 422 or DNxHR SQ in a MOV, plus a separate H.264 for review. Never hand over your only copy as a compressed delivery file.
- Archive: keep the project file, the source footage and one high-quality master. Not the YouTube upload.
What you cannot fix at export
Export settings recover nothing. If a shot is soft, noisy, or clipped in the highlights or the audio, a higher bitrate preserves the problem in more detail. Every re-encode loses a little more, so never export an H.264, re-import it, edit and export again — go back to the project.
Today
Export the same thirty seconds twice, at 8 Mbps and 40 Mbps, and watch both full-screen on a phone. If you cannot tell them apart, your content is bit-cheap and you can relax. If you can, you now know why.
Before you move on