WebM clips from Loom, OBS, and browser recorders don't play everywhere. Convert them to universally-readable GIFs in your browser — free, no upload.
Loading FFmpeg Core... (This may take a moment)
Files are processed locally and never uploaded.
Drop your .webm file into the uploader above — it stays on your device.
Set the FPS and width for the GIF (10 FPS / 480px suits most screen captures).
Convert, check the output size next to the download button, and download the GIF.
WebM is the default export of a huge slice of the modern recording stack: Loom's downloads, OBS Studio's default recording format, Chrome's built-in screen recorder, and most browser-based capture tools all hand you a .webm file. It's an excellent format — small files, good quality, open codecs (VP8/VP9).
The problem is acceptance. PowerPoint, Keynote, many email clients, older forums, and a long tail of internal company tools either can't play WebM or handle it badly. Safari's WebM support has historically lagged too. When the place you're posting doesn't speak WebM, GIF is the format everyone understands.
Converting WebM to GIF always feels like a step down, because it is: you're going from an efficient modern codec with millions of colors to a 1987 format with 256 colors per frame. Smooth gradients — the kind Loom's blurred backgrounds and OBS's webcam overlays are full of — will show banding in the GIF that the WebM never had.
Two mitigations actually help. First, keep the GIF's width generous (480–640px) so edges and text stay crisp; banding bothers people less when the image is sharp. Second, don't over-compress the FPS: 10–12 FPS hides more color banding than 6 FPS does, because the eye forgives gradient steps in moving images. If the GIF is too big at those settings, shorten the clip rather than crushing the quality.
OBS users: record the segment as WebM (the default), then trim ruthlessly. A GIF audience wants the 5-second bug reproduction or the satisfying before/after — not the 3-minute session. Many OBS users already record "GIF-first": short takes, mouse movements deliberate, on-screen actions paced for a loop.
Loom users: download the video as WebM from the share menu, then convert the best slice here. This is a common pattern for docs teams — a Loom walkthrough becomes three looping GIFs embedded in the help article, each showing one step, while the full Loom link stays below for anyone who wants narration.
A niche but real gotcha: WebM supports an alpha channel (transparency), and some motion-graphics exports use it. GIF also supports transparency — but the two systems don't map cleanly, and this tool converts the WebM as opaque video. If your WebM has transparency you need to keep, you'll need a desktop editor, not a format converter.
For the 99% case — screen recordings, webcam clips, gameplay — there's no transparency involved and this doesn't matter. Mentioned here only so the 1% doesn't discover it by surprise.
WebM files from screen recorders often contain exactly what you were doing: your inbox, your codebase, your unreleased product. Uploading that to a random converter site is a needless risk, and many "free" converters monetize precisely by being careless with uploads.
This page decodes your WebM and re-encodes the GIF entirely in your browser. The file never crosses the network — confirm it in the network inspector during a conversion. No account, no watermark, no per-day limit on how many clips you convert.
GIF is limited to 256 colors per frame while your WebM (VP9) has millions, so smooth gradients show banding. It's a format limit every converter shares. Keeping width at 480px+ and FPS at 10–12 hides most of the banding; shortening the clip keeps the file small without crushing quality.
Yes — download the Loom video as WebM from its share menu, then drop it here. Trim to the best 5–10 second slice for a GIF-sized file. Docs teams commonly turn one Loom walkthrough into several looping GIFs for help articles.
No — GIF has no audio track at all. If your clip's narration matters, keep it as WebM/MP4. Convert to GIF only for short, silent, visual moments.
No — this tool converts WebM as opaque video, so VP9 alpha channels don't survive. For transparency-preserving animation, use a desktop editor (or export as APNG/WebP instead). Standard screen and camera recordings have no transparency, so this affects almost nobody.