Mac Dictation Not Working in Claude? 9 Fixes That Actually Work (2026)

Short answer: Claude on a Mac has no dictation of its own in most versions, so the fix is almost always macOS or cursor focus. Click into the prompt box, check Enable Dictation under Keyboard settings, confirm the Fn shortcut, and close the Quick Entry bar before you speak.

You open Claude on your Mac, click into the prompt box, press the dictation key, and nothing happens. Or the indicator appears, you speak a whole paragraph, and the box stays empty. Or the words land, but in the wrong place: the sidebar search, a project description, a floating bar that closes when you look away. All of those get reported as "dictation is broken in Claude", and they have different causes. This guide walks through them in the order that finds your problem fastest.

The key thing to understand is that Claude, unlike some other assistant apps, mostly stays out of the way of dictation. It gives you a text field and leaves voice-to-text to macOS or to whichever dictation app you have installed. That is good news, because it means there is one less layer to debug. It also means that when dictation fails in Claude, the cause is usually one of three things: macOS dictation itself is off or broken, the cursor is not where you think it is, or a Claude window you did not notice is stealing focus. If dictation is failing in every app and not just Claude, start with our general guide to Mac dictation not working and come back here for the Claude-specific parts.

First, which microphone did you press?

There are up to three ways to get spoken words into Claude's prompt box on a Mac, and they fail for different reasons. Before you touch a setting, know which one you were using.

• macOS dictation. Triggered by the Fn or Globe key, pressed twice by default, or from the menu bar under Edit, then Start Dictation. A small microphone indicator appears near the cursor. This works in any text field on the Mac, including Claude's prompt box, and Claude has nothing to do with it beyond being the field that has focus.
• A third-party dictation app. Voice Keyboard Pro and tools like it use their own hotkey and insert text at your cursor. For the purposes of this guide they behave like macOS dictation: they type into whichever field has focus and do not care that the field belongs to Claude. They do use their own microphone permission, which matters in fix 5.
• A microphone button inside Claude. Some versions of the Claude desktop app and the claude.ai website show a microphone icon in or near the prompt box. If yours does, that is Claude's own dictation, and it depends on Claude having microphone permission and on your internet connection. If yours does not, nothing is missing. Voice conversation is a feature of the iPhone app, not something the Mac version is expected to offer.

Everything below assumes you know which of these you were using. If you were hunting for a button in Claude that does not exist in your version, the answer is to use the Fn key or a hotkey app instead, and you can skip straight to fix 2.

The 30-second split test

Before changing any settings, find out which layer is failing. Open Apple Notes, start a new note, click inside it, and press the Fn or Globe key twice, or your third-party hotkey. Say one full sentence.

• Dictation fails in Notes too. The problem is macOS, not Claude. Go straight to fixes 3, 4 and 5 below.
• Dictation works in Notes but the Fn key does nothing in Claude. The problem is focus or the window you are in. Fixes 2 and 6 are where to look.
• The Fn key works in Claude but Claude's own microphone button does not. The problem is Claude's microphone permission or your connection. Fixes 5 and 9 cover it.
• It works in the desktop app but not in the browser, or the other way around. The difference between the two is the problem. Fix 7 covers it.

This test takes less time than reading the rest of the article, and it stops you from resetting settings that were never broken.

The 9 fixes, in order

1. Put the cursor in the prompt box

Dictation types wherever the text cursor is. Claude has more places that accept text than it looks like, and only one of them is the prompt you want to send.

• The sidebar search. Searching your chat history takes focus into a search field. Dictating there filters your conversation list instead of writing a prompt. If your words appear and then your chat list shrinks, this is what happened.
• Project fields. Inside a Project, the name, the description and the custom instructions are all editable. If you clicked one of them to read it, it now has focus, and your dictation goes into it. Dictating a prompt into a project's instructions is easy to do and easy to miss, because the text is saved and looks perfectly normal until the next conversation behaves oddly.
• An edited message. Clicking edit on a message you already sent opens an inline editor. Dictation into that editor works, but the text changes the old message and reruns the conversation from that point rather than starting a new turn.
• The artifact panel. When Claude produces a document or code in the side panel, clicking into it to read or copy moves focus there. Nothing accepts text until you click back into the prompt.
• The reply to a previous answer. After Claude responds, focus sometimes stays on the response, especially if you scrolled, clicked a copy button, or used the thumbs-up control. Click into the prompt box again before you speak.

The fix is boring: click once inside the prompt box, confirm you see the blinking cursor there, and then start dictation. If you opened a new chat with a keyboard shortcut, click into the field anyway. Focus does not always follow.

2. Close the Quick Entry bar before you dictate in the main window

