How to go frame by frame on YouTube

Two keys most people never find, the three reasons they stop working, and what to do on a phone where they do not exist at all.

The short answer

Pause the video, then press . to go forward one frame and , to go back one. They are built into YouTube's desktop web player and they are exact. The player knows the video's frame rate, so each press moves one real frame rather than an approximation of one.

The keys sit on the same physical buttons as < and >, which is why the shortcut is sometimes written that way. You do not hold Shift.

The last row catches people out. Arrow keys step frames in QuickTime and in most editors, so the hands reach for them by habit. In YouTube they are a five-second jump.

Why frame by frame is not working

The keys either work perfectly or appear to do nothing at all, and there are only three reasons for the second case.

1. The video is still playing. By far the most common. Frame stepping is only defined while paused; press K first. If you are unsure, look for the play triangle rather than the pause bars.
2. Something else has keyboard focus. If you have clicked into the search box, a comment, or the description, your keystrokes go there. A comma typed into a comment box is genuinely invisible if the box is scrolled out of view. Click once on the video picture itself to hand focus back to the player.
3. You are on a phone or tablet. There are no keyboard shortcuts in the mobile apps or on mobile web, so there is nothing to press. See below.

A fourth, rarer case: some browser extensions bind , and . globally and swallow them before YouTube sees them. If the keys work in a private window but not a normal one, that is your answer.

On a phone, the shortcuts do not exist

This is the one situation YouTube simply does not serve. The Android and iOS apps have no frame-step gesture, and mobile web has no keyboard to shortcut from. The two workarounds people reach for both have real limits:

• Drop the speed to 0.25× and tap pause. Available in the app's settings menu. It gets you close, because at quarter speed you have four times as long to react. But you are still stopping wherever your thumb happens to land, and normal reaction-time variation still spans several frames.
• Scrub with your finger. The progress bar maps the entire video onto a few hundred pixels. On a ten-minute video that is roughly sixty frames per pixel of thumb movement, so it is useless for anything precise.

The way round it is a player that exposes stepping as buttons rather than keystrokes, since a tap works anywhere. The frame-by-frame player does exactly that. Paste a link and you get forward and back frame buttons, a timecode and a frame counter, on a phone as readily as on a desktop.

How long is one frame?

Longer than you would think, and not the same in every video. A "frame" is one over the frame rate, and YouTube carries at least five common rates:

A 24 fps frame lasts two and a half times as long as a 60 fps one. That matters the moment anything other than YouTube's own player is doing the stepping, because YouTube does not publish the frame rate: the IFrame Player API reports current time and duration and has no field for frames per second anywhere. A page driving the player from outside can only seek by a fraction of a second, and something has to decide the fraction.

So a frame-rate picker is not a missing feature, it is the honest interface for a number nobody can look up. The symptoms tell you which way to move it: if a step lands on the same picture twice, the real rate is lower than the setting, so try 24 or 25. If it appears to skip, the rate is higher, so try 60.

When you need true frame accuracy

Everything above is seeking a streamed video. If you are counting frames for a bug report, a sports call, a VFX reference or anything that has to be defensible, seek-based stepping on a stream is the wrong instrument. You are working from whatever quality the network gave you, against a frame rate you have inferred.

Working from the file is the difference. Open it in the video frame extractor and the browser's own decoder reports the real frame timings, so the rate is measured rather than assumed and each step moves one true frame. It is also the only route to the source's full resolution: a stream gives you what fits your connection, a file gives you every pixel that was encoded.

Download only what you have the right to: your own uploads, footage you have been given, or content whose licence permits it.

Frame keys in other players

Once the file is on your disk, most players can step through it:

VLC's missing backward step is the one that catches people mid-task: overshoot and you have to jump back a few seconds and walk forward again. Everything else here steps both ways.

Keeping the frame you landed on

Finding the frame and keeping it are separate problems, and the second one is where this usually falls apart. Stepping requires a paused player, and a paused player draws its play button, progress bar and title straight over the picture, so the screenshot you take at the end has all of it baked in.

The way out is to stop pausing: hold the frame still while playback continues underneath, so the controls never fade in because nothing was ever paused. The screenshot tool does that, and the screenshot guide compares it with every other way of getting a still: system screenshots, ffmpeg, and the auto-generated thumbnails.