Why the camera roll defeats most converters
Since iOS 11 an iPhone shoots HEVC (H.265) inside a .mov, a combination that still makes older GIF tools shrug and demand an mp4. Add slow-mo at 120 or 240 fps, and a forty-second clip whose good part lasts two, and the camera roll turns out to be a genuinely awkward starting line. None of that is your fault; the phone is optimizing for storage, and most of the converter industry never caught up.
The way around it is to let the browser do the decoding. Safari and Chrome play HEVC .mov files natively on Apple hardware, and this converter borrows that same decoder: if your device can play the clip, the clip can become a GIF, with no transcode and no format complaint. The container details, if you want them, live on the MOV to GIF page.
Laptop or phone, pick your screen
On a Mac, get the clip out of Photos first:
- AirDrop: share from Photos to the Mac; the .mov appears in Downloads.
- Files or iCloud Drive: save it to Files on the phone, collect it from Finder on the laptop.
- A cable: Image Capture still works exactly like it did in 2010.
No laptop around? Open the converter in mobile Safari, tap the drop zone, and pick the clip straight from Photos. Same tool, same controls, running on the phone's own silicon. A long 4K recording will tax a phone's memory, so cut the clip down early and keep sources short if Safari starts wheezing. In both cases the footage is processed where it sits, which is the entire pitch of a private converter: no copy of your kid, your dog, or your unreleased prototype ever exists on someone else's machine.
Find the two seconds, then frame them
Load the clip into the editor and the timeline reads its true frame rate, counting in seconds plus frames rather than vague decimals. Rough the cut with the handles, then give one focus and tap left or right; every tap is exactly one frame, which is how a loop lands on the beat instead of near it. Do this trimming before you fiddle with any quality settings: every second you shave makes the later choices easier, and on a phone it also keeps the memory pressure down.
Phone footage is vertical, so the crop does real work here. Lock 9:16 to keep portrait portrait, 1:1 or 4:5 for feeds, 16:9 when a landscape shot is headed for a slide. Ratios are exact; nothing gets quietly stretched on the way out, and no face arrives at the deck eight percent wider than it left.
Numbers that keep the file polite
iPhone clips start big, and GIF is not a forgiving format. The dials that matter:
- Frame rate: 10 to 15 fps does it. Your phone recorded 30 or 60; the loop won't miss them.
- Width: 480 to 640 pixels reads crisply in a chat or a deck at a fraction of the weight of 1080.
- Palette: 64 to 128 colors. Most footage is indistinguishable at 128 and meaningfully smaller.
- Dithering: on for skies, sunsets, and skin, where it hides banding; off for flat graphics, where it just adds sand.
The size projection updates while you drag, so you're steering toward a real number: under about 2 MB for chat and email, up to about 5 MB for a slide. If it's bound for a deck you can afford the extra width; decks travel as attachments anyway. The small-GIF guide continues from there if you need to go leaner.
No toll booth at the end
Nothing to install, no account to create, no watermark across the corgi. The tool is a web page, free and carried by its ads, and it behaves identically in Safari, Chrome, Firefox, and Edge on whatever machine is nearest. The clip goes in, the GIF comes out, and both stay yours. That's the entire transaction, and it's the same one every time you come back.
One habit worth keeping: hold on to the original .mov. The GIF is the shareable copy, but the video stays the master, and the next destination might want a different crop, a different length, or the sound the GIF had to give up.