The Claude desktop app has a global shortcut, Option-Space by default, that opens a small floating bar over whatever you are doing. It is convenient, and it is the source of a specific set of dictation complaints. It has its own text field. It sits above other windows. And it closes itself when it loses focus.

The usual failure looks like this: you press Fn twice, macOS shows the dictation indicator, the bar treats the indicator as a focus change and closes, and your sentence has nowhere to land. Or the bar is open behind another window, still holding focus, and the words go into it while you stare at the main Claude window wondering where they went. Look for the bar, close it, and dictate in the main window. If you want to dictate into the bar itself, click into it deliberately and use a hold-to-talk tool, which does not flash a separate indicator that can steal focus.

3. Turn on Enable Dictation and match the language

If the split test failed in Notes as well, start here. Open System Settings, go to Keyboard, and scroll to the Dictation section. Make sure the toggle is on. If it is already on, turn it off, wait a few seconds, and turn it back on. On some Macs this re-downloads the language files and clears a stuck state.

Check the language list underneath it. If you write prompts in English but the active dictation language is set to something else, you will get nothing or nonsense. Claude does not tell macOS what language you are prompting in, so a language you added for another task stays active until you change it.

If the toggle is greyed out and will not move, that is a management or parental-control restriction rather than a bug. Skip ahead to fix 8, or see the dedicated guide to greyed-out dictation.

4. Fix the shortcut and the Globe key setting

The same Keyboard settings pane has a Shortcut option for dictation. The default is pressing the Fn or Globe key twice, but it can be changed to a Control key press or a custom key, or set to Off. If it is Off, no key will start dictation no matter how many times you press it, and only the Edit menu will work.

Claude adds a wrinkle here. Its Quick Entry shortcut is Option-Space, which does not conflict with Fn on its own. But if you changed it to something involving Fn or Globe, or if a launcher, clipboard manager or window utility on your Mac claims a double-tap gesture, a double press can open the wrong thing or be swallowed before macOS sees it. Check Claude's shortcut in its settings and change it if it overlaps with anything. Then quit other utilities one at a time and retest. The Edit menu entry for Start Dictation always bypasses the shortcut, so use it as a control. Our guide to the Fn key not starting dictation goes deeper if this turns out to be your problem.

5. Check the microphone, twice

There are two microphone checks, and they fail independently.

The system input. Dictation starts, the indicator appears, and nothing is typed. That pattern almost always means macOS is listening to the wrong input, or to one with the gain turned down. Open System Settings, then Sound, then the Input tab. Speak and watch the level meter move. If it does not, the selected device is not hearing you. The usual culprits are AirPods still connected to your iPhone, an external display with a built-in microphone that macOS picked automatically, or a USB audio interface with its gain at zero. Select the built-in microphone, confirm the meter moves, and try again. The microphone troubleshooting guide has the full checklist.

Per-app permission. Apple dictation listens through the system and does not need a per-app permission, so the Fn key can work in Claude while a microphone button inside Claude, if your version has one, fails every time. Open System Settings, go to Privacy & Security, then Microphone, and check the list. If you use a third-party dictation app, it needs to be listed and switched on under its own name. If you use a microphone button inside the Claude desktop app, Claude needs to be listed. If an app is not listed at all, it never asked, which usually means it was quit before the prompt appeared. Trigger the feature again, and when the permission dialog appears, allow it. If you denied it once, the only way to get the dialog back is to switch the toggle on in that list, or in stubborn cases to reinstall the app.

If you use Claude in a browser rather than the desktop app, the permission belongs to the browser, and the browser then asks per site. Look for a microphone icon in the address bar and make sure claude.ai is allowed.

6. Watch for focus leaving the window mid-sentence

Claude is a conversation, and conversations move. While you are dictating, a response can finish streaming and scroll the page. A notification can arrive. An artifact can open in the side panel and shift the layout. None of these should move the text cursor, but in practice some of them do, and the second half of your sentence ends up nowhere.

The workaround is to dictate before Claude starts responding, not while it is still generating, and to keep the artifact panel closed while you speak if you have noticed the problem. If you are using the double-press Fn method, finish shorter sentences and stop dictation between them rather than running one long session across a response. A hold-to-talk tool sidesteps most of this because nothing is inserted until you release the key, at which point the text lands in one piece wherever the cursor is.

7. Switch between the desktop app and the browser to isolate the layer

You can run Claude on a Mac two ways: the desktop app, or claude.ai in Safari, Chrome, Firefox or another browser. They are the same account and the same conversations, but a different piece of software owns the text field, and that matters for dictation.

If dictation fails in the desktop app, open claude.ai in a browser, click into the prompt box, and try there. If it works in the browser, the app is the issue: quit it fully with Cmd-Q, reopen it, check for an update, and if it still fails, reinstall it. Reinstalling does not touch your conversations, which live in your account, but you will need to sign in again.

