Initializing... drag & drop files here
Supports: GIF
Final Cut Pro, iMovie, Premiere Pro and DaVinci Resolve all treat a GIF as an awkward guest — some import it as a single still, some refuse the frame rate, some drop it in at the wrong duration. Turning the GIF into a MOV (QuickTime) first hands the editor a normal video stream with real frame timing. This page walks through the conversion, the two settings that actually change the result, and the errors people hit when the source GIF has transparency or only a couple of frames.
Everything else on the panel is optional, but these two decide what lands on your timeline.
| Setting | Default on this page | Change it when |
|---|---|---|
| Video Codec | H.264 | You need H.265 for size, or a legacy codec for old software |
| Preset (File Compression) | Very High (Recommended) | You want a master (Highest) or a smaller file (Medium/Low) |
| Background Color | White | The GIF is transparent and white is the wrong matte |
| Video resolution | No mode preselected — pick "Keep original" to hold the GIF's pixel size | The timeline is a fixed 1080p or 4K sequence |
| Property | GIF (source) | MOV (output) |
|---|---|---|
| Kind | Indexed-colour image with frame delays | QuickTime container, Apple, 1991 — the ancestor of MP4's file format |
| Colour | Up to 256 per frame from an 8-bit palette | Full 24-bit colour through H.264 |
| Compression | LZW, per frame, no inter-frame prediction | Inter-frame H.264 or H.265 |
| Transparency | 1-bit on/off | None — filled with the Background Color |
| Audio | Not supported | Container supports it, but a GIF has none to carry |
| Looping | "Loop forever" flag in the file | No loop flag; a player or timeline decides |
| Editing support | Treated as an image or a still | Native in Final Cut Pro, iMovie, Premiere Pro, Resolve |
If your real goal is compositing a transparent element over other footage, a MOV from this page will not get you there — the codecs offered here are all opaque, and the alpha-capable QuickTime codecs used for that job (ProRes 4444, Animation) are not among them. In that case keep the artwork in an alpha-capable image format instead: convert the GIF to APNG keeps both the animation and the transparency, and most motion-graphics tools will import it. Likewise, if the GIF is a screen recording that was already lossy when it was made, no preset will restore detail the palette threw away.
Almost always smaller. GIF stores every frame independently with LZW compression and a 256-colour palette, so a busy loop balloons; H.264 encodes only the differences between frames. The exception is a GIF of two or three frames, where the video container's own overhead can match or exceed the source.
Yes. Each GIF frame carries its own delay value, and those delays drive the output's frame pacing, so the animation runs at the same speed as the original. What does not survive is the loop flag — video plays once unless your player or timeline repeats it.
Both usually carry the same H.264 stream, so picture quality and file size are effectively identical. MOV is the native container in Apple's tools and is what QuickTime, Final Cut Pro and iMovie expect. For broad web and device playback, GIF to MP4 is the safer target.
No. The codecs offered here — H.264, H.265 and the legacy options — have no alpha channel, so transparent pixels are composited onto the Background Color before encoding. White is the default for GIF sources; pick another from the dropdown if it clashes with your scene.
No. We always decode the GIF to raw frames and re-encode them, so a lossy codec discards some detail. In practice the output usually looks better than the source anyway, because the GIF's 256-colour palette and dithering are gone. "Highest" is the closest this page gets to a visually lossless master.
It follows the GIF. Most GIFs are authored somewhere between 10 and 25 frames per second, expressed as per-frame delays rather than a single rate, and those delays are what our pipeline reproduces. If your sequence needs a fixed rate such as 23.976 or 29.97, conform the clip in the editor after import.
Yes — queue them and they all convert with the same codec, preset and background colour. Each GIF produces its own .mov; there is no merge step on this page, so joining clips is an editing-timeline job.
Yes. MOV to GIF samples the video back down into an animated GIF, which is what you want when the destination is a chat app, a forum post, or an email client that only accepts images.