Add your TS file
Drop one or more .ts 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 .ts video into .opus 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 .ts video into .opus audio keeps what you can hear and drops the picture entirely. 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.
An .opus file contains audio compressed with the Opus codec, stored in an Ogg container. Opus represents the current state of the art in lossy audio, beating MP3, AAC, and Vorbis in listening tests at nearly every bitrate from whisper-thin speech settings up to transparent music encoding. For this route the practical draw is best-in-class efficiency at essentially every bitrate and royalty-free with an open reference implementation — balanced against older car stereos, AV receivers, and MP3 players have never heard of it, which is worth knowing before you commit a large batch.
The usual reason to take .opus audio out of a .ts 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, packet overhead runs several percent above an equivalent MP4; on the target side, the payoff is best-in-class efficiency at essentially every bitrate, which is exactly what you want for compressing podcast and voice-chat audio to tiny files.
| Aspect | MPEG transport stream (.ts) | Opus audio (.opus) |
|---|---|---|
| Format type | Container — quality depends on the codecs and settings inside | Lossy — discards detail it judges invisible to shrink files |
| How it stores data | fixed 188-byte packets with sync bytes and continuity counters allow receivers to detect and skip corrupted data | the hybrid SILK/CELT design switches coding modes automatically based on content |
| Strongest at | saving recordings from DVRs and set-top boxes | compressing podcast and voice-chat audio to tiny files |
| Weak spot | packet overhead runs several percent above an equivalent MP4 | older car stereos, AV receivers, and MP3 players have never heard of it |
| Metadata | broadcast service tables (SDT/EIT) can carry channel names and program-guide data, but there is no field for user tagging | vorbis comments in the OpusTags header, including cover art via METADATA_BLOCK_PICTURE, plus an output-gain field used for loudness normalization |
Drop one or more .ts 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 .opus in the output menu next to each file. The menu only offers targets this engine can genuinely produce, so if OPUS 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 OPUS file. Outputs keep the original filename with the .opus extension.
Since ts is container-oriented and opus is lossy-oriented, the conversion preserves the source content exactly as stored; no additional compression pass is applied beyond what .opus itself requires.
Yes — the .ts 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.
Chrome, Firefox, and Edge have played Opus for a decade and Android supports it natively, while Safari initially accepted the codec only inside CAF or WebM wrappers before extending support to .opus files. Legacy hardware such as older car head units remains the real gap, and conversion to MP3 or AAC bridges it.
Much smaller — the video stream is usually 80–95% of a .ts 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, broadcast service tables (SDT/EIT) can carry channel names and program-guide data, but there is no field for user tagging; none of it is transmitted anywhere because the file never leaves your browser.