Sunday evening, the footage is forty minutes long, and the timeline has been open since lunch. The video has been four minutes from finished for two hours. None of that is a hardware problem. Five habits decide how long an edit takes.
Proxies decide whether you watch the footage or wait for it. The rough pass decides how much polish gets thrown away. Cut density decides the first thirty seconds of retention. Audio decides whether anyone sits through the rest.
Knowing when to stop decides whether the video ships this week. The software barely registers.
If your edits take far longer than your filming, that is normal. The most common complaint from new creators is that editing is more exhausting than filming. The reason they give is that it takes triple the filming time or more. This guide says which of those hours to remove first.
Editing costs three times what filming does, and the tracked numbers say where it goes
Editing time runs from import to upload. It is not only the minutes you spend cutting. Most of it is decisions and waiting, and the two tracked cases below show the shape.
Aim for 1.5 hours per hour of footage. That is lower than most people's number. One creator felt small channels spend far too long editing. The reply puts a typical niche at 1.5 hours to edit an hour of footage completely, cutting, audio and special edits included. If an hour of footage is taking you six, the bottleneck is process.
Two real cases show the range. A creator who tracked a month needed almost 6 hours to take a 4-minute video from raw footage to upload. The recording took at most ninety minutes. Another who listed the stages needs around 6 to 8 hours to edit an hour of raw footage down to a 10 to 20 minute video. Case A spends ninety minutes per finished minute, case B about thirty.
The slow stage is usually not cutting. Time your own stages once, because the slow one is never the one you expect. The creator behind the best-known tracked month found the edit bogged down by what the post calls micro-decision fatigue. That is the small choices, not the big creative ones, made again in every video. Decide the repeatable things once, as presets and a fixed order, so the edit only asks the questions that matter.
Proxies come before the first cut, because stutter is where the rewatching starts
Proxies are small copies of your clips. They are easy to play, and you edit with them in place of the originals. The export still uses the full quality files. The point is not render speed. It is judging every cut on smooth playback the first time.
Turn proxies on for every project. Someone who asked for proxies explained in plain words was told they are low resolution copies of the clips that are easier to edit. A Premiere user who finally tried them had the same reaction as every thread. Everything got faster, and why did nobody say so earlier. Use them on every project, not only the ones that lag.
Making the copies takes time. That step is called a transcode, and the threads disagree on how long it takes because it depends on the footage. One Premiere editor finds most projects finish making proxies overnight. Someone choking on 170 GB of 4K60 reports five to six hours, because the system struggles with 4K.
Never sit in front of the progress bar. Both waits are fine, because neither is your time. Queue the proxies before bed and do something else. One thread on a faster proxy workflow is entirely about breaking the habit of watching it.
The first pass is ugly on purpose
A rough pass answers one question. It is the clips you keep, their order and rough timing, with no audio work, graphics, colour or transitions. Its only job is to say whether the video works. Polish is a second pass, and it only touches what survived the first.
Do not perfect clips one by one. The top answer in the editing 101 thread opens with “Start rough, finish refined” and names the beginner mistake, perfecting each clip before moving on. A reply to someone who hates editing says the same in fewer words, finish a rough cut first and polish afterwards. Ban yourself from the effects panel until the cut plays through once without you wanting to move a section.
Overwhelmed means one question per clip. One reply to a creator drowning in footage reduces the first viewing to a single question, keep or delete. No trimming and no arranging yet. Watch everything once, mark keep or delete, then start ordering.
Batch the passes, not the videos. A creator who says the editing process makes or breaks a channel rough-cuts every video first, then does the audio on all of them, then the graphics. We cut around 5,000 videos a year, and this is the part that separates a four hour edit from a nine hour one. It is not speed at the keyboard. It is not having to redo work that was never going to survive.
Cut density buys the first thirty seconds, and rhythm buys the rest
Cut density is how often the screen changes. It is the editing choice that shows most directly in the retention curve, the graph of who is still watching. It matters in one place far more than everywhere else.
Cut tightest in the first thirty seconds. The thirty second mark is where the curve is read, and the retention section of our analytics guide covers how. A partnered creator answering whether cuts every few seconds are best practice says the first 30 seconds need to be sharply edited. The pressure eases after that. Spend your tightest cutting on the opening and stop trying to make minute seven as dense as minute one.
Read your curve against two numbers. A retention thread puts the target at around 80% still watching after the first 30 seconds and 40% or more making it to the end. Those are the pair of numbers to read your own curve against. Check both after every upload.
The forums split on the rest. Past the opening, they disagree in a useful way. One camp keeps a two second rule, with something on screen changing every two to three seconds. The other finds that pace jarring.
Cut the gaps, not the breaths. The thread arguing that jump cuts help retention lands on the answer, that what most likely helps is losing the long silent segments. We take that side, because it explains both camps. The dense cut works when it removes dead air and jars when it removes speech. After the first upload, let the curve choose the next cut rather than your taste.
Audio goes first: clean it, level it, then cut to it
Clean the voice before you cut. Audio first means the voice track is cleaned and levelled before you arrange pictures. The cut is made to the speech, rather than the speech trimmed to fit the cut. Levels are checked on the worst speaker you own.
The ear leads, so audio goes first. One editor asked whether to record the voice over before or after the cut works in sync with the audio, so it always comes first. A podcast editor's order of work puts light noise cleanup and levelling up top, before any trimming. The biggest speed tip one editor has is to add the music as early as possible. Clean the voice and set the music under it before you cut.
The levels have numbers. One creator who asked how to balance voice, sound effects and music settled on voice around -6 dB, sound effects around -12 dB and background music around -20 dB. The mix in our music guide sits lower, with speech near -6dB and music near -30dB.
Check the music on a phone, not headphones. A creator asked why viewers hear the music as too loud when it was lowered on purpose in the edit. That complaint follows a headphone mix. Across roughly 5,000 videos a year, music level is the note we give more than any other on audio. It is almost always four or five decibels too present, so set it and then play the opening on your phone.
The tool YouTubers use in 2026 is whichever one they already know
Pick by the footage you shot. What YouTubers edit with has a stable answer. It is Premiere Pro, DaVinci Resolve or Final Cut for long videos, and CapCut for phone footage and Shorts.
Every survey thread splits by footage. In one thread asking which editor most YouTubers use, most cut long videos in Premiere, Final Cut or Resolve and use CapCut on mobile. One creator explaining their go-to software keeps both, Premiere for long videos and CapCut for Shorts. Pick by what you shot, and stop reading comparison articles.
Long videos in CapCut get people hurt. A creator warning others off it reports “My 20 minute video got deleted after 8 hours of work”, which is eight hours nobody gets back. The beginner threads settle it the same way, CapCut as the quick option for starting today and Resolve as what you learn to keep going. If a video will pass ten minutes, cut it in Resolve, which is free, and keep CapCut for vertical.
The 2026 threads split on Premiere. One editor finds Premiere Pro 26 faster and less laggy. Another blames the added AI features for the bloat. We cut around 5,000 videos a year across all of these, and the software is close to irrelevant to how good the result is.
Learn the shortcuts and stop switching. Tool choice decides how fast you work, not where the cut goes, and the cut is what viewers notice. Learning the shortcuts of the one you have is the step partnered creators credit with halving their editing time. Do that, then stop switching.
The 3:2:1 rule is about backups, and the 80/20 rule is about when to stop
Neither phrase is an editing technique. Both sit in the question box under a search for video editing tips. One protects the footage. The other says when a video is finished.
3:2:1 is a backup rule. Every thread using it in an editing context means backups, with one definition. A thread on how to back up footage gives it in six words, “3 copies. 2 formats. 1 off-site”, and the working editors' version specifies two different types of storage.
Nobody has a 3:2:1 rule for the cut. No thread defines one for the cut itself, so any video promising one has invented it. Back the footage up before the first cut.
Creators point 80/20 three ways. The 80/20 rule is the Pareto principle, the idea that a small share of the work gives most of the result. A post on how to 80/20 your editing defines it as 20 percent of your activities producing 80 percent of your results.
- Pointed at the edit, one creator's warning is that the editor will spend 80% more time to make the video possibly 20% better.
- Pointed at the timeline, a reply on how to edit faster says to get the clips 80% complete very quickly and save the details for the last 20%.
- Pointed at the software, a Premiere thread names shortcuts and three point editing, which is placing a clip by marking its in and out points first.
Adopt the first meaning. Beyond those three, the term has no fixed meaning. When the next hour buys a few percent, export.
AI editing tools in 2026 remove the boring cuts, not the decisions
AI does the boring work, not the choosing. The tools that save real time in 2026 all do the same kind of work. That is silence removal, filler word removal, rough cuts made from the transcript, captions and noise cleanup. None chooses a take.
Transcript editing changes the hours. It means cutting the video by deleting words in the text of what was said. A podcaster comparing Descript with Premiere for text-based editing found it cut the editing time in half. That is the rough pass from earlier, done in text. Use the transcript for pass one and the timeline for pass two.
Let a tool take the silence pass. Silence and filler removal is solved and mostly free. Auto-Editor cuts the silence, and one-click filler removal saves hours on a video with hundreds of cuts. Then walk the timeline once by ear, because the tool cuts where the sound level drops and not where the breath is.
Clipping tools get a colder reception. These chop a long video into short clips. A podcaster who tested a pile of them concludes that the time they save is not worth the expense.
The last 20% is still yours. On replacement, the 2026 threads agree. A career thread credits AI with simple cuts, subtitles and colour work, and stops there. A thread about Claude editing video puts it as AI doing the first 80% of an edit, or anything else, in 1% of the time. The last 20% is yours, and that 20% is what this article is about.
Stop editing yourself when the honest hours do not fit the week
Editing hours cap your upload rate. Ideas do not. Stop editing yourself at the point where the honest hours per video, times the uploads you want, exceed the hours you have.
The cap is a schedule nobody chose. A partnered creator's biggest bottleneck is upload frequency, at 3 to 6 weeks of editing per video. A creator worried about burnout sinks 20 to 25 hours into each one. The editor of a biking channel puts in about 15 hours a week to keep it fed. Run your numbers through the figure above.
On hiring, the forums disagree. The cautious camp says not to hire until the money comes back within a few days of the video going live. One reply to a creator asking whether to hire is a flat “Absolutely not. Just take longer”, which is the whole cautious case in five words. The other camp, in the thread on when to get an editor, says creators hire when editing slows their growth, whatever the subscriber count.
Right about money, wrong about time. Our side is that the cautious camp is right about money and wrong about time. Taking longer is not fine if the channel is meant to become the job. The channels that get there are the ones that kept publishing at a rate they could hold. If the honest hours do not fit, hand off the cut or shrink the format.
What you see, what it means, what to do next
| What you see | What it means | What to do next |
|---|---|---|
| Editing takes three or more times as long as filming | Normal. The hours are in decisions and rewatching, not in cutting | Time one edit by stage. Compare against 1.5 hours per hour of footage. |
| Playback stutters when you scrub | You are judging cuts on choppy video and rewatching to be sure | Make proxies before the first cut. Start the transcode and walk away. |
| A caption or transition you spent twenty minutes on gets cut | Polish went in before the structure was settled | Rough pass first: selects, order, timing. No polish until it plays through. |
| Retention under 80% at thirty seconds | The opening is not cut tightly enough | Cut the silence and every restart in the first thirty seconds. Then leave the rest alone. |
| Viewers say the music is too loud and it sounded fine to you | Headphones hid it | Voice near -6dB, music at -20dB or lower, then listen on a phone speaker. |
| CapCut crashes or loses a long project | The tool is built for Shorts, not twenty minute timelines | Move long videos to Resolve. Keep CapCut for vertical. |
| Someone tells you to follow the 3:2:1 rule | It is a backup rule: three copies, two media, one off site | Do it for the footage. It has nothing to do with the cut. |
| An AI clipping tool is on your shortlist | It will find candidates, not decide the edit | Use tools for silence, filler and captions. Keep the judgement calls. |
| The honest hours per video do not fit the week | Upload rate is capped by the edit, not by ideas | Hand the cut to someone else or shrink the format. Nothing else moves the number. |
Things to stop doing
- Buying hardware before turning on proxies. The same habits on a faster machine reach the same rewatching sooner.
- Adding captions, colour or transitions before the cut plays through once. That is the work most likely to be deleted.
- Judging the music level on headphones. Every too-loud complaint in the threads sounded fine at the desk.
- Working past the point where the next hour makes the video a few percent better. Export instead.
A four hour edit, in order
- The night before: queue proxies and back the cards up, three copies, two media, one off site.
- 0:00 to 0:30: watch every clip once and mark keep or delete. No trimming.
- 0:30 to 1:45: rough pass. Order the keeps, remove silence and restarts, watch it through.
- 1:45 to 2:15: audio. Noise cleanup, voice near -6dB, music at -20dB or lower.
- 2:15 to 3:15: polish. Captions, graphics and colour, only on the sections that survived.
- 3:15 to 4:00: export, then play the first thirty seconds on a phone speaker and fix what you hear.
- Change one thing in the next edit. One, so the retention curve can tell you whether it worked.
Change one thing per edit. The last rule is what makes the routine compound. Change the opening, the music level and the cut rate in the same video and the curve teaches you nothing. Three things moved, so it cannot say which one worked.
The short version
- Benchmark: about 1.5 hours of editing per hour of footage. Six or more means the process is wrong.
- Proxies before the first cut, every project, transcoded while you are away from the desk.
- Pass one is keep or delete, order and rough timing. Pass two is everything else.
- Cut tight for thirty seconds, aiming for 80% still watching there and 40% at the end. Then cut silence, not breaths.
- Voice first, near -6dB; music at -20dB to -30dB; checked on a phone.
- CapCut for phone footage and Shorts, Resolve or Premiere past ten minutes. Stop switching.
- 3:2:1 is a backup rule. 80/20 means export when the next hour buys a few percent.
- Give AI the silence, filler and captions. Keep the takes, the cut points and the order.
- When hours per video times uploads exceeds the hours you have, hand off the cut or shrink the format.
Read next
- How to Read YouTube Analytics, for the retention curve that tells you which of these cuts worked.
- How to Make an Effective Intro, for the thirty seconds the cut density section is about.
- Music for Video, for the licence question and the full mix levels behind the audio section.
Knowing where the hours go is quick. Removing them means changing the order you work in, and for most creators the honest number is still more hours than the week has. Our first video is free up to four editing hours.
Last reviewed 10 September 2026. The hours, the levels and the tool choices are from threads posted in 2025 and 2026.
First video free · up to 4 editing hours
Knowing where the hours go is quick.
15-min call. First cut in 2 days. No card needed.