H.265 vs H.264: Video Compression Codec Guide for CCTV Buyers (2026)

The same 4MP camera records 18-25 GB per day on H.264 and 9-13 GB per day on H.265. A 16-camera warehouse keeping 30 days needs about a 9-12 TB recorder on H.264. The same fleet fits on 4-6 TB with H.265. The codec choice decides the recorder you buy, the drives you stock, and the monthly bandwidth bill. Buyers who skip this decision pay for extra disk for years.

This guide explains the H.265 vs H.264 question for CCTV buyers in plain terms. It covers how the two video codecs compress footage. It compares real bitrate numbers per resolution and shows how much storage each one uses. It explains H.265+ smart encoding, which devices actually play H.265, and when it pays to upgrade. All figures are typical values from common deployments, not vendor maxima.

Keep reading for more!

The Snapshot

• H.265 (HEVC) is the successor to H.264 and delivers similar quality at roughly half the bitrate.
• Typical 4MP daily storage at 15 fps: 18-25 GB on H.264, 9-13 GB on H.265, and 6-10 GB with H.265+ smart encoding.
• 16 cameras at 30 days: about 9-12 TB on H.264, 4-6 TB on H.265, and 3-5 TB with H.265+.
• H.265 needs a full decoder chain: the camera, the recorder, and the viewer software must all support it.
• H.265+ is a scene-aware smart mode: it trims bitrate when nothing moves, saving another 30-60% on top of H.265.

What Is H.265 (HEVC)?

H.265 is the video compression standard published in 2013 under two names. ITU-T calls it H.265. ISO/IEC calls it HEVC, which stands for High Efficiency Video Coding (ISO/IEC 23008-2, MPEG-H Part 2). The bitstreams are identical, so a file labeled HEVC plays on any H.265 device.

H.265 was built for 4K and 8K video. Security camera makers adopted it fast, because surveillance is a bitrate business.

The compressor works in coding tree units up to 64x64 pixels. H.264 works in 16x16 macroblocks. Larger blocks mean fewer decisions per frame. H.265 also uses 35 intra prediction modes; H.264 uses 9.

Every codec removes redundancy between frames. H.265 and H.264 both use three frame types. I-frames store a complete picture. P-frames store only the changes from the previous frame. B-frames store changes from past and future frames. A group of pictures (GOP) starts with an I-frame and runs until the next one. A longer GOP means fewer I-frames and a lower bitrate. It also means slower seek times during playback.

The practical result is the same picture at roughly half the bitrate. H.265 supports resolutions up to 8192x4320 (8K). H.264 tops out at 4096x2304. The Main10 profile adds 10-bit color, which reduces banding in dark scenes and helps full-color night vision footage.

H.265 matters most where data is expensive. That means long retention sites, cellular cameras, solar-powered units, and WiFi fleets. It matters less on a small job with a 2MP camera and a 30-day disk. The savings scale with resolution, camera count, and retention. A single 2MP camera saves a little. A 32-camera warehouse saves terabytes.

On a spec sheet, the same standard shows up as "hevc" or "h265 codec" depending on the vendor. Distributors see both labels daily. The spelling changes nothing about the stream.

What Is H.264?

H.264 (AVC, MPEG-4 Part 10) arrived in 2003 and became the default video codec for CCTV, web video, and broadcast.

It encodes with 16x16 macroblocks and 9 intra prediction modes. It tops out at 4K resolution and 8-bit color depth.

Inside the standard there are profiles. Main Profile covers 8-bit video at common resolutions. High Profile adds higher bitrates for full HD and 4K. Baseline Profile is the light version used by video calls. Security cameras almost always use Main or High Profile. The profile matters less than the codec generation, but it belongs on the spec sheet for completeness.

Its strength is universality. Nearly every recorder, phone, browser, and viewer built in the last twenty years plays H.264. That is why legacy fleets keep running it.

The cost is bytes per minute of footage. A 4MP H.264 stream typically runs 4-6 Mbps, which means heavier storage and bandwidth than H.265 at the same quality.

For new installations H.264 is the baseline, not the goal. It still makes sense for tiny jobs, ultra-old recorders, or fleets that must stay interoperable with everything.

H.265 vs H.264: How the Codecs Compare

The "h265 vs h264" search is the real codec decision on a camera quote. The table below summarizes how the two standards differ.

← swipe to scroll →

H.265 wins on bytes per minute. H.264 wins on universality. The same 4MP camera at 15 fps typically records 18-25 GB per day on H.264 and 9-13 GB per day on H.265.

Distributors who search "h264 vs h265 cctv" are usually comparing recorders, not cameras. The answer they need is the same: choose H.265 for new fleets, keep H.264 where the recorder cannot decode it.

For B2B buyers the codec belongs in the spec sheet. A typical project line reads: 4MP, H.265 Main Profile, 2-4 Mbps, 30 days retention. That one line lets every integrator price the same system.

