Short answer: To dictate in IntelliJ IDEA, place your cursor in any editor or comment field and use Voice Keyboard Pro. On Mac, hold your hotkey and speak your commit message, code comment, or docstring; the text appears at the cursor. It works the same in every JetBrains IDE.
A lot of what you write inside IntelliJ IDEA is not code. It is the prose that lives around the code: commit messages, code comments, docstrings, pull request descriptions, ticket updates, design notes, and questions for the AI assistant. That writing is where dictation belongs. You keep your hands on the keyboard for the syntax, where precision matters, and you speak the English, where speed matters.
This guide shows how to dictate in IntelliJ IDEA on Mac using Voice Keyboard Pro, how the same setup works across the whole JetBrains family, and, just as importantly, where dictation helps and where it does not. If you write code in a JetBrains IDE all day, adding voice to the prose parts of that work is one of the easiest speed wins available.
Why voice belongs in your IDE (for prose, not syntax)
Dictating raw source code is a bad idea, and anyone who has tried to speak a line of nested brackets and camelCase identifiers already knows why. Punctuation-dense syntax is exactly the thing keyboards are good at and speech is bad at. So this is not a pitch to replace your keyboard.
The pitch is narrower and more useful: a surprising share of a developer's day is spent typing ordinary sentences, and those sentences are slow to type and fast to speak. Typing runs around 40 words per minute for the average person, and even strong touch typists top out near 80 to 100 WPM. Ordinary speech runs 130 to 150 WPM. When you are writing a paragraph explaining why a change was made, that gap is real time. Speaking the explanation and typing the code is the natural division of labor.
Type the syntax, speak the sentences. Your keyboard is great at brackets and identifiers; your voice is great at the paragraphs that explain them.
There is a second, quieter benefit. Prose you speak tends to be more complete. When developers type comments and commit messages, they cut corners because typing is effort, and you end up with a terse "fix bug" that helps no one in six months. When you speak, the full sentence comes out because talking is cheap. Dictation nudges you toward the documentation you know you should be writing. Our piece on how to dictate code comments goes deeper on that habit.
What to dictate in IntelliJ (and what to leave to the keyboard)
Before the setup, here is the honest map of where voice pays off inside a JetBrains IDE:
Great for dictation:
- Commit messages in the Commit tool window, especially the body paragraph explaining the why.
- Code comments and TODOs that describe intent, edge cases, or gotchas.
- Docstrings, Javadoc, and KDoc summaries, where the text is real English wrapped in a comment block.
- Pull request and merge request descriptions written in the IDE or the browser.
- Issue and ticket updates in tools like Jira or YouTrack, whether in a plugin panel or a browser tab.
- AI assistant prompts, where you are describing what you want in plain language anyway.
- Design docs, README files, and Markdown you edit inside the IDE.
Leave to the keyboard:
- Actual source lines with operators, brackets, and precise identifiers.
- Refactoring gestures, navigation, and multi-caret editing, which JetBrains shortcuts already make fast.
- Regexes, config syntax, and anything where one wrong character breaks the build.
Keep that split in mind and voice becomes an addition to your workflow rather than a fight with it.
How to dictate in IntelliJ IDEA on Mac
IntelliJ IDEA runs on the desktop, so the Mac is where this lives. Voice Keyboard Pro is a menu bar app that types into whatever field holds your cursor, which means it works inside the IDE's editor, its tool windows, and any dialog with a text box. Setup takes a minute.
Step 1: Install Voice Keyboard Pro
Download Voice Keyboard Pro for Mac and grant the microphone and accessibility permissions it requests during setup. The accessibility permission is what lets it place text at your cursor in another app, and IntelliJ is just another app as far as it is concerned. It sits in the menu bar and stays out of the way. The free tier is plenty to test it against a real day of committing and commenting.
Step 2: Put your cursor where the prose goes
Click into the field you want to fill. That might be the message box in the Commit tool window, a line inside a comment block in the editor, the description field of a ticket panel, or the input box of the AI assistant. The key is that the cursor is blinking in a text field, exactly as it would be if you were about to type.
Step 3: Hold your hotkey and speak
Press and hold your Voice Keyboard Pro hotkey and talk. Say the whole thought as a natural sentence: "This change moves the retry logic out of the request handler so the timeout is configurable per environment." Release the key, and the text lands at your cursor. Then you switch back to the keyboard for the code. Because Voice Keyboard Pro works system-wide, the same gesture works in every field in the IDE without any per-app configuration. For the wider picture, see our guide on how to dictate in any Mac app.
Step 4: Say your punctuation and structure
For longer prose, speak the structure out loud. Say "comma" and "period" for punctuation, and "new line" or "new paragraph" to break up a commit body or a docstring. A three-sentence explanation that would take you a minute to type takes about fifteen seconds to speak, and it tends to come out more thorough because talking is easy.
The same setup works across the whole JetBrains suite
Because Voice Keyboard Pro operates at the system level rather than as an IDE plugin, there is nothing IntelliJ-specific about it. The identical hotkey-and-speak workflow drops into every JetBrains product:
- PyCharm for Python, where docstrings and long comments are common.
- WebStorm for JavaScript and TypeScript.
- GoLand for Go, where doc comments are idiomatic and expected.
- PhpStorm, RubyMine, CLion, and Rider for their respective languages.
- DataGrip, where you might dictate a description of what a query does.
- Android Studio, which is built on the IntelliJ platform and behaves the same way.
Set it up once and you have voice in every editor you open. If you also work in other editors, the same idea carries over; we have companion guides for voice to text in VS Code and for dictating in Xcode.
Smart Vocabulary for identifiers, APIs, and product names
Developer prose is full of words that ordinary transcription mishears: library names, framework names, internal service names, API terms, and the CamelCase or snake_case identifiers you reference in a comment. Voice Keyboard Pro includes Smart Vocabulary, a personal dictionary with replacement rules, so you teach it your stack once and it stops guessing.
Entries worth adding early:
- Framework and library names you mention constantly, so "Kubernetes," "PostgreSQL," or "Kotlin coroutines" come out spelled right.
- Internal service and repo names that are not real English words.
- Product and feature names your team uses in tickets and commit messages.
- Common acronyms in your domain that you want capitalized correctly.
- A spoken shortcut that expands into a boilerplate comment header or a commit trailer you always append.
When you are dictating a comment that references an identifier, a good pattern is to speak the surrounding sentence and type the exact symbol. If you dictate identifiers often, our notes on voice coding with camelCase and snake_case cover how to make casing behave.
Commit messages, code review, and tickets
The single highest-value place to dictate in a JetBrains IDE is the commit message body. A good commit explains why, not just what, and the why is a paragraph of English that most developers skip because typing it feels like overhead. Speak it instead. Put your cursor in the Commit tool window's message box, hold the hotkey, and describe the change the way you would explain it to a teammate at your desk. The subject line you can still type short and sharp; it is the body that benefits from voice.
Code review is the same story. Whether you review inside a JetBrains plugin or in a browser tab, review comments are conversational English. Dictating them makes you more likely to leave the helpful, complete comment instead of a curt "why?" that the author has to decode. And ticket updates in Jira or YouTrack, whether you write them in an IDE panel or the web app, are pure prose that voice handles beautifully. Our developer overview, dictation for coding, ties these habits together.
Docstrings, Javadoc, and documentation
Documentation is the work everyone agrees is important and nobody wants to type. Docstrings, Javadoc, KDoc, and README files are English wrapped in a little syntax, and the English is the slow part. Type the /** and the tags, then dictate the sentences between them. A function summary, a parameter description, a note about thread safety: all of it comes faster by voice, and because speaking is low-effort, the documentation you produce tends to be fuller than the one-line stub you would have typed.
Markdown files get the same treatment. When you are editing a README or an architecture doc inside the IDE, dictate the paragraphs and type the code fences and headings. The prose-heavy parts move at conversation speed.
Dictating prompts for your AI assistant
Modern JetBrains IDEs put an AI chat panel right next to your code, and the thing you type into it is a plain-language description of what you want. That is dictation's home turf. Instead of thumb-typing a careful prompt, put your cursor in the assistant's input box, hold the hotkey, and describe the change or question in full sentences. Spoken prompts tend to be richer and more specific than typed ones, because you are not rationing keystrokes, and a richer prompt usually gets a better answer.
On iPhone: tickets, reviews, and notes on the go
IntelliJ itself does not run on a phone, but a lot of the writing around your code does happen there. When you are away from your desk and need to update a ticket, reply to a review thread, or capture an idea before it evaporates, Voice Keyboard Pro installs as a custom iPhone keyboard with a mic button, so you can dictate into any app.
Step 1: Add and enable the keyboard
Install Voice Keyboard Pro from the App Store, then open Settings → General → Keyboard → Keyboards → Add New Keyboard and add it. Tap it once more and turn on Allow Full Access, which lets the keyboard handle transcription.
Step 2: Switch to it and speak
In your ticket app, review tool, or notes app, tap into the text field, press the globe icon until you reach Voice Keyboard Pro, then tap the microphone and talk. A ticket comment or a "don't forget to check the null case" note takes seconds instead of a minute of thumb-typing on a phone.
Tips for dictating in a JetBrains IDE
- Draft in prose, then format with the keyboard. Speak the paragraph, then use IntelliJ's shortcuts to wrap comments, reflow, or add tags.
- Keep the subject line typed and the body spoken. Short titles are faster to type; explanatory bodies are faster to speak.
- Build Smart Vocabulary for your stack in week one. Add your framework, service, and product names and the accuracy jump is immediate.
- Speak identifiers in the surrounding sentence, type the exact symbol. Do not fight the tool over CamelCase; let it handle the words and you handle the token.
- Use "new paragraph" to structure longer docs. Dictated documentation reads better when you speak the breaks.
Troubleshooting IntelliJ dictation
Nothing appears when I speak on Mac
Confirm your cursor is clicked into a text field inside the IDE, then check that Voice Keyboard Pro has microphone and accessibility permissions in System Settings → Privacy & Security. Accessibility is the permission that lets it type into another app, and without it the IDE receives nothing.
Text goes into the wrong panel
JetBrains IDEs have many focusable panels. Click directly into the field you want, watch for the blinking cursor, and then start speaking. If focus is on a tree or a toolbar instead of a text box, the text has nowhere to land.
Library and identifier names come out wrong
Add them to Smart Vocabulary. Once "Kotlin," "gRPC," or your internal service name is in your personal dictionary, it is spelled your way from then on, in the IDE and everywhere else you dictate.
The mic button is missing on iPhone
This is nearly always the Full Access setting. Go to Settings → General → Keyboard → Keyboards, tap Voice Keyboard Pro, and turn on Allow Full Access.
A note on privacy
Developers care about where their words go, and rightly so, since commit messages and comments can describe internal systems. Voice Keyboard Pro's servers store only operational pings, not your audio and not the text of what you dictate. The prose you speak into your IDE stays yours.
Free tier and Pro
Voice Keyboard Pro has a free tier with a daily limit, which is more than enough to try dictating your commit messages and comments for a few days and see whether it fits your flow. Pro removes the limits and unlocks the full feature set for $4.99 per month or $34.99 per year. For a developer who writes prose around code all day, the time saved on commits, reviews, and docs adds up fast.
The bottom line
You do not dictate code in IntelliJ IDEA. You dictate everything around it: the commit message that explains the change, the comment that warns the next reader, the docstring that documents the function, the ticket update, the review note, the AI prompt. Those are English sentences, and English is faster spoken than typed. Type the syntax, speak the prose, and let Smart Vocabulary keep your stack's names accurate. The same setup works in PyCharm, WebStorm, GoLand, Android Studio, and every other JetBrains IDE, because it lives at the system level, not in a plugin.
Try Voice Keyboard Pro free and dictate your next commit message. Once the paragraph that explains your work is as cheap to write as it is to think, you will start writing the documentation you always meant to.