Why h.264 Sucks for Editing
45sExplains a common frustration for creators in a relatable, punchy way.
▶ Play ClipThe video explains why h.264 is a poor editing codec due to its heavy compression and reliance on previous frames, and introduces DNxHD as a superior alternative for smoother editing. The creator shares personal experience and practical advice on using editing codecs.
h.264 is heavily compressed, designed for viewing, not editing. It becomes choppy with many cuts, color grades, and effects.
Codec stands for encode/decode, a compression algorithm. Without compression, files would be too large (e.g., 21.6 GB per minute for 1080p60).
h.264 uses inter-frame compression, requiring previous frames to decode current frames. This causes performance issues with complex edits.
NVIDIA GPUs have NVENC for h.264 acceleration, but free DaVinci Resolve lacks it. Premiere Pro has it but is paid. Hardware acceleration still struggles with large projects.
Proxies re-render footage at lower resolution/bitrate but are still h.264. The creator dislikes proxies and recommends editing codecs like DNxHD.
DNxHD stores each frame independently (intra-frame), making editing smooth. No hardware acceleration, but time cost is offset by better performance.
DNxHD uses ~3 GB per minute (180 GB/hour). For dual-camera setups, double that. Recommended to use a fast SSD (e.g., 1 TB M.2).
Using an editing codec like DNxHD significantly improves editing performance and project stability, despite higher storage and time costs. For those unable to use it, h.264 proxies are a fallback.
"Title is slightly exaggerated but accurately reflects the transformative impact of switching to editing codecs."
What does 'codec' stand for?
Encode and decode.
0:35
Why is h.264 hard to edit?
It uses inter-frame compression, requiring previous frames to decode the current frame.
1:43
What is the storage cost of DNxHD per minute?
About 3 GB per minute.
5:10
What is the required read/write speed for editing 1080p video?
About 400 MB/s.
5:46
Which free video editor does NOT have hardware acceleration for h.264?
DaVinci Resolve (free version).
3:04
h.264 is not an editing codec
Fundamental insight that many creators overlook, causing editing performance issues.
Inter-frame compression explained
Clear explanation of why h.264 struggles with complex edits.
1:43DNxHD intra-frame benefits
Key technique for smooth editing: each frame stored independently.
4:04Storage cost trade-off
Practical consideration for adopting editing codecs.
5:10[00:00] I dropped h.264 Like a Rock now I edit
[00:03] with fire codex sexy kodaks and okay
[00:08] maybe that maybe I got carried away
[00:09] since forever creators have been wanting
[00:12] to take an SD card out of their camera
[00:13] put it in their computer and immediately
[00:16] start editing while it is the dream
[00:18] h.264 is heavily compressed it's meant
[00:21] to be a viewing codec not an editing
[00:24] codec so it might start out fine but
[00:25] once you have a hundred Cuts color
[00:27] grades Graphics animations things start
[00:31] to get choppy and hard to edit so let's
[00:33] see alternative first let me explain
[00:35] what a codec actually is the word Kodak
[00:37] is an amalgamation of encode and decode
[00:40] it's simply a compression algorithm
[00:43] applied to a file then whatever you're
[00:45] viewing the video on or editing knows
[00:47] what the compression algorithm is and
[00:49] uncompresses it in order to present it
[00:51] to the viewer without compression files
[00:53] would be unwieldy they'd be too large to
[00:55] be distributed on the internet on media
[00:57] like this here's some quick math as to
[00:59] why each pixel stores color in three
[01:02] bytes a 1920x1080 screen is 2 million
[01:06] seventy three thousand six hundred
[01:08] pixels with three bytes per pixel that's
[01:11] six million two hundred and twenty
[01:13] thousand eight hundred bytes that's
[01:15] 0.006 gigabytes for a single frame that
[01:18] doesn't sound too bad now multiply that
[01:20] by 60 frames per second now multiply
[01:23] that by 60 seconds in a minute and
[01:25] you're sitting at 21.6 gigabytes per
[01:29] minute not so great anymore a lot of
[01:31] cameras including the one I'm using
[01:32] right now will record by default into
[01:34] h.264 some may come with other options
[01:37] but mine doesn't even recording software
[01:40] like OBS will by default record to h.264
[01:43] h264 is great for viewing media it's a
[01:46] strong compression that also gives you a
[01:47] pretty decent looking image but that
[01:49] strong compression is exactly what makes
[01:51] it hard to edit for every frame that's
[01:53] pulled up the computer has to decode
[01:55] that compression to show you the frame
[01:56] but because of the way h.264 works it
[01:59] also needs pre previous frames in order
[02:01] to build the current frame because every
[02:03] frame doesn't store every single Pixel
[02:06] especially if there's no changes that's
[02:08] why if you're ever watching a football
[02:09] game and you see confetti rapidly fall
[02:11] everywhere the image stability just
[02:13] falls apart so why the hate for h.264 if
[02:16] you have a relatively decent computer
[02:18] h.264 probably won't give you any
[02:21] trouble but given enough effects and
[02:24] cuts h.264 will start to become a little
[02:27] bit on the sluggish side now I have
[02:29] watched someone take h.265 footage from
[02:31] a Sony a7s3 which is very hard footage
[02:34] to edit and throw it into an M1 Max
[02:36] MacBook Pro that was also a five
[02:38] thousand dollar computer and most of you
[02:41] are Gamers so you're probably not
[02:42] editing on Macs anyway today we're going
[02:44] to talk about PCS Nvidia gpus do come
[02:47] with a built-in h264 encoder decoder
[02:50] called in bank this is what is known as
[02:52] Hardware acceleration the GPU basically
[02:55] has a bunch of parts inside that make it
[02:57] easy to work with this kind of footage
[02:58] when you get a big enough project still
[03:00] find hardware acceleration still kind of
[03:02] struggles a bit if you're using the free
[03:04] version of DaVinci Resolve you do not
[03:06] get access to Hardware acceleration now
[03:09] I do think the studio version is money
[03:11] well spent but I also understand that
[03:14] that is 300 and it is a lot of money if
[03:17] you're using Premiere Pro you do have
[03:18] access to Hardware acceleration but
[03:20] Premiere Pro is not free so for the most
[03:23] part unless you're willing to pay some
[03:25] money you're not getting access to
[03:26] Hardware acceleration anyway we also all
[03:29] know about the memes regarding Premiere
[03:30] Pro and how it crashes all the time but
[03:32] I will say once you start using an
[03:34] actual editing codec I find that it
[03:36] doesn't really crash at all what are
[03:38] editing codecs proxies work by
[03:39] re-rendering the footage that you have
[03:41] at a smaller resolution and a lower bit
[03:43] rate
[03:44] typically becomes significantly easier
[03:46] to edit with then you just have to
[03:48] remember to turn on the proxies while
[03:49] you're editing and to turn them off
[03:51] while you're exporting otherwise your
[03:53] export looks like garbage I personally
[03:55] do not like proxies I find they're kind
[03:57] of a two-step forward one step back kind
[04:00] of deal there's still h.264 it's still
[04:02] not an editing codec so let's talk about
[04:04] dnxhd dnxhd was developed by Avid it's
[04:09] meant to be an editing and a
[04:10] presentation codec while I'll be calling
[04:12] this dnxhd keep in mind that that covers
[04:14] resolutions up to 1080 and then after
[04:16] that the codec uses dnxhr dnxhd is easy
[04:20] for a computer to edit because each
[04:23] individual frame is stored with all of
[04:25] its data intact with no need to
[04:27] reference previous frames this means the
[04:29] computer just grabs reads the frame and
[04:31] displays it and you're done there is a
[04:33] storage and a Time cost to using the NX
[04:36] HD and those costs are broken down like
[04:38] this the time cost is this there's no
[04:40] Hardware acceleration for dnxhd if you
[04:43] watch my video on how record videos like
[04:45] Markiplier you're going to have a double
[04:47] wide video that you're going to split
[04:48] into two parts if you're going to be
[04:50] rendering anyway you may as well try
[04:51] rendering out to dnxhd unless you're
[04:54] trying to turn around some super fast
[04:55] project on a tight deadline you probably
[04:57] have time to spare I highly recommend
[05:00] setting a project up to do some prep
[05:02] work let it render go get a snack take a
[05:05] nap get some water come here
[05:08] self-care take care of yourself because
[05:10] each individual frame is stored there is
[05:13] a storage cost to this as well you're
[05:15] looking at around three gigabytes per
[05:16] minute and so for an hour of footage
[05:18] you're looking at around 180 gigabytes
[05:21] if you're a gamer doing the double wide
[05:24] method that I just mentioned if you've
[05:25] got two files so we're doubling up so
[05:27] you're at about 360 gigs for an hour
[05:29] this is where I suggest if you're an
[05:31] Editor to invests in an editing Drive I
[05:33] personally have an additional M2 one
[05:35] terabyte SSD in my PC that I use just
[05:39] for storing projects that I'm currently
[05:40] working on that's a little Overkill
[05:42] because that reads and rides at about
[05:44] 3000 megabytes per second according to
[05:46] an article by Larry Jordan you only need
[05:48] about 400 megabytes of read and write
[05:50] speed in order to successfully edit a
[05:52] 1080p project and I have a link to that
[05:54] article down below if you want to read
[05:56] more secondly I'm a big fan of Samsung
[05:58] t7 ssds but they're also a little bit on
[06:00] the pricier and Overkill side based on
[06:03] the comments I have read on my other
[06:04] videos a lot of people here use the free
[06:07] version of DaVinci so Hardware
[06:09] acceleration is for the most part out if
[06:12] you can spare the storage space and the
[06:14] time I highly recommend giving dnxhd a
[06:17] try on a big project at least once you
[06:20] will be surprised at just how much
[06:22] better your project is maintained and
[06:25] performs when using a proper editing
[06:27] codec if you can't swing those then h264
[06:30] proxies are probably your next bet I
[06:32] just don't I just personally don't like
[06:34] them now that you're smart on codex
[06:35] you're going to go over here and watch
[06:36] this video on how to make cool vertical
[06:38] videos so you can get lots of views on
[06:40] Tech talk and have a good one foreign
⚡ Saved you time reading this? Transcribe any YouTube video for free — no signup needed.