[go: up one dir, main page]

What the GIFvideo → gif, the way creatives need it
webm to gif

WebM to GIF, from one browser-made file to another

The web records to WebM: OBS exports, Chrome captures, MediaRecorder blobs from your own code. Here that recording becomes a GIF that embeds in a README or a PR, and the file goes nowhere.

Drop a video, get a GIF free · frame-perfect · nothing leaves your browser Open the converter →

Convert a WebM recording into a GIF

What the GIF does the whole thing locally, right in your browser: nothing here ever leaves your machine.

  1. Bring the .webm. Drag it from your downloads onto the tool, or pick it with the file dialog. OBS, Chrome capture, and MediaRecorder output all open directly in the tab.
  2. Trim against the frame counter. Bracket the action with the handles, reading the seconds-plus-frames labels, and tap the arrow keys when a cut needs to shift a single frame.
  3. Lock the crop. Choose the ratio the destination expects, 16:9 for a landscape demo, 9:16 for mobile, and the export holds that shape precisely.
  4. Budget the bytes. Take UI motion to 12 or 15 fps, downsize until the long side is around 700 px, and set 64 to 128 colors with dithering for flat interfaces. The size estimate follows every change.
  5. Encode locally. Confirm the preview loops the way you want, then convert. The GIF is written by your own browser and saved to disk, with no watermark and no upload anywhere in the chain.

The web's own video format

WebM exists because of a licensing fight. Google bought the codec shop On2 in 2010, opened up VP8, and wrapped it in a slimmed-down Matroska container so the web could have video without H.264's patent tolls. VP9 and AV1 followed into the same box. Browsers embraced it, and it quietly became the format web software records to.

So a .webm in your downloads folder has a short list of likely parents: OBS Studio set to WebM output, Chrome's screen capture or a recorder extension, a MediaRecorder blob your own JavaScript wrote to disk, or an export from a meeting or Loom-style tool. Efficient, royalty-free, and everywhere in dev workflows.

It just doesn't paste. GitHub comments, Notion pages, and most chat apps won't inline a WebM, and a GIF sails through all of them. Drop the file here and make the swap without the recording leaving your machine.

Local processing, which matters for what WebM tends to contain

Be honest about what's in your WebM files: an unreleased feature, an internal dashboard, a bug repro with customer data in the corner. This converter decodes and re-encodes in the page's own memory, on your hardware. No byte of the recording is transmitted, no account or email is collected, and no watermark is added. Disconnect after the page loads and the conversion still runs to completion. There's no queue, either; decoding starts the moment the file lands, because nothing has to crawl up your uplink first.

The no-upload explainer spells out exactly what stays local, for anyone who needs to show a security team.

Driving the converter like you mean it

The timeline is built for precision rather than vibes. Here's the loadout:

A running estimate of the output size updates while you tune, so every tradeoff gets made against a real number instead of a render-and-see guess.

Format quirks worth knowing before you hit encode

The preview surfaces every one of these before you commit, which beats discovering them after a render finishes. Thirty seconds of scrubbing saves a re-encode.

Where a WebM-born GIF usually lands

Most of this traffic is developers documenting something. Headed for a repo? The GitHub README guide covers sizing that reads well on both light and dark themes. If the source came out of a screen recorder specifically, the screen recording page has advice tuned for captured UI.

Sizing targets from experience: around 2 MB keeps a GIF snappy inline in chat or a PR review, up to about 5 MB is tolerable in a slide deck that never has to travel, and anything heavier deserves a second pass through the trim before it ships anywhere.

The recording is done. Now make it loop.

Drag the WebM in, keep the good three seconds, and export a GIF that pastes straight into the PR.

Open the converter

Questions, answered

Is anything sent to a server when I convert a WebM?
No. The file is decoded in the tab, held in memory, and re-encoded to GIF by your own machine. That makes it safe for recordings of internal tools, and it's why the page keeps functioning after you disconnect.
Will files from OBS, Chrome capture, or MediaRecorder open?
Yes, those are the bread-and-butter cases. VP8 and VP9, the codecs almost all WebM uses, decode in every modern browser. The rarer AV1-in-WebM variant may require a recent Chrome or Edge.
My recording has a variable frame rate. Does the GIF inherit the jitter?
No. You set one fixed output rate and the converter resamples to it. A GIF wants steady timing anyway; if the source feels uneven, locking 12 or 15 fps smooths it out.
What happens to the audio track?
It's dropped. The GIF format has no concept of sound, so a demo loop or reaction comes out silent. If the audio is the point, keep the WebM.
How do I land under 2 MB?
Trim tighter than feels natural, run the frame rate at 12 to 15, shrink the long side toward 600 px, and hold the colors between 64 and 128 with dithering on. The estimate tells you when you've made it.
Does it stamp a watermark or cap the file size?
Neither. Nothing is drawn over your GIF, and no size ceiling exists because the file never reaches any server. The practical bound is your machine's memory, which handles normal recordings without complaint.