01
Which should short video use?
H.264 for anything being delivered. It is accepted essentially everywhere with no negotiation. H.265 halves the size at similar quality, and it is refused or handled awkwardly by enough tools and older devices that the saving rarely pays for the trouble on a short clip.
02
The trade in practice
The saving is real and the compatibility cost is what stopped it replacing H.264 for delivery.
| Aspect | H.264 | H.265 |
|---|---|---|
| File size at similar quality | Larger | About half |
| Accepted everywhere | Yes | Not reliably |
| Older devices | Fine | Often not |
| Good as a camera source | Yes | Yes |
| Good as a deliverable | Yes | Only where you control the destination |
03
Where H.265 makes sense
Recording and storing large originals is where H.265 shines. A long 4K recording takes much less space on a phone or a drive, which matters when storage is tight. Many phones record in it by default for exactly that reason.
The trade-off is that editing and converting may be slower on older computers, because decoding H.265 takes more processing power.
04
Checking what your phone records
Most phones have a setting labelled something like high efficiency or most compatible. High efficiency usually means H.265; most compatible usually means H.264. If you run into problems importing or sharing files, switching this setting is often the fix.
If you keep high efficiency on for storage reasons, convert a copy before sending files to others.
It is also worth knowing what your editing software prefers. Some editors handle H.265 smoothly on modern machines but stutter on older laptops, and a proxy or a converted copy can make editing far more pleasant. The format you record in and the format you edit in do not have to be the same, as long as the final delivery file is the widely accepted one.
05
Converting without losing quality
Converting between the two formats always involves re-encoding, which can reduce quality slightly. Use a generous setting when converting a master file, and do it once rather than repeatedly. Every extra conversion adds a little loss.
For finished clips, export directly in H.264 rather than exporting in one format and converting afterwards.
Keep the original recording alongside any converted copy, so a better conversion is always possible later.
06
Keeping it simple
For most creators, a simple rule avoids all the trouble: record in whatever your device does best, and deliver finished clips in H.264. That combination works with every platform, every messaging app and every client's laptop.
Revisit the choice every couple of years, as support for newer formats keeps improving.
07
Deliver in the one nothing refuses
- Record in whichever your device prefers. Phones often default to the newer one, and that is fine as a source.
- Export deliverables as H.264. It is the one nothing argues with.
- Only reach for H.265 to solve a size problem. That is the single case where it earns its complications.
Send whatever your camera produced and see what comes back.
Questions people ask
- Is H.265 better quality?
- At the same file size, yes. At the same quality it makes a smaller file. The picture itself is not inherently better.
- Why do some tools refuse it?
- Support is less universal and in places is tied to hardware and licensing. That is why it never became the default for delivery the way H.264 did.
- Does my phone record in H.265?
- Many do by default, usually under a setting about space saving. Recordings from them work fine as source material.
- Will it make my clips smaller?
- Clip size comes from how the clip is produced rather than from what you sent in, so the source format does not carry through in that way.
- Should I convert before uploading?
- Only if you hit a size limit. Otherwise an extra export costs quality for nothing.