Initializing... drag & drop files here
Supports: TS
yt-dlp all work. Batch is supported — drop a whole season's worth of episodes at once.TS (MPEG-2 Transport Stream) is what every DVR, broadcast tuner, IPTV recorder, and ATSC / DVB capture device writes. It's designed for error-resilient transmission, not local playback — which is why a .ts file often won't scrub cleanly, won't show accurate duration, and won't import into most media-server libraries. MKV (Matroska) is the open container the Plex / Jellyfin / Emby / Kodi ecosystem standardized on. It preserves multiple audio tracks, subtitle tracks, and chapter markers, fixes seek tables, and presents the recording as a clean indexable file. Common reasons to convert TS → MKV:
.ts from a cable-box export or HDHomeRun often shows wrong duration, won't scrub, and crashes when you try to skip ahead. Re-muxing into MKV rebuilds the index and produces a file that scrubs frame-accurately.| Property | TS (Transport Stream) | MKV (Matroska) |
|---|---|---|
| Origin | MPEG-2 Systems (ISO/IEC 13818-1, 1996) | Open Matroska standard (2002) |
| Designed for | Broadcast, satellite, IPTV, error-resilient transmission | File-based playback, media libraries |
| Common video codec | MPEG-2, H.264, occasionally HEVC | H.264, H.265, AV1, MPEG-2, anything |
| Common audio codec | AC-3 (Dolby Digital), AAC, MP2, E-AC-3 | AAC, AC-3, DTS, FLAC, Opus, anything |
| Multiple programs / streams | Yes — multiplexed PAT/PMT/PCR | Single program; multi-track within program |
| Subtitle tracks | Embedded captions (EIA-608/708) | Multiple switchable tracks (SRT, ASS, PGS) |
| Chapter markers | No | Yes |
| Seek / scrub accuracy | Often broken on raw captures | Frame-accurate (proper index) |
| Plex / Jellyfin direct-play | Often transcodes | Direct-play in most cases |
| Best for | Capture, broadcast, streaming segments | Media-server libraries, archival |
| Codec | File size (relative) | Hardware compatibility | Best for |
|---|---|---|---|
| MPEG-2 (keep source) | 100% | Universal in MKV-aware players | Near-lossless remux, fastest conversion |
| H.264 | ~40-50% | Universal — every modern device since 2010 | Default modern target, broad direct-play |
| H.265 / HEVC | ~25-35% | 2017+ devices, Apple TV 4K, modern smart TVs | Best size/quality balance for new libraries |
| AV1 | ~20-30% | 2022+ devices, modern browsers | Smallest archive, future-proof |
| MPEG-4 / Xvid | ~50-60% | Legacy MKV-aware players | Rarely useful — H.264 is better |
Yes — MKV preserves multiple audio tracks. The primary AC-3 surround track and any secondary tracks (SAP, descriptive audio, second language) are kept as switchable streams in the output. Set audio codec to AC-3 or E-AC-3 to keep the original Dolby Digital track bit-for-bit; pick AAC or Opus to re-encode for size. For best results when archiving broadcast captures, leave the primary audio in AC-3 and let MKV carry it untouched.
Raw transport streams from DVRs and tuners don't carry a clean duration field or seek index — they're a continuous stream that was meant to be played live. VLC, MPC-HC, and Kodi work around it; Windows file properties, web players, and most media servers don't. Converting to MKV rebuilds the index, writes a correct duration, and makes scrubbing instant. This alone is the reason many people remux TS captures the moment they land on disk.
MPEG-2 when you want to keep the source video untouched — fastest, near-lossless, but file size unchanged. H.264 for a modern universal target with broad Plex / Jellyfin direct-play support and ~40-50% size reduction. H.265 / HEVC for newer devices (Apple TV 4K, 2017+ smart TVs, modern phones) at ~25-35% of the source size. AV1 for the smallest possible archive when your audience is on 2022+ hardware. For a Plex / Jellyfin library that mixes old and new client devices, H.264 is the safest direct-play default.
Embedded EIA-608 / 708 closed captions in broadcast TS streams can be extracted to a switchable subtitle track in the MKV output. SRT, ASS, and PGS subtitle tracks (if your TS source is from an IPTV provider that includes them) are preserved as separate selectable tracks. This is one of MKV's main advantages over MP4 — subtitle handling is first-class instead of a workaround.
Multi-hour DVR captures (4-12 GB transport streams from a full football game or an overnight recording) work. Conversion runs in your browser session, so the practical ceiling is your device's available memory and your patience for the upload. For very long broadcasts, trim first with Time Range to extract just the part you want — converting a 30-minute slice of a 6-hour recording is dramatically faster than processing the whole stream.
Effectively yes. Picking MPEG-2 as the video codec and AC-3 as the audio codec converts the operation from a re-encode into a container remux — the codec data is copied from TS into MKV unchanged. There's no generation loss, conversion is dramatically faster (CPU-light), and the output is bit-for-bit identical to the source video. The only thing that changes is the wrapper.
ATSC over-the-air captures often pack a primary HD program plus 1-2 SD subchannels (a network feed plus a weather subchannel, for example) into a single 6 MHz mux written to one .ts file. The converter selects the primary video and audio program by default and writes a single-program MKV. If you need a specific subchannel, demux the TS first with a tool like Project X or ffmpeg -map 0:p:N, then convert the extracted program to MKV here.
MKV is the media-library format — multiple audio tracks, multiple subtitle tracks, chapter markers, anything-goes codec support. MP4 is the universal-playback format — phones, browsers, smart TVs, AirPlay, Chromecast all play it natively. Pick MKV when the destination is Plex / Jellyfin / Emby / Kodi or when you need to preserve multi-track broadcast audio and subtitles. Pick TS to MP4 when the destination is a phone, a generic smart TV, or a web embed.