Video to GIF

A GIF is what you reach for when a video player would be too much: a three second loop in a bug report, a hover animation on a product page, a clip in a chat that plays without anyone pressing anything. I built this because the usual route is uploading your footage to a stranger's server, waiting in a queue, and getting back a file with a logo in the corner. Here you load a video file, choose where the clip starts, how long it runs, how wide the output should be and how many frames per second it uses, and the GIF is encoded on your own machine.

The preview shows the frame range you have selected so you can nudge the start time until the loop begins where you want it, and an estimated size updates as you change the settings, which saves the tedious cycle of exporting something enormous and starting over. Nothing is uploaded, so unreleased product footage, screen recordings full of customer data and family videos all stay on your device. For still images rather than motion, a modern format is a better bet, and the image to WebP converter handles that side of things.

How to use

1. Drop your video file onto the box, or press the button and choose one from your device.
2. Scrub to the moment you want and set the start time.
3. Set the duration. Ten seconds is the maximum, and shorter almost always looks better.
4. Choose the width. Smaller widths make dramatically smaller files, since every frame shrinks.
5. Pick a frame rate. Around 10 to 15 frames per second is smooth enough for most clips.
6. Watch the preview of the selected range and check the estimated size before committing.
7. Export, wait while your browser encodes the frames, then download the finished GIF.

Why use our video to gif?

Doing the encoding locally is the whole point, and it comes with an honest cost. Your browser is doing work a server farm would normally do, so a long clip at a large width and a high frame rate is slow and hungry for memory. That is exactly why the duration is capped at ten seconds. The cap is not a paywall waiting to be lifted, it is the line past which a browser tab starts struggling. Short clips encode quickly, and short clips make better GIFs anyway.

The second honest thing concerns the format itself. GIF dates from 1987 and carries a hard limit of 256 colors per frame, which is why sunsets, skin tones, gradients and shadows come out banded and blotchy. Flat graphics, screen recordings, terminal output and cartoons survive it beautifully because they were never using many colors to begin with. If what you want is video quality for sharing, an actual video file will be smaller and look better every time. GIF wins when you need silent, looping, autoplaying motion that works anywhere with no player attached.

Three settings control everything. Width is the biggest lever, because halving it removes roughly three quarters of the pixels in every frame. Frame rate is second: dropping from 30 to 12 frames per second more than halves the frame count and most viewers will not notice on a short loop. Duration is third and the most brutal, since every extra second is another stack of full frames. If you need the height that goes with a chosen width, the aspect ratio calculator does the arithmetic.

The part I got wrong first was defaulting to 24 frames per second because that number sounded cinematic. It made every export enormous for no visible gain, and it made the encoder crawl. Dropping the default to a sane low rate made the tool feel twice as fast and the files three times smaller, and I could not see a difference in any test clip. Smooth is worth less than small in a format like this.

Nothing is uploaded and there is no watermark, a combination rarer than it should be among GIF makers. It matters most for the commonest source material of all: screen recordings. A recording of your own app, dashboard or inbox is full of details you would never knowingly hand to a free website in exchange for a conversion.

Who is this tool for?

Software teams live on this. A GIF of a bug reproducing, attached to the ticket, ends more back and forth than any written description. Product documentation uses short loops to show a feature being used, and release notes with a two second clip get read where a paragraph gets skipped. For static screens the image compressor keeps the file sizes down instead.

Marketing and social teams pull the best three seconds out of a longer video and use it as a hook, since a looping clip plays automatically in places a video will not. Email is the classic case: many email clients happily animate a GIF and refuse to play video at all.

Sellers and creators use it for product motion. A ring rotating, a fabric moving, a tool being opened. Short loops make an object feel real in a way a still photograph cannot, and they load fast enough to sit on a listing page. Personal clips are the rest of it: a reaction from a family video, a pet doing something ridiculous, two seconds of a wedding. Exactly the files nobody should be uploading to a random converter.

Frequently asked questions