Where your clip is already sitting
Game capture tools all spit out a video file, and that's exactly what this converter eats. You bring the recording you already made; What the GIF turns it into a GIF. A quick map of where to find yours:
- NVIDIA ShadowPlay (now NVIDIA App). Instant Replay and manual captures land in your Videos folder as .mp4, usually 1080p or 1440p at 60fps. That high frame rate is great source material to downsample from.
- Xbox Game Bar on Windows. Win+Alt+G grabs the last 30 seconds. Captures show up under Videos/Captures as .mp4. The free GIF route from there is the GIF maker for Windows.
- macOS screen capture and Apple's game capture. The built-in recorder writes .mov; some tools hand you .m4v. Mac users can jump straight to the GIF maker for Mac, and the same trim controls apply.
- AMD ReLive, OBS, Steam. ReLive and Steam default to .mp4; OBS often gives you .mkv or .mov depending on your settings. All of them decode here.
Whatever the container, the workflow is the same. If you want the format-specific walkthrough, there's MP4 to GIF, MOV to GIF, and MKV to GIF. You don't need to convert formats first. Just drag the raw capture in.
Fast motion is the whole problem, and frame rate is the lever
Gameplay moves. A flick shot, a 180, a vehicle blur, a particle explosion. GIF is an old, hungry format, and the tension is always the same: more frames per second means smoother motion but a bigger file. You get a frame rate (fps) slider so you can decide that tradeoff yourself instead of letting a server pick badly for you.
- 10 to 15 fps is the sane default for most clips, and it keeps the file reasonable. A talky build-craft moment or a slow zoom looks fine at 12.
- 20 to 24 fps is where you go for genuinely fast action. A frag montage, a drift, a whip-pan. The motion stops looking choppy, but watch the live size estimate climb.
- Pair fps with a shorter trim. The honest move for fast gameplay isn't cranking fps on a 10-second clip, it's cutting to the 2 to 3 seconds that actually matter and spending your frame budget there.
There's no speed control here beyond frame rate, so this isn't the place for slow-mo ramps. What you get is honest sampling of the frames you already shot. If your source is 60fps ShadowPlay footage, downsampling to 20fps in the GIF still pulls clean frames, which is why high-frame-rate capture is worth keeping.
Crop to the action, then keep the file small
A raw 1440p capture is overkill for a GIF and will balloon the file. Two controls fix that. The scale slider downsizes the whole frame, and the crop locks to exact ratios so you can frame the part of the screen that matters: 16:9 for the full widescreen view, 1:1 or 4:5 for a feed, 9:16 if you grabbed a vertical mobile-game clip. Nothing stretches; the output matches the ratio you pick.
Then there's the part most converters skip: a color palette reduction control plus dithering. GIF tops out at 256 colors, and gameplay HUDs, neon, and gradients are exactly the kind of thing that bloats a palette. Drop to 64 to 128 colors and most clips still look sharp while the file gets dramatically smaller. Turn dithering on when banding shows up in smoky or dark scenes. The live size estimate updates as you tweak, so you can land under a target before you ever render. For a deeper squeeze, see making a small GIF from video; if you'd rather bias toward crispness, high-quality video to GIF walks the other direction.
Where the GIF is going changes how you cut it
A gameplay GIF for a Discord server has a different budget than one for a Reddit highlight thread or a clan recruitment post. Match the clip to the destination:
- Discord and chat. Keep it tight and under a couple of megabytes so it plays inline without a click. Trim to the single play, 2 to 4 seconds.
- Reddit. Threads love a clean loop of the moment. The Reddit GIF guide covers sizing for the feed.
- Twitter / X. The platform converts GIFs to video anyway, so prioritize motion clarity. See GIFs for Twitter / X.
- A README or wiki. Showing off a mod, a tool, or a speedrun route? A looping GIF in a GitHub README beats a video embed nobody can preview.
If your clip is closer to a screen recording of a launcher or menu than live action, the screen recording to GIF page has tips tuned for that. And because the converter is just a website, it works the same on a Chromebook in a school esports club as it does on a tricked-out tower.
Nothing uploads, and that's not a footnote
The whole conversion runs client-side, inside the browser tab. Your gameplay capture is never sent to a server, never sits in someone's queue, never gets logged. There's no account, no email, no watermark stamped across your highlight, and no server-imposed file-size cap. It's free, supported by ads on the page, and once it has loaded it'll even work offline. Open the converter and the clip stays on your machine the whole way through.
That privacy matters more than it sounds for capture footage, which often catches a Discord overlay, a username, a stream key, or a half-open browser tab in the corner of the screen. Crop those out, and they were never anywhere but your own machine to begin with. If that's the part you care about, converting video to GIF without uploading says more, and the no-watermark maker covers the clean-output angle.