Preparing a downloaded clip for an editing timeline
H.264 video in an MP4 is the friendliest thing you can drop onto a timeline. Premiere, DaVinci Resolve and iMovie all import it without a transcode and scrub it smoothly, which is why this tool prefers it wherever the platform offers it. The files that cause trouble are the ones carrying VP9 or AV1, and the trouble is usually not a refusal to import but a timeline that stutters and a playhead that will not move cleanly. Frame rate and frame shape matter too, and they matter before you start cutting rather than after.
Why H.264 is the format that just works
It is the codec every editor has supported for the longest, and the one that almost every machine can decode in hardware. Hardware decoding is the part that matters on a timeline, because an editor is not playing a file once from start to finish, it is jumping around inside it constantly and decoding whatever frame the playhead lands on.
That is a much harder job than playback, and it is why a file that plays perfectly in a media player can still feel sluggish in an editor. When decoding is handled by a dedicated part of the processor, scrubbing stays responsive. When it falls back to software, everything slows down at once.
This tool prefers H.264 and only falls back to another codec when nothing else exists at the resolution you picked. That is a deliberate choice in favour of the thing you are most likely to do with the file. The distinction between the MP4 wrapper and the codec inside it, which is where most confusion about formats comes from, is drawn properly in the format guide rather than repeated here.
Two MP4 files can behave completely differently on the same timeline. The container is identical, the codec inside it is not.
Why a VP9 or AV1 file stutters
Because older machines decode them in software, and an editor asks for far more decoding than a player does. VP9 is common on YouTube above 1080p and AV1 is the newest and most efficient of the three, but efficiency at storage time is paid for at decode time, and an older processor without hardware support for either has to do all that work itself.
The symptoms are recognisable once you know what causes them. The clip imports, the thumbnail appears, and then playback drops frames, scrubbing lags behind the mouse, and the whole project feels heavier than the length of the footage justifies. Older versions of Premiere, DaVinci Resolve and iMovie also have genuinely weak support for these codecs, so the file may not import at all rather than importing badly.
None of that is a fault in the download. It is a mismatch between what the file needs and what the machine can give it, which is exactly why picking H.264 at download time is worth more than any amount of fixing afterwards.
| Codec | On a modern machine | On an older machine |
|---|---|---|
| H.264 (AVC) | Smooth, hardware decoded everywhere | Still smooth, this is the safe choice |
| VP9 | Usually fine | Software decoding, sluggish scrubbing, weak support in older editors |
| AV1 | Fine where hardware support exists | The worst case, decoding can stutter badly |
Frame rate belongs to the timeline, not to the clip
Set the project frame rate to match your footage, or accept that the editor will convert it. A 60fps clip on a 30fps timeline has to lose half its frames, and a 30fps clip on a 60fps timeline has to invent or repeat frames, and both operations show up as judder in motion.
The cleanest workflow is to check the frame rate of the downloaded file first and build the project around it. When everything on the timeline shares a frame rate, nothing is being converted and motion stays exactly as it was shot.
Mixing rates is sometimes unavoidable, and it is survivable. The thing to avoid is doing it accidentally, discovering the judder at the end, and having to rebuild. A 60fps source also carries twice as many pictures per second as a 30fps one, which is one of the reasons file sizes move the way they do, as the file size guide explains.
- Match the timeline to the footage when the footage all shares one frame rate.
- Decide deliberately when it does not, rather than letting the editor decide for you.
- Expect judder whenever a conversion happens, and check a motion heavy section before committing.
Resolution and frame shape on the timeline
Pick the resolution you are going to finish at, not the largest one available. A 2160p clip on a 1080p timeline is scaled down on every frame, which is work your machine does continuously for a result you could have had by downloading 1080p in the first place.
There is one good reason to take a larger file anyway: reframing. If you intend to punch in, crop or stabilise, extra pixels give you room to do it without softening the result. That is a deliberate choice with a known cost, which is a very different thing from taking 4K because it was the top button.
Frame shape is the other decision, and it is where vertical footage catches people out. A Reel or a Short is vertical, usually 9 by 16, and dropping one onto a horizontal timeline leaves pillarboxing that becomes part of the exported picture. Decide the orientation of the project before you import, not after. Vertical downloads here keep their shape rather than being padded or cropped, so what arrives is what was published.
Check the file before you build on it
Play the first few seconds with the sound up before you cut anything. Two minutes of checking prevents the worst version of this problem, which is discovering at export that the source was silent all along.
A downloaded video that plays with no sound almost always means the audio stream was never fetched, since YouTube stores video and audio separately above 360p. The silent download guide explains that and the other cause, which is a platform side mute after a copyright claim. Files from here are merged with ffmpeg before they reach you, so both tracks are present, and the merge copies rather than re-encodes so the picture is untouched. The general question of whether any of this costs quality is answered in the guide on downloading and quality.
Once the file checks out, move it out of the Downloads folder and into the project. Editors dislike source files that wander, and the Downloads folder is a place both operating systems treat as disposable, which the desktop guide covers.
- Play the downloaded file through, with sound, before importing it.
- Check its frame rate and resolution, then set the project to match what you intend to finish at.
- Move the file into the project folder rather than editing from Downloads.
- Import a short section first and scrub it, so any decoding problem shows up before you have built anything.
Frequently asked questions
What is the best format for editing downloaded video?
MP4 with H.264 video. Premiere, DaVinci Resolve and iMovie all import it without a transcode, and almost every machine decodes it in hardware.
Why does my downloaded clip stutter in my editor?
Usually because it carries VP9 or AV1 and your machine is decoding it in software. An editor decodes far more aggressively than a player, so the difference shows up there first.
Should I download 4K for a 1080p project?
Only if you plan to crop, punch in or stabilise. Otherwise the editor scales every frame down for a result you could have had by downloading 1080p.
Does the frame rate of the download matter?
Yes. A frame rate that does not match the timeline has to be converted, and conversions show up as judder in motion. Match the project to the footage where you can.
Will a vertical clip be letterboxed?
Not by the download. The vertical shape is preserved as published, so what happens to it depends entirely on the orientation of the timeline you drop it onto.
My clip has no audio on the timeline. What went wrong?
The audio stream was probably never fetched, since YouTube stores video and audio separately above 360p. Files from here are merged before download, so both tracks are present.