A container older than the web it won't paste into
QuickTime shipped in 1991, and .mov is its container, old enough that when MPEG needed a foundation for the MP4 standard a decade later, they started from Apple's design. Today the extension mostly means one of three things: an iPhone camera clip (often HEVC under the hood), a Mac screen recording from Command-Shift-5, or an export out of QuickTime, iMovie, or Final Cut.
Inside the Apple world, those files behave. Everywhere else, a MOV is an attachment: paste one into Slack, into a GitHub comment, into Notion or an email, and it just sits there waiting to be downloaded, scrubbed, and closed. A GIF plays the instant it loads, right in the conversation. Closing that gap is this page's whole job.
The converter closes it inside the tab: no detour through an MP4 export, no ffmpeg incantation, no third-party server holding your footage while it works.
Screen recordings are exactly the files you shouldn't upload
Consider what a Mac screen recording usually shows. An inbox with subject lines readable. The name of every private channel in a sidebar. A revenue dashboard. A customer's account details. That's precisely the footage you don't want to hand to an upload-and-convert site with a retention policy you've never read.
Here the pipeline is client-side from end to end: decode, trim, and encode all happen on your own CPU, and nothing is transmitted anywhere. Load the page, then switch Wi-Fi off if you want proof; the conversion finishes anyway. The no-upload page walks through the whole design if that's the part you care about.
It's also free, paid for by ads rather than by your email address. No account to make, no watermark on what you export, and nothing about the session survives closing the tab.
What you control on the way out
Nothing here is a mystery one-click preset. Every dial is exposed, and each one moves the file size in a direction you can predict:
- Trim. The timeline reflects the MOV's actual frame rate, 30 or 60 fps for iPhone clips, sometimes 25 for older captures, and the arrow keys walk a handle frame by frame until the cut lands.
- Crop. Fixed ratios only: 1:1, 9:16, 4:5, 4:3, 16:9. Vertical phone footage stays properly vertical, widescreen captures stay widescreen.
- Frame rate. A 30 fps source resampled to 12 or 15 fps still reads as smooth motion in a loop, at a fraction of the weight.
- Scale. Retina screen captures are gigantic in pixels. Shrink the output to what a chat window actually renders.
- Color and dithering. Flat UI recordings compress happily at 64 colors; footage with gradients might want 128 plus dithering to stop banding.
- Size feedback. The estimated output ticks up or down with every adjustment, so you land the target before exporting rather than after.
The two MOVs everyone converts, with numbers
The iPhone clip. A reaction, a pet, something in your hand. These arrive at 30 or 60 fps and enormous resolution, far more than any GIF needs. Trim to one or two seconds, crop 9:16 or 1:1, resample to 12 to 15 fps, and bring the long edge to 480 or 640 pixels. That lands a clean loop under 2 MB, which plays nicely in Slack, email, and most timelines.
The Mac screen recording. A bug repro or a feature walkthrough. Screen captures are flat color and sharp edges, which GIF palettes love. Keep 12 to 15 fps, crop to the window instead of the whole desktop (losing the menu bar and dock can halve the file), and pull colors toward 64. The screen recording page continues from there.
No Mac required to open a Mac file
A quietly useful consequence of living in a browser: converting a MOV doesn't require the machine that made it. The AirDrop landed somewhere without QuickTime? Somebody sent an iPhone clip to your work PC? Neither matters. If a browser can play the clip, this page can convert it, wherever it ended up.
Chrome, Safari, Firefox, and Edge all work, on Mac, Windows, ChromeOS, and Linux. The MOV you couldn't even preview on a PC becomes the GIF that pastes anywhere. If most of your files end in .mp4 instead, that page is next door.