Skip to content

Understanding transcription

How to Search Across All Your Transcripts

What full-text search over a transcript library actually matches, what it misses, and how to phrase a query so it finds the moment you remember.

The Scriptorium team ·

Once you have transcribed more than a handful of recordings, the problem stops being "transcribe this file" and becomes "find the five minutes, somewhere across dozens of files, where someone said a specific thing." A transcript library only pays off if you can search it, so it is worth knowing what that search actually does before you rely on it.

It is a keyword search, not a mind reader

Search matches the words that are actually in a transcript's text, ranked by how well they match — it does not understand what you meant if you use a different word than the one that was said. Searching for "budget" will not find a segment where the word used was "spend" or "cost" instead.

The practical version of this: search for the specific word or phrase you remember hearing, not the general topic. "Renewal date" finds more than "contract stuff" does.

It jumps straight to the moment, not just the file

A result is not just "this recording contains that word" — it is the exact segment, with its timestamp, so you can jump straight to the moment it was said and confirm it in context rather than re-reading a whole transcript to find one line.

It only searches your own library

Results are scoped to your own account — search never reaches into anyone else's transcripts, including on a shared or team deployment. What you can search is exactly what you can already open.

What it will not find

  • A word that was said but transcribed wrong. If the transcript itself has the wrong word in that spot, searching for the right one will not surface it — this is the main reason correcting recurring terms after transcribing is worth doing.
  • A concept discussed without the word you searched for ever being used.
  • Anything in the audio that has not been transcribed yet.

This is also why the correction pass matters for more than just readability: a transcript you never fix stays hard to search, not just hard to read.

Building a library worth searching

Search gets more useful the more you have transcribed, which is really an argument for transcribing routinely rather than only when something specific is needed. A year of meeting or call transcripts, kept and lightly corrected, turns into an archive you can actually query later — the alternative is trying to remember which recording something was in, or re-listening to find out.

Questions

Does transcript search understand synonyms?
No — it matches the words actually present in the transcript text. Search for the specific word you remember, not a rough paraphrase of the topic.
Can search find something in someone else's transcripts?
No. Search is scoped to your own account only, on a shared or team deployment as much as anywhere else.
Why does a search miss something I know was said?
Either the transcript has the wrong word in that spot, the recording has not been transcribed yet, or the exact word you searched for was never used — only paraphrased.

Transcribe a file

Free for a first file, with no account.