M2TS to AVIF Converter

M2TS to AVIF Converter

This tool takes one frame out of an .m2ts clip and writes it as a single AVIF still image. M2TS is the BDAV MPEG-2 transport stream that Blu-ray Discs and AVCHD camcorders record into; AVIF is the AV1 Image File Format published by the Alliance for Open Media, the newest of the mainstream still-picture formats. The pairing exists for one job: getting a printable, shareable photograph out of high-definition video footage without dragging the whole clip along with it. The output is always a static picture — AVIF can technically hold animation, but this conversion does not produce it.

M2TS at a Glance

AVIF at a Glance

How to Convert M2TS to AVIF

1. Upload Your M2TS File: Drag your .m2ts clip onto the page or click "+ Add Files". This page accepts the .m2ts extension only — camcorder cards that write .MTS are handled at MTS to AVIF. Several clips can be queued and processed with one set of settings.
2. Pick the Frame Under Frame Selection: Specific Frame is selected by default with Time (seconds) set to 0, so an untouched job returns the very first frame. Type a decimal timestamp — 4.5, 61.25 — to land somewhere else, or switch to Multiple Screenshots and set a Capture Rate to sample the clip at a fixed interval instead.
3. Set Quality Preset and Image Resolution: Quality Preset starts on Very High (Recommended) and runs from Highest down to Lowest; Specific file size is the alternative if the still has to hit a byte target. Image resolution starts on Keep original, with Resolution Percentage, Preset Resolutions, and an exact Width x Height available.
4. Convert and Download: Click "Convert" and save the AVIF. Files upload over an encrypted connection, are processed on our servers, and are deleted automatically after a few hours — no sign-up, no watermark.

What the Frame Extraction Actually Does

The clip is decoded on our servers, the requested instant is located, and that one decoded frame is handed to the AVIF encoder. Nothing about the surrounding video survives: audio is discarded, motion is discarded, and the timestamp, camera model, and shooting metadata carried in the transport stream are not transplanted into the image — a frame grab produces a fresh file, not a photograph with the camcorder's EXIF attached. Two consequences follow from working at the frame level. Interlaced source frames arrive with both fields already woven together, because this pipeline contains no deinterlacer of any kind. And a frame from an anamorphic 1440×1080 recording is stored at its literal pixel dimensions, so it looks horizontally squeezed until you correct the geometry yourself.

Frequently Asked Questions

Does this produce an animated AVIF or a single still?

A single still, always. The AVIF specification does support image sequences — it is built on the AV1 video codec — but this conversion reads one frame out of your M2TS and writes exactly that. There is no frame-rate control on the page and no animation output. If you want the movement preserved, M2TS to GIF produces a real animated loop, and M2TS to MP4 keeps the clip as video with its audio intact.

Which frame do I get if I don't change any settings?

The first one. Frame Selection opens on Specific Frame with Time (seconds) pre-filled as 0, so an untouched job grabs the frame at the very start of the clip — which on camcorder footage is often the least interesting moment on the card, sometimes a dark or half-exposed frame from the instant recording began. Type a timestamp before converting. The field takes decimals, so at 25 fps each 0.04 you add steps forward roughly one frame, and at 30 fps roughly 0.033.

Why does my extracted frame show thin horizontal lines on motion?

Because the recording is interlaced. AVCHD specifies 60i and 50i modes and a large share of consumer camcorders shipped recording 1080i by default. Each interlaced frame is woven from two fields captured a fraction of a second apart, so anything that moved between them lands in the extracted still as comb teeth along its edges. This converter has no deinterlacing step, and no quality preset, resolution setting, or intermediate conversion introduces one. The workable fix on-page is to pick a moment where the subject is still — nudge Time (seconds) by a few hundredths until you find one. Progressive recordings (1080p, 720p) never show this.

Will saving to AVIF make an old camcorder frame look sharper?

No, and that is worth being blunt about. AVIF is a more efficient way to store a picture, not a way to improve one. The frame you start with is whatever H.264 already committed to the transport stream — HD-era at best, softer if the shot was interlaced, handheld, or badly lit, and already carrying one generation of lossy compression. AVIF gives you that same picture in a smaller file with cleaner gradients than a JPEG would manage. It cannot recover detail the camcorder never recorded.

What can actually open an AVIF file?

Browsers, overwhelmingly — caniuse puts global support at roughly 95%, covering Chrome 85+, Firefox 93+, Safari 16.4+, and Edge 121+. Desktop applications lag: older image viewers, some email clients, and plenty of legacy business software still refuse it, and Safari 16.1–16.3 sits in a partial-support window. If the still has to open literally anywhere without a conversation, M2TS to JPG is the safer target. M2TS to PNG is the other universally-readable option — note that its default quality preset applies palette quantisation, so choose the Highest preset there if you want a true-colour result.

A frame from my 4K Blu-ray rip looks washed out and grey — why?

You are almost certainly grabbing from HDR source. Ultra HD Blu-ray stores HEVC video with HDR10 metadata inside the same .m2ts wrapper, and the wide-gamut, high-dynamic-range values in that stream only look right on a display that knows to expand them. This converter performs no HDR tone-mapping — the frame gets a plain colour conversion, which is why HDR sources come out flat, desaturated, or milky. There is no setting that changes this. Tone-map in a desktop tool before extracting if the still has to look like the disc does.

My 1440×1080 clip's frame came out looking squashed — what happened?

That is AVCHD's anamorphic mode. The specification permits 1440×1080 alongside 1920×1080, and the 1440-wide modes store non-square pixels that are meant to be stretched back to 16:9 at playback time. A still image has no equivalent of that stretch flag once it has been written, and this converter applies no pixel-aspect correction, so the frame keeps its literal 1440×1080 geometry and reads as horizontally compressed. Set it right explicitly: choose Width x Height under Image resolution and enter 1920 × 1080. Clips shot at a native 1920×1080 are unaffected.

Can I pull several frames from one clip at once?

Yes. Switch Frame Selection from Specific Frame to Multiple Screenshots and set a Capture Rate — the dropdown runs from ten frames a second down to one frame every ten seconds. The converter samples the clip at that interval and returns the set together, which is usually a faster way to find the shot you want than re-running a single grab and guessing at timestamps. Pick the sharpest one and discard the rest.

My footage is named .MTS, and how long do you keep my upload?

.MTS and .m2ts are the same BDAV transport stream — camcorders write the short .MTS name to the memory card, and the clip commonly arrives as .m2ts after being copied to a computer — but this page accepts .m2ts only. Send camcorder-named files to MTS to AVIF, or simply rename the file, since the bytes are identical. Either way your upload travels over an encrypted connection, is processed on our servers, and is deleted automatically after a few hours — no sign-up, no watermark, never shared or made public. The real constraint on a long recording is upload time, not the frame grab, which is quick once the file has arrived.