Check an Ogg file before retrying recognition
Ogg is a container. A valid extension is not a guarantee that the codec inside can be decoded by your browser. This guide sends you to the existing audio tool.
1. Begin with a complete local Ogg recording
Choose a recording you may process, up to 100 MB, and check the opening and closing seconds in a player. The public practice file uses Opus inside Ogg; it is a real encoded sample, not a renamed WAV. One sample does not verify all Ogg codecs.
Check: You have the actual recording rather than a messaging-app link or partial download.
Continue in the matching tool2. Locate the failure stage
Open Audio to Text and select the Ogg file. The browser first decodes the recording, checks its language with a multilingual checkpoint, then recognizes English with a separate English checkpoint. First use may download both models. Cached resource files can avoid another download, but they do not guarantee an initialized model: the English instance is released before the next language check. There is no fixed completion time. An undecodable file is different from a language result. Detected non-English speech stops recognition; an uncertain result or a technical language-check failure stops with a separate message and creates no transcript. For a damaged or unsupported file, export a new playable audio copy from its source: renaming the extension does not convert it. Recording Format Guide explains these boundaries.
Check: A decoder failure, uncertain language result and model/network failure are not treated as the same outcome.
Continue in the matching tool3. Review words and save the output
Replay the recognized speech before using it. The accompanying illustration comes from the real Opus/Ogg practice run in Audio to Text, not from a separate Ogg engine. Copy, TXT and Markdown use your edited words and are untimed by default. Enable Include timestamps in TXT, Markdown and Copy to include available start times. Markdown escapes markup and exports transcript paragraphs, without creating a summary. SRT, VTT and Open in Subtitle Editor require nonempty text and complete valid start/end times; missing ends are not estimated. If timing is incomplete, save TXT or Markdown and keep the recording.
Check: The saved file contains your edits and any timed output has valid cue ranges.
Continue in the matching toolMore questions and limits
What processing and privacy boundaries apply?
Local decoding, recognition, replay, edits and downloads run in your browser. Model resources need network access, but the local recording and transcript are not uploaded. There is no account history or saved cloud project; download your work before closing the tab. Same-origin editor transfer keeps the cues and recording local between tabs. Instagram URL retrieval and YouTube caption lookup have separate server-assisted privacy boundaries.
Where should I continue?
Open the matching tool and follow its current input requirements. Keep the original, review your result and download it before closing the tab.