Drop an Ogg file. Any size.
safe · secure · no server · works offline · fast
…or just start typing at the cursor.
safe · secure · no server · works offline · fast
…or just start typing at the cursor.
Ogg is a container, not a codec: the same
.ogg / .opus / .oga wrapper carries
Vorbis, Opus, FLAC,
Speex or Theora inside it. Drop the file and
OmniViewer reads the container the way the Ogg spec does: a stream of
pages, each with the OggS capture pattern, a
granule position, a bitstream serial number and a CRC, lacing the codec’s
packets back together. The PAGES tab lists every one
— sequence, serial, flags, granule, size — so you can see exactly
how the audio is framed. Nothing is uploaded, and the audio body is never read
into memory, so even a multi-gigabyte recording opens in a couple of tiny reads.
An Ogg stream keeps its metadata in a comment header right at
the front — VorbisComment for Vorbis/FLAC,
OpusTags for Opus — a simple list of
KEY=value pairs. OmniViewer’s METADATA tab
shows every tag and lets you edit, add or remove them, then download a
re-tagged copy. The trick that makes this instant on huge
files: only the header pages are rebuilt, padded so the header keeps the
exact same page count — so every audio page keeps its
sequence number and is copied byte-for-byte. The audio is
never re-encoded and loses no quality. Curious how it works? Read
inside an Ogg file: pages, packets and codecs.
The STATS tab reads the codec’s identification header for the channel count and sample rate, derives the duration from the granule position of the last page (one read at the end of the file), and reports the bitrate and every logical bitstream the file multiplexes — all without decoding a single audio frame.
The PLAYER tab uses your browser’s own decoder: Chrome,
Firefox and Edge play Ogg Vorbis and Opus; older Safari builds don’t.
When the browser can’t decode it, OmniViewer says so plainly — and
the METADATA, PAGES, STATS and hex tabs read the container directly and work
in every browser. Detection is by the file’s OggS magic,
never the extension. Powered by the same engine as
fastjsonviewer.com and
hugecsv.com; OmniViewer opens
every file format.
No. OmniViewer is a static page with no server-side processing: your Ogg file is read directly by your browser and never leaves your computer. Even the re-tag download is assembled locally, from byte slices of your original file.
Ogg is a container format, not a codec. The file is a sequence of pages — each with the "OggS" capture pattern, a granule position (a codec-defined timestamp), a bitstream serial number, a CRC and a segment table — and those pages lace the codec’s packets back together. The codec inside is usually Vorbis or Opus, but can be FLAC, Speex or Theora (video). One file can multiplex several logical bitstreams, each with its own serial number.
They are all the same Ogg container. Historically .ogg meant Ogg Vorbis; .oga is Ogg audio generally; .opus is the conventional extension for Ogg Opus. OmniViewer detects the container from the file’s OggS magic and the codec from its first packet, so it opens all three the same way regardless of the extension.
Yes — that is the point. The VorbisComment/OpusTags metadata lives in a small comment header at the front of the stream. OmniViewer rebuilds just those header pages with your edits and copies every audio page byte-for-byte, so the audio is never touched and loses no quality. The header is padded to keep its page count identical, which is what lets the downstream pages be copied unchanged and makes re-tagging instant even on a multi-gigabyte file.
Open the METADATA tab. It lists every VorbisComment/OpusTags field — TITLE, ARTIST, ALBUM, DATE, GENRE and any custom key — as an editable KEY=value row. Change what you want, add or remove tags, and click "Download re-tagged copy". Editing is available for single-stream Vorbis and Opus files; multiplexed files (e.g. Ogg Theora with an audio track) are read-only for now.
Effectively unlimited. The codec headers and the metadata sit in the first pages, and the duration comes from the granule position of the last page — so opening the file, reading its tags and stats, and even re-tagging it cost a handful of small reads at any size. The audio body is only touched by the browser’s player, which streams it.
It is Ogg’s per-page timestamp: the number of samples (for Opus, always at 48 kHz, minus the pre-skip) decodable by the end of that page. OmniViewer reads the last page’s granule position to compute the total duration without decoding the audio, and shows every page’s granule in the PAGES tab.