H.264 and HEVC Playback Problems: Hardware Decoding

Footage straight from a mirrorless camera, a phone or a drone is usually H.264 or HEVC (also called H.265). It looks small on disk and plays well in a media player, but in an editor it can stutter, lag when you scrub, or fall behind when you stack layers. The cause is how the video is compressed, and how much of the decoding your computer can hand to dedicated hardware. This article explains both and gives a safe order of fixes.

Version note: the steps follow Adobe's Premiere Pro help for the 26.x releases (Adobe's pages list 26.5, from September 2026, as the newest at the time of writing). The DaVinci Resolve points come from third-party guides and Blackmagic forum users, because we could not find the exact option described in Blackmagic's public documentation. Hardware support changes with every GPU generation and driver, so check the model and driver you have.

The quickest first thing to try

In Premiere Pro, open the Media preferences (Edit, Preferences, Media on Windows, or Premiere Pro, Settings, Media on a Mac) and check the option called Enable hardware accelerated decoding (requires restart). Adobe's reference lists it as enabled by default, and says to restart Premiere after changing it. If it was off, turn it on and test the same clip again. If it was on and the clip still struggles, use the steps below. Do not assume that this one box decides the outcome.

Why H.264 and HEVC are hard to edit

Camera codecs are designed to keep file sizes small while recording. They use inter-frame (long-GOP) compression, which means most frames are stored as changes from nearby frames, not as complete pictures. To show a single frame the editor may need to decode several others first. That is why playing forward is easier than scrubbing or reversing, and why stacking several clips multiplies the work. Edit-friendly formats such as ProRes and DNxHR store every frame on its own, which is easier to decode and produces much larger files.

What hardware decoding does

Hardware decoding moves some of that work to dedicated circuits in a graphics card, an Intel processor with Quick Sync, or an Apple silicon chip, instead of running everything on the general-purpose processor cores. It helps only when the circuit supports the exact flavor of video you have. The flavor depends on four things: the codec, the bit depth (8-bit or 10-bit), the chroma subsampling (4:2:0 or 4:2:2) and the resolution. Adobe's documentation says:

• Apple silicon (M1 Pro, M1 Max, M1 Ultra or newer) supports hardware-accelerated encoding and decoding for H.264 and H.265, including 10-bit 4:2:2 decoding.
• On Intel systems, a CPU with Intel Quick Sync support is required for hardware-accelerated decoding. Adobe says HEVC 4:2:2 10-bit decoding is supported on Intel platforms from version 22.0, with driver requirements for some generations, and that integrated graphics on systems with 8 GB of memory or less can be limited.
• Adobe's release notes for 26.0 describe rewritten H.264 support, and the 26.5 notes add hardware 4:2:2 10-bit decoding for AVC and HEVC in MXF on NVIDIA Blackwell GPUs.

Support for other combinations varies by GPU generation and driver. Adobe community threads include reports of high-resolution 4:2:2 HEVC files falling back to software decoding on some systems. Those are user reports and not Adobe statements, so use them as a reason to test your own footage.

Step by step: fix H.264 and HEVC playback

1. 1Find out what the footage really is. Look at the clip's properties or a media-info tool for codec, bit depth, chroma subsampling, frame rate and whether the frame rate is variable. A 10-bit 4:2:2 file is a heavier case than 8-bit 4:2:0.
2. 2Run the local copy test: play the clip from the computer's internal SSD. If it stutters there too, the cause is decoding and not storage. Our stutter guide explains the full method.
3. 3Update the editing software, the GPU driver and the operating system. Adobe's known-issues page, for example, lists a fixed bug where MKV files recorded with OBS could drop frames on a Mac, fixed in 26.5. Old builds carry old bugs.
4. 4Check the hardware decoding option in Preferences, Media, and restart Premiere after any change.
5. 5Test the effect. Play or export the same short clip with the option on and then off, and compare the time or the smoothness. On Windows, the Performance tab of Task Manager can show activity on the GPU video decode engine for many graphics cards. If nothing changes, the footage may be falling back to software decoding.
6. 6Try lower playback resolution and turn off High Quality Playback in the Program Monitor settings. This reduces load while you cut.
7. 7Use proxies for the edit. This is the dependable fix for heavy long-GOP footage. See our proxy workflow guide.
8. 8If proxies are not enough, transcode to an edit-friendly codec such as ProRes or DNxHR, with a plan for storage. These files are much larger than the camera originals.
9. 9In DaVinci Resolve, third-party guides place a setting called Decode H.264/H.265 using hardware acceleration under Preferences, Decode Options, with a choice of GPU vendor. Reports differ about the free edition and the Studio edition, and Blackmagic forum users note that some 10-bit 4:2:2 H.264 files lacked hardware decoding on certain GPUs, so check Blackmagic's current documentation for your version.

What usually causes it

• Footage the hardware decoder does not support, so it runs on the CPU.
• A mismatch between the hardware, driver and software versions.
• Variable frame rate files from phones and screen recorders.
• High-bitrate 10-bit files from newer cameras.
• Many layers, effects or multicam angles, all decoding at once.

What not to do

• Do not turn hardware decoding off permanently without testing. For supported footage it usually helps, and the results are easy to check.
• Do not transcode a whole shoot to ProRes before you know you have the storage for it.
• Do not buy a new graphics card on a guess. First confirm that the card's decoder supports your footage format.
• Do not edit from the original camera cards. Copy and verify them first. See our DIT workflow guide.

When it is time to call someone

Ask for help when a team shoots on mixed cameras and each editor gets different results, when you are about to buy workstations for a camera format you have not tested, or when proxies and hardware decoding still cannot deliver a usable timeline. Our guide to video editing workstations covers the hardware side, and a test of your own footage on the candidate machine is worth more than any spec sheet.

Want a person to look at it?

This is the kind of problem our production consulting team handles: matching workstations, GPU, storage and ingest settings to the camera formats you actually shoot. See our editorial suite setup service, or tell us what is happening in your edit bay and a real person on our team will reply.