The short answer
H.264 and H.265 are two video compression standards. H.265, also called HEVC, is the newer one and typically needs about half the data of H.264 to deliver similar visual quality. For a dash cam this means one of two things: the same card holds roughly twice as much footage, or the recorder keeps the file size the same and spends the savings on more detail. The cost is heavier processing during recording, a little more heat, and a compatibility question when customers open the files on older computers or software. For a buyer, the codec is best treated as a planning variable: it sizes the card, the loop length and the playback instructions that ship with every unit. For 4K models H.265 is the common default; for 1080P entry models H.264 remains widespread because it is universally playable.
How the two codecs compare
| Item | H.264 | H.265 (HEVC) |
|---|---|---|
| Storage at similar quality | Baseline | About half |
| Processing load in the recorder | Lower | Higher |
| Playback compatibility | Very broad | Broad, but older software may need support |
| Typical use in dash cams | 1080P entry models, some 1440P | 4K and higher-bitrate modes |
| Heat effect | Lower | Slightly higher on weaker chipsets |
| App and cloud streaming | Easy to decode on phones | Fine on newer phones; check the app |
The roughly-half figure is general codec knowledge and varies with the content and the encoder. Treat it as an expectation rather than a fixed ratio, and confirm it with sample files recorded on the actual unit.
Notice what the table does not say: that either codec changes the lens or the sensor. Compression happens after capture, so a codec decision cannot rescue a weak image, but it can waste a strong one if the bitrate is set carelessly.
What it means for storage
Dash cams record constantly, so storage efficiency affects the experience directly. A longer loop means more days of footage before overwriting, which matters for parking mode and for fleet managers who download only when an incident is reported. It also reduces write volume on the card, which eases the constant rewriting that wears cards out and quietly extends service intervals for the card you bundle. Efficient codecs do not replace good cards: loop recording still needs high-endurance microSD in capacities such as 64GB or 128GB, as covered in why loop recording needs them and the SD card line. For an estimate of card size by use, see how much storage a dash cam needs.
Fleets feel the difference in workflow. A longer loop before overwrite means a manager who hears about an incident on Thursday can still pull Monday's drive, and fewer forced downloads mean less driver time spent on maintenance. For programs that upload over 4G, smaller files at similar quality also cut monthly data use, which is a recurring cost rather than a one-off.
Quality is a bitrate decision too
Choosing H.265 does not, by itself, deliver better video. If a recorder uses the codec but sets a low bitrate, it banks the savings as a smaller file and the picture may be no better than a generous H.264 setting. The reverse also holds. This is why the spec sheet should list the codec together with the default bitrate and the resolution it applies to. The interaction with motion blur and plate readability is covered in frame rate and bitrate. When comparing two models, record the same scene and compare both file size and zoomed detail. When comparing quotes, ask both suppliers for the average file size per hour in the default mode: two numbers are easier to compare than two adjectives, and the difference between them is the storage your customers will buy or the loops they will shorten.
Compatibility and customer support
Where H.265 causes trouble, it is usually on the customer's computer. Older media players or some in-built operating system players may not open HEVC files without an add-on. Phone apps normally handle it, but older phones may struggle with smooth playback at 4K. For a business selling at scale, a few steps reduce the support burden:
- Include a plain instruction card or app note on how to play H.265 clips.
- Offer a codec or quality setting in the menu where the platform supports it, and set a sensible default.
- Test the supplied app and desktop viewer with the real footage before the first shipment, on the oldest phone your customer base plausibly uses rather than the newest device in the office.
- For insurance or fleet programs, confirm that the receiving system accepts the format before standardizing on it.
A short note in the box, in plain language, resolves most playback questions before they become messages to support. Customized apps and viewers are part of firmware and app customization programs, and the player question belongs in the specification.
Chipset support and heat
Whether H.265 is available depends on the chipset. Public spec sheets show 4K-class platforms such as the Novatek NT96670 handling high-resolution encoding, while very simple designs stay with H.264. Encoding HEVC takes more compute, and combined with a screen, WiFi and a hot cabin it can raise the temperature. If your market is warm, request footage from a long continuous run and check for slowdowns or shutdowns. The margin matters more in hot climates, where the processor already works against cabin heat; a conservative default mode that the user can raise is often kinder than an aggressive default that stalls in July. The platform side is explained in chipsets explained, and the power buffer choice adds its own heat tolerance.
Which codec for which line, and how to specify it
- 1080P entry range: H.264 keeps compatibility simple and the processor cool.
- 1440P mid range: either; choose according to the supported players and card sizes you bundle.
- 4K lines: H.265 is normally the sensible default, with the bitrate confirmed in writing.
- Fleet and cloud programs: follow the receiving platform's decoder support, and check mobile data use if footage is uploaded over 4G.
State the codec, the resolution and frame rate it applies to, and the default bitrate. Add a line that the supplier will confirm the average file size per hour of footage from a production sample, so you can publish accurate storage claims. The 4K single-channel line shows models where this applies. Whatever the default, freeze it in the written specification and verify it on a production sample, because firmware revisions sometimes change encoding defaults quietly. Roadtrace confirms codec and bitrate settings with partner factories in writing for each program; send your requirements through the quote form.