Capturing Video Frames and Making a GIF in Your Browser

Pulling stills out of a video, and turning a short clip into a GIF, are two different jobs that people expect to behave alike. They don't. Video Frame Capture grabs individual frames at full resolution; Video to GIF re-encodes a window of time into an animation. Both run entirely in the browser, with no server-side transcoding.

What frame capture is doing

The tool plays the video into an off-screen canvas and copies the pixels out — the same mechanism as taking a screenshot of a playing video, but driven by the decoder rather than your monitor.

Two consequences follow from that:

The image is the video's own resolution, not the player's. A 1080p source gives you a 1080p PNG, even if the preview window on the page is small. You cannot capture more detail than the file contains, and there is no upscaling step pretending otherwise.

What you get is the frame the decoder produced at that timestamp. For most MP4 and WebM files that matches what you see. For variable-frame-rate footage — screen recordings and phone video especially — a frame grabbed at a precise time can be a hair earlier or later than the one you were looking at. If you need a specific moment, nudge the playhead and take two or three shots; it costs seconds and is cheaper than guessing.

Output is PNG or JPEG, chosen with a radio control, PNG by default. JPEG is written at a fixed quality of 0.92 — good, and not adjustable. For anything with text, motion blur or sharp edges, stay on PNG; the file is larger but nothing is added by the encoder's block decisions.

Single captures download with the timestamp in the name — a wall-clock stamp plus the frame position, in the form capture_20260929_114207_00-12-34.png — which keeps a set of stills in order without you renaming anything.

Batch capture

Set an interval and the tool steps the playhead forward, capturing at each stop. The field is labelled 0.5 to 60 seconds, but only the lower bound is enforced — a manually typed 120 is accepted and used as-is, so an interval longer than the clip yields one frame and a stop, not an error.

Think in terms of frame count rather than "more is safer". A 90-second clip at 0.5 s intervals is 180 captures, each a full-resolution PNG; that is hundreds of megabytes of canvas work and a ZIP you will have to sift through. Start at 2 s, skim the gallery, then re-run a tighter interval on the region you actually care about.

One behaviour to watch: the batch loop waits for the seek to complete, with a timeout as a backup. On a slow or heavily-keyed file, both can fire, so near-duplicate frames occasionally land in the gallery. Skim before exporting — sorting duplicates out afterwards is worse.

Captures accumulate in a gallery on the page. Download All packages them into a screenshots folder inside a ZIP named with the date and time, something like screenshots_2026-09-29-11-42-07.zip. That ZIP step uses a script loaded from a CDN, so the bulk download needs a connection even though nothing about your video leaves the machine.

One video per page load

The upload zone disappears the moment a file loads and never comes back. To work on a second clip, reload the page. That is also the fix when a file fails to open: the page has no decode-error reporting, so an unsupported container simply does nothing — the video element stays blank and no message appears. If a file refuses to load, suspect the codec (HEVC/H.265 in an MP4 is the usual culprit on non-Apple browsers) rather than the tool.

Video to GIF: the fixed choices

The GIF converter takes a start time, a duration and a width, and animates that window.

The hard boundaries:

• Duration is capped at 30 seconds. Over that, you get an explicit refusal before any work starts. The default is 3 seconds.
• Frame rate is fixed at 10 fps and there is no control for it. Every GIF from this tool is 10 frames per second. That is a deliberate trade: GIFs store each frame as a full image, and 10 fps keeps a few seconds of motion at a size people can actually send. It also means fast motion looks strobed, and slow, subtle motion can look slightly jerky.
• Width is yours, from 80 to 1920 px, defaulting to 320. Height follows the source's aspect ratio.
• The encoder runs with two workers and a quality value of 10, both fixed in code and neither exposed as a control.

Two practical quirks:

The progress bar moves twice. One bar is shared by the two phases — first "Generating GIF (n/total)", then "Encoding GIF…". The fill resets when encoding starts, so the percentage goes backwards mid-run. That is cosmetic; the job is not restarting.

The output name never changes. Whatever you feed in, you get video-to-gif.gif, so rename it yourself if you are making several. The finished GIF lives only in page memory until you download it — refreshing the tab loses it. On browsers that block programmatic saves, the page offers two fallbacks: right-click the preview and save it, or copy the base64 data out of the shown textarea.

Why your GIF is 12 MB and what to cut first

GIF is a 256-colour, uncompressed-adjacent format. It has no motion compensation, so every frame costs a picture. Size is roughly width × height × frames × colour complexity, which tells you the order of operations:

1. Shorten first. Duration is the cheapest win — 3 seconds instead of 8 removes more than half the file with no visible loss in most reaction clips.
2. Narrow second. 320–480 px is the sweet spot for chat and social embeds. Halving the width removes far more bytes than any quality tweak.
3. Trim the motion. A section with a lot of change per frame costs more than a mostly-still one. Pick the smallest window that reads.

Raising width to 1920 is technically allowed and rarely wise; expect a file too large to send anywhere.

If the silent, looping format is not the point, a WebM or MP4 clip is smaller and better — but that is an encoding job this pair of tools does not do. For stills from the same video, use frame capture instead: one PNG beats five frames of the same paused scene.

Privacy

Both pages read the file locally, decode it in the tab and hand you a blob to download. No upload, no queue, no server copy — which is also why these tools inherit your browser's codec support rather than the site's. Analytics and advertising scripts load like anywhere else on the site. The one external dependency to name honestly: the frame ZIP and the GIF encoder both come from CDNs, so those pages need network access to complete the final step.

Related guides

• How to convert audio files in your browser — pulling the soundtrack out of the same video file
• How to stitch screenshots into one long image — joining captured frames side by side
• How to compress an image without making it worse — when a full-resolution PNG is too heavy to send