How to Re-encode M2TS Online
- Upload Your M2TS File: Drag and drop or click "Add Files" to select your
.m2tsrecording from a Blu-ray rip or AVCHD camcorder (Sony, Panasonic, Canon, JVC). Batch processing is supported — queue multiple clips and they re-encode in the same session. - Pick Video Codec and File Compression: Under Video Codec, the default is H.264 — switch to H.265/HEVC for roughly 40-50% smaller files at equivalent perceived quality, or to MPEG-2 if you need strict legacy Blu-ray authoring compliance. Under File Compression choose Quality Preset (Highest through Lowest), Specific file size (MB/KB target with auto-scaling), Constant Bitrate, Variable Bitrate, Constant Quality (CRF 18-22 broadcast for H.264, 20-26 for H.265), or Constraint Quality.
- Resolution, Audio Codec, and Trim (Optional): Under Video Resolution, Keep original or pick a Preset (2160p, 1440p, 1080p, 720p, 480p), Resolution Percentage, Width, Height, or Width × Height. Under Audio Codec, AAC is default; AC3 (Dolby Digital) and DTS (DCA) are available for Blu-ray-style soundtracks. Under Trim, switch from Unchanged to Time Range and enter Start Time + Duration to keep only the segment you want.
- Convert and Download: Click Convert. 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.
Why Re-encode M2TS to M2TS?
M2TS (BDAV MPEG-2 Transport Stream) was introduced by the Blu-ray Disc Association in August 2004 and is the native container for Blu-ray discs and AVCHD camcorders from Sony, Panasonic, Canon, and JVC. Re-encoding M2TS to M2TS keeps the same .m2ts wrapper your authoring tool, set-top player, or NAS expects while you change what's inside — the codec, bitrate, resolution, or duration.
- Shrink Blu-ray rips for archival — A full 1080p Blu-ray title runs 20-40 GB. Re-encoding the H.264 stream to H.265 at CRF 22-24 typically cuts the file in half (10-20 GB) with no visible quality loss on consumer displays, which fits comfortably on a single-layer 25 GB disc or external drive partition.
- Compress AVCHD camcorder footage — Consumer AVCHD camcorders record at up to 28 Mbps for 1080p60 and 24 Mbps for 1080p30 (AVCHD 2.0 spec). A one-hour reel is 10-12 GB; dropping to a 50% target file size or switching codec to H.265 makes the same hour fit on a 6 GB cloud upload slot.
- Upgrade legacy MPEG-2 streams — Older Blu-ray titles and first-generation AVCHD camcorders used H.262/MPEG-2 video. Switching to H.264 typically halves the file at matching visual quality; H.265 halves it again.
- Trim multi-hour AVCHD recordings — Camcorder reels often capture an entire event in one file. Time Range trim lets you pull a single dance, speech, or innings without spinning up a full NLE.
- Normalize mixed-codec libraries — A media library with H.262, H.264, and VC-1 M2TS files can choke older Blu-ray players that only fast-forward cleanly on one codec. Re-encoding everything to H.264 AAC at a fixed bitrate gives a consistent playback profile.
- Lower resolution for slower hardware — Older standalone media players and TVs with USB playback often stutter on 1080p H.264 high-profile. Dropping to 720p and a Quality Preset of High produces a file that plays smoothly without re-mounting in a different container.
M2TS Codec and Quality Quick Guide
| Goal | Video Codec | File Compression | Notes |
|---|---|---|---|
| Smallest file, same quality | H.265 | Constant Quality CRF 22-24 | ~50% smaller than H.264 source |
| Maximum compatibility | H.264 | Quality Preset: Very High | Plays on every Blu-ray player |
| Half the file size | Keep current | Specific file size: 50% | Smart auto-scales bitrate |
| Legacy Blu-ray authoring | MPEG-2 (H.262) | Variable Bitrate ~25 Mbps | Strict BD-spec compliance |
| Cinema archival | H.264 | CRF 18 | Visually transparent |
| Camcorder reel for cloud | H.265 | Specific file size: 2 GB | Auto-scales bitrate to fit |
| Extract a clip | Unchanged codec | Trim: Time Range | Re-encodes the trimmed range |
M2TS vs Alternative Containers
| Property | M2TS | MTS | MP4 | MKV |
|---|---|---|---|---|
| Full name | BDAV MPEG-2 Transport Stream | AVCHD Transport Stream | MPEG-4 Part 14 | Matroska |
| Released | 2004 (Blu-ray Disc Assn) | 2006 (AVCHD spec) | 2003 (ISO/IEC) | 2002 |
| Packet header | 4-byte timestamp prefix | Raw 188-byte TS packet | ISO base media | EBML |
| Native use | Blu-ray BDMV/STREAM | AVCHD camcorders (8.3 filenames) | Web, mobile, streaming | Open-source archival |
| Video codecs (spec) | H.262, H.264, VC-1 | H.264 (AVCHD 2.0: also H.265) | H.264, H.265, AV1, MPEG-4 | Container-agnostic |
| Audio codecs (spec) | Dolby Digital, DTS, LPCM | Dolby Digital, LPCM | AAC, MP3, AC3, Opus | Container-agnostic |
| Streaming-friendly | Yes (built-in error recovery) | Yes | With fragmented MP4 | Limited |
| Chapter / menu support | Yes (with .mpls playlist) |
Limited | Yes | Yes |
If you actually need MP4 or MKV instead of staying in M2TS, see M2TS to MP4 and M2TS to MKV. For pure compression without changing settings yourself, Compress M2TS uses an auto-tuned preset.
Frequently Asked Questions
Will re-encoding M2TS to M2TS lose quality?
Yes — any lossy re-encode loses some information. Use Constant Quality (CRF 18-20 for H.264, 20-22 for H.265) or Quality Preset "Very High"/"Highest" to keep the loss below visual threshold on a 1080p consumer display. If you only need to trim and not re-compress, see the next question.
Can I trim without re-encoding?
True stream-copy trimming requires cutting on a keyframe boundary, which not every clip will allow at the second you want. Setting Trim to Time Range with the same codec/bitrate/resolution as the source minimizes re-encode artifacts. For a clean cut-only workflow, Trim M2TS is the right tool.
Should I switch to H.265 if my source is H.264?
If the destination plays H.265 (any Blu-ray UHD player, modern smart TV, recent NAS transcoder, all 2017+ iPhones and 2018+ Android flagships), yes — at CRF 22-24 you'll roughly halve the file with no visible loss. Stick with H.264 if you're feeding a 2012-era Blu-ray player, a legacy set-top recorder, or a device that lacks hardware HEVC decode (it'll stutter on CPU-only playback at 1080p).
Why is my converted M2TS still huge?
M2TS itself is just a container; the size is set by your video codec, bitrate, resolution, and duration. If you kept Quality Preset "Highest" on a 90-minute 1080p clip you'll get a 10-15 GB output. Switch to Specific file size with a 2-4 GB target (auto-scales bitrate), drop to CRF 24 on H.265, or lower the resolution to 720p.
What's the difference between M2TS and MTS?
Both contain the same MPEG-2 transport stream payload. M2TS adds a 4-byte timestamp prefix to each 188-byte TS packet (used by Blu-ray for accurate seeking) and uses long filenames; MTS is the raw stream variant AVCHD camcorders write with 8.3 filenames (00001.MTS). The audio and video bytes are interchangeable in most workflows — see MTS to M2TS if you need to rewrap.
Can I change the audio codec while keeping the M2TS container?
Yes. Under Audio Codec, switch from AAC to AC3 (Dolby Digital — the Blu-ray default), DTS (DCA), or PCM (uncompressed LPCM). AC3 and DTS keep AV-receiver passthrough working on home-theater setups; AAC is more efficient but bypasses passthrough on older receivers.
Will the output play on a standalone Blu-ray player?
Standalone Blu-ray players are picky: stick to H.264 (default) or MPEG-2 video, AC3 or LPCM audio, and 1080p or 720p resolution at standard Blu-ray bitrates (≤40 Mbps). Authoring to a burnable BDMV folder structure requires extra steps beyond this tool — the converted M2TS plays back fine when copied to a USB stick on most 2014+ players.
Can I batch-convert an entire AVCHD BDMV/STREAM folder?
Yes — drop multiple .m2ts files at once and the same codec, bitrate, and resolution settings apply to all. AVCHD camcorders split long recordings into 2 GB chunks (00001.m2ts, 00002.m2ts...); converting them individually keeps the split, while merging them in a separate step before conversion gives you a single output file.
Where does the conversion run, and are my files private?
Files are uploaded over an encrypted connection and converted on our servers, then deleted automatically after a few hours — they are not stored permanently and are not indexed or accessible by other users. There's no sign-up requirement, no watermark on the output, and no waiting in a queue behind paid users.