Short answer: Zed has no built-in dictation, but a system-wide voice-to-text tool like Voice Keyboard Pro types wherever your cursor sits, so you can dictate comments, docstrings, commit messages, and AI-panel prompts directly in Zed on Mac. Dictate the prose, keep typing the syntax, and use Smart Vocabulary to keep identifier names correct.
Zed has built a devoted following by being fast. It is a native, GPU-accelerated code editor written for macOS, and developers who switch to it usually mention the same thing first: it feels instant in a way that Electron-based editors never quite do. What Zed does not have, and by design likely never will, is a dictation feature. It is a code editor, not a writing suite, and voice input is not part of its job.
But a surprising amount of what you do in a code editor is not code. It is the prose that lives alongside the code: the comment explaining why a function exists, the docstring at the top of a module, the commit message, the pull request description, and increasingly the natural-language prompt you type into an AI assistant panel. All of that is writing, and writing is exactly where dictation beats typing. This guide covers how to dictate in Zed on a Mac, where voice helps and where it gets in the way, and how to keep your identifier names from turning into gibberish.
Why there is no dictation button in Zed
Zed focuses hard on the editing experience and deliberately keeps its surface area small. It is not going to grow a microphone button, because that is not the problem it exists to solve. The good news is that it does not need to. On macOS, the clean way to add voice input to any app is not to modify the app but to run a system-wide dictation tool that types wherever your cursor already is.
That is the model Voice Keyboard Pro uses. It lives in your menu bar, and it inserts text at the current cursor position in whatever app has focus. When your cursor is blinking inside a Zed buffer, that is where the text goes. Zed does not have to know anything about it, which is exactly why it works. The same approach we describe in how to dictate in any Mac app applies to Zed unchanged.
The basic workflow
The mechanics are the same everywhere on the Mac:
- Place your cursor in the Zed buffer where you want text, for example on a comment line or inside a string.
- Hold your Voice Keyboard Pro hotkey.
- Speak your sentence, saying punctuation where you need it.
- Release. The text appears at the cursor.
That is the whole loop. The interesting part is not the mechanics but knowing which parts of your work in Zed are worth dictating, because trying to dictate raw code is a losing game and trying to type long prose is slow. The rest of this guide is about drawing that line well.
Where dictation wins in Zed
Comments and docstrings
Comments are the clearest case. A good comment explains intent in plain English: why this code exists, what edge case it guards against, what the reader should watch out for. That is prose, and prose is faster spoken than typed. Put your cursor after the comment marker for your language, hold the hotkey, and explain the thing the way you would explain it to a teammate looking over your shoulder.
Docstrings benefit even more, because they are longer and more structured. A module or function docstring that would take a couple of minutes to type is a fifteen-second job by voice. The natural rhythm of speech also tends to produce clearer explanations than typing does, because you are describing the behavior out loud rather than assembling it word by word. Our guide to dictating code comments goes deeper on writing comments that read well when spoken.
Commit messages and PR descriptions
Commit messages are prose too, and most developers write them too tersely because typing a proper explanation feels like a chore. Dictation removes the friction. Zed has a built-in Git panel where you write your commit message, so put your cursor in the message field and talk through what changed and why. A commit body that actually explains the change is far more useful to whoever reads the history later, and voice makes writing that body cheap enough that you will actually do it.
Pull request descriptions follow the same logic, though those usually live in a browser tab on GitHub or GitLab rather than in Zed itself. Wherever the text field is, the workflow is identical, and we cover the platform specifics in our guides to dictating in GitHub and GitLab.
AI assistant prompts
This is the fastest-growing reason to dictate in a code editor. Zed's AI panel lets you talk to an assistant in natural language, and prompts to a coding assistant are prose, often long, rambling prose where you describe what you want, paste in constraints, and explain the context. Typing a paragraph-long prompt is slow. Speaking it is fast, and speaking tends to produce more complete prompts because you naturally include the context you would have skipped while typing.
Put your cursor in the AI panel's input, hold your hotkey, and describe the change you want in full sentences. "Refactor this function to take an options object instead of five positional arguments, and keep the existing behavior for the timeout parameter" is a much better prompt spoken in one breath than typed in fragments. Developers who lean on AI assistants find this the single biggest reason to add voice, which is the same thread that runs through our pieces on voice typing in the Cursor AI editor and voice dictation in Windsurf.
Where dictation does not belong
Being honest about the limits is what keeps this credible. Dictation is a prose tool, and code is not prose. A few things you should keep typing in Zed:
- Actual code. Symbols, brackets, operators, and precise indentation are miserable to dictate and instant to type. Do not try to speak a for-loop.
- Identifiers mid-code. Variable and function names in
camelCaseorsnake_casedo not come out of a general transcription engine cleanly. Type them. - Anything that depends on exact characters. Regexes, format strings, config keys. Precision beats speed here, and your fingers are more precise than your voice for symbols.
The rule that keeps you sane: dictate the sentences, type the syntax. Comments, docstrings, commit bodies, and prompts are sentences. Everything between the braces is syntax. Once you internalize that split, voice becomes a genuine speed-up rather than a novelty you fight with.
Keeping identifier names correct with Smart Vocabulary
Even in prose, a developer's writing is full of terms a general transcription engine will not know: your project's name, a service called authproxy, a library, a domain acronym. When you mention these in comments and commit messages, you do not want to correct them by hand every time.
Voice Keyboard Pro's Smart Vocabulary is a personal dictionary with replacement rules. Add the product names, service names, and technical terms you use constantly, and the app produces them correctly. You can even set up rules so a spoken phrase maps to an exact written form. This is the difference between dictation being a fun demo and dictation being something you actually keep on all day, and it is the same capability we cover in custom vocabulary that learns your words. For the special problem of case conventions, our guide to voice coding with camelCase and snake_case is worth a read.
Speed, for the developers who care about numbers
Zed users care about performance, so here is the performance argument for voice. Adults type at around 40 words per minute on average, and even fast professional typists top out near 80 to 100. Everyone speaks at 130 to 150 words per minute without any practice at all. For the prose parts of your work, that is a two-to-three-times speed-up, before you count the fact that you are not context-switching your hands off the home row to reach for punctuation.
It also changes the economics of good documentation. The reason comments are thin and commit messages are terse is that typing them feels expensive. Make the writing cheap and you write more of it, which is exactly the kind of documentation debt most codebases are drowning in. Our broader case for dictation while coding covers this in more depth.
Setting it up takes about a minute
There is no Zed-specific configuration to do, which is the whole point of a system-wide tool. Install Voice Keyboard Pro from the menu bar app, grant it the accessibility and microphone permissions macOS asks for the first time, and pick a hotkey you can hold comfortably while your other hand rests on the keyboard. Many developers set the hotkey to a modifier they do not otherwise use much, so it never collides with Zed's own shortcuts.
That last point is worth a beat. Zed is heavily keyboard-driven, with its own dense set of bindings for navigation, multi-cursor editing, and the command palette. Your dictation hotkey should be something Zed does not already claim, so that holding it never accidentally triggers an editor action. A dedicated modifier key or a function key works well. Once that is set, the tool stays out of your way until you hold the key, and then it just types.
When you are away from the desk
Most of your Zed work happens at a keyboard, but the writing that surrounds a project does not stay put. You draft an issue reply from your phone, jot a note about a bug on the train, or answer a code review comment while away from your desk. The Voice Keyboard Pro iPhone keyboard adds a mic button to your keyboard in every iOS app, so the same voice workflow follows you into GitHub, a notes app, or your team chat on mobile. The prose is still prose whether you are at your Mac or not, and Voice Edit on the phone lets you fix a sentence by speaking the change rather than wrestling the cursor on a small screen.
A note on privacy
Developers are rightly cautious about what leaves their machine. Voice Keyboard Pro's transcription engine converts your speech to text and delivers that text to your cursor. The team does not store your transcripts or your audio; only operational pings are kept to run the service. Your comments, commit messages, and prompts are yours. As always, follow your employer's policy on what may be transmitted off-device, especially when dictating anything tied to proprietary code.
The bottom line
Zed is a fast editor that will never grow a microphone, and it does not need to. Add a system-wide dictation tool and the prose half of your coding day, the comments, docstrings, commit messages, and AI prompts, moves to your voice while the code half stays on the keyboard where it belongs. Dictate the sentences, type the syntax, and let Smart Vocabulary keep your names straight. You already think faster than you type; this just lets the explaining part of programming keep up.
Voice Keyboard Pro has a free tier. Install it, open Zed, and dictate the docstring you have been putting off. It is the fastest way to see whether voice belongs in your workflow.