Three things people need from a video file they already have: the pictures out of it, the sound out of it, or a short animation they can paste somewhere. These tools do those three, in your browser, and each one prints the numbers that show it did the job properly — how many frames came out, how many bytes of audio were copied, which settings were tried and rejected.
Which one to use
| You want to… | Tool |
|---|---|
| Save every frame of a clip as PNG, JPG or WebP | Video to Frames |
| Take one picture every second, or every tenth frame | Video to Frames |
| Keep the soundtrack and throw the picture away | Extract Audio from Video |
| Get uncompressed audio to edit or transcribe | Extract Audio from Video — WAV |
| Turn a few seconds of video into an animated GIF | Video to GIF |
| Make a GIF small enough for a 10 MB upload limit | Video to GIF — Fit a size limit |
| Shrink a GIF you already have | Compress GIF |
Frames are decoded, not screenshotted
Nearly every online video tool works by loading your file into a hidden player, jumping the playhead to a timestamp and copying whatever is on screen. It is easy to build and it is not accurate: seeking is not frame exact, so two requests a fraction of a second apart can hand back the same picture while the frames between them are never seen. You get a folder of images with duplicates in it and nothing says so.
These tools read the container instead and pass each stored frame to the decoder once, in order. That is why Video to Frames can show three numbers after every run — frames coded, frames decoded, frames written. When the first two match, nothing was repeated and nothing was missed. It is the same decoding path that feeds Video to GIF, which is why the frame rate you ask for is the frame rate you get.
Audio is copied, not converted
The sound inside a video is already a finished, lossy stream. A converter decodes it and compresses it again into MP3, and that second pass has no idea what the first pass already threw away, so it throws away more. Extract Audio lifts the frames straight out of the container and adds only the seven-byte header each one needs to stand alone. The page prints the audio bytes, the framing bytes and the frame count, so the claim is arithmetic rather than a promise.
A GIF that fits, instead of a GIF you guess at
Almost nobody wants a particular frame rate. They want something that will go through Discord, a forum or an email, and that number is a file size. Video to GIF takes the limit and works down a ladder — fewer colours first, then frame rate, then dimensions, then lossy as a last resort — and lists what it tried and rejected on the way. Expect GIFs to be large: the format stores whole pictures at 256 colours, so five seconds that are 500 KB as an MP4 can be 8 MB as a GIF. If your limit is being enforced by a server, it is worth knowing that a 500 KB limit is not always 500,000 bytes.
What is not here yet
There is no trimming, compressing, muting or format conversion on this page. All four write a new video file back out, which needs machinery these tools do not carry yet, and shipping a half-working version would be worse than saying so. MP4, M4V and MOV are read properly; WebM and MKV fall back to a slower playback route, and the pages say when that happens and how many frames the browser dropped, rather than quietly handing you an incomplete sequence.
Nothing is uploaded — the video is read on your machine and never sent anywhere. That is common in this category now rather than unusual, so it is not the reason to use these tools. The reason is that every claim on the three pages comes with the number that backs it.