OGV to AV1 Converter

Convert OGV to AV1: What This Tutorial Covers

An .ogv is an Ogg container (Xiph.Org) that almost always carries Theora video and Vorbis audio — a pairing that current desktop browsers no longer decode. AV1 is the codec that replaced it in the same royalty-free lineage: newer, far more efficient, and supported by every current major browser engine. This walk-through covers the upload, the settings that actually change the result, what the .av1 file really contains, and the cases where MP4 or WebM is the smarter target.

How to Convert OGV to AV1

1. Upload Your OGV File: Drag and drop your .ogv files onto the page or click "Add Files" to browse. Several clips can be queued and converted with the same settings.
2. Check Audio Codec: The Video Codec group offers only AV1 on this page, so there is nothing to change there. The Audio Codec list defaults to Opus and also offers AAC, AC3, DTS (DCA), EAC3, FLAC, MP2, MP3, and Vorbis — leave it on Opus unless a specific player of yours refuses it.
3. Set File Compression, Video resolution, and Trim: File Compression opens on Quality Preset with the Preset dropdown at "Very High (Recommended)". Video resolution opens on "Keep original"; a Preset Resolution, Width, Height, Width x Height, or Resolution Percentage will rescale. Trim stays on "Unchanged" unless you switch it to Time Range.
4. Convert and Download: Click Convert. Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours later — no sign-up, no watermark, never shared or made public.

Walk-through: Choosing a File Compression Mode

Quality Preset is the mode to keep unless you have a specific target in mind. It scales the encode against the bitrate the source file already had, which is exactly what you want for a straight format migration: the Theora original sets the reference point and AV1 hits it with fewer bits.

Two details are worth knowing before you touch Video resolution. Preset heights are snapped down to a multiple of 16 for macroblock alignment, so the "1080p" preset produces 1072 lines rather than 1080 (1904 x 1072 from a 16:9 source), while 720p, 1440p, and 2160p land exactly on their nominal heights. If you need a precise frame size, use Width x Height, which is passed through as typed. Rescaling also normalises the pixel aspect ratio to square — for a source with non-square pixels, set an explicit Width x Height rather than leaving the correction to chance.

What the .av1 File Actually Is

The output is a Matroska file written under the .av1 name. It is not a raw AV1 elementary stream: the audio track is muxed in alongside the video, which is why the sound survives the conversion at all. Most desktop players (VLC, mpv, MPV-based front ends) sniff the container and play it regardless of the extension, but phone galleries, older editors, and some smart-TV apps route strictly on the extension and will refuse it. Renaming the file to .mkv fixes that instantly and changes nothing inside the file. If you would rather not rename anything, OGV to MKV writes the same container under the extension those apps expect.

OGV (Theora) vs AV1 at a Glance

Common Errors and How to Fix Them

• "The output is only 10 seconds long" — the Trim group was switched from "Unchanged" to Time Range. Its Duration box is pre-filled with 10 seconds, so leaving it untouched silently truncates the clip. Either set Trim back to Unchanged or type the real duration you want.
• "Nothing will open the .av1 file" — see the container note above. Rename it to .mkv, or use OGV to MP4 for a file that phones and editors accept without any renaming.
• "The conversion is taking a while" — AV1 is a computationally heavy codec. SVT-AV1 is dramatically faster than the libaom reference encoder, but a long recording still takes noticeably longer than an H.264 encode of the same footage.
• "The picture is no sharper than the original" — expected. Theora is lossy, so the source has already discarded detail; AV1 preserves what is there in far fewer bytes but cannot reconstruct what was thrown away.
• "My interlaced capture still shows combing" — there is no deinterlacing step in this pipeline. An interlaced source keeps its combing baked into every AV1 frame. Deinterlace in a desktop editor before uploading if the footage needs it.
• "The colours look washed out" — HDR sources get a plain colour conversion with no tone-mapping, so highlight roll-off is not preserved. Convert HDR footage to SDR before uploading if the grade matters.

When AV1 Is the Wrong Target

