OGV to HEVC Converter

OGV to HEVC Converter

This page re-encodes an .ogv — an Ogg container carrying Theora video and, almost always, Vorbis audio — into HEVC, also known as H.265. It is a jump of about a decade in compression technology, and the trade is explicit: you get a much smaller file and lose the royalty-free status the Ogg original had. What follows is a reference on both formats, what the tool actually writes to disk, and which controls matter.

OGV / Theora at a Glance

HEVC / H.265 at a Glance

What the .hevc File Actually Contains

The output is a Matroska file written under an .hevc name. That is deliberate — a bare HEVC elementary stream could not carry your audio at all, so the video and the re-encoded soundtrack are muxed into Matroska and the requested extension is kept. Players that identify files by content (VLC, mpv, ffmpeg, most desktop players) open it without complaint. Anything that routes on the extension alone — phone galleries, older editors, some TV apps — will refuse it until you rename the file to .mkv, which changes nothing inside. If you would rather not rename anything afterwards, OGV to MKV produces the same container with the extension those tools expect.

Where an HEVC File Will Actually Play

How to Convert OGV to HEVC

1. Upload Your OGV File: Drag and drop the .ogv onto the page or click "Add Files". Several files can be queued and share the same settings.
2. Confirm Video Codec and Audio Codec: Video Codec offers H.265 and HEVC — two labels for the same libx265 encoder — with H.265 selected. Audio Codec defaults to AAC and also lists AC3, DTS (DCA), EAC3, FLAC, MP2, MP3, Opus, and Vorbis.
3. Set File Compression, Video resolution, and Trim: File Compression opens on Quality Preset with the Preset dropdown at "Very High (Recommended)"; Constant Quality exposes a CRF field on a 16–51 scale that opens at 23. Video resolution opens on "Keep original", and Trim on "Unchanged".
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.

Reading the Quality Controls

Quality Preset is the mode to leave alone for a straight migration: on a video source it scales the encode relative to the bitrate the original already carried, so a modest .ogv is not blown up into a bloated .hevc. Constant Quality is the mode to reach for when you want a consistent look regardless of size — its CRF field runs 16 to 51 with lower meaning more detail, and it starts at 23, a conservative setting that keeps close to the source. Moving into the high twenties shrinks the file noticeably; going below about 18 mostly spends bits faithfully preserving Theora's existing compression artefacts rather than recovering anything real. Constraint Quality adds a Max bitrate ceiling on top of the same CRF value, and Specific file size lets you name a number in megabytes and let the encoder work backwards from it.

One resolution detail worth knowing: Preset Resolution heights are rounded down to a multiple of 16 for macroblock alignment, so the "1080p" preset yields 1072 lines rather than 1080, with the width derived from the source aspect ratio and rounded the same way. 720p, 1440p, and 2160p divide evenly and land exactly. Use the Width x Height fields when a downstream tool insists on specific numbers.

Frequently Asked Questions

Does converting OGV to HEVC improve the picture?

No — it makes the file smaller, not better. Theora is lossy and HEVC is lossy, and the server always re-encodes rather than copying the stream, so this is a lossy-to-lossy pass that can only subtract. What HEVC buys is efficiency: roughly half the bitrate of H.264 for equivalent quality according to the standardisation group's own subjective studies, and far less than Theora needs. If the result looks worse than the original, the Quality Preset or CRF was pushed too hard — move back toward "Very High" or a CRF in the low twenties.

Why won't my .hevc file open in some apps?

Because the file is a Matroska container under an .hevc name, and some apps decide what a file is purely from its extension. Players that read the actual container — VLC, mpv, and anything ffmpeg-based — open it immediately. Phone galleries, several older editors, and some smart-TV apps will not. Renaming the file to .mkv resolves it without altering a single byte of the contents. Separately, HEVC decoding itself is not universal: Windows needs the paid HEVC Video Extensions from the Microsoft Store, and Chrome only decodes H.265 where hardware support exists.

Is moving from Theora to HEVC a step backwards on licensing?

On openness, yes, and it is worth being clear about. Theora is royalty-free and stewarded by the Xiph.Org Foundation; HEVC is patent-encumbered and licensed through multiple patent pools, which is precisely why browser vendors were reluctant to ship it. You gain modern compression and native playback across Apple hardware, and you give up the royalty-free status. If that trade bothers you, OGV to WebM keeps efficiency and royalty-free licensing together, and OGV to AV1 goes further on both.

Does the audio survive, and in what format?

Yes. The Vorbis track from the Ogg source is decoded and re-encoded into the output, with the Audio Codec group defaulting to AAC. Because the source audio is lossy and the target is too, this is a second lossy generation on the soundtrack rather than a copy — noticeable only if the original was already low-bitrate. AC3, DTS (DCA), EAC3, FLAC, MP2, MP3, Opus, and Vorbis are all available if a specific device needs one of them. If you only want the sound, OGV to MP3 skips the video entirely.

Why does the encode take longer than the original file's duration?

Because HEVC spends computation to save bits. Its coding tree units run up to 64 x 64 pixels with deep recursive partitioning, its motion search is far more exhaustive than H.264's, and its entropy coding is heavier — all of which is what produces the roughly halved bitrate. There is no setting that makes HEVC simultaneously faster than H.264 and smaller than it. If throughput matters more than file size, OGV to MP4 with H.264 finishes considerably sooner.

The HEVC came out barely smaller than the OGV. What went wrong?

Probably nothing. If the source was already compressed hard — a small Wikimedia upload, an old web embed, a low-bitrate screen capture — there is little redundancy left for a better codec to exploit, and a high Quality Preset will spend bits faithfully reproducing the artefacts that are already there. Lower the preset, drop the resolution, or switch to Constant Quality with a CRF in the high twenties. Use Specific file size if you need a guaranteed number rather than an estimate.

Will an interlaced or HDR source be handled correctly?

No, and this is worth stating plainly. There is no deinterlacing stage in this pipeline, so an interlaced capture keeps its combing artefacts baked into every output frame — deinterlace in a desktop editor before uploading if the footage needs it. There is likewise no HDR tone-mapping: an HDR source gets a plain colour conversion and can look flat or washed out. Convert HDR footage to SDR with a proper tone-map beforehand if the grade matters to you.

Why did the output stop after ten seconds?

The Trim group was switched from "Unchanged" to Time Range. Its Duration box arrives pre-filled at 10 seconds, so switching modes and converting without editing that value truncates the clip. Set Trim back to "Unchanged" for the whole video, or enter a genuine Start time and Duration — both fields accept plain seconds or HH:MM:SS.sss. Because the kept segment is re-encoded rather than stream-copied, the cut lands exactly on the timestamp you typed instead of snapping to a keyframe.

How long do you keep 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 any purpose beyond producing your file, and there is no sign-up, no watermark, and no email required.