AVIF to TS Converter

Putting an AVIF Still Inside a .ts Clip: What This Covers

TS is the MPEG-2 Transport Stream, the container defined in MPEG-2 Systems (ISO/IEC 13818-1, also published as ITU-T H.222.0) and used by DVB and ATSC broadcast, IPTV middleware, and HLS segments. An AVIF is a single still picture. This page turns one into the other: the tool holds your image on screen for a duration you choose and encodes that as a real, silent .ts file. Below you will find the four steps, then a walk-through of the codec choice, the duration-to-frame-rate mapping, and the failure cases where a still-in-TS is not what you actually wanted.

How to Convert AVIF to TS

1. Upload Your AVIF File: Drag your .avif onto the page or click "Add Files". Drop several at once and set Merge strategy to "Merge images" for one combined clip, or "Video per image" for a separate .ts per picture.
2. Set Image Duration: The Image Duration dropdown opens on "5 seconds per frame" and runs from 1/60 of a second up to 10 seconds. This is the length of the finished clip when you convert a single image.
3. Pick the Video Codec and Background Color: Video Codec opens on H.264, the safe choice for HLS and modern set-top boxes; MPEG-2, H.265, MPEG-1, MPEG-4, DivX and Xvid are also in the list. Background Color opens on White and fills any transparent region of the AVIF as well as any letterbox bars.
4. Convert and Download: Click Convert and save the silent .ts. No sign-up, no watermark. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours.

Walk-through: Choosing the Codec Inside the Transport Stream

The container is always MPEG Transport Stream — what changes is the video elementary stream carried inside it, and that is what decides whether the receiving equipment accepts your file.

Because the input is a still image with no soundtrack, the Audio Codec control does not appear on this page and the resulting .ts is silent by design. A transport stream would normally carry AAC, AC-3 or MP2 audio alongside the video; there is simply nothing to encode from a single picture.

Image Duration and the Frame Rate It Implies

The short entries at the top of the Image Duration list exist to emit a one-frame clip at a specific frame rate, which is what most ingest tools want from a slate or test card.

Common Errors and How to Fix Them

• "The video just shows a frozen picture" — That is the intended output. A still image has no motion, so the encoder repeats one frame for the duration you chose. To get movement you have to start from a real video or an animated source.
• "There is no sound" — Also intended. An AVIF carries no audio track, so the audio stage is switched off entirely. Add a soundtrack afterwards in a video editor if you need one.
• "My player seeks badly or the scrub bar jumps" — A transport stream carries no global index; it is built to be received as a continuous broadcast, not scrubbed like a file. For random-access playback, convert AVIF to MP4 instead.
• "Transparent parts came out white" — Video formats cannot store an alpha channel, so transparent pixels are filled with the Background Color, which opens on White. Change it to Black or any other colour before converting.
• "My encoder or multiplexer refuses the file" — It almost certainly expects a specific elementary stream. Re-run with Video Codec set to whatever the receiving facility specifies, usually H.264 or MPEG-2.
• "The picture looks softer than the AVIF" — Video encoding is lossy and works in 4:2:0 chroma, which thins out fine coloured detail. Leave Quality Preset on "Very High (Recommended)" and avoid downscaling under Video resolution.

When This Doesn't Work

A still wrapped in a transport stream is a deliberately narrow tool: it exists to slot a slate, test card, logo or standby image into a pipeline that only consumes .ts — a playout server, an HLS segmenter, or IPTV middleware. If you simply want to share or play the picture as a video, AVIF to MP4 makes a smaller file that plays on effectively every current device and editor. This page also will not unwrap an animated AVIF into motion: even though the AVIF specification defines image sequences, the image-to-video stage treats the file as a single picture. And if you only wanted a viewable photo rather than a clip, convert AVIF to JPG is the page you want — a .ts will not open in a phone gallery.

Frequently Asked Questions

Will this animate my AVIF image?

No. The output is one frame repeated for the duration you set, so the clip looks frozen throughout. AVIF can technically store an animated image sequence, but this image-to-video conversion treats the upload as a single picture rather than playing frames back. For motion you need to start from a video or an animated GIF instead.

Why is the .ts file silent, and can I add audio?

A single image has no audio track, so there is nothing for the encoder to carry and the Audio Codec control is hidden on this page. Transport streams normally hold AAC, AC-3 or MP2 audio, and you can add a soundtrack afterwards by importing the .ts into a video editor or muxing an audio elementary stream alongside it with a tool such as FFmpeg or tsMuxeR.

What codec does the TS output use by default?

H.264. That is the broadest-compatibility payload for transport streams and what HLS packagers, IPTV set-top boxes and most modern decoders expect. The Video Codec list also offers MPEG-2 for classic DVB and ATSC chains, H.265 for smaller segments on newer decoders, and MPEG-1, MPEG-4, DivX and Xvid for legacy targets. The container stays MPEG Transport Stream whichever you pick.

Can I drop this .ts straight into an HLS stream?

The container type is right — RFC 8216, the HTTP Live Streaming specification published in August 2017, defines MPEG-2 Transport Stream as a media segment format in section 3.2 and requires each segment to contain a single MPEG-2 Program with its Program Association and Program Map Tables. But one .ts is not a complete stream: you still need an .m3u8 playlist and segments cut to a consistent target duration. Keep the codec on H.264 and let your packager slice and index the file.

Why does a transport stream seek so badly compared with MP4?

Because it was designed for broadcast, not for files. A transport stream is a series of small fixed-size packets that a receiver can join at any moment, with tables repeated periodically so a late tuner can sync. There is no central index mapping timestamps to byte offsets the way an MP4 moov atom does, so players have to estimate positions when you scrub. That trade buys robustness on a lossy transmission path.

What happens to transparency and HDR in the AVIF?

Both are lost, and deliberately so. AVIF supports alpha image items and high bit depths, but video containers have no alpha channel, so transparent regions are painted with the Background Color instead. Wide-gamut and high-dynamic-range values are mapped down to the standard range the video encoder writes. If either matters, keep the file as a still and convert AVIF to PNG.

Why would anyone convert a photo into a broadcast format?

Compatibility with playout and streaming tooling, not quality. Broadcast automation systems, HLS packagers and IPTV middleware ingest transport streams, not image files, so a slate, holding card or channel ident has to arrive as a .ts even though the content is a single picture. Outside those pipelines there is no reason to choose TS over MP4.

How are my files handled after conversion?

Your AVIF is uploaded over an encrypted connection, encoded on our servers, and both the upload and the finished .ts are deleted automatically after a few hours. There is no sign-up, no watermark, and files are never shared or made public. If you need to bring an existing transport stream back into a normal file, convert TS to MP4 does the reverse trip.