Initializing... drag & drop files here
Supports: AVCHD
AVCHD is the Sony/Panasonic camcorder format from 2006: H.264 video wrapped in a Blu-ray-style transport stream, recorded as .mts or .m2ts files inside an AVCHD folder. This tool resamples a short stretch of that HD footage into a looping animated GIF — the right move when you want a camcorder moment to autoplay in a chat, forum post, or README where video stays paused. If you actually need the full clip with sound, keep it as video instead; the section below lays out exactly what the GIF gains and loses.
| Property | AVCHD source | GIF output |
|---|---|---|
| Standard / spec | AVCHD (Sony + Panasonic, 2006); 2.0 added 1080p in 2011 | GIF89a (1989), LZW-compressed |
| Video codec | H.264 / MPEG-4 AVC | Per-frame indexed bitmap, no codec |
| Container | BDAV MPEG-2 transport stream (.mts / .m2ts) |
Single self-contained .gif |
| Typical resolution | 1080i, 1080p, or 720p HD | Whatever you downscale to (480p/360p common) |
| Scan type | Often 1080i — interlaced | Progressive frames only |
| Color | 8-bit 4:2:0, millions of colors | 256 colors per frame, banding likely |
| Audio | Dolby AC-3 or linear PCM | None — GIF is silent |
| Compression | Inter-frame (P/B frames), very efficient | Per-frame LZW, no motion comp — large files |
| Best at | Full HD clips, editing, archival | 2-6 second silent loops for chat and web |
An HD camcorder clip is the worst possible input for a format with no inter-frame compression, so a first-pass GIF is often far bigger than people expect. These are the controls that actually move the number, in the order worth trying:
| Lever | Where it lives | Effect on size | What it costs you |
|---|---|---|---|
| Resolution | File Compression → Custom → Image resolution (preset / Width x Height / percentage) | Largest single lever — halving each dimension cuts pixel count to a quarter | The loop is physically smaller on screen |
| Duration | Trim the source before converting | Directly proportional — half the seconds, roughly half the frames | You lose part of the moment |
| Frame rate | Framerate (default 10 FPS) | Strong — fewer frames stored means fewer full images | Motion gets choppier below about 10 FPS |
| Quality preset | File Compression (default High) | Moderate — each rung down tightens per-frame quality | Visible banding or a stippled dither texture at the low rungs |
| Max file size | File Compression → Max file size | Absolute — the converter fits your cap (percent of source, exact value, or a Discord/Email/Forum preset) | Quality lands wherever the cap forces it; you're warned when that's low |
Work top-down: a 1080p source dropped to 480p and trimmed to four seconds usually solves the problem before you touch the quality controls at all.
.mts or .m2ts file, or click "+ Add Files" to browse. Batch upload works — the same settings apply to every file in the queue.It can, because AVCHD camcorder footage is frequently 1080i — interlaced, where each frame is two fields captured a fraction of a second apart. Flatten that into a single progressive GIF frame and fast motion shows comb-tooth artifacts. Nothing here deinterlaces — the fields pass through exactly as recorded. Two ways around it: pick a low-motion segment where the two fields nearly match, or if combing is heavy, deinterlace the footage in a desktop editor first and make the GIF from that progressive export.
GIF has no inter-frame motion compression — every frame is stored as its own LZW-compressed 256-color image, while AVCHD's H.264 only encodes the differences between frames. So a few seconds of HD footage that was a couple of megabytes as AVCHD can balloon into tens of megabytes as a GIF at the same size and frame rate. The biggest lever is resolution: a 1080p source downscaled to 480p (File Compression → Custom → Image resolution) drops the pixel count by roughly three-quarters. After that, trim the duration, then lower the frame rate — or set File Compression → Max file size and let the converter fit a cap. If it's still heavy, run the output through Compress GIF for a second optimization pass.
GIF caps each frame at 256 colors drawn from a 24-bit space, while AVCHD carries millions. Skies, skin tones, and gradients — common in camcorder footage — posterize after quantization, and that limit is inherent to GIF. The encoder reduces and dithers each frame's palette automatically; keeping the File Compression Quality preset high gives gradients the most palette room. If you need full color with the same autoplay-in-chat behavior, AVCHD to WebP keeps the full range and is usually much smaller.
No. GIF is an image format with no audio track, so the Dolby Digital or PCM soundtrack from the AVCHD file is dropped. If sound matters, AVCHD to MP4 preserves the audio and plays inline on every modern platform. GIF earns its place precisely where silent autoplay is the point — email bodies, READMEs, and chat apps that mute or strip video.
10-15 FPS and 2-6 seconds is the sweet spot. GIF89a stores each frame's delay in hundredths of a second, so 25 FPS and 50 FPS are the cleanest high rates and 50 FPS is the practical ceiling — browsers won't render faster. Most AVCHD is shot at 25-30 fps (or 50i/60i fields), so dropping the GIF to 10-12 FPS sheds redundant frames you won't miss and meaningfully cuts the file down.
Upload the individual clip files, not the folder. AVCHD writes a Blu-ray-style directory tree onto the card — typically an AVCHD or PRIVATE folder containing BDMV, and inside that a STREAM subfolder holding the actual recordings as .mts or .m2ts files, one per clip. Those .mts / .m2ts files are what this converter accepts; drag one (or several) straight from the STREAM folder onto the page. The surrounding CLIPINF and PLAYLIST files are index and playlist metadata that camcorders and Blu-ray players use to stitch clips together, and they are not needed here. If your camera software already exported the footage as a single .mts file elsewhere on disk, that works identically.
Attack it in the order the size table above sets out, because the levers are not equally strong. Start with resolution — an HD camcorder frame carries far more pixels than a chat window will ever show, and stepping a 1080p source down to 480p (File Compression → Custom → Image resolution) removes roughly three-quarters of them in one move. Then trim the clip: GIF stores every frame as its own image, so seconds translate almost linearly into megabytes. Only after those two should you lower the Framerate toward 10 FPS — or skip the manual loop and set File Compression → Max file size to whatever cap your destination enforces. If the result is still heavier than the destination accepts, run it through Compress GIF for a second optimization pass, or switch target entirely — AVCHD to WebP gives you the same autoplaying loop with full colour at a fraction of the size.
This converter outputs an animated GIF — a moving loop — using the Framerate control, so the whole short segment plays. If you only want one frozen frame from the camcorder clip, a video-to-image grab like AVCHD to JPG is the cleaner route, since it gives you a full-color single image without GIF's 256-color limit. In our testing, a 4-second 1080p AVCHD segment downscaled to 480p at 10 FPS produced a GIF in the low tens of megabytes — fine for a quick share, but a still frame is a fraction of that if motion isn't the point.