Pick H.265 when the fleet is new, the retention is long, or the uplink is limited. Pick H.264 when the recorder is old, the project is tiny, or every client must play the footage on ancient hardware. Most 2026 projects land in the first group. The decision rule takes one sentence: if the recorder can decode H.265, buy H.265.

Bitrate Comparison: Real Stream Numbers

Bitrate is the number of bits the camera sends per second, and it drives both storage and bandwidth. The table lists typical peak bitrates for busy scenes at constant bitrate.

← swipe to scroll →

Two rules make these numbers useful. First, treat bitrate as a range, not a fixed value. Second, remember that peak figures describe busy scenes. A camera watching an empty corridor records far less data per day than the same camera on a busy street.

Daily averages run lower than peak bitrates suggest. Real scenes mix idle periods with motion, and scene-aware encoding drops the bitrate when nothing moves. That is why a 4MP camera at 15 fps typically lands near 18-25 GB per day on H.264. On H.265 the same camera records 9-13 GB, and 6-10 GB with H.265+.

Bitrate control explains part of the gap between paper and practice. Cameras typically offer two modes. Constant bitrate (CBR) holds the stream steady, whatever the scene shows. Variable bitrate (VBR) spends bits only where they are needed. VBR is why a quiet corridor records far less data than a busy street. For new fleets, run VBR with a sensible maximum bitrate. That combination captures the H.265 savings without starving a busy scene of quality.

Storage Math: How Much Disk H.265 Saves

Storage is where the codec decision becomes money. The rough conversion is that 1 Mbps of continuous recording equals about 10.8 GB per day. The table applies typical daily averages to real fleet sizes.

← swipe to scroll →

Over a year, one 4MP camera drops from roughly 6.5-9 TB on H.264 to 3-5 TB on H.265. Multiply by the camera count and the retention period, and the disk bill roughly halves. Add H.265+ and it drops to about a third of the H.264 figure.

Two rules keep the estimate honest. Always add 20% headroom for firmware updates and motion spikes. And size the recorder from the H.265+ figures, not the H.264 figures that older calculators still quote. Our NVR buyer guide covers recorder sizing in more depth.

Walk one example through the math. A site runs sixteen 4MP cameras at 15 fps with 30 days of retention. Each camera averages 10 GB per day on H.265. Sixteen cameras produce 160 GB per day. Thirty days multiply to 4.8 TB. Add 20% headroom and the recorder needs about 5.8 TB, so a 6 TB drive fits. The same site on H.264 averages 20 GB per camera per day. That comes to 9.6 TB before headroom, and a 12 TB recorder after.

Recording mode changes the daily figure too. Continuous recording stores everything, day and night. Motion-triggered recording stores only events, with a few seconds of pre-buffer. A camera on motion trigger can use 30-50% less disk than the same camera on continuous. The trade-off is risk: a camera that misses its trigger misses the event. Most business sites run continuous recording with H.265+ to keep both safety and savings.

H.265+ and Smart Encoding

H.265+ is the marketing name for scene-aware smart encoding on top of H.265. It analyzes the image and drops the bitrate when the scene is static, then restores full quality when motion appears.

Smart encoding works because most security scenes are static most of the time. A loading bay at night holds still for hours. The encoder detects the change and holds the bitrate low until something moves. When motion appears, it raises the bitrate within a frame or two. The recorder stores the higher-quality frames for that moment. Playback still shows the full timeline. The savings come from the quiet hours, not the event.

In practice the savings are real. An empty corridor at night records at a fraction of the bitrate of a busy loading bay. Typical H.265+ savings land at 30-60% beyond H.265 itself.

The catch is compatibility. Smart modes are vendor-specific, so the camera and the recorder must come from the same brand line. Mixing brands usually falls back to plain H.265.

H.265+ also has limits. For license plate capture or other scenes that need every frame at full quality, run plain H.265 instead of the smart mode. The two settings coexist per camera in most firmware.

Every FULLCOLORCAM IP camera supports H.265 and H.265+ recording with matching recorders.

Bandwidth and Network Planning

Bandwidth is the second bill the codec controls. Sixteen 4MP cameras on H.264 at 4-6 Mbps need 64-96 Mbps of sustained throughput. The same fleet on H.265 needs 32-64 Mbps.

On a local network the difference rarely matters. A 1 Gbps switch handles either. It matters on the uplink, on WiFi, and on cellular.

A typical access point comfortably carries 4-8 cameras at 2-4 Mbps each. Doubling the bitrate with H.264 means half the cameras per AP, or a denser AP plan.

Cellular sites feel the savings most. A 2MP 4G camera on H.265 typically uses 10-20 GB per day. The same camera on H.264 needs roughly double. Solar budgets and data plans both shrink.

Plan the network from the H.265 figures and keep the sub-stream on H.264 for old viewers.

