Voice memos are drafts, not documents

A voice memo is usually spoken the way people think: in fragments, repetitions, and half-finished sentences. Transcription keeps those fragments, so the first draft is closer to notes than to polished prose. That is expected, and it is why the review step exists.

Before transcribing, decide what the memo is for. A shopping reminder needs only the items; a client idea needs names, dates, and commitments. The purpose tells you which words to verify and which fragments can be dropped in the final note.

Record with transcription in mind

Quiet surroundings and a nearby microphone improve recognition more than any setting in the tool. If you record while walking outdoors or with music playing, expect more errors in the draft. The file also matters: the local workflow accepts MP3, WAV, M4A, and MP4 up to 200 MB or 20 minutes, which is generous for voice notes.

Keep one idea per recording when practical. A single memo with three unrelated topics takes longer to organize than three short files. If you already have a long memo, the transcript timestamps let you split it by topic during review.

The quick capture workflow

The fastest reliable path is short: record, upload the file, choose the language, add the names and terms you expect, transcribe, skim the text, fix the important words, and export. Most of the time is spent in the skim, not in the processing.

You can add names, dates, places, and product terms to the glossary field before starting. The list guides the local model and gives you a checklist. It does not insert anything automatically, so a word that was not spoken should not appear in the final note.

  1. Record one topic per memo in a quiet environment.
  2. Upload the file and add names, dates, or terms that matter for this note.
  3. Transcribe, skim with the timestamps, fix what matters, then export TXT or JSON.

Check names, dates, and commitments

A voice note is most often wrong where the stakes are highest: a person’s name, a date, a price, or a promise like “I will send it on Tuesday”. Search the draft for those words and replay the corresponding audio position before accepting them.

If the recording is unclear and the commitment matters, write “confirm with [person]” with the timestamp in the note instead of guessing. A note that flags uncertainty is more useful than a clean-looking note with a wrong date.

Turn fragments into notes

After verifying the important words, rewrite the fragments into a readable note in the editor: combine related sentences, remove filler such as “um” and “you know”, and keep the meaning. The textarea keeps the segment timestamp, so the rewritten note still points back to the audio.

Do not delete the original recording after editing. The edited note is your working document, but the recording is the source of truth if a question comes up later.

A concrete example: a raw memo might say “call Maya, Tuesday, the proposal price, and ask about the Azure discount, also remember the logo”. The cleaned note becomes “Call Maya on Tuesday: confirm the proposal price and ask about the Azure discount. Follow up on the logo.” The meaning stays, the filler goes, and the timestamp still points to the recording.

When manual language selection helps

Auto detect works well for a short memo with one clear language. Choose the language manually when the memo is very short, contains a strong accent, or starts with music or background noise. A manual choice removes one source of variance and makes the draft more predictable.

If you switch languages inside one memo, the transcript will be less reliable at the transition points. Listen to those sentences and correct names and numbers by ear, treating the draft as a first pass.

Privacy and device expectations

The transcription runs locally: the audio is not uploaded to a server for processing. The first run downloads the speech model and caches it, so setup needs an internet connection once, while later runs can reuse the cache. No account or registration is needed.

The transcript exists only in the current page session until you export it. Save the export if you need the note later on another device or after closing the tab. Local processing is a privacy boundary, not a backup or synchronization service.

A weekly voice memo cleanup routine

A practical pattern is record often, transcribe once a week. During the week you capture ideas as they happen without interrupting the moment. On a fixed day, upload the files from the week, transcribe them in one sitting, and work through each note with one of three outcomes: file it, act on it, or delete it. The cached model makes repeat runs faster, and the batch habit keeps the review small enough to maintain.

For the weekly pass, sort the notes into an actionable item with a date or owner, a reference note that belongs in a project file, or a fragment that has lost its purpose. Export the first two and delete the third if the recording no longer matters. Keep the timestamps in the exported note so a later question can be checked against the original memo.

Organize the exports

TXT is easiest for pasting into your notes app; JSON keeps segments and timestamps for a personal archive or script. Use a simple naming pattern such as date plus topic so the exported files are searchable later. A small habit of naming files at export time saves more time than any tool feature.

For the interactive workflow, use the voice to text tool. If the memo is a longer recording you want to prepare carefully, the audio preparation guide explains recording checks and language choices in more detail.