Choosing a transcription app shouldn't take this much research.

Buzz is the kind of tool that handles a single problem and then leaves you alone. The problem — running OpenAI's Whisper model on a file that shouldn't leave your device — used to mean spinning up a virtual environment, running a handful of pip install commands, and a coin-flip chance of hitting a cryptic ffmpeg error. Buzz compresses all of that into a window with a "Transcribe" button. Drop in your audio, pick a model, watch progress tick along. Output lands in a folder. That's it.

That's the whole story. The pitch sounds modest because the surface is deliberately minimal. What makes it interesting is everything it omits: no account registration, no cloud uploads, no push toward a premium credits plan. It's a thin shell around a powerful model. After extended time with it across two laptops and three operating systems, that restraint turns out to be the app's biggest asset.

What Buzz is, exactly

Buzz is an open-source desktop app built by Chidi Williams. The GitHub repository has been active since 2022 and keeps receiving updates. Internally, it packages two transcription engines: the original OpenAI Whisper implementation in Python, and the considerably faster whisper.cpp port in C++. You choose between them at the model selection screen — and the right choice depends on the hardware you're working with.

Users familiar with Audacity will recognise the spirit immediately: utilitarian, slightly behind the times in its widget styling, and very clearly built by people who care more about the output than the visuals. No inflated whitespace or feature dashboards. The main window is a job list — each row tells you whether a transcription is queued, running, or complete.

The real experience of using it

The standout first impression is the time from "freshly downloaded" to "transcript in hand." On a 2021 M1 MacBook Pro, the whole setup took roughly three minutes — most of it spent on the initial model download, which weighs in around 1.5 GB for the medium size. On a five-year-old Windows machine with no discrete GPU, transcription itself took longer, but the setup process was identical.

The interface is not pretty — worth saying upfront. It's built with PyQt and carries all the visual charm that implies: functional in the way a folding knife is functional. You won't use it to demonstrate Mac aesthetics to anyone.

I tested it on a 47-minute interview recorded for an unrelated project. The tiny model finished in around 90 seconds and got the gist. The medium model took four minutes and caught most proper nouns. The large model ran for about fourteen minutes and produced output I'd actually show someone.

The highest compliment I can offer Buzz is that it disappears. You start a job, you walk away, the file is there when you come back.

What's happening inside

Buzz lets you choose between several model sizes (tiny, base, small, medium, large) and several backends. The most important choice is between the original OpenAI Whisper Python implementation, the whisper.cpp backend, and Hugging Face's transformers-based implementation. There's also support for using OpenAI's hosted Whisper API if you'd prefer to send the file to OpenAI in exchange for faster results — but that defeats the privacy advantage, and almost no one I know who installs Buzz uses that mode.

Two practical observations from real-world use:

• On Apple Silicon, the whisper.cpp backend with Core ML acceleration is the fastest by a wide margin. You'll want to enable that.
• On any machine with a recent NVIDIA GPU and CUDA installed, the original PyTorch backend will tap the GPU and become noticeably faster — large-model transcriptions that took 25 minutes on CPU finished in under four minutes. Install CUDA drivers first if you're on Windows with an NVIDIA card.

Buzz also supports a "Live Recording" mode where it'll transcribe directly from your microphone as you speak. I've used this feature exactly twice, and both times I came away thinking that this is not what Buzz is for. The latency is wrong for it — you'll get text in chunks of several seconds — and it doesn't integrate with other apps. If you want dictation that drops text where your cursor is, look at VoiceInk instead. If you want live captions for a video call, look elsewhere entirely. Buzz is a file-based tool with a microphone option grafted on, and you can feel the seam.

Pros and cons

Step-by-step: from download to transcript

This is the section most write-ups skip, so here it is. The complete flow, from "I haven't installed anything" to "I have a clean SRT", without skipping the parts that actually trip people up.

