You can extract frames from video on Android by opening a browser-based frame extractor on your phone, choosing a local MP4, WebM, MOV, M4V, or Ogg file, entering the time you want in seconds, and downloading the decoded frame as a full-size PNG. The whole process happens in the browser tab on your device — the video never leaves the phone, no dedicated Android app is installed, and the original clip is not re-encoded or modified. What changes is that one still image, drawn from the video at its native decoded dimensions and exported as a new PNG file that includes the selected time in its filename.
This single-still approach is the right fit when you need a thumbnail, a reference shot, a screenshot from a clip you already have, or a quick still for a slide deck and you want to keep working from your phone. The browser handles decode and seek locally using the standard HTMLMediaElement seeking behavior, then captures the current frame through a Canvas drawImage call and encodes it as PNG in the same tab, so the workflow stays self-contained on Android.
Why a browser-based frame extractor fits Android
Most Android video tools that grab a frame either require installing a separate app from the Play Store or upload the file to a remote server, and many free apps are limited to lower-resolution outputs, watermarks, or batch grids rather than a single full-size still. A browser-based approach skips both of those problems: there is no APK to download, no permissions to grant beyond the file picker, and no upload bandwidth used, which matters on cellular connections where uploading a multi-hundred-megabyte phone recording can take a long time and burn through data.
Because the tool runs in the Android browser using the same HTMLMediaElement and Canvas APIs that desktop browsers use, the path is the same whether you reach it from Chrome on Android, Samsung Internet, or another modern mobile browser. The decoder inside the browser decides which clips can open, and that is the main place Android-specific behavior shows up — codec support on a given Android device depends on the browser version and the underlying media stack, not on the tool itself.
How to extract frames from video on Android
The full workflow on an Android phone stays in a single browser tab and takes only a few seconds per frame.
- Open the Video Frame Extractor page in your Android browser. Tap the file picker and choose one supported local video from your phone's storage — MP4, WebM, MOV, M4V, or Ogg files are the formats the browser will try to load.
- Wait for the duration and the preview to load. The page reports the video's duration once the browser has read enough metadata, and the preview becomes available once enough of the file is buffered for the timeline to display.
- Enter the frame time you want. Use a value between zero and the displayed duration, including decimals when you need sub-second precision — for example 0.5 for half a second in, or 12.75 for twelve and three-quarter seconds in.
- Tap Extract PNG frame. The browser seeks the local media element to the time you requested, draws the decoded frame onto a same-size canvas, and encodes that canvas as a PNG.
- Verify the still on screen. If it is the frame you wanted, tap the download link that appears and save the PNG to your phone's downloads folder.
- If you want a different still, change the time and run the extraction again. Each result is its own PNG file with the selected time in the filename, so earlier captures are not overwritten.
This is the same approach covered in the extract frames from a video without uploading walkthrough, with the addition that the file picker is sourcing from your Android device rather than a desktop folder.
What the tool does and what it does not change
The extractor does four things and only four things: it validates the chosen local file against the shared video safety limits, parses the time you typed, seeks the browser's media element to that point, and writes the decoded frame to a PNG. The video itself is not modified — no re-encode, no transcode, no metadata rewrite — so the original clip on your phone is unchanged after you extract a still.
The PNG it produces uses the decoded frame's native pixel dimensions and preserves transparency only if the browser's decoded video frame provides it. There is no resizing, no cropping, no sharpening, no interpolation between frames, and no filter applied. If you need any of those adjustments — for example, you want a square thumbnail for a profile picture or you need a specific pixel rectangle — pair the output with an image editor or use the Video Cropper on the source clip first and then extract from the cropped version.
The time you enter is treated as a position on the media timeline rather than a numbered source frame. According to the MDN reference for HTMLMediaElement currentTime, seeking to a fractional second lands on the nearest playable position, which on most clips is the closest decoded keyframe. That is why two extractions at times that differ by a few milliseconds can return the same image — the browser may not be able to render every microsecond of the timeline as a unique still. The Canvas drawImage call writes whatever frame the media element currently holds, with no interpolation between adjacent source frames.
Limits, codecs, and Android-specific gotchas
Android phones record clips in a handful of common containers, but each container can hold different audio and video codecs, and the browser is the only thing that decides whether the file will open. The table below summarizes the supported containers and the codec caveat.
| Container | Common Android use | Browser requirement |
|---|---|---|
| MP4 | Default camera recording on most Android phones | Browser must support the codec inside the container (commonly H.264 video and AAC audio) |
| WebM | Screen recordings and some editor exports | Browser must support VP8, VP9, or AV1 video |
| MOV | Older iOS exports and some pro camera apps | Browser must support the codec inside; MOV is a QuickTime container |
| M4V | iTunes-style videos and some Android downloads | Browser must support the audio and video codecs inside |
| Ogg | Rare on Android but still encountered | Browser must support Theora video and Vorbis audio |
A supported extension does not guarantee playback. For example, an MP4 recorded with HEVC (H.265) will open on some Android browsers and not on others, even though the file extension is the same. When the browser cannot decode the codec, the extraction reports a decode, seek, canvas, or encoding failure instead of producing an empty download, so a missing result is the signal that the file's codecs are not supported on that device.
The shared video safety policy applies on Android the same way it does on desktop: the file must be at most 500 MiB, the duration must be five minutes or less, no side of the video may exceed 4096 pixels, and the total area must stay within 3840 × 2160 pixels. Phone recordings are usually well inside those bounds, but a long 4K screen recording can hit the pixel cap quickly and will be rejected before extraction starts.
When to reach for a dedicated Android app or desktop tool
The browser tool is the right pick for one still at a known time, from a short clip, in a container the browser can decode. It is the wrong tool for jobs that the page itself lists as out of scope: frame-accurate editorial work, HDR or color-managed output, batch extraction of many stills at once, exact frame numbers instead of timeline positions, very long footage, or any format the browser cannot decode.
For batch or frame-accurate work on Android, a dedicated app such as an FFmpeg-based extractor or a pro video editor will let you target frame numbers, walk the timeline one frame at a time, or export a contact sheet. For HDR and color-managed work, you typically need a desktop tool that can read the master metadata and preserve the color pipeline rather than going through a browser decoder.
For anything else — a single still, at a known time, from a clip your phone already plays back — the in-browser path on Android is enough, and the original video never leaves your device.