AV1 is right when you want the smallest, most future-proof royalty-free file and you will play it on current browsers or reasonably recent hardware. It is wrong in two situations. First, when the file has to open on anything and everything today — old phones, TV boxes, an editor from 2016 — in which case OGV to MP4 with H.264 is the pragmatic choice. Second, when you want the open-format lineage but with wider immediate support: OGV to WebM writes VP9 in a container browsers have understood for a decade. Note also that hardware AV1 decoding is a recent arrival; machines without it fall back to software decoding, which is fine for 1080p on a modern laptop and painful on an old one.

Frequently Asked Questions

Will the AV1 file look better than my OGV?

No. Theora is lossy and AV1 is lossy, so this is a lossy-to-lossy re-encode and every conversion here re-encodes rather than copying the stream. Detail the Theora encoder discarded is gone for good. What you gain is size and longevity: the same apparent picture in far fewer bytes, in a codec that current players actually decode. Keep the Preset at "Very High (Recommended)" or use Constant Quality at a low CRF if you want the new file to track the original as closely as possible.

Why won't my OGV play in Chrome or Firefox any more?

Because both removed the Theora decoder, not because your file is damaged. Chrome ran a staged turndown from Chrome 120 and removed the code in Chrome 123, which reached stable in March 2024. Firefox disabled Theora video by default in version 126 (May 2024). Safari never shipped Theora at all. VLC, mpv, and ffmpeg still decode it perfectly, and so does this converter — the file is fine, the decoders are gone.

Which audio codec should I keep for the AV1 output?

Opus, which is what the Audio Codec group selects by default. It is the modern Xiph codec, it is efficient at low bitrates, and it is the natural partner for AV1 in a Matroska container. Switch to AAC only if a specific downstream tool refuses Opus; AC3, DTS (DCA), EAC3, FLAC, MP2, MP3, and Vorbis are also offered for niche targets. The original Vorbis track is decoded and re-encoded either way, so this is a second lossy pass on the audio — pick the codec your destination needs and leave it alone.

Is Theora actually dead?

The codec is frozen, not abandoned. The Theora I bitstream format was frozen on 1 June 2004 and has not changed since — that is what makes old .ogv files decodable forever. The reference library is still maintained: libtheora 1.2.0, codenamed "Ptalarbvorm", shipped on 29 March 2025, the first major release in roughly sixteen years. What has ended is browser support and new adoption; Xiph's own forward path moved to Opus for audio, and open video moved to VP9 and AV1.

How much smaller should I expect the AV1 file to be?

That depends entirely on how the original was encoded, so treat any single ratio with suspicion. The useful reference point is codec efficiency: Meta's 2018 comparison reported AV1 averaging 34.0% lower bitrate than libvpx-VP9 at matched quality, and VP9 is itself generations ahead of Theora. An .ogv encoded generously will shrink a lot; one that was already squeezed hard for a 2010-era web page has little left to give, and pushing the preset lower will start to show. Use Specific file size if you need a guaranteed number instead of a guess.

Can I convert just one section of the video?

Yes — switch the Trim group from "Unchanged" to Time Range and set Start time and Duration. Both boxes accept plain seconds or HH:MM:SS.sss, so 00:01:30.500 is valid. The kept segment is re-encoded rather than copied, so the cut lands on the timestamp you typed instead of snapping back to the nearest keyframe. Watch the Duration field: it is pre-filled at 10 seconds, so it needs a real value before you convert. To cut the source before converting it, Video Cutter accepts .ogv directly.

Does the AV1 file keep the original resolution and frame rate?

Resolution stays untouched while Video resolution is on "Keep original", which is how the page opens. Choose a Preset Resolution and the height is rounded down to the nearest multiple of 16 — so "1080p" yields 1072 lines, and the width follows the source aspect ratio, also rounded to 16. Width x Height is honoured exactly as typed, which is the option to use when a downstream tool demands specific numbers. Frame rate is carried over from the source; there is no frame-rate control on this page.

What happens to my uploaded OGV and the converted file?

Your file is uploaded over an encrypted connection, converted on our servers, and both the upload and the output are deleted automatically a few hours after conversion. Nothing is shared, published, or used for anything beyond producing your file, and there is no sign-up, no watermark, and no email required.