If dictation fails in the browser but works in the app, the browser is the middleman causing trouble. Try a private window to rule out extensions, since ad blockers, grammar checkers and privacy extensions sometimes interfere with text fields on the Claude site. Try a second browser. Chrome in particular has its own quirks with Mac dictation that we cover in our guide to dictation not working in Chrome.

8. Check management profiles and Screen Time on a work Mac

If your Mac was issued by an employer or school, a management profile can disable dictation outright. The symptom is a greyed-out toggle in Keyboard settings, or a toggle that flips back off on its own. Open System Settings, go to Privacy & Security, and look for Profiles near the bottom. If one is installed and dictation is restricted, only your IT team can change it.

Claude adds a second layer on managed Macs. Many organisations restrict assistant tools through the same profiles, blocking the desktop app from being installed, blocking the website, or blocking its microphone access specifically. If a feature exists on your personal Mac and is missing on your work Mac, that is almost certainly policy, not a bug. Screen Time on a personal Mac can do the same thing through Content & Privacy restrictions, so check there too.

9. Quit, update, sign out, restart

If everything above checks out and dictation still fails only in Claude, work through the blunt instruments in this order:

1. Quit Claude completely with Cmd-Q. Closing the window may not be enough; the app can keep running for the Quick Entry shortcut.
2. Check your connection. If your version has its own microphone button, it sends audio to a server and returns text, so it does nothing offline or on a captive Wi-Fi portal that has not been signed into yet. The Fn key does not have this dependency in the same way, which is a quick way to tell the two failures apart.
3. Update Claude, and update macOS if an update is pending. The app changes often, and bugs tied to a specific version do get fixed in point updates.
4. Sign out of Claude and back in. A stale session can leave the prompt box in a half-working state where text appears but nothing sends.
5. Restart the Mac. This clears stuck audio sessions that no individual quit will release.
6. Test in a new chat, so a very long conversation with hundreds of messages and several artifacts is ruled out as the cause of a sluggish prompt box.

If dictation still does not work in Claude after a restart while it works in every other app, you have found a Claude bug rather than a Mac problem. Report it through the app's help menu, and use the workaround at the end of this article until it is fixed.

Claude quirks that look like broken dictation

Some behaviour is not a failure at all, just Claude doing something you did not expect while you were talking.

• Return sends the prompt. In Claude, pressing Return sends and Shift-Return inserts a line break. If you are used to hitting Return to end dictation, you will send half-finished prompts. End dictation with the key you started it with, proofread, then send.
• Long text becomes an attachment. The Claude website and app turn a long block of pasted text into a small attachment chip rather than showing it inline in the prompt box. Some dictation tools insert text in a way the page treats as a paste. If you dictated a long, detailed prompt and it appeared as a chip with a word count instead of as text, nothing was lost. Claude will read it as part of your message. If you want it inline so you can edit it, dictate in shorter pieces.
• Spoken punctuation. Apple dictation expects you to say "comma", "period" and "new line". Most third-party dictation apps punctuate for you from your pauses. If your punctuation vanished, or the word "comma" is appearing in your prompts, you switched from one to the other.
• Long prompts trail off. Apple dictation stops on its own after a pause of a few seconds and after a fixed maximum duration. A detailed prompt with background, constraints and examples can easily run past it. Dictate in shorter bursts, or use a tool without that limit.
• The at-sign and slash. In some versions, typing an at-sign or a slash in the prompt box opens a picker for files, projects or tools. If dictation inserts the word "at" or "slash" rather than the symbol, no picker opens and it is just text. Add those by hand.
• Switching chats mid-sentence. Clicking another conversation while dictation is running moves focus, and the rest of the sentence lands in the new chat's prompt box, or nowhere. Finish or stop dictation first.
• Code blocks. Dictating three backticks to open a code block rarely works; you get the word "backtick". Dictate the description, then type the fences. If you write a lot of code with Claude, our guide to dictation for coding covers the habits that make this painless.
• Usage limits. If a banner says you are near or past your usage limit, your dictated text may appear but the prompt will not send until the limit resets. That is an account state, not a dictation problem.

Dictating into Claude Code in the terminal

A growing number of people talk to Claude not in the app but in a terminal, through Claude Code. Dictation works there too, with two differences worth knowing. First, terminal apps vary in how well they accept text from Apple dictation. Some show the words as they arrive, others show nothing until dictation ends, and a few drop characters. If the Fn key gives you nothing in your terminal, try a different terminal app before assuming dictation is broken; the built-in Terminal is a good control. Second, Return in a terminal runs the command. If Apple dictation inserts a line break because you paused, you may send a partial instruction. A hold-to-talk tool that inserts the whole sentence at once avoids that. Our separate guide to voice typing in the terminal goes into detail.

