MOV to GIF

MOV is QuickTime's container and the default of macOS screen recording, older iPhone video and a great deal of camera footage. Whether a MOV to GIF conversion works depends entirely on the codec inside the wrapper — so this MOV to GIF converter is upfront about both outcomes.

The two kinds of MOV

• H.264 inside MOV — phone clips, macOS screen recordings, most consumer sources. These decode in every modern browser and the MOV to GIF conversion runs exactly as it does for MP4 files.
• ProRes, Animation or HEVC inside MOV — professional camera and edit-suite exports. No browser ships these decoders, so no browser tool can sample them. The upload is refused with that explanation rather than a silent failure.

Making the MOV to GIF loop worth sharing

A MOV to GIF conversion has three settings, and their order matters. Isolate the moment with the start and stop fields before adjusting anything else; three to six seconds is the range that reads as a loop rather than a clip. Then width — 480 px for legibility, 320 px for chat — and finally frame rate, where 8–10 fps covers almost everything people loop.

What is inside the file decides the MOV to GIF result

On a Mac this takes two seconds: open the clip in QuickTime Player and choose Window, then Show Movie Inspector. The format line names the codec directly, and H.264 there means the MOV to GIF conversion will work here while HEVC, Apple ProRes or Animation means it will not. On Windows the properties dialog in Explorer reports a video codec under the Details tab for most MOV files, and any player that surfaces codec information does the same job.

There is a faster test that needs no software. Drag the file into an empty browser tab. If the tab plays it, the MOV to GIF conversion can sample it, because both use exactly the same decoder — the browser's own. If the tab offers a download instead of a picture, the codec is missing and re-exporting is the only route forward.

iPhone footage deserves a specific mention. Recordings made since the HEVC option appeared are usually .mov wrapping HEVC, and whether they play in a browser depends on the machine's hardware decoder rather than on anything in the file. The same clip can convert on one computer and be refused on the next. Setting Camera, then Formats, then Most Compatible makes future recordings H.264 and removes the ambiguity.

macOS screen recordings

The recorder behind Command-Shift-5 writes MOV wrapped around H.264, which is the combination a MOV to GIF conversion always welcomes — those files convert here without exception. The catch is resolution rather than codec. On a Retina display the capture is taken at the panel's full pixel count, roughly twice the point size the interface reports, so a full-screen recording from a 2560-pixel-wide MacBook arrives as a 2560-pixel video.

At Large (640) that is a scale of one quarter, and 14-pixel menu text becomes 3.5 pixels tall. Record a single window rather than the whole screen, or crop the capture afterwards, and the identical conversion produces text that people can actually read in a bug report.

If your MOV to GIF conversion is refused

Re-export from the source app as H.264 (QuickTime's “Export As” menu, or any editor's MP4 preset). The MOV to GIF conversion then succeeds unchanged, and the re-exported file is also the one every other web tool will accept.

One thing worth saying plainly: the four video pages on this site — MOV, MP4, WebM and the format-agnostic video to GIF — are the same tool wearing four labels. They sample through the same browser decoder and expose exactly the same controls, so a clip refused here would be refused on any of the others, and the diagnosis above applies unchanged whichever container the footage arrived in — a MOV to GIF conversion here behaves exactly like its siblings.

Private MOV to GIF conversion

Every MOV to GIF conversion on this page samples the clip locally: the file is seeked through the browser's own decoder, painted frame by frame onto a canvas and encoded with gifenc, and a 100 MB QuickTime recording stays on your disk for the whole of it. There is no upload, no queue and no account, which matters for the footage that typically needs this route — client walkthroughs, internal demos, family clips — because a MOV to GIF tool that runs in the tab gives those files no destination other than your own download folder.