Review the part of a meeting you actually recorded
Choose an existing permitted local meeting recording up to 100 MB. This page does not log in to Zoom, import a private cloud link, join a meeting or generate automatic minutes.
1. Which meeting recording should I use?
Check the actual file, its start and end, and whether it covers the discussion you need. A recording that starts late cannot establish an earlier decision. The practice video is a historical speech with a neutral picture, not a Zoom meeting or platform export test.
Check: The source coverage is known; missing sections remain explicitly missing.
Back to the tool2. What processing happens locally?
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.
Check: The browser reaches a transcript or a specific failure without uploading the recording.
Back to the tool3. How do I check decisions and who agreed?
Search for the relevant phrase and replay the reply, including qualifications or objections. Assign names manually only when the source supports them. A transcript does not automatically establish agreement, ownership or an action deadline. Click a transcript timestamp to seek in the local recording player. Replay the surrounding phrase before editing its cue. Text edits do not move cue boundaries. Use Find in this transcript to locate an exact word in the latest edits; Previous and Next navigate matches, Enter moves forward, Shift+Enter moves back, and Escape clears the search.
Check: Spoken words and your meeting interpretation remain distinguishable.
Back to the tool4. How do I record meeting times accurately?
A local cue at 00:30 is relative to this recording, not the wall clock. If you know the recording start, document that mapping separately; do not invent missing coverage. 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.
First cue from the actual teaching export (including the deliberate [reviewed] edit):
1 00:00:00,000 --> 00:00:07,740 And so my fellow Americans ask not what your country can do for you [reviewed]
Check: Your notes identify the source and any known offset.
Back to the toolMore questions and limits
Does my recording leave this device?
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.
What if decoding or the language check fails?
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.
Can I cancel and try again?
Only one transcription task runs at a time. Cancel processing discards its result; an in-progress model or audio operation may need to finish before controls unlock. Then use Try the same input again. Choosing another input clears the previous retry target. A cancellation is not a transcript of silence.
Where is the complete audio workflow?
Audio to Text explains search, text corrections and output choices. For timing changes, use Subtitle Editor.
Historical measurements and method limits
Measured browser timings
These are historical measurements from 2026-09-14 using only whisper-tiny.en. They do not measure the current language-detection plus English-transcription workflow, and exclude Instagram lookup and media download.
| Audio length | Historical wall-clock time | Historical model load |
|---|---|---|
| 11 s | 16.89 s | included |
| 11 s | 6.49 s | already in memory |
| 30 s | 8.98 s | already in memory |
| 60 s | 16.06 s | already in memory |
| 120 s | 28.58 s | already in memory |
In the historical test, the first run included model loading; subsequent runs retained the English model in memory. Current jobs release that instance before language detection, so a resource cache hit still requires initialization. Wall-clock time is not CPU time, and subtracting two runs does not isolate download or initialization time.
One machine, one WASM browser, one run per historical data point. Audio clips were constructed from a repeated public JFK recording. These rows do not predict today's end-to-end time, other devices or other recording content.
Sources: historical raw CSV · current two-model measurements (2026-10-14) · method, environment and limitations.
InstaScript is independent and is not affiliated with or endorsed by the source platforms mentioned here.