AV1 to TS Converter

How to Convert AV1 to TS Online

1. Upload Your AV1 File: Drag and drop or click to add one or more .av1 (or AV1-in-MP4 / AV1-in-MKV) clips. Batch is supported.
2. Pick a Quality Preset and Output Codec: Default is "Very High (Recommended)". Choose Highest for archival masters, High or Medium for IPTV/broadcast staging, Lower for slim distribution copies. The TS container defaults to MPEG-2 video / MP2 audio for maximum receiver compatibility — switch to H.264 (AAC) or H.265 (AAC) under Advanced for far smaller files at the same quality. You can also pin a Specific file size, or fine-tune with Constant Bitrate, Variable Bitrate, Constant Quality (CRF-style), or Constraint Quality.
3. Set Resolution and Trim (Optional): Keep original, pick a Preset Resolution from 4320p down to 144p, scale by Resolution Percentage, or set Width × Height (with aspect-ratio lock). Use Trim → Time Range to extract a single segment by start time and duration in seconds or HH:MM:SS.sss.
4. Convert and Download: Click Convert. Files are processed in your session — no sign-up, no watermark, no email required.

Why Convert AV1 to TS?

AV1 (AOMedia Video 1, bitstream finalized June 2018) is a royalty-free codec with roughly 30% better compression than HEVC and ~50% better than H.264 — excellent for web streaming and storage, but a poor fit for the broadcast and professional-video workflows that still expect MPEG-2 Transport Stream (ISO/IEC 13818-1). TS chops video, audio, and metadata into 188-byte packets with PCR timestamps and PSI tables so a receiver can join the stream mid-flight and recover from packet loss. That's why DVB, ATSC 1.0, IPTV head-ends, hardware encoders, and live ingest endpoints (RTMP→TS, SRT, Zixi) speak TS first.

• IPTV and OTT head-end ingest — Most professional encoders (Harmonic, Ateme, AWS Elemental MediaLive, Nimble Streamer) accept TS as a primary input. AV1 source rarely passes through unchanged because the AV1-in-MPEG2-TS specification is still an AOM Working Group Draft (last updated 25 March 2026, registration descriptor 'AV01', stream_type 0x06) — re-encoding to H.264 or H.265 inside TS is the safe path.
• Set-top boxes and DVB receivers — Cable, satellite, and terrestrial DVB receivers decode MPEG-2 universally and HEVC widely; AV1 hardware decode is currently confined to newer consumer SoCs (Apple A17 Pro / M3+, AMD RDNA 3+, Intel Arc, Nvidia RTX 40+) and almost no broadcast STBs.
• HLS legacy segments — HLS originally used .ts segments; Apple's HLS authoring spec now permits AV1 only inside fMP4 (CMAF) segments, not TS. If your CDN or origin still ships TS chunks, your AV1 source must be transcoded to H.264 / HEVC.
• OBS, vMix, and Wirecast capture — Many studio capture pipelines ingest TS (often over SRT or UDP multicast). Converting an AV1 master to TS lets it flow through existing automation and graphics insertion.
• Archival or contribution feed — Broadcasters' contribution links and tape-out tools expect TS; an AV1 master converted to MPEG-2 or H.264 inside TS is the standard hand-off.
• Editing on Avid / Edius / FCP — None of the major NLEs accept raw AV1 elementary streams. A TS wrap (with H.264 or DNxHR-friendly intermediates) is a common compatibility step.

AV1 vs TS — Codec vs Container

A frequent point of confusion: AV1 and TS aren't peers. AV1 is a video codec (the compression). TS is a transport container (how packets travel). Conversion always means decoding AV1 frames and re-encoding them as MPEG-2, H.264, or H.265 inside the TS multiplex.

TS Inner-Codec Quick Guide — Pick the Right Video Codec

Frequently Asked Questions

Can I keep AV1 inside the TS container without re-encoding?

In theory yes — the AOM "Carriage of AV1 in MPEG-2 TS" specification defines the registration descriptor 'AV01' and uses stream_type 0x06. In practice the spec is still an AOM Working Group Draft (last revised 25 March 2026), and broadcast equipment, set-top boxes, and most software players don't recognize AV1 elementary streams in TS. We default to MPEG-2 for the broadest compatibility. If you have a known-good downstream pipeline that supports AV1-in-TS, transcoding to H.264 or H.265 first is still the safer choice today.

Why does my TS file get bigger than the AV1 source?

AV1 is one of the most efficient codecs ever shipped — replacing it with MPEG-2 inside TS commonly produces files 3–5× larger at equivalent perceived quality. Switch the inner codec to H.265 under Advanced and you'll typically land within ~1.5–2× of the AV1 source while keeping the TS container that broadcast and IPTV infrastructure expects.

Should I pick MPEG-2, H.264, or H.265 as the inner codec?

MPEG-2 if your target is a DVB / ATSC 1.0 receiver, a legacy hardware decoder, or a contribution feed that demands it. H.264 for the broadest "modern but universal" compatibility — every Smart TV, IPTV STB, and OBS / SRT pipeline since ~2010. H.265 (HEVC) for 4K IPTV, ATSC 3.0 (whose video standard A/341 mandates HEVC), and any pipeline where bandwidth matters more than older-decoder coverage.

Does HLS support AV1 segments?

Apple's HLS Authoring Specification lists AV1 as a permitted video codec — but only inside fMP4 (CMAF) segments, never inside .ts segments. If your CDN or player still uses classic TS chunks, AV1 is off the table; you must transcode to H.264 or H.265. AV1-in-fMP4 plays natively on iPhone 15 Pro / 15 Pro Max, Apple silicon Macs (M3 and newer), and iPads with M4+.

Can I convert audio too?

Yes. The TS output uses MP2 audio by default (the broadcast standard). Switch to AAC for IPTV / streaming targets, AC-3 (Dolby Digital) for ATSC 1.0 / DVD-style outputs, or E-AC-3 for ATSC 3.0 5.1+ delivery. Channel layout, sample rate, and bitrate are all selectable under Advanced.

How is .ts different from .m2ts and .mts?

.ts is the raw 188-byte MPEG-2 Transport Stream. .m2ts and .mts are the AVCHD / Blu-ray flavor that prepends a 4-byte timing prefix to each packet (192-byte units instead of 188). They share the same multiplex structure — most modern players accept either. We emit .ts here; if you need true AVCHD .m2ts, see our MKV to TS and related video-to-TS converters which can target the AVCHD variant.

Will the converter preserve subtitles and multiple audio tracks?

Multiple audio tracks (PIDs) survive the multiplex; you can pick which to keep. Soft subtitles from MKV-style sources are not carried — TS uses DVB-Sub or Teletext, which require burn-in or external SCC/PAC sidecar workflows we don't currently expose. For full subtitle support keep the source in MKV or MP4.

Can I trim during conversion?

Yes. Open Trim → Time Range and enter a start and duration in seconds or HH:MM:SS.sss. Only the selected segment is decoded from AV1 and re-multiplexed into TS, which is faster than processing the full file when you only need a clip.

What's the reverse path — TS back to a modern format?

Use TS to MP4 for distribution, or convert your AV1 to a modern web container with AV1 to MP4 or AV1 to MKV. To re-encode to HEVC for ATSC 3.0 / 4K IPTV use AV1 to HEVC, and to shrink an AV1 master without changing format use Compress AV1.