When macOS dictation is the problem, not Claude

If you have reached this point, run the split test again with fresh eyes. A lot of people discover that Apple dictation is unreliable for them everywhere, and Claude was simply where they noticed it because prompts are long and they write a lot of them. The Fn key needs a double press that sometimes registers as one. Long prompts cut off. The product names, project names and technical terms you use in every prompt come out wrong each time, and there is no easy way to teach it.

Voice Keyboard Pro is our answer to that. It is a small menu bar app for Mac. You hold a hotkey, speak, and release, and the text appears at your cursor in whatever app is in front, including the Claude desktop app, the Quick Entry bar, claude.ai in any browser, and a terminal running Claude Code. There is no separate dictation window to manage and nothing to copy across. Because it inserts text into whichever field has focus, everything in fix 1 still applies: the cursor needs to be in the prompt box. But the trigger is a hotkey you hold rather than a double tap you hope registered, so the "did it start?" ambiguity goes away, and there is no silence timeout to end a long prompt early.

Two features matter specifically for prompting. Smart Vocabulary is a personal dictionary with replacement rules, so the names of your projects, your company's products, and the acronyms you use in every prompt get spelled the way you want every time. And Voice Keyboard Pro's transcription engine punctuates from how you speak without rewriting your words, so when you want your exact phrasing preserved in a prompt, it is. We wrote a separate guide to dictating Claude prompts that covers structuring a long request by voice.

Like most third-party dictation apps, it inserts text through macOS accessibility features, so it asks for Accessibility permission and microphone permission once, under its own name. It does not need Claude's microphone permission, and Claude does not need to know it is there. If you have had trouble with other utilities in this category, the guide to third-party dictation apps not working covers the permission dance in full.

On privacy, since prompts often contain work that is not public: the server stores only operational pings, such as whether a device is active. No audio and no transcript content are kept. What you dictate into a prompt goes to your Mac and then to Claude, and nowhere else.

There is a free tier with daily limits, and Pro is $4.99 a month or $34.99 a year. If your Claude problem was really an Apple dictation problem, it is a cheaper fix than the hours you have spent in System Settings.

If you also use ChatGPT on your Mac and its dictation misbehaves, the causes overlap but are not identical, because that app brings its own voice features. We cover it separately in our guide to Mac dictation not working in ChatGPT.

Frequently asked questions

Dictation works in Notes but not in Claude. Why?

Because Claude has more text fields than it looks like, and one of its windows closes when it loses focus. The most common causes are the cursor sitting in the sidebar search, a project field or an edited message rather than the prompt box, or the Quick Entry bar being open somewhere and either holding focus or closing when dictation starts. Run through fixes 1 and 2.

Where is the dictation button in Claude on Mac?

In most versions there is not one. Claude on Mac relies on macOS dictation or a third-party dictation app, both of which type into the prompt box like any other text field. Start macOS dictation with the Fn or Globe key or from the Edit menu. If your version shows a microphone icon near the prompt box, that is Claude's own dictation and it needs Claude to have microphone permission.

Does the Fn key need Claude's microphone permission?

No. Apple dictation listens at the system level and inserts text into the focused field. It never asks Claude for anything. Only a microphone button inside Claude would need the app to appear in the Microphone list under Privacy & Security. Third-party dictation apps use their own permission, under their own name, rather than Claude's.

My dictated prompt turned into an attachment chip. Did I lose it?

No. The Claude website and app convert long pasted text into an attachment so the prompt box stays readable. Some dictation tools insert text in a way that triggers this. Claude reads the attachment as part of your message. If you need the text inline to edit it, click the chip to view it, or dictate the prompt in two or three shorter pieces.

Why does my dictation cut off in the middle of a long prompt?

If you are using the Fn key, Apple dictation ends after a few seconds of silence and after a maximum session length, and a detailed prompt often runs past both. If you are using the Quick Entry bar, it may be closing when it loses focus. Dictate in the main window, in shorter bursts, or use a hold-to-talk tool with no session limit.

Does dictation in Claude work offline?

Apple dictation works offline for languages you have downloaded, and a third-party app needs a connection for transcription. Either way, you still need a connection to send the prompt. In practice, if you are offline, Claude is not going to be much use whichever way you enter the text.

Is this a privacy risk? Who hears my prompts?

With the Fn key, your speech is handled by macOS, on device for supported languages, and only the resulting text goes to Claude. With Voice Keyboard Pro, the server stores only operational pings; no audio and no transcript content are kept. Whichever route you take, the text of the prompt itself is then sent to Claude, so treat the prompt as you would any message to an online service.