How to Dictate in VS Code: Voice Coding & Copilot (2026)

TL;DR: To dictate in VS Code, you have two good options. Microsoft's free VS Code Speech extension adds on-device dictation to the editor and GitHub Copilot Chat (including "Hey Code" activation). Or run a system-wide Mac dictation tool like Voibe, which types into every VS Code surface and every other app, and resolves your workspace's file and folder names as you speak. Pick the extension if you live entirely in VS Code; pick a system-wide tool if you want one hotkey everywhere plus workspace-aware accuracy.

If you also use Cursor, the same system-wide setup carries over — see our companion guide on how to dictate in Cursor. This guide covers the VS Code Speech extension honestly, then the system-wide setup, Developer Mode file resolution, and real voice-prompt examples for Copilot.

VS Code has several inputs, and which ones accept voice depends on your tool. A system-wide dictation tool works in all of them because it inserts text wherever the cursor is; the VS Code Speech extension covers the editor and Copilot Chat:

VS Code's AI lives in GitHub Copilot — Copilot Chat, inline chat (Cmd+I), and Copilot's Edits and Agent modes for multi-file work. All of them are driven by prose, which is what dictation speeds up. The VS Code Speech extension hooks voice into Copilot Chat and editor dictation; a system-wide tool extends it to the terminal, the commit box, and every app outside VS Code.

Unlike Cursor's native voice mode, VS Code's official voice option is genuinely strong, so this is a fair comparison rather than a one-sided one. Microsoft's VS Code Speech extension processes audio locally (no internet required), dictates into the editor (Voice: Start Dictation in Editor, Ctrl+Alt+V), powers Copilot Chat voice, and supports "Hey Code" keyword activation. If you spend your whole day inside VS Code, it is a legitimate, private, free choice.

The case for a system-wide on-device tool is not about privacy here — both run locally — it is about scope and accuracy:

The honest verdict: if VS Code is the only place you dictate, the extension is hard to beat for free. The moment you want to dictate in your browser, your chat apps, your terminal, or a second editor — and to have spoken file names land as real identifiers — a single system-wide tool replaces a per-app patchwork. The two even coexist: some developers keep VS Code Speech for "Hey Code" and use a system-wide tool everywhere else.

The setup mirrors any Mac dictation tool; this guide uses Voibe for its on-device processing and the Developer Mode workspace resolution that plain dictation lacks.

1. Download Voibe from getvoibe.com (or the direct .dmg) and drag it to Applications.
2. Launch it. On Apple Silicon (M1–M4, macOS 13+) it downloads a local Whisper model (~2 GB) on first run.
3. No account, and no internet needed after the model downloads.

For the full install walkthrough, see our Voibe setup guide.

A system-wide tool needs two macOS permissions to type into VS Code:

1. Accessibility — to insert text (System Settings > Privacy & Security > Accessibility, then enable the app).
2. Microphone — to capture speech (granted on first use, or under System Settings > Privacy & Security > Microphone).

Pick a hotkey you can hold while your hands rest on the keyboard. Voibe defaults to holding Fn: press and hold, speak, release, and the text appears at the cursor. Reassign it in settings if Fn clashes with your layout — see our Mac dictation keyboard shortcuts guide for options and conflicts. Hold-to-talk suits coding because your hands return to the keys the instant you release.

This is the capability the VS Code Speech extension does not have, and the reason a system-wide tool can be more accurate inside VS Code, not just broader. Open Voibe's settings and toggle Developer Mode on. It detects your open VS Code (or Cursor) window and resolves file names, folder names, and project-specific terms from your workspace as you dictate.

Plain dictation transcribes identifiers literally: say "auth middleware dot t s" and you get those words. Developer Mode matches them against your open workspace and inserts authMiddleware.ts. The same applies to folders, components, and any term in your project tree — so a dictated comment, commit message, or Copilot prompt references the real file without manual fixing.

Here is what dictating into each VS Code surface looks like with a system-wide tool. Hold your hotkey, speak, release.

Copilot Chat — Codebase Questions and Changes

Click into the Copilot Chat box and dictate:

• "Why does the checkout request fail when the cart is empty? Look at the cart store and the checkout page."
• "Add a loading state to the Pay button and disable it while the request is in flight."

Copilot Inline (Cmd+I) — Targeted Edits

Select a block, press Cmd+I, and dictate the change:

• "Convert this to use async/await and add a try-catch around the fetch."

The Editor — Comments, Docstrings, Markdown

Place your cursor in the file and dictate prose directly: a docstring above a function, a section in your README, or a TODO note. With Developer Mode on, referencing other files by name stays accurate.

The Terminal — Commit Messages

In the integrated terminal or the Source Control box, dictate a commit message: "fix: prevent duplicate submissions on the checkout button."

Keep prompts short and structured — voice handles a focused two-sentence instruction far better than a long run-on. For a repeatable structure, use the Five-Part Voice Prompt framework (Goal, Inputs, Constraints, Example, Output) in our voice-prompt AI guide, and the Talk-Draft-Polish loop in our voice input workflow guide.

