Initializing... drag & drop files here
Supports: AVCHD
AVCHD is the format Sony and Panasonic announced jointly in May 2006 and licensed from July 2006 for HD camcorders — H.264/MPEG-4 AVC video plus Dolby AC-3 (or linear PCM) audio inside an MPEG-2 transport stream, written as .mts or .m2ts. Original AVCHD caps at 24 Mbit/s; the 2011 "AVCHD Progressive" amendment added 1080/50p and 1080/60p at up to 28 Mbit/s. The format produces excellent quality at low bit rates, but the transport-stream container and consumer-camcorder folder layout (BDMV/STREAM) trip up older editors.
AVI is the opposite end of the timeline — Microsoft released it in November 1992 as part of Video for Windows, built on the RIFF chunk structure. It is intentionally codec-agnostic: the container holds whatever the codec writes, which is why it still works in software written before MP4 existed. Converting AVCHD to AVI is a deliberate compatibility downshift, useful when:
.mts outright or stutter on long-GOP H.264; an AVI re-wrap with a codec they recognise (Xvid, DivX, Cinepak, or uncompressed) lets them import cleanly..mts.If your goal is just modern playback or web upload, AVCHD to MP4 or AVCHD to MOV is the better path; choose AVI only when you specifically need the AVI container.
| Property | AVCHD (.mts /.m2ts) | AVI (.avi) |
|---|---|---|
| Released | May 2006 spec, July 2006 licensing (Sony + Panasonic) | November 1992 (Microsoft, Video for Windows) |
| Container | MPEG-2 Transport Stream | RIFF chunk format |
| Video codec | H.264 / MPEG-4 AVC (fixed) | Codec-agnostic — H.264, Xvid, DivX, MPEG-4 ASP, Cinepak, Indeo, MJPEG, uncompressed |
| Audio codec | Dolby AC-3 or linear PCM | Codec-agnostic — MP3, AC-3, PCM, more |
| Max video bitrate | 24 Mbit/s (1.0); 28 Mbit/s (2.0 Progressive, 2011) | Defined by the chosen codec |
| Resolutions | 720p, 1080i, 1080p (1080/60p in 2.0) | Any |
| Streaming-friendly | Yes — transport stream is designed for it | No — AVI predates streaming; VBR audio under 32 kHz is unreliable |
| Modern editor support | Strong (Premiere, Resolve, FCP, Vegas 2010+) | Universal but mostly via legacy code paths |
| Legacy / pre-2007 software | Rare | Near-universal on Windows |
| Typical 1 hour file | ~10–13 GB at 24 Mbit/s | Varies by codec — Xvid ~1–2 GB, uncompressed >100 GB |
| Goal | Pick | Notes |
|---|---|---|
| Editor that lists "DV-AVI" or "AVI" only | Constant Bitrate, lower bitrate | Older NLEs prefer simpler bitrate models |
| Visually lossless archive | Constant Quality (CRF 18) | Near-source quality; file size grows with motion |
| Roughly half-size copy | Target file size 50% | Predictable disk footprint for large camcorder dumps |
| Hard size cap (e.g. 700 MB CD, 4 GB FAT32) | Specific file size in MB | One-pass cap, useful for FAT32 and optical media |
| Want headroom for color/grade rework | Variable Bitrate, high ceiling | Lets bitrate spike during high-motion shots |
| Want a fixed quality with a sane ceiling | Constraint Quality (CRF + max bitrate) | Best when target hardware has a peak-bitrate limit |
Microsoft documented limited AVCHD support in Movie Maker but the long-GOP H.264 decoder it shipped with was unreliable on real-world camcorder transport streams; many users hit "can't import" or freezes. Re-wrapping the H.264 video into an AVI (or transcoding to a simpler codec like Xvid) sidesteps the decoder entirely and the clip imports as a regular AVI.
Sony Vegas Pro builds before roughly v10 (2010) handle Xvid and DivX MPEG-4 ASP cleanly. For Vegas 10 onward, H.264-in-AVI works but adds nothing over MP4. If the project still uses an older build, pick Xvid for the best size/quality balance, or MJPEG if the editor needs intra-frame editing.
Yes, depending on the codec. AVCHD's H.264 encoder is highly efficient (24 Mbit/s 1080p looks like 50+ Mbit/s in older codecs). An AVI written with Xvid or DivX at equal visual quality is typically 1.3–2× the size of the AVCHD source. Picking H.264-in-AVI keeps the size similar but loses most of the legacy-compatibility benefit you came for.
.mts clips at once?Yes — drag the individual .mts files into the page and they queue as a batch. Many camcorders split a long recording into 2 GB segments at the FAT32 boundary; you'll get one AVI per .mts segment. To stitch them into one continuous AVI, run them through a join step in your editor afterwards, or use a join tool before conversion.
Audio is re-encoded as part of the conversion. If the source carries 5.1 AC-3 (some Panasonic and Canon prosumer camcorders do), the AVI output stream is mixed/encoded based on the chosen audio settings — the converter typically targets a stereo track for compatibility. If you specifically need surround preserved, MOV or MKV containers are a better destination than AVI.
The source is decoded as 1080i; what happens next depends on your settings. If you keep the original resolution and don't deinterlace, the AVI carries interlaced frames (some editors handle them, others don't). For modern editing, deinterlacing to 1080p before encoding usually looks better and avoids combing artifacts on progressive displays.
Use the Trim → Time Range control in step 3. Enter a start time and an end time and the converter writes only that segment to the AVI. This is faster than a full re-encode of the whole tape and is the simplest way to pull individual scenes out of a 30-minute camcorder reel.
AVI is reasonable when the destination tool, hardware, or pipeline specifically requires it — legacy editors, kiosks, broadcast ingest, AviSynth/VirtualDub. For everything else (web, mobile, modern editors, streaming), AVCHD to MP4 is more efficient, supports modern audio codecs cleanly, and produces smaller files. If you only need to shrink the original, Compress AVCHD keeps the native container.
Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — no sign-up, no watermark, never shared. No watermark is applied, no sign-up is required, and the page does not retain your AVCHD or AVI files after conversion. If you also need to convert from .mts directly, MTS to AVI and M2TS to AVI target the same container.