M2TS to WebM Converter

M2TS to WebM Converter

.m2ts is a delivery-and-capture format: the BDAV MPEG-2 transport stream that Blu-ray discs use and that AVCHD camcorders write to memory cards. WebM is the opposite kind of thing — a deliberately small, royalty-free format built for HTML5 <video> playback on the open web. The two share no codecs at all, so this conversion is a genuine re-encode of both streams, not a re-wrap. The reference tables below spell out what each format is before the how-to, because on this pair the codec facts are what decide your settings.

M2TS at a Glance

WebM at a Glance

How to Convert M2TS to WebM

1. Upload Your M2TS File: Drag the .m2ts onto the page or click "+ Add Files". Blu-ray and camcorder imports often appear as numbered streams such as 00001.m2ts inside a BDMV/STREAM folder; queue several at once if you want them all converted with the same settings.
2. Pick the Video Codec and Audio Codec: Video Codec starts on VP9, the modern default, with VP8 (faster to encode, decoded by older devices) and AV1 (smallest files, slowest encode) as alternatives. Audio Codec starts on Opus, with Vorbis as the older-compatibility option.
3. Set Quality, Resolution, or Trim: Under File Compression the Preset dropdown starts on "Very High (Recommended)"; switch to Specific file size, Constant Bitrate, Variable Bitrate, Constant Quality, or Constraint Quality if you need a size or rate target. Video resolution starts on Keep original, and Trim → Time Range takes a start time plus a duration.
4. Convert and Download: Click Convert and save the .webm. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours. No sign-up, no watermark.

Frequently Asked Questions

Will I lose quality converting M2TS to WebM?

Some, unavoidably. WebM does not permit H.264, so the video has to be decoded and encoded again as VP9, VP8, or AV1, and that second generation costs detail no container change could preserve. In practice the loss is hard to see at the Very High preset, because VP9 reaches comparable visual quality at a much lower bitrate than the up-to-24 Mbps transport streams AVCHD produces. Raise the preset to Highest if the output will be edited again later.

Should I choose VP9, VP8, or AV1?

VP9 is the sensible default and is what the page starts on: broad browser support, good compression, reasonable encode time. Choose VP8 only if you are targeting genuinely old devices, since it compresses noticeably worse. Choose AV1 when file size matters more than anything and your audience is on current browsers — it encodes far more slowly and Safari's support is still partial, so it is a poor fit for a general-purpose embed.

My M2TS is 1080i. Will the WebM show combing?

It can. AVCHD camcorders commonly record 1080i, where each frame holds two fields captured a fraction of a second apart, and nothing in this pipeline deinterlaces — the field structure is re-encoded as it stands, so fast motion can show comb-tooth lines on a progressive web player. Deinterlace in a desktop editor first and convert the progressive export here if that matters. The same applies to anamorphic 1440×1080 material: picking a resolution option squares off the pixel aspect, so set Width × Height explicitly (1920 × 1080) when the geometry has to be right.

Does my M2TS soundtrack carry over, and in what codec?

Yes, but re-encoded. AVCHD carries Dolby AC-3 or linear PCM, and Blu-ray may add DTS — WebM allows none of them, so the track is transcoded to Opus by default or Vorbis if you select it. The audio stays in sync; it is simply moved into a codec the container permits. Opus is the better choice unless you specifically need to support something that predates it.

Will the WebM play on iPhones and in Safari?

On current versions, yes. Desktop Safari added WebM in version 16 and iOS Safari in 17.4, joining Chrome 25+, Firefox 28+, and Edge 79+ for roughly 96% coverage. Older iPhones, most smart TVs, and most social platforms will not take a .webm at all, so if the file has to play everywhere rather than in a browser, M2TS to MP4 is the right target instead.

Why is my WebM so much smaller than the M2TS?

Because you started from a capture format and ended in a delivery format. AVCHD records at up to 24 Mbps to keep editing headroom, while VP9 was designed to hit comparable perceived quality at a fraction of that rate. The exact ratio depends on resolution, motion, and the source bitrate. If the result is still too large for your page, run it through our WebM compressor or drop the Quality Preset a step before converting.

Can I convert a .mts file here too, or a whole Blu-ray folder?

A .mts file is the same BDAV stream under a different extension, so use MTS to WebM for the matching page. A Blu-ray or AVCHD folder is not a single file, though — you upload the individual stream files from BDMV/STREAM, one clip at a time. Long recordings sometimes split across several numbered streams, in which case each converts separately.

Why did the conversion fail on a file from a retail disc?

Almost certainly AACS encryption, sometimes with BD+ layered on. A protected stream cannot be decoded by any converter, so the job fails rather than producing a scrambled result. Unprotected sources — camcorder footage, your own renders, legally decrypted files — convert normally. A partially-copied .m2ts fails the same way, because the transport stream ends mid-packet.

Does the converter change HDR footage or handle it specially?

No. There is no tone-mapping stage in this pipeline, so high dynamic range material gets an ordinary colour conversion and can look flat or washed out compared with the source. Most AVCHD camcorder footage is standard dynamic range and is unaffected; if you are starting from an HDR Blu-ray stream, grade it in a desktop tool before converting.

How are my files handled, and how large can they be?

The practical limit is upload time rather than a processing tier — a multi-gigabyte transport stream takes a while to reach the server, so trimming first with our video cutter is often faster than sending the whole recording. Files travel over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours. They are never shared or made public, and no account is required.