• Add a custom vocabulary for your stack. Library, framework, and API names (e.g. "Vitest", "Prisma", "useQuery") are what dictation gets wrong. Add them once.
• Let Developer Mode handle file names. Say the file name naturally rather than spelling the path; workspace resolution maps it to the real identifier.
• Decide your division of labor. If you like "Hey Code," keep the VS Code Speech extension for chat activation and use a system-wide tool for the editor, terminal, and other apps.
• Dictate in short bursts. Ten-to-thirty-word phrases are most accurate; pause between thoughts.
• Speak the goal, then constraints. "Paginate the users table, twenty per page, server-side" beats narrating implementation steps.
• Use a decent microphone. A basic USB mic noticeably reduces errors on technical terms.
• Edit with the keyboard. Voice is fastest for the first draft of a prompt or comment; fix the last few words by hand.

A system-wide tool isn't typing into VS Code

Check Accessibility permission first: System Settings > Privacy & Security > Accessibility, and confirm the app is enabled. If it is on but still not typing, remove and re-add it to reset the permission — this resolves most cases after an update.

The VS Code Speech extension isn't transcribing

Confirm the extension is installed and that you have downloaded a speech model when prompted. "Hey Code" requires the keyword-activation setting (accessibility.voice.keywordActivation) to be enabled. Editor dictation is triggered with Voice: Start Dictation in Editor (Ctrl+Alt+V).

File names aren't resolving

Confirm Developer Mode is on and VS Code is the frontmost window with the workspace open. Resolution matches files in the open project; add the term to your custom vocabulary as a fallback.

Technical terms are mis-transcribed

Add the library, framework, or API names to your custom vocabulary. General speech models don't know "Zod" or "Drizzle" until told.

Dictation feels slow

On-device transcription shares the Neural Engine with other apps. Close memory-heavy apps or pick a smaller local model on an 8 GB Mac.

• VS Code Speech (Microsoft) — free, on-device, covers the editor and Copilot Chat with "Hey Code." The best free option if you work only in VS Code; no workspace file resolution or custom vocabulary, and VS Code-only.
• Voibe — system-wide and on-device, with Developer Mode workspace resolution and custom vocabulary. Works in VS Code and every other app. $149 lifetime or $7.50/month, 7-day trial, no account. See our best dictation software for developers guide.
• Apple Dictation — free, system-wide baseline, but with a session timeout and no custom vocabulary or workspace awareness.
• Wispr Flow — polished cloud dictation with AI formatting; cross-platform but cloud-based, so weigh that for proprietary code. $144/year.
• Superwhisper — on-device Whisper modes plus optional cloud LLM cleanup; $249.99 lifetime, no dedicated IDE file resolution.

Using the AI editor Cursor instead of VS Code? See our companion how to dictate in Cursor guide. For the architecture comparison, see cloud vs local dictation and offline dictation privacy on Mac.

Basics

Can you dictate in VS Code?
Yes — with Microsoft's on-device VS Code Speech extension (editor + Copilot Chat + "Hey Code"), or with any system-wide Mac dictation tool that types into every VS Code surface and every other app.

Does VS Code have built-in voice dictation?
Not in core, but the official VS Code Speech extension adds it: on-device speech-to-text for the editor and Copilot Chat, with keyword activation. It works only inside VS Code.

Setup

Is the VS Code Speech extension private?
Yes. It processes audio locally and never sends recordings to an online service, so it works offline — a safe choice for proprietary code. A system-wide on-device tool offers the same privacy plus broader coverage.

What is Developer Mode?
A Voibe setting that resolves spoken file names, folder names, and project terms from your open VS Code workspace to their exact spelling — turning "auth middleware" into authMiddleware.ts automatically.

Workflow

How do I dictate into Copilot Chat?
With VS Code Speech, use the mic button or "Hey Code." With a system-wide tool, click the chat box, hold your hotkey, and speak — the same gesture works in inline chat, the editor, and the terminal.

Should I use the extension or a system-wide tool?
Use the extension if VS Code is the only place you dictate. Use a system-wide tool if you also dictate in the browser, Slack, email, the terminal, or Cursor, and want workspace file-name resolution.

VS Code dictation comes down to scope. Microsoft's VS Code Speech extension is a genuinely good, on-device, free option — if VS Code is the only place you talk to your computer. A system-wide on-device tool wins the moment you want one hotkey across every app and spoken file names that resolve to real identifiers in your workspace.

Voibe is the Mac-native, on-device option built for that: download it free (7-day trial, no account), enable Developer Mode, and dictate your next Copilot prompt — and your next Slack message and commit — with the same hotkey.

Keep going:

• How to dictate in Cursor — the AI-editor companion to this guide
• How to voice-prompt ChatGPT, Claude, and Cursor — the Five-Part Voice Prompt framework
• The voice input workflow — the Talk-Draft-Polish loop
• Best dictation software for developers — the full buyer's view
• Getting started with Voibe — complete setup guide