Convert M4V to TS — Free Online Tool
Convert M4V files — Apple's iTunes-compatible MPEG-4 video format — to MPEG-2 Transport Stream (TS), a robust container built for broadcast and live streaming workflows. This conversion re-encodes the video with H.264 and packages audio as AAC, making your iTunes content compatible with HLS pipelines, broadcast systems, and tools that expect standard TS segments.
to
FFmpeg Command
Copy this command to run the same conversion locally with FFmpeg on your desktop. Download FFmpeg
Drop your M4V file here
or click to browse
Free — no uploads, no signups. Your files never leave your browser.
Settings
Note: Browser-based encoding uses approximate quality targets. For precise CRF compression, copy the FFmpeg command above and run it on your desktop.
Estimated output:
Conversion Complete!
DownloadHow It Works
M4V is essentially a standard MP4 container with Apple-specific extensions, typically holding H.264 video and AAC audio. During this conversion, the H.264 video stream is re-encoded using libx264 at CRF 23 (rather than stream-copied) because the TS container uses a fundamentally different bitstream framing and packetization model — it structures data into fixed 188-byte transport packets designed for transmission reliability. The AAC audio is similarly re-encoded at 128k. Critically, the TS format does not support chapters, so any chapter markers embedded in the M4V will be silently dropped. Apple FairPlay DRM-protected M4V files cannot be converted — only DRM-free M4V files will process successfully.
What Each Flag Does
| Flag | What it does |
|---|---|
ffmpeg
|
Invokes the FFmpeg binary — the open-source multimedia processing engine that powers this conversion both in the browser (via FFmpeg.wasm) and on the desktop command line. |
-i input.m4v
|
Specifies the input file as an M4V — Apple's MPEG-4 based video container. FFmpeg will detect its internal streams (typically H.264 video and AAC audio) and use them as the source for re-encoding. |
-c:v libx264
|
Sets the video encoder to libx264, re-encoding the video stream as H.264 for the TS output. Even though the M4V source is also likely H.264, a full re-encode is required because the TS container uses different bitstream packetization than the MP4/M4V family. |
-c:a aac
|
Re-encodes the audio track using FFmpeg's native AAC encoder, producing an AAC stream compatible with the TS container and with HLS-based streaming systems that expect H.264 + AAC transport streams. |
-crf 23
|
Sets the Constant Rate Factor for libx264 to 23, which is the default quality level. This controls the trade-off between visual quality and file size — lower values like 18 produce higher quality at larger file sizes, while values like 28 reduce size with some perceptible quality loss. |
-b:a 128k
|
Sets the AAC audio bitrate to 128 kilobits per second, a standard quality level appropriate for most speech and music content in broadcast and streaming TS files. |
output.ts
|
Defines the output file with a .ts extension, telling FFmpeg to mux the re-encoded H.264 video and AAC audio into an MPEG-2 Transport Stream container — the format used by broadcast systems, HLS pipelines, and IPTV delivery. |
Common Use Cases
- Preparing iTunes-purchased or exported M4V video for ingestion into an HLS (HTTP Live Streaming) pipeline, which expects TS-segmented content
- Feeding DRM-free M4V content into broadcast playout software or hardware encoders that accept MPEG-2 TS as their primary input format
- Converting Apple-exported M4V recordings into TS files for use with DVB or IPTV distribution systems that require transport stream packaging
- Stripping Apple-specific container metadata and structure from M4V files to produce a clean, universally compatible TS file for archival in broadcast storage systems
- Testing or debugging video pipelines that consume TS streams by converting a known-good M4V source file into TS for use as test input
- Converting M4V video exports from Final Cut Pro or iTunes into TS format for compatibility with streaming servers like Wowza or Nginx-RTMP
Frequently Asked Questions
Yes, some generation loss is expected because the video is re-encoded rather than remuxed. M4V files typically contain H.264 video that is already compressed, so re-encoding with libx264 at CRF 23 introduces a second round of lossy compression. For most content at standard resolutions, the difference at CRF 23 is subtle, but if you need to minimize quality loss you should lower the CRF value (e.g., CRF 18) at the cost of a larger output file.
No — chapter data will be lost. The MPEG-2 Transport Stream format does not support embedded chapter markers in the way that M4V (and its parent MP4 format) does. If your M4V file contains iTunes chapter data, those markers will not be present in the output TS file. If chapters are important, consider converting to a format like MKV or MP4 instead, both of which support chapter metadata.
No. M4V files protected by Apple FairPlay DRM are encrypted and cannot be decoded or re-encoded by FFmpeg or any other standard tool without authorization. This converter — and the underlying FFmpeg command — will only work on DRM-free M4V files, such as those exported from Final Cut Pro, Handbrake, or iTunes-matched content that has had DRM removed by the rights holder.
MPEG-2 Transport Stream has inherent overhead from its fixed 188-byte packet structure, which includes error correction headers and synchronization bytes that don't exist in the M4V/MP4 container. Additionally, if the original M4V was encoded at a lower bitrate or higher CRF than the output settings, the re-encode may produce a different file size. You can increase the CRF value (e.g., CRF 28) to reduce file size, trading a small amount of quality.
To adjust video quality, change the '-crf 23' value — lower numbers (e.g., 18) produce higher quality and larger files, while higher numbers (e.g., 28) reduce file size with some quality trade-off. For audio quality, replace '128k' in '-b:a 128k' with a higher bitrate like '192k' or '256k'. For example: 'ffmpeg -i input.m4v -c:v libx264 -c:a aac -crf 18 -b:a 192k output.ts' would produce a noticeably higher-quality output suitable for broadcast use.
Yes — MPEG-2 TS with H.264 video and AAC audio is exactly the segment format used by HLS (HTTP Live Streaming), which is the standard Apple originally designed for iOS and Safari delivery. The output from this conversion can be used directly as TS segments in an HLS playlist (.m3u8), or fed into a segmenter tool. This makes the M4V-to-TS conversion particularly useful for preparing Apple-originated content for CDN-based adaptive streaming.
Technical Notes
M4V and TS are structurally very different containers despite both commonly carrying H.264 and AAC streams. M4V uses the ISO Base Media File Format (like MP4), storing data in a hierarchical 'box' structure with a moov atom that describes the entire file — this is why M4V works well for progressive download with the '-movflags +faststart' optimization, but is not used for live streaming. TS, by contrast, is a streaming-first format that multiplexes audio and video into a continuous stream of 188-byte packets, each with a Program ID (PID) and continuity counter to allow synchronization even if packets are received out of order or with gaps — essential for broadcast and live delivery. Because of this structural difference, a simple remux is not possible; the bitstreams must be repackaged with full re-encoding. The TS format also lacks a native chapter index structure, so any iTunes chapter metadata present in the M4V will be discarded entirely. Multiple audio tracks from the source M4V are theoretically preservable since TS supports multiple audio PIDs, but the FFmpeg command as written maps only the default streams — use '-map 0' to carry all tracks. The absence of '-movflags +faststart' in the TS output is correct and intentional, as that flag is specific to the MP4/M4V container family.