MKV to TS Converter

How to Convert MKV to TS Online

1. Upload Your MKV File: Drag and drop or click "Add Files" to select MKV (Matroska) files. Plex / Jellyfin / Emby / Kodi library masters, Handbrake encodes, ripped Blu-ray remuxes, and recorded streams all work. Batch is supported — drop a whole season at once and each episode is wrapped to its own .ts.
2. Pick a Video Codec and Quality: Default keeps the source video. Pick H.264 for the safest IPTV / HLS target (every set-top box and STB chipset since 2010 plays it), H.265 / HEVC for ~40-50% smaller segments at the same visual quality on 2017+ decoders, MPEG-2 to match traditional digital-TV broadcast pipelines, or AV1 for newest hardware. Set Quality Preset (Highest → Lowest, default Very High), target a percentage of source size, lock to a specific file size in MB, or fine-tune with Constant Bitrate, Variable Bitrate, Constant Quality (CRF), or Constraint Quality.
3. Resize or Trim (Optional): Pick a Preset Resolution (2160p / 1440p / 1080p / 720p / 480p / 360p) to downscale a 4K master to a more bandwidth-friendly broadcast profile, enter a custom Width × Height, or scale by Resolution Percentage. Use Time Range trim with start time + duration in HH:MM:SS.sss to cut out the file to a specific segment. Audio codec defaults preserve the source — switch to AC-3 / E-AC-3 to match Dolby Digital broadcast audio standards, AAC for HLS streaming, or MP2 to match legacy DVB pipelines.
4. Convert and Download: Click Convert. Files process in your browser session — no sign-up, no watermark, no upload to a third-party server.

Why Convert MKV to TS?

MKV (Matroska) is the open container that media-library tools standardized on — flexible, multi-track, chapter-aware, but designed for file-based local playback. TS (MPEG-2 Transport Stream) is the broadcast-and-streaming container — packetized, error-resilient, designed to be transmitted over networks where dropped packets are expected. Converting MKV to TS is the step that takes a clean library master and turns it into something an IPTV head-end, HLS packager, broadcast encoder, or Blu-ray authoring tool can ingest. Common reasons to convert MKV → TS:

• IPTV and DVB head-end ingest — IPTV middleware, DVB-IP gateways, and broadcast encoders typically require MPEG-TS input. An MKV won't ingest into a Harmonic / Ateme / Anevia / Tvheadend pipeline; a .ts with H.264 video + AC-3 or MP2 audio will.
• HLS / DASH segmenter input — Apple HLS and many DASH packagers consume MPEG-TS as their source, then chunk it into segment files. Pre-wrapping an MKV into TS lets ffmpeg, Bento4, Shaka Packager, and similar tools segment cleanly without an extra demux pass.
• DLNA streaming to set-top boxes and smart TVs — Older DLNA receivers and many cable / IPTV STBs play TS reliably but stumble on MKV. Re-wrapping the library to TS fixes "format not supported" on living-room hardware that won't take a Matroska file.
• Blu-ray and AVCHD authoring — Blu-ray (.m2ts) and AVCHD camcorder workflows are MPEG-TS at heart. Converting an MKV master to TS is the prep step before authoring tools like tsMuxeR, multiAVCHD, or BDMV pipelines pick it up.
• Hardware encoder / decoder pipelines — Professional broadcast encoders, satellite uplinks, and hardware transcoders (Harmonic, Ateme, Elemental, Ericsson) speak MPEG-TS as their native interchange format. MKV is rarely supported on the ingest side.
• Stream-loss-tolerant playback over flaky networks — TS packets are 188 bytes and self-synchronizing, so a corrupted chunk only takes out a fraction of a second. MKV scrubbing breaks if the index is damaged. For unattended playback over an unreliable Wi-Fi or LTE link, TS keeps going where MKV stalls. See also MKV to MP4 for universal device playback and TS to MKV for the reverse direction.

MKV vs TS — Format Comparison

Video and Audio Codec Choice Inside the TS

Frequently Asked Questions

Why would I want a TS file when MKV is "better"?

MKV is better for libraries; TS is better for transmission. If the destination is a broadcast encoder, IPTV head-end, HLS / DASH packager, DLNA set-top box, or Blu-ray authoring tool, those pipelines speak MPEG-TS and either don't accept MKV or accept it poorly. The conversion isn't about quality — it's about handing the right wrapper to the right pipeline. Keep the MKV as your master; produce TS for the specific delivery target.

Should I pick H.264, H.265, MPEG-2, or AV1 for the TS video?

H.264 is the safest IPTV / HLS / STB target — every set-top, every smart TV, every middleware speaks it. H.265 / HEVC halves the bitrate on 2017+ decoders; verify the receiving end supports it before committing. MPEG-2 matches traditional DVB and ATSC broadcast pipelines and some legacy hardware encoders that won't accept H.264-in-TS. AV1 is bandwidth-best for new IPTV deployments but decoder support outside 2022+ chipsets is still spotty — don't pick it unless you control the receiver.

Does AC-3 audio survive the conversion?

Yes — AC-3 (Dolby Digital) is the native broadcast / Blu-ray audio codec and carries cleanly into TS. Multi-channel 5.1 surround is preserved. If your MKV has AC-3 already, set audio codec to AC-3 and the conversion remuxes the audio bit-for-bit (no re-encode, no quality loss). If the MKV has DTS or FLAC, those don't belong in a broadcast-style TS — re-encode to AC-3 or E-AC-3 for compatibility.

Can I use this output as input to an HLS segmenter?

Yes — that's one of the main reasons to produce TS. Apple HLS spec input is MPEG-TS with H.264 video + AAC audio. Pick H.264 + AAC, then feed the .ts to ffmpeg -hls_time …, Bento4 mp4hls, Shaka Packager, or any HLS-aware CDN tool. The packager will chunk the TS into 6-10 second segments and write the .m3u8 playlist.

What about subtitles and chapters from the MKV?

Chapters don't carry into TS — the format has no chapter concept. Multi-track soft subtitles (SRT, ASS) are also dropped because TS subtitle support is limited to broadcast caption formats (EIA-608 / 708, DVB subs). If you need subtitles in the TS output, burn them into the video before conversion or carry them separately as a sidecar file. For a target that preserves all of this, pick MKV → MKV (re-encode in place) or MKV to MP4 instead.

Why does my TS file look slightly bigger than the source MKV?

TS adds packetization overhead — 188-byte packets, PAT / PMT / PCR tables, padding for constant bitrate, and program-specific information all carry a small file-size cost (typically 2-5%). That's the price of the error-resilience that makes TS work over unreliable networks. If file size matters more than transport reliability, pick a different container; if you need TS for the pipeline, the overhead is unavoidable.

Will the output play in VLC, MPC-HC, or my regular media player?

Usually yes — VLC, MPC-HC, mpv, and Kodi all play TS files directly. The catch is scrubbing: TS doesn't carry a clean seek index, so jumping around the file may be slow or imprecise depending on the player. TS is meant to be played start-to-finish like a broadcast; if you want random-access playback for a regular library, keep the MKV master and produce TS only for the pipeline that requires it.

How big a file can I convert?

Multi-hour MKV masters (4-12 GB Blu-ray remuxes or season-length encodes) work. Conversion runs in your browser session, so the practical ceiling is your device's available memory and your patience. For very long sources, trim first with Time Range to extract just the part you want — converting a 30-minute slice of a 4-hour file is dramatically faster than processing the whole stream.