If you’ve ever wondered why a two-hour movie fits in a few gigabytes instead of filling an entire hard drive, the answer is video encoding. Here’s a practical rundown of what it is, why it matters, and what to consider when you’re encoding video on your own server.<\/p>\n
Raw, uncompressed video is enormous — a camera sensor recording 30 frames per second is really just capturing 30 full-resolution photos every second, which adds up to gigabytes per minute of footage. Video encoding compresses that raw stream into a much smaller file using a codec, without destroying the video’s usability.<\/p>\n
Most compression works by finding redundancy between frames. If two consecutive frames are nearly identical, the encoder can store the differences instead of two full frames — often shrinking file size dramatically with little visible quality loss.<\/p>\n
A codec (short for coder\/decoder) is the software that compresses video during encoding and decompresses it during playback. The most common codec today is H.264 — nearly every phone, browser, and streaming platform supports it. Others you’ll encounter include HEVC (H.265), VP9, and AV1, each offering different trade-offs between compression efficiency, quality, and hardware support.<\/p>\n
Codec is different from container format. The codec determines how the video data is compressed; the container (MP4, MOV, MKV, etc.) is the file format that wraps the compressed video, audio, and metadata together.<\/p>\n
The two terms get used interchangeably, but they’re not quite the same:<\/p>\n
Transcoding is always a form of encoding, but not all encoding is transcoding.<\/p>\n
Higher-quality video means larger files, longer uploads, and more bandwidth for anyone watching. Lower-quality video is smaller and loads faster, but looks worse. Four factors mainly drive file size for a given codec:<\/p>\n
A rough guide to common resolutions:<\/p>\n
| Resolution<\/th>\n | Typical Bitrate<\/th>\n | Best For<\/th>\n<\/tr>\n |
|---|---|---|
| 360p<\/td>\n | 350–800 kbps<\/td>\n | Slow connections, smooth playback over quality<\/td>\n<\/tr>\n |
| 720p (HD)<\/td>\n | 1200–1900 kbps<\/td>\n | Good general-purpose quality<\/td>\n<\/tr>\n |
| 1080p (Full HD)<\/td>\n | 1900–4500 kbps<\/td>\n | High-quality playback where bandwidth allows<\/td>\n<\/tr>\n |
| 4K (2160p)<\/td>\n | 15,000+ kbps<\/td>\n | Maximum quality; most viewers can’t stream it reliably yet<\/td>\n<\/tr>\n<\/table>\nWhy Encoding Needs Real CPU Power<\/h2>\nEncoding, especially at higher resolutions or with newer codecs like HEVC\/AV1, is CPU-intensive — the encoder is running complex math on every frame to find the best possible compression. This is exactly the kind of workload that benefits from a high single-thread and multi-thread performance CPU rather than a general-purpose shared server, since encode time scales directly with available processing power.<\/p>\n |