Let’s make the words usable.
This is a plain-English glossary with a simple checklist and the pitfalls that cause the most wasted time: blurry video, huge files, washed-out color, stuttery motion, and audio that slowly goes out of sync.
Quick checklist (use before you export or upload)
These are the “don’t step on the rake” checks. If you do nothing else, do these.
- Match resolution to the destination: 1080p for most web, 4K only if you truly need it.
- Pick a sane frame rate and stick to it: 30 fps or 60 fps; avoid mixing timelines if you can.
- Use H.264 for maximum compatibility (or HEVC/H.265 if you control the playback environment).
- Use a reasonable bitrate: too low = blocky; too high = massive files without visible benefit.
- Make sure audio sample rate matches your project: typically 48 kHz for video.
- Prefer CFR (constant frame rate) exports if you’ve had sync issues.
- Do a 10-second test export and watch it in the player your audience will use.
Codec vs container (the most common confusion)
Container is the “box” the file comes in (like MP4, MOV, MKV). Codec is how the video/audio inside is compressed (like H.264, HEVC, AAC).
A file can be “an MP4” and still fail to play somewhere because the codec inside isn’t supported.
- MP4 is a container. It often contains H.264 video + AAC audio (a very compatible combo).
- MOV is a container. It can be compatible, but it’s not automatically “higher quality.”
- MKV is a flexible container. Great for archiving, sometimes annoying for editors and web platforms.
Pitfall: “I exported MP4, so it should work.” Not necessarily—check the codec, not just the extension.
Bitrate (why your file is huge or looks blocky)
Bitrate is how much data per second goes into the video. More bitrate usually means better quality, but only up to a point.
- Too low: smearing in motion, blocky gradients (skies/walls), text becomes crunchy.
- Too high: giant files, slower uploads, and sometimes no visible improvement (especially for talking-head or screen recordings).
- Variable bitrate (VBR): spends more data on complex moments, less on simple scenes. Usually a good default.
- Constant bitrate (CBR): predictable, sometimes required for strict workflows, often less efficient.
Pitfall: Cranking bitrate to “maximum” to fix blur. If the source is low-quality (or scaled up), higher bitrate won’t recreate detail—it just preserves the blur more faithfully.
Resolution vs scaling (why 1080p can look worse than 720p)
Resolution is frame size (e.g., 1920×1080). Scaling is resizing video from one resolution to another.
Upscaling (720p → 1080p/4K) can look softer, especially for screen recordings with small text.
- Native resolution: keep your export at the same resolution you recorded whenever possible.
- Downscaling: 4K → 1080p often looks great and can reduce noise/aliasing.
- Upscaling: only do it if you must meet a platform requirement.
Pitfall: Editing a 1080p timeline with a mix of 720p clips and assuming it will “auto-enhance.” It won’t—those clips will still be 720p detail, just stretched.
Frame rate, CFR/VFR, and the audio sync trap
Frame rate is frames per second (24/30/60 are common). But the sneaky part is whether it’s constant or variable.
- CFR (constant frame rate): every second has the same number of frames. Editors and players tend to behave predictably.
- VFR (variable frame rate): frames per second changes over time (common with phone footage, screen recording, and some capture tools).
Pitfall: “Audio drift” where sound slowly stops matching lips. This is often VFR footage inside a CFR timeline (or exports that keep VFR).
On Windows, if you keep seeing drift, your practical goal is: convert VFR sources to CFR (or export CFR) before doing lots of edits.
Color and HDR terms (washed out, too dark, weird skin tones)
Color terms look scary, but most problems come from a couple of mismatches.
- SDR vs HDR: HDR can look gray/washed out when viewed or exported as SDR without proper tone mapping.
- Color space (Rec.709, Rec.2020): Rec.709 is the normal “web video” expectation; Rec.2020 is common for HDR.
- Color range (limited vs full): a mismatch can crush blacks or raise them, making video look faded.
Pitfall: Recording HDR on a device, then exporting “normal MP4” and being surprised the upload looks wrong. The fix is usually consistent SDR handling end-to-end, or intentional HDR delivery (only if the platform supports it).
Audio terms that matter (and the ones you can ignore)
Good video with bad audio still feels bad. The good news: you don’t need studio jargon.
- Sample rate (44.1 kHz vs 48 kHz): for video, 48 kHz is the common standard.
- Bitrate (audio): higher helps a bit, but AAC at typical settings is usually fine for web.
- Mono vs stereo: voice is often fine in mono; stereo is useful for music/ambient.
- Normalization / loudness: makes volume more consistent across clips; avoids “why is this part quiet?”
Pitfall: Mixing 44.1 kHz and 48 kHz audio sources and then wondering why exports behave oddly. If you can, convert/standardize early.
Takeaway: pick “boring” defaults and avoid the classic rakes
If you want a safe, broadly compatible baseline on Windows: MP4 (container) + H.264 (video) + AAC (audio), export CFR, keep resolution and frame rate consistent, and don’t use HDR unless you mean to deliver HDR.
Most video pain isn’t about advanced settings—it’s about one mismatch that quietly compounds through the workflow.