Recording and remote viewing compete for the same pipe. The main stream records at full resolution. The sub-stream serves live view on phones. A 4MP H.265 camera sends 2-4 Mbps on the main stream and about 0.5 Mbps on the sub-stream. Remote viewing works best when the viewer pulls the sub-stream, not the main. That habit alone cuts mobile data use sharply.

Compatibility: What Actually Plays H.265

H.265 changes the whole playback chain, not just the camera. The camera must encode it, the recorder must decode and store it, and the app or browser must decode it again for viewing.

Cameras from roughly 2018 onward usually encode H.265. Recorders are the bottleneck: an H.264-only DVR or NVR cannot decode H.265 streams, no matter how new the cameras are.

On the viewer side, modern browsers decode HEVC in hardware on most devices, and P2P apps handle it automatically. Old clients and cheap third-party players may not.

Firmware updates change the answer over time. Some older recorders gained H.265 decode through a firmware release. Others never will, because the chip lacks the decoder. Check the vendor's support page for the model and the exact firmware number. A recorder that cannot decode H.265 is a hardware limit, not a settings problem. Factor that limit into the upgrade plan before you buy cameras.

For mixed fleets, check whether the NVR assigns codec per channel. Many do, so H.265 cameras and H.264 cameras can share one recorder. If the recorder is locked to one codec, run the new cameras on H.264 until the recorder is replaced.

Our NVRs and DVRs list codec support per model. The HEVC vs H.265 explainer covers the naming question in depth.

Upgrading Your System: Devices and Fleet Decisions

Upgrade decisions depend on which generation your fleet is. The table maps the typical components and what each codec generation means for them.

← swipe to scroll →

A practical migration path has five steps. Audit the current recorders and their decode support. Choose new cameras with H.265 encoding. Set the new cameras to H.265 with a dual-stream fallback. Replace recorders that cannot decode H.265. Then switch the streams and verify playback on every client.

If the recorders are already H.265-ready, buy H.265 cameras immediately and the storage math improves from day one. If the recorders are old, replace the recorder first, then roll out H.265 cameras. Mixing an old recorder with H.265 cameras forces the cameras down to H.264 and cancels the savings.

The cost case is simple to state. H.265 cameras cost about the same as H.264 cameras at the same resolution. The savings live in the recorder and the network. A 16-camera site that drops from 12 TB to 6 TB of disk saves on drives, bays, and power. The same site halves its uplink load for remote viewing. Over a five-year fleet life, the codec choice is worth more than the camera price difference.

Resolution and codec interact, so pair this decision with our megapixel IP camera guide.

Buying Checklist: Specifying H.265 Systems

When a buyer asks which codec to choose, walk through this checklist in order. Every item maps to a line you can demand from a supplier.

• 1. State the codec per camera. Write H.265 (HEVC) on the spec, not a vague "H.264/H.265" label.
• 2. Confirm the recorder decodes it. Ask for per-channel codec support and the firmware version.
• 3. Ask for typical bitrate. A supplier should state Mbps per resolution, not just "smart codec".
• 4. Size storage from the H.265+ figures. Use 6-10 GB per 4MP day and add 20% headroom.
• 5. Match H.265+ brands. Smart mode needs camera and recorder from the same line.
• 6. Check the viewer chain. Confirm the app and browser versions decode HEVC.
• 7. Plan the uplink. Budget 32-64 Mbps for sixteen 4MP H.265 cameras.
• 8. Keep a dual-stream fallback. Main stream H.265, sub-stream H.264 for legacy clients.
• 9. Demand a spec-matched quote. Include codec, bitrate, retention days, and headroom.

Two phrases belong on every order. Ask for "H.265 Main Profile" or "H.265 Main10" in writing, and ask how the recorder handles H.265+ streams from another brand. A written answer protects the handover. Integrators who skip these two lines discover the mismatch after installation, when cameras fall back to H.264 silently and the storage math changes. The checklist above exists to prevent exactly that.

A supplier that cannot state the codec, the typical bitrate, and the retention math is selling boxes, not a system.

H.265 vs H.264 Questions Buyers Ask

The Bottom Line

The codec decision is a storage and bandwidth decision. H.265 delivers the same footage at roughly half the bytes, and H.265+ trims it further. Specify H.265 for every new camera and match the recorder's decode support. Size storage from the H.265+ figures and keep a dual-stream fallback for legacy clients.

At FULLCOLORCAM we build 4MP and 5MP full-color night vision IP cameras with 1/1.8-inch sensors and F1.0 lenses. They record in H.265 and H.265+ and pair with H.265-ready NVRs. Every unit is tested before shipping, ONVIF-conformant, and available with free P2P remote access. Send your camera count and retention days to cj226144@gmail.com for a spec-matched quote. We will tell you the codec, bitrate, and disk size your site actually needs.