OGV to AVCHD Converter

OGV to AVCHD: A Reference for What This Page Produces

AVCHD is not a file extension. It is a recording specification Sony and Panasonic introduced jointly in 2006 for consumer HD camcorders: H.264 video and Dolby Digital audio multiplexed into an MPEG-2 transport stream, written to a card inside a defined folder structure. Cameras that record it name the files .mts; computers that import it use .m2ts. Nobody's camera writes .avchd.

So this page occupies a specific niche: it takes an .ogv — Xiph.Org's Ogg container, usually holding Theora or VP8 with Vorbis audio — and re-encodes it into the AVCHD stream format, then names the result .avchd. Everything below is about what that file genuinely is, what it is not, and what to rename it to.

How to Convert OGV to AVCHD

1. Upload Your OGV File: Drag the .ogv onto the page or click "Add Files" to browse. Several clips can be queued and each runs with the same settings.
2. Leave the Codecs Alone: Video Codec contains H.264 and nothing else; Audio Codec contains AC3 and nothing else. Those are the only entries in either list, because they are what the AVCHD specification permits. There is nothing to change and nothing to get wrong.
3. Set Video Resolution and File Compression: Video resolution opens on "Keep original", with Resolution Percentage, Preset Resolutions, Width, Height and Width x Height available. File Compression opens on Quality Preset at "Very High (Recommended)", with Specific file size, Constant Bitrate, Variable Bitrate, Constant Quality and Constraint Quality as alternatives. Trim takes a Start time and Duration.
4. Convert and Download: Click Convert and take the file. Files are uploaded over an encrypted connection, converted on our servers and deleted automatically after a few hours — no sign-up, no watermark, never shared or made public.

The AVCHD Specification, and What This Page Honours

Bitrate figures are as published in the official AVCHD format specification.

What the .avchd File Is at the Byte Level

This matters more than it sounds, because there are two different transport-stream packet layouts in play and the extension is what decides which one you get.

We converted the same source through this page's target and through the neighbouring ones and inspected the first bytes of each. The .avchd file begins with the sync byte 0x47 at offset 0 — that is a plain 188-byte transport stream, the broadcast layout. A .m2ts file from OGV to M2TS instead begins 0e bf 46 22 and puts its sync byte at offset 4, because BDAV framing prefixes every 188-byte packet with a 4-byte arrival-timestamp header for 192 bytes total.

The practical consequence is about renaming:

• Renaming movie.avchd to movie.mts is byte-accurate. Both are plain 188-byte transport streams, so the name matches the contents.
• Renaming it to movie.m2ts is not. You would be labelling a plain transport stream with the extension that implies BDAV framing, and a tool that checks the packet size will notice. If BDAV is what your workflow needs, use OGV to M2TS rather than renaming.
• Players that inspect the file rather than the name — VLC, mpv, MPC-HC and anything ffmpeg-based — open the .avchd as it comes.
• Camcorder software, authoring tools and most consumer players route on the extension and will ignore an unknown one entirely.

Common Errors and How to Fix Them

• "Nothing on my computer will open the file" — .avchd has no file association anywhere. Rename it to .mts or open it in VLC, which ignores the extension.
• "My camcorder software or Blu-ray player rejects it" — either the extension, or the fact that a loose stream is not a disc. Authoring software has to write the BDMV and STREAM structure around it first.
• "The picture is soft after I chose 1080p" — an OGV is usually modest web-resolution video, and upscaling stretches the pixels it already has rather than inventing new ones. Keep the resolution at or near the source size.
• "The file is enormous" — on H.264 the "Very High" preset resolves to a quality target — CRF 18 at 1080p, a step or two lower at smaller frame sizes — which is close to visually lossless, so it spends bits faithfully reproducing the compression artefacts your .ogv already had. Transport-stream packet overhead adds a little more. Use Constant Bitrate inside the AVCHD envelope, or Specific file size.
• "There is no sound" — check that the source .ogv actually had an audio track. Some screen-recorder and Wikimedia-sourced OGV files are video-only, and there is nothing for the AC-3 encoder to encode.
• "Comb lines through movement" — the source is interlaced and nothing in this pipeline deinterlaces. Deinterlace before uploading.

When This Doesn't Work

The single most common misunderstanding about this page is that it produces media a camcorder or set-top player will mount. It does not, and no converter can: a playable AVCHD disc or card needs the BDMV directory, the STREAM folder, clip-information and playlist files, and index metadata, all of which authoring software writes around a stream like this one. Copying the file loose onto an SD card will not make a camera recognise it. Tools such as multiAVCHD and tsMuxeR exist for exactly that step; this page produces their input.

