Convert a screen recording to a GIF — without uploading it

Why your recording should stay with you

A screen recording can include more than the interaction you meant to show: a customer name in a sidebar, an API key in a terminal, an internal URL, or a feature that has not launched. An online upload gives another service a copy of that interface. For a five-second GIF, that is often unnecessary.

This converter reads the file on your device and creates the GIF in your browser. The video, extracted images and output stay local. There is no video-upload endpoint in this tool and no server conversion fallback. You download the conversion engine, rather than sending your recording away.

Basic categorical diagnostics help us find failures: browser family, container, codec and outcome. They contain no recording bytes, frames, file names, internal URLs or full browser identifier. The GIF tool does not use session replay. If you want to check the local conversion yourself, let the engine finish loading, disconnect, and convert a file in this tab.

Three steps, about thirty seconds to set up

Conversion time depends on your recording and device. Short clips finish fastest.

1. 

   Pick the recording.

   Drag in an MP4, MOV, WebM or M4V up to 200 MB. Your browser opens it locally; nothing is uploaded while it loads. Choose a supported recording, then select up to 60 seconds to convert.

2. 

   Set the clip and the size.

   Choose the start and end of the moment worth showing, then pick a width (640 px is the sweet spot) and a frame rate (10–12 fps). The estimated file size updates as you change them.

3. 

   Generate and download.

   The frames are encoded in your browser. When it finishes, download the GIF and drop it wherever it is going: a README, a changelog, a pull request or a support ticket.

Why your GIF is huge — and how to cut it down

GIF compresses image data, but it does not have the efficient motion compression of modern video. A useful way to think about the work is frames × pixels × color information. That is not an exact file-size formula: palettes, repeated content and compression also affect the download.

Length is the biggest lever. Thirty seconds at 15 fps means 450 frames. Ten seconds at 10 fps means 100 — 4.5 times fewer frames before you change anything else. For a menu opening or a checkout step, aim for five seconds. Keep the context in the surrounding document.

Width works in two dimensions. With the same aspect ratio, dropping from 800 px to 640 px leaves 64% of the pixels; 480 px leaves 36%. A 600–640 px GIF is usually enough inside a document. The converter offers 480, 640 and 800 px and avoids enlarging smaller originals.

Frame rate comes next. Going from 15 to 10 fps removes a third of the frames. Menus, forms and cursor movements often read well at 10–12 fps. Compared with 30 seconds at 15 fps and 800 px, ten seconds at 10 fps and 640 px involves about seven times less pixel-frame work. Actual byte savings depend on the scene.

Try fewer colors and fewer changed pixels. Start with 128 colors, then try 64 for a flat interface. Dithering can help photographs but adds noisy patterns to UI screens; this converter leaves it off. The unchanged-frame setting enables GIF transparency and offset optimizations so static areas need less repeated image data. It preserves the timing of pauses rather than cutting them out.

Finally, crop unnecessary desktop space in your recorder before importing. Cropping is not an in-page feature in this version. Use the estimate to compare settings, then check the actual output size. Aim under 3 MB for documentation or under 1 MB for chat; each destination can have its own limit.

Start with a recording you already have

A GIF for a detail. A video for the whole story.

A GIF works well when one interaction says everything: a hover state in a changelog, a short fix in a support ticket, a before-and-after in a pull request, or one feature in a README. It plays inline, needs no audio, and lets a teammate see the point without opening a player. It can also work in Slack or Feishu, subject to the app's file limits.

For more than ten or fifteen seconds, video is usually smaller and clearer. Choose video when sound matters, when the text must stay sharp at full resolution, or when the viewer needs the entire walkthrough. GIF has a limited palette and is a poor substitute for a long product demonstration.

If the recording itself contains wrong turns or hesitation, that is a separate job. Use DemoRefine to clean up the whole recording, then convert the short moment you need. You can keep using the recorder you already have; the GIF tool does not remove pauses or mistakes.

Screen recording to GIF questions