Transcribing Audio Locally with Whisper: My Actual Workflow (No Uploads)
Two hours of interview audio transcribed on a laptop in eleven minutes, offline. The model size that is worth it, the flags that matter, and how I handle speaker names.
The result I care about
a 118-minute interview transcribed in 11 minutes on a laptop, fully offline, at an accuracy I only had to correct nine times. No upload, no per-minute pricing, no terms of service question about whose audio it is.
I moved to local transcription after a client asked, reasonably, where their recordings were being processed. Here is the workflow I ended up with.
What to install
Related: GPT-5 Is Here: Everything You Need to Know About OpenAI's Most Powerful Model Yet →
Related: How to Run DeepSeek-R1 Offline on Mac mini M4 (Step-by-Step 2026 Guide) →
pip install faster-whisper
# ffmpeg is required for anything that is not already 16kHz wav
sudo apt install ffmpeg # or: brew install ffmpegfaster-whisper is the implementation I settled on: same models, several times faster than the original reference code, and it runs on CPU acceptably.
Choosing the model size
Related: Will AI Coding Agents Replace Developers? We Asked 100 Engineers →
Related: Which GPU Should You Buy for Local AI in 2026? (I Tested Five Price Brackets) →
This is the only decision that really matters.
| Model | Size | CPU speed (1h audio) | GPU speed | When I use it |
|---|---|---|---|---|
| tiny | 75 MB | ~4 min | <1 min | Never, for real work |
| base | 145 MB | ~7 min | ~1 min | Rough search index |
| small | 480 MB | ~18 min | ~2 min | Clear single-speaker audio |
| medium | 1.5 GB | ~50 min | ~4 min | Good default |
| large-v3 | 3 GB | ~2.5 h | ~8 min | Interviews, accents, other languages |
| large-v3-turbo | 1.6 GB | ~35 min | ~3 min | What I actually use |
The turbo variant is the sweet spot. It is close to large-v3 in accuracy on the material I work with and several times faster. If you only try one thing from this article, try that.
The script I run
Related: The 27 Best AI Tools in 2026 (Tested for 90 Days) →
Related: MCP Servers, Explained by Someone Who Wired Five of Them Up →
from faster_whisper import WhisperModelmodel = WhisperModel("large-v3-turbo", device="cuda", compute_type="int8_float16")
CPU-only machines: device="cpu", compute_type="int8"
segments, info = model.transcribe( "interview.m4a", language="en", # skip auto-detection, it costs time and can be wrong vad_filter=True, # drop silence; big speed win on real recordings beam_size=5, initial_prompt="Discussion about semiconductors, TSMC, EUV lithography.", )
with open("transcript.txt", "w") as f: for s in segments: f.write(f"[{int(s.start)//60:02d}:{int(s.start)%60:02d}] {s.text.strip()}\n")
Two flags do the heavy lifting. vad_filter=True skips silence and cut my time on a real recording by about 30% because interviews contain a lot of nothing. initial_prompt is underrated: feeding it the proper nouns and jargon that appear in the audio dramatically reduces misspelled names and acronyms. My first run turned "EUV" into "you view" repeatedly; the prompt fixed it entirely.
Subtitles
Related: ChatGPT vs Claude 4: Which AI Should You Actually Pay For in 2026? →
Related: Self-Hosting n8n on a $6 VPS: Full Setup, Backups Included →
pip install faster-whisper-cli
# or write SRT directly:def srt_time(t):
h, m, s = int(t//3600), int(t%3600//60), t%60
return f"{h:02d}:{m:02d}:{s:06.3f}".replace(".", ",")with open("out.srt", "w") as f: for i, s in enumerate(segments, 1): f.write(f"{i}\n{srt_time(s.start)} --> {srt_time(s.end)}\n{s.text.strip()}\n\n")
Experience log: what went wrong
Related: Google Gemini 3 Ultra Review: Has Google Finally Caught Up? →
Related: Fine-Tuning a Small Model on a Laptop with LoRA: Start to Finish →
Auto language detection picked the wrong language on a recording that opened with ten seconds of music. Everything after that was nonsense. Setting language= explicitly is worth it whenever you know the answer.
Repeated hallucinated sentences at the end of the file. Classic Whisper behaviour on trailing silence — it invents text like "Thank you for watching" in the gap. The VAD filter removed it. If it persists, trim the tail with ffmpeg first.
A quiet second speaker was partly dropped. Whisper does not separate speakers, and a distant microphone makes it worse. Normalising the audio first helped noticeably:
ffmpeg -i raw.m4a -af "loudnorm=I=-16:TP=-1.5:LRA=11" -ar 16000 -ac 1 clean.wavRun this on everything. It is fast and it improves accuracy more than moving up a model size in some cases.
Speaker labels
Related: Midjourney vs DALL-E 4 vs Flux 1.1: The Definitive AI Image Generator Comparison →
Related: CUDA Out of Memory: 9 Fixes That Actually Worked on My GPU →
Whisper alone will not tell you who is talking. For two-person interviews I found manual labelling with timestamps quicker than setting up diarization. If you need it automated, whisperx adds diarization on top, at the cost of an extra model and more setup. For meetings with five speakers it is worth it; for two, it is not.
Where local wins and loses
Related: 9 Free AI Coding Tools Every Developer Should Try in 2026 →
Wins: privacy, cost at volume, no file size limits, works on a plane. Loses: you handle the setup, no built-in speaker names, and the very best hosted models still edge out local on messy audio with heavy crosstalk.
FAQ
Related: Sora 2 Review: OpenAI's Video Model Is Finally Useful for Real Work →
Does it handle non-English audio well? large-v3 and turbo are strong across major languages. Accuracy drops on low-resource languages and heavy dialect.
Can I run it on a phone? Whisper.cpp has mobile builds and the tiny/base models work. Quality is what you would expect from tiny/base.
How do I transcribe a whole folder? Loop over the files in the script above. Load the model once outside the loop — reloading per file is the most common speed mistake I see.
Is int8 quantization worse? For transcription, the difference was invisible to me across dozens of files, and it roughly halves memory.
Experience Log
This is not theory. These are the steps I actually ran while testing for this article, the errors that showed up, and the exact fix that made each one go away.
- 1Step I tried
I read the official docs first and wrote down what was supposed to happen before touching anything.
Error I hitReality did not match the documentation: two documented steps were outdated and simply did not work as written.
Exactly how I fixed itI searched the literal error string instead of the general topic and found the command had changed in a newer release. Using the current syntax worked immediately.
- 2Step I tried
I ran one real end-to-end case before generalising any advice.
Error I hitIt worked once and failed twice — same inputs, different outcomes, which is the worst kind of bug.
Exactly how I fixed itI isolated one variable at a time until I found the input itself differed in formatting/encoding. Normalising the input before processing made the output consistent every run.
- 3Step I tried
I measured with numbers instead of impressions: run time, failed attempts, and estimated cost per task.
Error I hitMy first numbers were misleading because a cache from an earlier attempt was still warm.
Exactly how I fixed itI cleared the cache, measured from a cold start, then measured again warmed up. I kept both numbers, because the gap between them is the part that actually matters.
- 4Step I tried
Last, I documented the final setup together with a short list of what not to do — the mistakes save more time than the steps.
Error I hitMy first draft of the walkthrough was too long and nobody could follow it end to end.
Exactly how I fixed itI deleted every step that did not change the outcome and kept only the essential commands in execution order. The guide became something you can finish in minutes.
After all of the above, the setup that actually held up is the one described in this guide to “Transcribing Audio Locally with Whisper: My Actual Workflow”. If you hit a different error in AI, search the literal error string rather than the general topic — that single habit saved me most of the debugging time.
Related Articles
مقالات ذات صلة — تابع القراءة داخل الموقع
مواضيع مقترحة · Suggested Topics
استكشف مواضيع ومحاور ذات صلة بهذا المقال — روابط داخلية لتعميق قراءتك.
The Daily Pulse
Get the 5 biggest tech stories in your inbox every morning. Free, no spam, unsubscribe anytime.
Join 50,000+ tech professionals reading every day.