1. Grab Buzz from the official GitHub releases page. Pick the build for your operating system. On macOS, that's a .dmg; on Windows it's an .exe installer; on Linux you've got AppImage and Snap options.
2. Install it like any other app. On Mac, drag to Applications. On first launch, macOS may complain about an unidentified developer; control-click and choose "Open" once and the warning goes away.
3. Open Preferences and set your preferred backend. On Apple Silicon, "Whisper.cpp" with Core ML support is the right answer. On Windows with an NVIDIA GPU, the OpenAI Whisper backend will use CUDA. Otherwise, leave it on the default.
4. Drop your audio or video file into the main window. Buzz accepts MP3, WAV, M4A, FLAC, MP4, MOV — basically anything ffmpeg can read.
5. Select a model size. Start with base if you're not sure. Move up to medium for cleaner output. The large model is the most accurate but slow and memory-hungry.
6. Choose your output formats. For interviews, TXT plus SRT is the right combination. The first is for reading; the second is for any future cleanup work in a subtitle editor.
7. Press Transcribe and go do something else. Seriously. Make a cup of tea. The progress bar updates honestly. When it finishes, the output files appear next to the source.

How Buzz stacks up against the others

Staying within this site's shortlist, here's how Buzz stacks up against the others:

Versus Subtitle Edit: Subtitle Edit can run Whisper too, but it's a much bigger tool — full waveform editor, an enormous range of subtitle formats. If captioning or translation is your work, Subtitle Edit is probably already your main app and Buzz adds nothing new. If you just need a transcript, Buzz has a shorter learning curve.

Versus Whisper Transcription (Mac): Whisper Transcription is more refined, visually cleaner, and slots into macOS more naturally. It's also Mac-only and locks some features behind payment. Buzz is less attractive but costs nothing on any platform.

Versus Pyrenees: Pyrenees is faster on Apple Silicon — definitively — but exclusively on Apple Silicon. If you're running an M-series Mac and working with shorter files, Pyrenees wins on speed. Buzz holds the advantage for cross-platform use and its range of backend options.

