A dead plugin, a perfectly fine codec
FLV had a remarkable run. For roughly a decade it was the default way video moved around the web, so it piles up in old download folders, tutorial captures, screen recordings made by 2000s-era software, and archives someone squirreled away before browsers pulled the plug on Flash. The player is what died. The files are still sitting there, and plenty of them hold moments worth looping.
The part most people never learn is that FLV is only a container, a box with an outdated label on it. The video inside that box is very often plain H.264, the exact codec the modern web runs on every day. What the GIF skips Flash entirely and hands your file to the browser's built-in video decoder. No plugin, no codec pack, no ancient shareware converter. If the tab can play the clip, the converter can turn it into a GIF.
First test: does it play?
Point your browser at the converter and drag the FLV onto the drop zone, or click and pick it from disk. The file is read on your own machine and a preview appears with a timeline underneath it. Nobody asks for an email address on the way in.
One honest caveat before you plan the loop: browser support for FLV is patchy. When the preview plays, you are through the hard part and every control behaves normally. When it loads but sits black, your browser cannot decode that particular encoding. The detour takes about two minutes: open the file in VLC or another free player, save a copy as MP4, and drag that copy in instead. It is the same rescue move the AVI to GIF page recommends for other formats of that vintage.
Cut the archive down to one moment
Footage from the Flash era tends to run long, and a GIF wants one idea told in two to five seconds. Slide the timeline handles until only that idea is left; when a handle needs to move by exactly one frame, an arrow key does it, so the loop closes precisely where it should. A loop that restarts mid-motion reads as a glitch; a loop that restarts on the right frame reads as intentional.
Cutting is also the cheapest compression you will ever get. Halve the duration and you have halved the frame count, and with it most of the file, before touching a single quality control. If the moment needs more setup than five seconds can carry, make two short GIFs rather than one long one; both will load faster than the combined version ever would.
Settings that fit low-resolution-era footage
A lot of FLV was encoded at 320 by 240 or 640 by 480, small by modern standards, which means the resize control may have nothing to do here. The other dials still earn their keep:
- Crop comes only in preset ratios (1:1, 9:16, 4:5, 4:3, 16:9), and 4:3 matches most Flash-era frames without cutting anything meaningful away.
- Frame rate between 10 and 15 fps suits old footage well, and every frame you drop is bytes you never write.
- Colors: old footage rarely needs more than 64 to 128 palette entries, and a touch of dithering stops compressed gradients from splitting into stripes.
- Scale only matters if the source turns out larger than expected; downscaling then pays off fast.
The estimated result size recalculates after every adjustment, so you always know where you stand. Under 2 MB travels anywhere a chat message goes; under 5 MB sits comfortably in a document or a slide deck.
Fifteen-year-old footage deserves privacy too
Everything above happens inside the tab, on your hardware. The FLV is never transmitted, so no server ends up holding a copy of an archive you have kept safe for fifteen years. That also means there is no quota to bump into: the practical ceiling on input size is whatever RAM your machine has, not someone's pricing tier. When preview and estimate both satisfy you, convert; the GIF is written straight to your disk with nothing stamped across it. If the unbranded export is the part you care about most, the no-watermark GIF maker page covers it in detail.