Add your MP4 file
Drop one or more .mp4 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.
Pulling the soundtrack out of a .mp4 video into .ts audio keeps what you can hear and drops the picture entirely. 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.Pulling the soundtrack out of a .mp4 video into .ts audio keeps what you can hear and drops the picture entirely. An .mp4 file is a multimedia container that bundles compressed video, audio, subtitles, and chapter data into a single stream-friendly package. It is the default delivery format for nearly every phone, camera, and video platform, which makes .mp4 the safest target when a clip has to play everywhere.
A .ts file is an MPEG transport stream, the packetized format built to carry television through unreliable channels like antennas, satellites, and cable. DVR recordings, IPTV captures, and HLS streaming segments all use .ts, making it one of the most common raw broadcast formats people encounter. For this route the practical draw is corruption costs a fraction of a second, not the whole file and trivially concatenable without remuxing — balanced against packet overhead runs several percent above an equivalent MP4, which is worth knowing before you commit a large batch.
The usual reason to take .ts audio out of a .mp4 file is that only the sound matters — a talk, interview, song, or podcast segment. Keeping the video stream would waste storage, and a dedicated audio file is easier to trim, tag, and play. On the source side, fewer track, attachment, and chapter features than Matroska; on the target side, the payoff is corruption costs a fraction of a second, not the whole file, which is exactly what you want for saving recordings from DVRs and set-top boxes.
| Aspect | MP4 video (.mp4) | MPEG transport stream (.ts) |
|---|---|---|
| Format type | Container — quality depends on the codecs and settings inside | Container — quality depends on the codecs and settings inside |
| How it stores data | typically carries H.264/AVC or H.265/HEVC video with AAC audio, though the box structure also accepts AV1, MP3, and timed-text tracks | fixed 188-byte packets with sync bytes and continuity counters allow receivers to detect and skip corrupted data |
| Strongest at | publishing video to the web, social media, or a client who has not specified a format | saving recordings from DVRs and set-top boxes |
| Weak spot | fewer track, attachment, and chapter features than Matroska | packet overhead runs several percent above an equivalent MP4 |
| Metadata | iTunes-style metadata atoms (title, artist, cover art) plus XMP and per-track language tags; ID3 is not native to the container | broadcast service tables (SDT/EIT) can carry channel names and program-guide data, but there is no field for user tagging |
Drop one or more .mp4 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 .ts in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if TS is selectable, the route is real and validated.
Press Convert. A WebAssembly FFmpeg build demuxes the audio track and re-encodes it locally; the video stream is simply discarded.
Each result is signature-checked before the download unlocks, so a failed encode can never masquerade as a valid TS file. Outputs keep the original filename with the .ts extension.
Since mp4 is container-oriented and ts is container-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .ts itself requires.
Yes — the .mp4 file is processed inside your browser tab and never uploaded. A WebAssembly FFmpeg build demuxes the audio track and re-encodes it locally; the video stream is simply discarded. Close the tab and the file is gone from memory.
VLC, ffmpeg, and every broadcast tool read .ts natively, and smart TVs often play recordings made by their own tuners. Browsers only consume transport streams indirectly through JavaScript HLS players, so standalone .ts files need conversion for the web.
Much smaller — the video stream is usually 80–95% of a .mp4 file's weight, and it is discarded entirely. The remaining audio is re-encoded at the bitrate implied by your quality setting.
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, iTunes-style metadata atoms (title, artist, cover art) plus XMP and per-track language tags; ID3 is not native to the container; 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 .mp4 → .ts → .mp4 is not a perfect undo when any lossy step is involved; keep your original if fidelity matters.