Initializing... drag & drop files here
Supports: MOV
A QuickTime .mov is built to be stored, scrubbed and edited; an MPEG transport stream is built to be sent. TS chops the same audio and video into fixed 188-byte packets, repeats its program tables continuously, and expects that some of those packets will be lost — which is exactly what satellite, terrestrial, IPTV and HTTP streaming pipelines need, and exactly what a local file does not. The short answer: convert to TS when the file is going into a broadcast chain, a set-top box or PVR, or an HLS packager. Stay on MOV or MP4 for anything you will edit, upload or simply hand to somebody.
| Property | MOV (QuickTime) | TS (MPEG Transport Stream) |
|---|---|---|
| Origin | Apple's QuickTime container, introduced December 1991 | The MPEG-2 systems layer — ISO/IEC 13818-1, also published as ITU-T H.222.0, first issued 1995 and still maintained (current edition 04/2025) |
| Internal structure | A hierarchy of atoms with an index; the file must be largely intact to play | A flat run of fixed 188-byte packets, each starting with a 0x47 sync byte |
| Behaviour on damage | An index or header loss can break the whole file | A player resynchronises on the next sync byte and keeps going |
| Random access | Index-driven and frame-accurate | By resynchronising to the stream; less precise, no index to consult |
| Video codecs offered here | Source side: usually H.264, HEVC or ProRes | H.264 (preselected), H.265, MPEG-1, MPEG-2, MPEG-4, Xvid, DivX |
| Audio codecs offered here | Source side: usually AAC, sometimes PCM or ALAC | AAC (preselected), AC3, EAC3, DTS (DCA), MP2, MP3 |
| Chapters, timecode, rich metadata | Yes | No — the container carries program and timing tables, not authoring metadata |
| Size at equal quality | Baseline | Slightly larger; per-packet headers and repeated program tables cost a few percent |
| Where it belongs | Editing, archiving, handing to a person | Broadcast (DVB/ATSC), IPTV, PVR ingest, HLS segments |
.ts written here contains: one program, a program association table on PID 0 and a program map table alongside it.Stay on MP4 or MOV when…
.MOV, .MPEG-1, .MPEG-2, .MPEG4, .MP4, .MPG, .AVI, .WMV, .MPEGPS, .FLV, 3GPP, WebM, DNxHR, ProRes, CineForm and HEVC — .ts is not on it. Use MOV to MP4 instead..ts, but seeking through one is slower and less exact than through an indexed file..mov onto the page or click "+ Add Files" to pick one or several. Each file is uploaded over an encrypted connection and converted on our servers, with the same settings applied across the batch..ts. No sign-up, no watermark; your upload and the finished file are both deleted from our servers automatically after a few hours.These two extensions are frequently treated as interchangeable and are not. A plain transport stream packet is 188 bytes and begins with the 0x47 sync byte; the BDAV variant used on Blu-ray and AVCHD prefixes each packet with a four-byte arrival timestamp, making 192-byte packets whose sync byte sits at offset 4. Our converter follows the extension you ask for, so this page writes plain 188-byte packets and MOV to M2TS writes the BDAV framing.
.ts (this page) |
.m2ts |
|
|---|---|---|
| Packet size | 188 bytes | 192 bytes (188 + 4-byte timestamp prefix) |
| First byte of file | 0x47 sync | 0x0e header byte, sync at offset 4 |
| Built for | Broadcast, IPTV, HLS segments, PVR ingest | Blu-ray BDAV and AVCHD disc structures |
| Caveat | Not a disc structure on its own | Also not a disc structure — a single .m2ts has no BDMV/STREAM layout, and our AAC default is not BDAV-legal audio |
Because the two containers are designed around opposite assumptions. MP4 and MOV assume the whole file arrives and can be indexed; TS assumes a stream that may lose packets and must keep playing anyway, which is why it repeats its program tables and uses a fixed packet size with a sync byte to lock onto. If your file is going into a broadcast, IPTV or HLS pipeline, that structure is the entire point. If it is going onto a hard drive or a website's download link, it is pure overhead.
Yes, a little, because this is a re-encode rather than a container swap — our server decodes the video and encodes it again into the transport stream; it never copies the original stream through untouched. With Video Codec left on H.264 and the Quality Preset high, the loss is generally not visible, and the output lands close in size to an equivalent H.264 MP4 plus a few percent of packet overhead. If you need a true bit-preserving remux, that is a job for a local tool such as ffmpeg with stream copy.
H.264 video with AAC audio — the pair this page already preselects. RFC 8216 lists MPEG-2 transport streams as an HLS media segment format and requires each segment to contain a single program with a PAT and PMT; the files written here satisfy that. What this page does not do is segment the stream or write the .m3u8 playlist, so you still need a packager to slice the output into short segments and generate the manifest.
VLC, MPV and most desktop players open .ts directly, and a great many smart TVs, media boxes and PVRs treat it as a native format. Web browsers do not — there is no <video> support for raw transport streams, which is why HLS exists as a delivery layer on top. If you simply want a file that plays everywhere without explanation, convert the other direction with TS to MP4.
No. A transport stream carries the tables a decoder needs — program association, program map, timing and program clock references — and has no equivalent of QuickTime's chapter tracks, creation metadata or authoring tags. Anything of that kind is dropped in the conversion. Keep the original .mov or an MP4 master alongside the transport stream if that information matters.
Two reasons stack up. Every 188-byte packet spends four bytes on its header, and the muxer repeats the program tables at regular intervals so a receiver tuning in mid-stream can start decoding — both are the cost of being resilient to loss. On top of that, the re-encode targets your chosen quality rather than the source's exact bitrate. Lowering the Quality Preset or setting an explicit bitrate closes the gap.
Yes — MPEG-2 is in the Video Codec list precisely for that. Be aware that MPEG-2 has no CRF mode, so the Constant Quality and Constraint Quality sliders do nothing when it is selected and the encoder falls back to a bitrate derived from the output frame size. With MPEG-2 chosen, set the frame size and an explicit bitrate rather than reaching for a quality slider.
The real constraint is upload size and time rather than anything on your end, so for a long recording the Trim control — a start time plus a duration, in seconds or HH:MM:SS.sss — is the quickest route to the part you actually need. Files travel over an encrypted connection, are converted on our servers, and both the upload and the result are deleted automatically after a few hours. Nothing is shared or made public, there is no sign-up, and no watermark is added.