MTS to WebM Converter

How to Convert MTS to WebM Online

1. Upload Your MTS File: Drag and drop or click "Add Files" to select MTS or M2TS files straight off your AVCHD camcorder's SD card or BDMV/STREAM folder. Sony Handycam, Panasonic Lumix, Canon VIXIA, and JVC Everio recordings all work. Batch is supported — drop in a whole shoot's worth of clips.
2. Pick a Codec and Quality: Default is VP9 (Google's modern web video codec). Choose AV1 for the smallest output on modern devices, or VP8 for legacy compatibility. Set a Quality Preset (Highest → Lowest), target a percentage of the original size or an exact size in MB, or fine-tune with CRF on the VP9/AV1 scale (15 = visually lossless, 30 = default for web, 36 = small).
3. Resize or Trim (Optional): Pick a resolution preset (1080p / 720p / 480p / 360p), enter custom width × height, scale by percentage, or trim in HH:MM:SS.sss using start time + duration to extract just the segment you need.
4. 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 Convert MTS to WebM?

MTS (and its sibling M2TS) is the AVCHD container used by Sony, Panasonic, Canon, and JVC camcorders since the format launched in 2006. It's H.264 video plus AC-3 / LPCM audio in an MPEG-2 transport stream — designed for Blu-ray-style playback, not the modern web. WebM (VP9 / AV1 / VP8 video, Opus / Vorbis audio) is the open-source format Google designed specifically for HTML5 <video> tags. It's smaller than MTS at the same quality and royalty-free. Common reasons to convert MTS → WebM:

• Self-hosting old camcorder footage — That tub of MTS files from a 2010 Sony HDR-CX160 won't play in any browser. Re-encoded to WebM, the same footage embeds in a personal site, family archive, or Memorial page with a single <video src="reunion-2012.webm"> tag.
• HTML5 <video> embedding without YouTube — Browsers will not play.mts natively. WebM is the de-facto open web format — the <source type="video/webm"> tag works in Chrome, Firefox, Edge, Opera, and Safari 14.1+ with no plugin and no third-party hosting.
• Smaller files for the web — AVCHD MTS at 1080p typically lands at 17-24 Mbps. VP9-WebM at the same visual quality is usually 30-50% smaller. AV1 cuts another ~30% on top. For a hobby site on a $5/month VPS, that's the difference between viable and not.
• Royalty-free codec for commercial use — H.264 inside MTS is patent-encumbered. WebM (VP8 / VP9 / AV1) has no licensing fees, which matters for commercial streaming, paid platforms, and embedded video in apps.
• Background loops and hero videos — A muted, autoplaying camcorder clip behind a landing-page hero needs to be small and fast. WebM loads in a fraction of the time MTS would, even if browsers could play MTS at all (they can't).
• Linux and open-source toolchain compatibility — Many CMS plugins, static site generators, and open-source video pipelines (Hugo, Jekyll, Plyr, Video.js) handle WebM natively but stumble on the AVCHD transport stream wrapper.

MTS vs WebM — Format Comparison

Codec Choice for the WebM Output

Frequently Asked Questions

Will the interlaced AVCHD footage convert cleanly?

Older Sony / Panasonic AVCHD camcorders shoot 1080i (interlaced) at 50i / 60i. The conversion deinterlaces by default so the WebM plays smoothly on progressive-scan browsers. If your source is already 1080p (most 2014+ camcorders), no deinterlacing is applied and the original frame structure is preserved.

Why is my.mts file so much bigger than the WebM I get back?

AVCHD records at 17-24 Mbps to keep camera-side encoding fast and edit-friendly. VP9 and AV1 use modern compression techniques (better motion prediction, larger coding blocks) that recover the same visual quality at a fraction of the bitrate. For self-hosted family footage that's a feature, not a bug — same picture, smaller file, faster page load.

Should I pick VP9, AV1, or VP8?

VP9 for almost everything — universal modern browser support, 30-50% smaller than the H.264 inside your MTS, encodes fast in the browser. AV1 for the smallest possible files when audience is on 2022+ devices — encoding takes 5-10x longer but file is roughly half the size. VP8 only for very old Android devices or extremely conservative legacy compatibility (rare in 2026).

Will Safari play my WebM?

Safari 14.1+ (macOS Big Sur, iOS 14.5+) plays WebM with VP9. For older Safari, embed both formats in your <video> tag — WebM first, MP4 fallback second. Modern Safari picks the WebM; older Safari falls back. See also MTS to MP4 for the fallback file.

Can I batch convert a whole BDMV/STREAM folder?

Yes. AVCHD camcorders write a BDMV/STREAM/ directory full of sequentially numbered.mts clips (00001.MTS, 00002.MTS, etc.). Drop the whole folder — every.mts is queued, converted in parallel withon our servers, and downloads individually or as a single ZIP.

What about M2TS files from a Blu-ray rip or AVCHD disc?

Same workflow. M2TS is structurally identical to MTS (just a different file extension used inside the AVCHD/Blu-ray BDMV directory). The converter accepts both. If your source is a full disc, see also Convert M2TS to WebM for the format-specific landing page.

Will the audio track come through?

Yes. AVCHD audio is typically AC-3 (Dolby Digital) at 256-384 kbps or LPCM. Both are re-encoded to Opus (default for WebM) or Vorbis. Opus at 96-128 kbps is transparent — for camcorder audio, the result is indistinguishable from the source. If your MTS has multiple audio tracks (5.1 surround on prosumer rigs), the primary track is kept and downmixed to stereo.

Can I trim part of an MTS clip while converting?

Yes. Use the trim section to enter a start time and duration. Both accept seconds (2.5) or HH:MM:SS.sss (00:00:02.500). Trimming first means the encoder does less work and the output is smaller. For a pure-trim pass with no codec change, see Trim MTS.

What's the file size limit?

XConvert handles large MTS files including 30-minute camcorder clips and multi-GB AVCHD discs. Conversion runs on our servers, so the practical limit is upload size and connection speed and patience for the upload. No fixed cap, no quantity limit on batch jobs, no watermark.