Add your MTS file
Drop one or more .mts files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Converting .mts video to .mov means re-encoding the picture and sound into a different container and codec family, and this page does it entirely in your browser. Free, private, and validated — the file never leaves your browser.
Batch files can each use a different output. Nothing uploads for local conversions.
Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.Converting .mts video to .mov means re-encoding the picture and sound into a different container and codec family, and this page does it entirely in your browser. An .mts file is AVCHD footage as written to a camcorder's memory card, containing H.264 video inside an MPEG transport stream. Sony and Panasonic camcorders from the late 2000s onward filled SD cards with .mts clips, so the extension is familiar to anyone importing family or event video.
A .mov file is Apple's QuickTime movie container, which stores video, audio, text, and timecode tracks in a flexible atom-based layout. iPhones, iPads, and professional cameras that record ProRes all write .mov, so the extension shows up constantly in editing workflows. For this route the practical draw is first-class treatment on every Apple platform and ideal editing intermediate when paired with ProRes — balanced against proRes recordings consume enormous disk space, which is worth knowing before you commit a large batch.
The practical trigger for this conversion is usually a mismatch: with .mts, transport-stream packet overhead makes files larger than the same video in MP4. Switching to .mov buys you first-class treatment on every Apple platform, which is why it is the better fit for importing iPhone footage into an edit without conversion. Because the conversion runs locally, trying it costs nothing but a few seconds of compute on your own machine.
| Aspect | AVCHD video (.mts) | QuickTime video (.mov) |
|---|---|---|
| Format type | Container — quality depends on the codecs and settings inside | Container — quality depends on the codecs and settings inside |
| How it stores data | uses 192-byte transport packets, standard 188-byte packets plus a 4-byte arrival timestamp, matching Blu-ray's BDAV layout | media lives in a hierarchy of atoms, each declaring its own size and type, which makes the format easy to extend |
| Strongest at | importing camcorder footage into Premiere, Resolve, or Final Cut | importing iPhone footage into an edit without conversion |
| Weak spot | transport-stream packet overhead makes files larger than the same video in MP4 | proRes recordings consume enormous disk space |
| Metadata | recording date, camera settings, and GPS coordinates on some models are stored in the AVCHD folder's clip-info files rather than in the .mts stream itself | quickTime metadata atoms and keys, including camera model, location, and timecode data written by iPhones and professional cameras |
Drop one or more .mts files onto the converter above, or browse for them. They load into browser memory only — nothing is uploaded, so there is no size-based pricing and no server queue.
Select .mov in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if MOV is selectable, the route is real and validated.
Press Convert. The conversion runs on an FFmpeg engine compiled to WebAssembly, executing entirely inside your browser tab.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid MOV file. Outputs keep the original filename with the .mov extension.
Both sides are re-encoded, so expect a small generation loss controlled by the quality setting: mts is container-oriented and mov is container-oriented. For visually or audibly transparent results keep quality high; for smaller files lower it and compare.
Yes — the .mts file is processed inside your browser tab and never uploaded. The conversion runs on an FFmpeg engine compiled to WebAssembly, executing entirely inside your browser tab. Close the tab and the file is gone from memory.
macOS and iOS treat .mov as a native format, and Windows plays H.264 variants through modern Media Player builds and most editors. On the web the container is unreliable, so re-wrapping to MP4 remains the standard route for online publishing.
It depends on the content: media lives in a hierarchy of atoms, each declaring its own size and type, which makes the format easy to extend. Convert one representative file first and compare before batch-processing a large set.
This converter strips container metadata deliberately (the FFmpeg command runs with metadata mapping disabled) so exported files do not leak recording details. In the source, recording date, camera settings, and GPS coordinates on some models are stored in the AVCHD folder's clip-info files rather than in the .mts stream itself; none of it is transmitted anywhere because the file never leaves your browser.
Yes — the reverse route exists as a separate tool. Bear in mind that round-tripping .mts → .mov → .mts is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.