Initializing... drag & drop files here
Supports: M2TS
Turn a stretch of Blu-ray or AVCHD camcorder footage into a looping animated GIF — the format that autoplays silently in chat apps, forum posts, issue trackers, and README files where an embedded video player would just sit there paused. This is a genuine animation, not a frozen still: frames are extracted from the .m2ts clip and assembled into a real GIF loop at the frame rate you choose. The trade-offs are real too, and the honest ones are all below.
.m2ts clip onto the page or click "+ Add Files". This page accepts the .m2ts extension only — camcorder cards that write .MTS are handled at MTS to GIF. Several clips can be queued and share one set of settings.| Property | M2TS (source) | GIF (output) |
|---|---|---|
| Container | BDAV MPEG-2 transport stream, 192-byte packets | GIF89a, published 1989 |
| Video coding | H.264/AVC with inter-frame prediction (P and B frames) | Per-frame LZW-compressed indexed bitmaps, no motion compensation |
| Colour | 8-bit-per-channel video, millions of colours | Up to 256 colours per frame |
| Audio | Dolby Digital (AC-3), 1–5.1 channels, or linear PCM | None — GIF has no audio track at all |
| Typical resolution | 1920×1080, 1440×1080, or 1280×720 | Whatever you cap it at; 480p and 360p are the common choices |
| Timing | Frame rates like 29.97 or 59.94 fps | Per-frame delays stored in whole hundredths of a second |
| Scan | 60i / 50i are specified AVCHD modes | Progressive frames only — interlacing arrives already woven in |
| Size behaviour | Very efficient for long HD footage | Grows roughly linearly with frames × pixels |
| Best at | Recording and archiving HD video | Short silent loops that autoplay anywhere |
GIF does not store a frame rate. It stores a delay for each frame, in whole hundredths of a second, which means only frame rates that divide evenly into 100 can be represented exactly. For the rates that do not divide evenly, our pipeline normalises every frame to a single rounded delay so the animation plays at a steady speed instead of visibly stuttering between two different delays — but the true playback rate then sits slightly off the number on the label.
| Framerate you pick | Frame delay | Lands exactly? |
|---|---|---|
| 50 FPS (Max Speed) | 2/100 s | Yes |
| 25 FPS | 4/100 s | Yes |
| 20 FPS | 5/100 s | Yes |
| 10 FPS (Recommended) | 10/100 s | Yes |
| 5 FPS | 20/100 s | Yes |
| 2 FPS (Slow) | 50/100 s | Yes |
| 1 FPS (Slideshow) | 100/100 s | Yes |
| 30 FPS (Smooth) | 3.33 rounds to 3/100 s | No — effective rate about 33 fps |
| 15 FPS | 6.67 rounds to 7/100 s | No — effective rate about 14 fps |
| 12 FPS | 8.33 rounds to 8/100 s | No — effective rate about 12.5 fps |
| 8 FPS | 12.5 rounds to the nearest whole hundredth | No — effective rate about 8 fps |
If exact timing matters more than the number, 1, 2, 5, 10, 20, 25, and 50 FPS are the safe picks — they are the frame rates that divide evenly into 100. The rest are perfectly usable; they just play a few percent off the labelled speed, which nobody notices on a short loop but which will drift audibly out of sync if you are matching the GIF to something else.
A real animated loop. The clip is decoded, frames are pulled at the rate you set under Framerate, and those frames are assembled into a looping GIF — the whole segment moves. If a single frozen image is what you actually want, a still-image target is much better suited: M2TS to JPG gives you one full-colour frame without GIF's 256-colour ceiling, and at a tiny fraction of the size.
Because GIF has no motion compensation. H.264 inside your M2TS encodes mostly the differences between frames, which is why a few minutes of HD fits in a modest file. GIF stores every frame as its own complete LZW-compressed image, so file size scales with frames multiplied by pixels and nothing is shared between them. A few seconds of 1080p can easily outweigh the entire source clip. The levers, in order of effect: drop Image resolution to a 480p or 360p preset (under File Compression → Custom; a 1080p source loses about three-quarters of its pixels at 480p), shorten the clip before uploading, and lower the Framerate — or set File Compression → Max file size and let the converter fit your cap. If the result is still heavy, run it through Compress GIF for a second optimisation pass.
Not on this page — there is no trim control in the M2TS to GIF options, so the whole clip becomes the animation. Since GIF size scales directly with the number of frames, cutting first is usually the most valuable step you can take: Video Cutter accepts .m2ts directly, so trim the segment you want there and bring the short clip back here. A four-second loop from a forty-minute camcorder take is a completely different file from the forty-minute version.
No. GIF is an image format with no audio track in the specification, so the Dolby Digital (AC-3) or linear PCM soundtrack in your M2TS is discarded entirely. That is not a limitation of this converter — no GIF anywhere has sound. If the audio matters, M2TS to MP4 keeps picture and sound together and plays inline on every modern platform. GIF earns its place precisely where silence is the point: email bodies, READMEs, and chat clients that mute or strip video.
Because a GIF frame can hold at most 256 colours, drawn from a palette, while your M2TS carries full-range 8-bit-per-channel video. Skies, skin tones, film grain, and any smooth gradient have to be quantised down to that palette, and posterised bands are the visible result. The encoder chooses its palette automatically for each conversion, so there is no manual tuning that escapes the 256-colour ceiling — it is inherent to the format. If you want a silent looping animation without that ceiling, M2TS to APNG produces an animated PNG with full 24-bit colour and alpha, supported by Chrome 59+, Firefox, Safari 8+, and Edge 79+ — around 96% of browsers per caniuse. The catch is size: APNG has no motion compensation either, so it is not the format to pick when the file has to stay small.
Because the recording is interlaced. AVCHD specifies 60i and 50i modes and a great many consumer camcorders shipped set to 1080i, where each frame is woven from two fields captured a fraction of a second apart. Flatten that into a progressive GIF frame and moving edges show comb teeth. There is no deinterlacing step anywhere in this pipeline — no framerate, resolution, or quality setting introduces one, and converting to MP4 first does not help either, because the combing is already part of the frames. Either pick a low-motion segment where the two fields nearly agree, or deinterlace in a desktop editor and make the GIF from that progressive export.
That is AVCHD's anamorphic mode. The specification allows 1440×1080 alongside 1920×1080, and the 1440-wide modes record non-square pixels intended to be stretched back to 16:9 during playback. GIF has no way to carry that stretch instruction, and this converter applies no pixel-aspect correction, so the frames keep their literal geometry and read as horizontally compressed. Correct it explicitly: under File Compression → Custom → Image resolution, choose Width x Height and enter a 16:9 pair such as 854 × 480. Clips recorded at a native 1920×1080 are unaffected.
No. On this page the resolution preset is applied as a maximum — Use as max resolution is enabled for video-to-GIF conversions — so choosing 480p shrinks a 1080p source down to 480p but leaves anything already smaller exactly as it is. That is deliberate: upscaling a GIF adds pixels and file size without adding any detail. If you genuinely need a larger output, set the dimensions yourself with Width x Height (File Compression → Custom).
.MTS and .m2ts are the same BDAV transport stream — camcorders write the short 8.3-style .MTS name on the memory card, and the same clip usually appears as .m2ts once copied to a computer — but this page accepts .m2ts only. Send camcorder-named footage to MTS to GIF, or rename the file, since the bytes are identical. Whichever route you take, your upload travels over an encrypted connection, is processed on our servers, and is deleted automatically after a few hours — no sign-up, no watermark, never shared or made public. There is no fixed size cap; on a long HD recording, upload time is the real constraint.