Versus VoiceInk: Different tool for a different job. VoiceInk is for live dictation (talking into apps as you'd talk into iOS dictation). Buzz is for files. They don't really compete.

Who Buzz is right for

FAQ

Here's an admission upfront. The first time I sat down with Subtitle Edit, I closed it after fifteen minutes and went back to Buzz. The interface resembled a Windows XP control panel held together by determination, and I couldn't work out how to get Whisper running inside it. I assumed something was broken. Nothing was. I'd just misunderstood what kind of application I was dealing with.

Subtitle Edit is not a transcription tool with caption editing tacked on. It's a caption editor with transcription capability built in. That distinction changes everything about how you learn to use it.

Two workflows, two kinds of users

There are essentially two workflows the app supports, and people who try Subtitle Edit generally fall into one of two camps based on what they came for.

Workflow A: you have an audio or video file and you want clean, correctly-timed captions. You import the media, you tell Subtitle Edit to run Whisper on it, you wait. You get a populated cue list. Then you spend twenty or thirty minutes cleaning it up: fixing punctuation, merging short cues, splitting long ones, retiming the parts where the model got confused. The output goes out as .srt or whatever else you need. This is the workflow professional captioners use.

Workflow B: you have a transcript already (from Buzz, from Whisper Transcription, from Otter, doesn't matter) and you want to fix it. You open the existing file, you bring in the audio so the waveform syncs with the cues, and you fix the obvious mistakes by listening and clicking. This is what I personally use it for, and I think it's the underrated use case. Even if your primary transcriber is something else entirely, Subtitle Edit makes a phenomenal "second tool".

What using it day-to-day feels like

The interface is dense. There's no softer way to put it. Every pixel earns its place. On first launch you see a toolbar with maybe a hundred icons, a waveform panel occupying the bottom third of the screen, and a cue list between them. It's a lot.

Spend an afternoon with it and the density starts feeling like a feature. The reason every command has a keyboard shortcut is that captioners work at pace — they need to jump from a timestamp correction to a spell-check to an export without lifting their hands from the keyboard.

Whisper integration sits under Video → Audio to text (Whisper). From there you choose the engine — Subtitle Edit supports the original Python Whisper, whisper.cpp, Const-me's GPU implementation, Purfview's Whisper Faster, and a couple of others depending on which version you have installed. Each engine has its own strengths. On a Windows laptop without a GPU, Purfview's implementation gave me the best balance of speed and accuracy. On a machine with an NVIDIA card, Const-me's GPU build was faster than anything else by a wide margin.

The format support is genuinely extraordinary

This is the part nobody talks about, and the thing that makes Subtitle Edit irreplaceable in some workflows. The app reads and writes well over two hundred subtitle formats. If you've ever stared at a file with a strange extension and wondered how to convert it to .srt without losing timing or styling, Subtitle Edit is almost certainly the answer.

A partial list of what it handles:

• The everyday ones: SRT, VTT (WebVTT), ASS, SSA, TXT
• Broadcast formats: EBU STL, Cavena 890, EBU-TT, EBU-TT-D, IMSC 1.1, TTML, DFXP, SCC, SMPTE-TT
• DVD/Blu-ray: VobSub (.sub/.idx), SUP (BD), and OCR support for both
• Streaming/professional: Netflix's IMSC variant, Apple iTT, MicroDVD, MPL2
• Weird and old: JSON Web, FAB, Sonic Scenarist, ATS, plus a long tail of pretty obscure formats

If your transcription job ends with "and then we hand it to a broadcaster," Subtitle Edit may be the only free tool capable of producing a file that will actually pass.

Where it stumbles

Honest section. Subtitle Edit is not for everyone, and there are genuine friction points beyond the dense interface.

The platform story is uneven. The Windows version is a proper, signed, native application that has had two decades of polish. The Mac version is a newer port that runs natively on both Intel and Apple Silicon, but feels less mature — keyboard shortcuts that work flawlessly on Windows occasionally do nothing on Mac, certain dialogs appear off-screen, and waveform extraction sometimes fails on file types that work fine on the Windows build. On Linux, you're typically running it through Mono, which works but has its own assortment of papercuts. If you're not on Windows, expect rougher edges.

It's not a transcription-first app. If your goal is to get a clean .txt transcript and you don't care about timing, you'll find yourself fighting a UI that wants you to care about timing. You can absolutely use it for plain transcripts — just export to TXT after the cues are populated — but you'll spend a lot of attention on widgets you didn't need.

The translation features are uneven. There are translation integrations (Google, DeepL, libretranslate, ChatGPT API, others), but the quality varies and the UX of running them feels grafted on. For pure translation work, you're better off elsewhere.

The learning curve is real. Out of every tool we cover on this site, Subtitle Edit has the steepest first-week curve. Plan for it.

Pros & cons, condensed

How to use it: three short walkthroughs

Because Subtitle Edit covers more than one workflow, a single step-by-step guide doesn't quite fit. Here are three focused ones instead.

1. From audio file to clean SRT (full Whisper workflow)

1. Open Subtitle Edit and load your video or audio. File → Open video file. The waveform should appear at the bottom; if it doesn't, the file extension may not be supported and you'll need to convert.
2. Open the Whisper dialog: Video → Audio to text (Whisper). Pick the engine and model size. Faster-Whisper with the medium model is a good default on most Windows machines.
3. Let it run. Progress shows in a small log window. A 30-minute file on a midrange Windows laptop typically completes in 8–15 minutes.
4. Review the cue list. Each cue is a row. The waveform shows where it sits in the audio. Use the keyboard arrows to step through cues; spacebar plays the current one.
5. Fix obvious problems. Common ones: cues that are too long (use Tools → Split lines longer than…), overlapping cues, wrong proper nouns. Most of this can be handled with built-in batch tools.
6. Export. File → Save as → SRT for general use, or whichever format your downstream tool needs. Subtitle Edit can also do batch convert in case you have many files.

2. Cleaning up an SRT another tool already produced

1. Open the existing SRT in Subtitle Edit (File → Open).
2. Bring in the original audio via Video → Open video file. The waveform now syncs with the existing cues.
3. Run "Fix common errors" from the Tools menu. This catches things like missing spaces after periods, capitalization issues, double spaces, and Whisper's habit of starting cues with hesitation markers.
4. Walk through the cues that look suspicious — usually the very long ones and the very short ones — and fix them by listening to the audio.
5. Save. Done.

3. Extracting subtitles from a Blu-ray rip

1. File → Import → VobSub or Blu-ray sup, depending on what you have.
2. Choose the OCR engine. The built-in nOCR is decent for European languages; Tesseract is better for some scripts.
3. Run OCR. Review the results and correct any glyphs the engine misread.
4. Save out as SRT for use anywhere else.

Subtitle Edit vs. the others

Measured against the rest of the shortlist:

Compared to Buzz, Subtitle Edit is the heavy tool. Buzz is for "I have a recording, I want a transcript". Subtitle Edit is for "I have a recording, I want broadcast-ready captions, and I'm willing to spend an afternoon getting them right." Both are free; they're answers to different questions.

Compared to Whisper Transcription, Subtitle Edit is dramatically uglier and dramatically more capable. Whisper Transcription will get you a clean transcript faster on a Mac. Subtitle Edit will let you actually shape it.

Compared to Pyrenees, the comparison doesn't really hold — Pyrenees is a transcription engine optimized for speed, Subtitle Edit is an editing environment. They could even live alongside each other: Pyrenees produces, Subtitle Edit edits.

Compared to VoiceInk, they share no overlap at all. Different jobs.

Who it's for

FAQ

Setting expectations

This is one of the rare apps in this space where someone clearly designed it rather than simply shipped it. You can tell immediately. The icon doesn't look like a Python logo with a microphone grafted on. The window has the right corner radius. The settings panel uses the macOS sheet style that actually lets you find what you need. When you import a file, the app shows you metadata — sample rate, channels, duration — that most transcription tools simply ignore.

None of this changes the underlying transcription quality. Whisper is Whisper, regardless of which app calls it. So the question Whisper Transcription has to answer is: given that the model is the same, what does this app give me that the free options don't?

The honest answer, after two weeks of regular use: a collection of small things, none individually decisive, that together add up to "this is the app I'd hand to someone who doesn't want to think about it."

What it actually does

The core flow matches every other tool in this category. Drop in a file, select a model, press a button, receive text. Where Whisper Transcription sets itself apart is in the details.

The transcript view is interactive. Click a sentence, the audio jumps to that timestamp. Edit the sentence in place. Highlight a span and you get inline tools to merge cues, split them, change capitalization, mark a speaker. It's not Subtitle Edit's level of cue-editing power, but for working with prose-style transcripts, it's genuinely faster than re-opening your output in another app.

It can capture system audio, not just microphone. A small but uncommon feature. If you want to transcribe a YouTube video, a podcast you're listening to, or a Zoom call (with appropriate permissions), Whisper Transcription can pipe the system's audio output directly in. Most of the free alternatives only see the microphone.

Export is well thought through. SRT, VTT, plain text, and DOCX are all one click away. The DOCX export in particular is more polished than what you'll get from running Whisper through a script — it preserves paragraph breaks at sensible points, includes timestamps as headers if you want them, and doesn't dump everything into a single block of unreadable prose.

There's a menu-bar mode. If you click the menubar icon, a small palette appears that lets you start a recording, drop in a file, or pull up your recent transcripts without opening the main app. It's the kind of detail a tinkerer never builds and a designer always insists on.

The pricing question

This is where we have to discuss money, because it's the main thing separating Whisper Transcription from the free alternatives.

The app is a free download from the Mac App Store. The free tier includes the smaller Whisper models — typically tiny and base — which are adequate for casual notes but noticeably weaker than what you'd want for professional work. Unlocking the larger models (medium, large, and various distilled variants) requires a one-time in-app purchase. Since pricing shifts over time and varies by region, check the App Store listing rather than relying on a figure from this review.

Worth noting: the pricing model is a one-time unlock, not a subscription. Pay once and the larger models are yours. No monthly fee, no per-minute charge, no credits. That alone makes it cheaper than most cloud-based transcription services if you transcribe more than a few hours per month.

Where the polish ends

I want to be direct about the limitations here, because every "the polished one" review I've ever read tends to gloss over them.

Mac only. Obvious but worth saying. If you ever switch to Windows or Linux, your purchase doesn't follow you and your workflow doesn't follow you.

Less flexible than open-source alternatives. The app picks reasonable defaults and hides most of the tuning knobs. If you want to set custom Whisper parameters, run a fine-tuned model, or experiment with non-standard backends, you'll outgrow Whisper Transcription quickly. Buzz lets you switch backends; this doesn't.

Speed is good but not the best. On Apple Silicon, Pyrenees is faster — sometimes substantially faster — for the same model size. Whisper Transcription uses solid acceleration but isn't the speed champion of the field.

No deep subtitle editing. The interactive editor is a pleasure for prose, but it's not pretending to be Subtitle Edit. If your job involves cue-by-cue caption work, you'll still be exporting to .srt and finishing the job elsewhere.

App Store review constraints. Because it's distributed through the App Store, it lives inside Apple's sandbox rules. That has security upsides (the app can't quietly access files you didn't grant it access to) but the occasional UX papercut — for instance, you'll be re-asked for microphone permission after some macOS updates.

Pros and cons

How to actually use it

The workflow is shorter than for most tools we've reviewed. Here's the condensed version.

1. Install from the Mac App Store. Search "Whisper Transcription" and install. No external installer, no permissions juggling.
2. Open it and let it download the default model. The free models are small enough that this is fast.
3. Drop in a file or click the record button. Audio and video files work; the app strips audio automatically.
4. Pick the model and language. If you've unlocked the larger models, medium is a sweet spot for most use cases. Language can be left on auto-detect.
5. Start the transcription. Watch the progress bar — or, more usefully, switch to another app and ignore it until it's done.
6. Edit the transcript inline. Click any sentence to play it back. Fix mistakes. Tag speakers.
7. Export. File → Export, pick the format. Done.

Compared to the others

Quick reference points across the rest of the shortlist:

Versus Buzz: Buzz is free everywhere; Whisper Transcription is a paid Mac app. If you're disciplined enough to set up Buzz and don't mind its plain UI, you get the same transcription quality without spending anything. If you want it to feel like a Mac app and you transcribe regularly enough that the time savings matter, the purchase pays itself back.

Versus Pyrenees: Pyrenees is faster and free, but barer-bones. No interactive editor, no DOCX export, no system audio capture. If raw speed and zero cost are your priorities, Pyrenees. If polish is your priority, this.

Versus Subtitle Edit: Different category. Whisper Transcription is for getting transcripts; Subtitle Edit is for grooming captions. If you do both, you'll likely use both.

Versus VoiceInk: Different again. VoiceInk is for live dictation into other apps. Whisper Transcription is for files (with optional recording). They cover different problems.

FAQ

What it is, in brief

Pyrenees is a free macOS transcription app for Apple Silicon Macs. It's built around MLX, Apple's open-source machine-learning framework released in late 2023. MLX is designed specifically for the unified-memory architecture of M-series chips — it runs models on the GPU and Neural Engine without copying tensors back and forth across separate VRAM and system RAM the way frameworks designed for NVIDIA cards have to. For models like Whisper, that translates into noticeably faster inference than running the same model through plain PyTorch or even whisper.cpp's Core ML path.

The app is compact, unobtrusive, and does essentially nothing beyond transcription. Import a file, select a model, receive a transcript. What earns it a dedicated guide is how it handles that one function on Apple Silicon hardware.

So how fast is it, actually?

The usual disclaimers apply. Speed comparisons between transcription apps vary heavily by hardware, and precise figures will be stale by the time you read this. With that caveat on the table, here's what we found.

On every Apple Silicon machine tested — an M1 MacBook Air, an M2 MacBook Air, and a Mac Studio with M2 Max — Pyrenees completed the same jobs faster than any other tool in the comparison. The margin was not small.

The qualitative shift is more telling than raw numbers. Where the same hardware running Buzz felt like "kick it off and go make a drink," Pyrenees on the same machine feels like "start it and pause a second."

Pyrenees isn't faster the way a hardware upgrade feels faster. It's faster the way switching from email attachments to AirDrop feels faster — you've crossed into a different category, not just nudged the dial.

What actually sets it apart from the others

Most Mac transcription apps fall into one of two technical camps. They either ship the original PyTorch Whisper implementation with whatever GPU acceleration they can scrape together, or they bundle whisper.cpp, the C++ port that Georgi Gerganov maintains. Both are perfectly good options.

Pyrenees sits in a third camp. It uses MLX-converted Whisper weights and runs them through the MLX runtime. Because MLX is built specifically for Apple Silicon's unified memory architecture, it can keep the model and audio in the same memory pool the GPU and CPU share — which is why the speed gap is so pronounced.

The practical consequences:

• Lower memory pressure. The large model on a 16 GB Mac is genuinely usable in Pyrenees. Other apps running the same model often push the system into heavy swap and grind to a halt on longer files.
• The Neural Engine gets real use. Many "Apple Silicon–optimised" apps gesture toward the ANE without truly engaging it. MLX reaches it for the parts of the Whisper pipeline where it makes a difference.
• Quantised models are fast to load. Pyrenees includes several quantised variants — 4-bit, 8-bit — that deliver accuracy close to full-precision models while consuming a fraction of the resources.

What Pyrenees doesn't do

This is the section where the case for a different tool gets made. Pyrenees is deliberate about its scope, and the things it won't do are worth knowing before you commit to it.

It won't run on Intel Macs. Apple Silicon is a strict requirement. If you're still on a 2019 MacBook Pro, this app isn't an option — you'll need to upgrade first or use Buzz instead.

No Windows or Linux support. Follows from the platform requirement, but worth stating clearly for anyone building a cross-platform workflow.

No interactive transcript editor. What you get is a completed transcript. Minor typo fixes in the export are possible, but there's no click-to-play timeline, no inline cue editing, no speaker separation.

No system audio capture. Microphone input is available for on-the-fly recording, but unlike Whisper Transcription, Pyrenees can't pull audio from another running application.

Not built for dictation. It's file-based only. If you want to speak into other apps, VoiceInk is the tool you're after.

No broadcast-grade subtitle exports. SRT, VTT, and plain text cover the everyday cases. For TTML, EBU-STL, or other broadcast formats, you'll need to bring the SRT into Subtitle Edit.

Pros & cons

How to use it

This is the most concise how-to in any of these guides, because the app genuinely has that few steps.

1. Download Pyrenees from the developer's site (look for the official notarized DMG; avoid mirrors).
2. Drag the app to /Applications. First launch will hit Gatekeeper; right-click the icon, choose "Open", confirm. macOS will remember the choice.
3. Pick a model on first launch. The app will offer to download one. Medium 4-bit is a good first choice on most M1/M2 Macs.
4. Drop your audio or video file in. Or hit the record button to capture from the microphone.
5. Confirm the language if you don't want auto-detection.
6. Wait. Briefly. Pyrenees is faster than the alternatives; you'll often be done before you finish your coffee.
7. Export. File → Export → SRT/VTT/TXT.

How it compares to the rest of the shortlist

Versus Buzz: Pyrenees is faster and better-looking. Buzz has more versatility — Linux, Windows, multiple backends, batch queuing, OpenAI API option. Mac-only users with no need for that flexibility are better off with Pyrenees. Anyone working across platforms or needing the options should keep Buzz around.

Versus Whisper Transcription: Pyrenees is faster and costs nothing; Whisper Transcription is more refined and includes features (interactive editor, system audio capture, DOCX export) that Pyrenees lacks. A genuine tradeoff. Start with Pyrenees — it's free. If after a week you're missing the extras, Whisper Transcription becomes a reasonable buy.

Versus Subtitle Edit: Different jobs. Pyrenees produces, Subtitle Edit edits. The natural workflow is to use both.

Versus VoiceInk: Different jobs again. Pyrenees is for files, VoiceInk is for live dictation.

FAQ

What it's replacing

Apple has shipped dictation as part of macOS for well over a decade. Press a hotkey, speak into any text field, it works. It's been there long enough that most people have stopped thinking about it. VoiceInk exists because the system version has persistent limitations — it routes your voice to Apple's servers (or used to; recent releases can run on-device for English on Apple Silicon, though the implementation isn't transparent), handles technical vocabulary poorly, and offers almost no customisation.

VoiceInk is a more capable substitute. It's open-source, runs Whisper on your own hardware, and binds a hotkey to dictation. Text appears wherever the cursor sits. The model never leaves your machine. The configuration is yours to adjust. It's free, code is on GitHub, and after a week with it, falling back to system dictation feels like a pointless regression.

The interaction, described precisely

This is the one guide where the physical interaction is more central than the underlying technology — worth describing in some detail.

You assign a hotkey in VoiceInk's preferences — the fn key works well since it's already on your keyboard and almost nothing uses it by default. After that, from any application — browser, terminal, email, code editor — you can:

1. Hold the hotkey down. A small overlay appears at the bottom of the screen showing that recording has started.
2. Talk. The overlay shows a moving waveform so you know the mic is active. Talk normally; the model is forgiving of "um" and "uh" and natural speech rhythm.
3. Release the hotkey. A second or two of processing happens (faster if you have a small model loaded, slower if you have a large one), and then the transcribed text gets typed into wherever your cursor was. As if you'd written it yourself, just much faster than you can type.

That's the whole interaction. Press, speak, release. Once it's in muscle memory, it reshapes how you handle short writing tasks — Slack messages, email drafts, code comments, search queries. I've seen people use it for the first time and start bypassing their keyboard for short messages before the afternoon is out.

How the model works in context

Like every other tool covered here, VoiceInk runs Whisper locally. Several model sizes are available, and the speed-versus-accuracy tradeoff matters more here than for file transcription. Dictation won't tolerate a fifteen-second wait — you need results quickly. Most users settle on the base or small model, which is fast enough to feel immediate.

There's a real cost to that choice. Smaller Whisper models are measurably less accurate, particularly for proper nouns, specialised vocabulary, or non-standard accents. VoiceInk includes a vocabulary feature that lets you register specific words — colleagues' names, project identifiers, domain-specific terms — which closes the gap considerably. Still, light corrections after dictating something important are a reasonable expectation.

What VoiceInk is genuinely good at

I want to be specific about this rather than general, because vague reviews don't help when you're deciding whether to install something.

Quick replies. Slack messages, email responses, "yeah looks good", "let me get back to you tomorrow on that." Things that take three seconds to say and ten seconds to type. The hotkey workflow shaves real time off a real day.

First drafts. Talking out a paragraph and then editing it on the keyboard is genuinely faster than writing the paragraph from scratch for many people. VoiceInk fits this workflow especially well because the text lands directly in your editor of choice — no copy-paste step.

Note-taking. Quick thought, capture it before it goes away. The hotkey-anywhere model means the friction of "where is my notes app, where is the cursor, what was I about to say" disappears.

Code comments and commit messages. Anywhere a thought is more important than its phrasing. The fact that you can be in your terminal or your editor makes this work without breaking flow.

Accessibility. For people with RSI, hand injuries, or other reasons keyboard input is painful, a fast on-device dictation tool is genuinely valuable. VoiceInk's open-source nature also means you can audit it for any concerns about where your voice goes.

What it isn't built for

Long-form writing. An hour of dictation is exhausting in a way an hour of typing isn't. People who try to dictate entire essays usually go back to keyboards within a week.

Anything you don't want misheard. If accuracy is critical — a legal document, an academic citation, a medical reference — dictation will let you down at small but inconvenient frequency. Always read it back.

File transcription. Said it once, saying it again. VoiceInk doesn't accept input audio files. It records from your microphone, processes it, and types the result. If you have a file, use Buzz or Pyrenees.

Multi-speaker situations. The mic captures whoever is loudest. A meeting recording is the wrong input for VoiceInk.

Pros & cons

Setting it up

1. Install VoiceInk from its GitHub releases page or the developer's site.
2. On first launch, grant permissions. macOS will ask for microphone access and accessibility access (the latter is what lets the app type into other apps). Both are required.
3. Pick a model. Small is a good starting point; bump up to medium if you have an M-series Mac and want better accuracy.
4. Set a hotkey you'll remember. The function key (fn) works well because it's not used for much. Some people prefer right-Option, which is also unused on most layouts.
5. Add custom vocabulary if you have specialized words. Names of coworkers, project codenames, technical terms. The model uses these as hints during transcription.
6. Try it in a low-stakes app first. Open a TextEdit window, hold the hotkey, dictate a paragraph, see how it goes. Adjust your speaking pace based on what happens.

How VoiceInk fits alongside the others

VoiceInk sits entirely apart from the other four tools here. The rest answer the question "I have an audio file, give me text." VoiceInk answers "I want to speak, put the text wherever I'm typing." They don't really overlap.

If you're running VoiceInk and want to transcribe a meeting recording, reach for Buzz or Pyrenees instead. And if you're using Buzz and wish you could talk into Slack the same way, add VoiceInk. Having both is the most sensible setup.

FAQ