The other honest caveat is about the source. AVCHD is a high-definition specification with defined resolution tiers and H.264 levels, and .ogv files are usually neither high-definition nor recorded with a camcorder-shaped picture. Forcing a 640x480 Theora clip up to 1080p produces a large soft file that satisfies the letter of the format and nothing else. If all you need is a playable video, OGV to MP4 is the better target by a wide margin.

Frequently Asked Questions

Why does the file have an .avchd extension instead of .mts or .m2ts?

Because AVCHD is a specification rather than a file type, and this page names its output after the specification. Camcorders write .mts to their own media and computers use .m2ts once a clip has been imported into a BDMV folder; neither name is produced here. The bytes are an H.264-plus-AC-3 transport stream either way — the extension is only a label your workflow may or may not accept. Rename it and nothing about the payload changes.

If I rename it, should I choose .mts or .m2ts?

.mts. Both this page and the MTS page write plain 188-byte transport packets with the sync byte at offset 0, so that rename is byte-accurate. The .m2ts spelling implies BDAV framing — 192-byte packets, each a 188-byte packet behind a 4-byte arrival-timestamp header — and our .avchd output does not have it. A player that ignores the extension will not care either way, but a tool that validates packet size will. If BDAV framing is genuinely required, convert again with OGV to M2TS instead of renaming.

Why can I not choose AAC or any other audio codec here?

Because AVCHD does not permit it. The specification allows Dolby Digital (AC-3) or uncompressed linear PCM and nothing else, so the Audio Codec list on this page contains AC3 alone rather than letting you build a file that calls itself AVCHD and is then refused by the first hardware player that reads it. If AAC in a transport stream is what you actually want — perfectly reasonable when the destination is a computer or a media server — use OGV to MTS or OGV to M2TS, where AAC is the value the list opens on.

Is the file I download a finished AVCHD disc or memory card?

No. What you get is the AVCHD video stream on its own. A player-ready AVCHD volume also needs the BDMV directory structure, the STREAM folder holding the media, clip-information and playlist files, and the index metadata a set-top player navigates. Authoring software writes all of that around a stream like this one. Treat this file as the correct input to that step, not as a substitute for it.

Will converting a small OGV to AVCHD make it high definition?

No. AVCHD is a high-definition format, but nothing can recover detail that was never recorded. Most .ogv files in circulation are web-resolution — Wikimedia Commons material, old HTML5 fallbacks, Linux screen captures — and selecting 1080p under the resolution controls simply stretches those pixels across a larger frame, producing a soft picture in a much bigger file. The output is genuinely HD only if the source was. Stepping up no further than 720p is the gentler compromise if a tool insists on an HD frame.

What bitrate keeps the file inside the AVCHD envelope?

The specification caps at 24 Mbit/s, dropping to 18 Mbit/s for material recorded to DVD media, with the 2011 AVCHD Progressive amendment raising the ceiling to 28 Mbit/s for 1080/50p and 1080/60p. This page does not enforce those limits, so set them yourself: switch File Compression to Constant Bitrate and pick a figure under whichever applies to your device. For a web-resolution OGV source, anything above roughly 8 Mbit/s is spending bits on artefacts the source already had.

What happens to the Vorbis or Opus audio in my OGV?

It is decoded and re-encoded to AC-3 — a transport stream conforming to AVCHD has nowhere to put a Vorbis or Opus track, and nothing here copies streams through untouched. The video is re-encoded too, including the rare case of an .ogv that already contains H.264. Because the source audio is already lossy, this is a second generation of loss on the soundtrack; keep the original .ogv if the audio matters and you might need to try a different target later.

Does converting to AVCHD deinterlace or tone-map anything?

No to both. There is no deinterlacing filter anywhere in this pipeline, so an interlaced source keeps its field structure and any combing is encoded into the output. There is no HDR tone-mapping stage either, so high-dynamic-range material gets a plain colour conversion and reads washed out on a standard-range display. Neither is a setting you have missed — both have to happen in a desktop tool before you upload.

How is my file handled during and after the conversion?

It is uploaded over an encrypted connection, converted on our servers, and both the upload and the output are deleted automatically after a few hours. There is no sign-up, no watermark, and nothing is shared or made public. Since the encoding runs on our side, the practical limit is upload size and connection speed rather than anything on your machine. If you only need part of a long recording, trimming it first with the video cutter shortens both the upload and the encode.