Step through any YouTube video one frame at a time. Use the buttons, or the same , and . keys YouTube uses. Then save the frame you land on, without the paused controls in shot.
or
Free · no sign-up · nothing recorded. Frames are drawn straight to a canvas in this tab.
Drag a box around just the video picture
Shared source preview. Click Capture frame to save the current frame.
F freeze / resume · Space freeze while the preview is focused
YouTube has frame stepping built in. It is genuinely good, and most people never find it. But it has three hard edges.
| Key | What it does |
|---|---|
| , | Back one frame, paused only |
| . | Forward one frame, paused only |
| K / Space | Pause without summoning the control bar |
| < > | Slow down to 0.5× and 0.25× |
| J / L | Jump ten seconds back or forward |
On a phone there are no shortcuts at all. Dropping to 0.25× and tapping pause is the usual workaround, and it is never exact. The buttons here are taps.
Stepping needs the video paused, and a paused player draws its controls over the picture. The shortcuts get you there; they cannot get you out with the image.
The player shows seconds. If you are logging a moment, citing a frame or comparing two takes, you want milliseconds and a frame count. Both are under the player here.
A web page cannot press YouTube's keys for you. The player runs in a cross-origin iframe, and synthetic keystrokes do not cross an origin boundary. That is a security boundary, not an oversight.
What is available is YouTube's own IFrame Player API, which accepts a seek to a precise time. So a frame step here is a seek of exactly one frame's worth of time. That was worth checking rather than assuming: five consecutive 30fps steps each moved 0.0333s, landing exactly where asked, with no accumulated drift.
The API reports current time and duration, but there is no field anywhere for frames per second. YouTube does not tell us. So a step has to be expressed as a fraction of a second, and something has to choose the fraction.
The default is 30. If a step lands on the same picture twice, the real rate is lower. Try 24 or 25. If it appears to skip, the rate is higher. Try 60. Most YouTube uploads are 24, 30 or 60, and the picker sits next to the timecode so you can correct it in one click.
This is where the built-in shortcuts stop being enough. Pausing is exactly what pins the play button, progress bar and title over the picture, so a screenshot of a paused player always contains them.
Capture this player crops the recording to the video element alone, so no browser or page furniture can appear. Freeze then holds your chosen frame still while playback continues underneath. The controls never fade in, because as far as YouTube is concerned nothing was paused. Full detail on that is on the screenshot tool.
Stepping works anywhere. Saving uses the Screen Capture API, which is desktop only. On a phone, step here and use your device's own screenshot, or open the file in the video frame extractor if you have it.
On YouTube itself: pause the video, then press . to move forward one frame and , to move back one. They only work while paused, and the player must have keyboard focus. Click the video once first.
Paste a link above and you get the same thing as buttons, plus a running timecode, a frame counter and a way to save the frame you stop on.
Nearly always one of three things. The video is still playing. The frame keys do nothing until you pause. Something else has keyboard focus, usually the comments or the search box; click once on the video itself. You are on a phone. The mobile apps and mobile web have no keyboard shortcuts at all. That is the one case YouTube cannot serve. The buttons on this page are ordinary taps, so they work there.
You cannot do it in the YouTube app. There is no keyboard, and no frame-step gesture. The usual workaround is dropping the speed to 0.25× and tapping pause at the right moment, which gets you close but not exact. Use the step buttons above instead; they are taps rather than keystrokes, so they work on a phone.
It cannot. The player lives in a cross-origin iframe, and synthetic keystrokes do not cross an origin boundary. Instead this drives the player through YouTube's own IFrame Player API, seeking by exactly one frame's worth of time per step. In testing, five consecutive 30fps steps each moved precisely 0.0333 seconds with no drift.
Because YouTube does not publish it. The API reports the current time and duration but has no field for frames per second, so a step has to be expressed as a fraction of a second and something has to decide the fraction. 30fps is the default; if a step lands on the same picture twice, or skips one, switch to 24, 25 or 60 and it will line up. Most YouTube uploads are 24, 30 or 60.
Yes, and this is the part YouTube's own shortcuts cannot do. There is a catch worth knowing: stepping requires a paused player, and a paused player draws its play button, progress bar and title over the picture. An ordinary screenshot catches all of it. Capture this player crops the recording to the video alone, and Freeze holds your frame still while playback continues underneath, so no controls are ever drawn. Saving needs a desktop browser; stepping does not.
Neither. There is no account, no export cap and no watermark, and nothing is uploaded. The video streams from YouTube to your browser as normal. Any frame you save is drawn locally.