Short answer: Dictation usually fails in Obsidian for three reasons: your shortcut is claimed by an Obsidian hotkey before macOS sees it, focus is in a panel rather than the note editor, or a plugin is rewriting dictated text as it arrives. Test in TextEdit first, then turn on Restricted Mode to isolate plugins.
Obsidian is one of the best places to think and one of the more hostile places to dictate. Not because the developers did anything wrong, but because of what Obsidian is: a browser engine running a text editor, wrapped in a hotkey system that treats almost every key as a potential command, extended by a plugin ecosystem whose entire purpose is to modify text while you type it.
Each of those three properties can break dictation on its own, and they produce very different symptoms. Dictation that never starts is a hotkey problem. Dictation that starts but inserts nothing is a focus problem. Dictation that inserts text and then mangles it is a plugin problem. Telling them apart takes about a minute, and once you know which of the three you have, the fix is usually one setting.
Worth saying up front: Obsidian has no dictation feature of its own. Whatever you are triggering belongs to macOS or to a third-party app. There is no Obsidian dictation setting to find, which is why searching Obsidian's settings for one is frustrating.
Start here: the TextEdit split test
Open TextEdit, create a blank document, trigger dictation, and say a short sentence.
If TextEdit also fails, the system service is the problem and Obsidian is a bystander. Check that Dictation is switched on in System Settings under Keyboard, then check your input device in System Settings under Sound. If the input level meter does not move when you speak, dictation has nothing to work with. That is fixes 1 and 8 below.
If TextEdit works, the service is healthy. Continue down this list, which is ordered from most to least common in Obsidian specifically.
Now open a brand new note in a scratch vault, not the note you were working in. A large daily note with heavy formatting is the worst possible test surface. You want an empty note in a plain vault so that nothing else is competing.
Fix 1: Obsidian is eating your shortcut before macOS gets it
This is the most common cause and the least obvious, because from your side it looks like the key simply did nothing.
Obsidian binds an unusually large number of keys, and community plugins add more. When a key is bound to an Obsidian command, Obsidian handles it and stops it from propagating. Your dictation trigger never reaches the system.
Open Obsidian Settings, go to Hotkeys, and type your dictation key into the search field at the top. Anything that appears is claiming it. Either clear the Obsidian binding or, better, move the dictation trigger somewhere unclaimed.
The Globe key deserves special attention. On modern Macs the default dictation trigger is a double press of Globe, and a double press of anything is a bad trigger in an app with a busy keymap: if your timing slips, macOS reads it as two single presses and opens the emoji picker or cycles your input source instead. In System Settings, under Keyboard and then Dictation, change the shortcut to a single dedicated key. F13 through F19 are the conventional choice because essentially nothing binds them by default, including Obsidian.
The same failure shows up in every Electron editor for the same reason. If you also work in a code editor, Mac dictation not working in VS Code covers the identical conflict from the other side.
Fix 2: Focus is in a panel, not in the note
Obsidian's window is full of places that accept keyboard input and are not your note. Dictation types into whatever is focused, and it does not care whether that thing is where you wanted the words.
The usual suspects:
- The command palette or quick switcher. If either is open, even barely visible, it has focus. Press Escape before triggering dictation.
- The search pane. Clicking search leaves focus in the search field, and dictated text lands there and quietly filters your vault instead of writing a note.
- The properties or frontmatter fields. These are separate input contexts at the top of a note. Text dictated into a property key or value goes into the metadata rather than the body.
- Canvas cards. A selected card is not an editing card. You need to enter edit mode on the card before it accepts input.
- Sidebars and file explorer. Clicking a filename focuses the explorer, not the editor. Renaming state in the explorer will happily take dictated text as a filename.
The test is to type a single character on the keyboard before you dictate. Whatever the character does tells you exactly where focus is. If it does not appear in your note, dictation was never going to appear there either.
Fix 3: Microphone permission, and why Obsidian probably is not in the list
Open System Settings, go to Privacy & Security, then Microphone. If you use Apple's built-in Dictation, Obsidian will most likely not be listed, and that is correct. Apple Dictation runs as a system service outside the app, so Obsidian never requests microphone access.
This changes if you use a third-party dictation app. Those apps do need microphone access, and they generally also need Accessibility permission so they can insert text into other applications. Both live in Privacy & Security.
There is an Electron-specific trap worth knowing here. macOS ties permission grants to the app on disk, and Obsidian updates itself frequently. After an update, a permission entry can end up in a stale state where the toggle appears on but the grant no longer functions. The fix is to select the entry, remove it with the minus button, quit and reopen the app, and grant permission again when prompted. If dictation broke on the same day Obsidian updated itself, check this before anything else.
Fix 4: Vim mode is treating your sentence as a series of commands
If you have Vim key bindings enabled, in Settings under Editor, dictation in normal mode is genuinely destructive rather than merely broken.
In normal mode, every letter is a command. A dictated sentence is dozens of letters arriving in rapid succession, which means deletions, joins, jumps, undos, and changes firing in an order nobody intended. People describe this as dictation "scrambling my note," which is accurate.
Two workable approaches. Either confirm you are in insert mode before every dictation, which is a discipline that fails eventually, or use a dictation tool that inserts text directly rather than simulating keystrokes. Tools that paste or insert at the cursor bypass the modal layer entirely, because no individual keys are being pressed.
If a dictated sentence ever destroys work, Command-Z repeatedly will usually walk it back. Obsidian's undo history is granular enough to recover from this.
Fix 5: A plugin is rewriting the text as it arrives
This is the failure where dictation is working perfectly and the result is still wrong. Several popular plugin categories modify text as you type, and dictated text arrives fast enough to trigger their worst behaviour.
- Autocomplete plugins. Anything that suggests completions from your vault will pop a suggestion mid-sentence, and if it accepts on space or Enter, your dictated space silently accepts a word you never said. This is the single most common cause of "dictation inserts random words from my notes."
- Smart typography plugins. These convert quotes, dashes, and ellipses on the fly. Usually fine, occasionally surprising, and a real problem if you dictate anything that will be pasted into code or a terminal.
- Templater and similar. Templates that fire on triggers can react to dictated characters in ways that were designed around deliberate typing.
- Linter plugins. Formatting on save will reflow and reformat what you dictated, which looks like dictation produced the wrong structure.
- Auto-pairing brackets and callout helpers. Dictated punctuation can open pairs that never close, leaving stray characters through the note.
Do not guess which plugin is responsible. Open Settings, go to Community plugins, and turn Restricted Mode on. That disables every community plugin at once. Test dictation. If it works, turn Restricted Mode off and re-enable plugins in halves, testing each time. Two or three rounds of that finds the culprit reliably, and it is much faster than reasoning about which plugin seems suspicious.
Fix 6: Live Preview is hiding the markdown you dictated
This one is not a bug at all, but it generates a lot of confused reports.
In Live Preview, markdown syntax is rendered rather than displayed. If you dictate spoken punctuation that produces markdown characters, the editor may render the result immediately, and the characters you expected to see are hidden inside formatting you did not want. Dictating a line that happens to begin with a hash and a space turns into a heading. Dictating asterisks produces emphasis or a bullet.
Switch the note to Source mode from the view menu at the top right of the pane, or from the command palette. In Source mode you see exactly what is in the file, which makes it obvious whether dictation produced the wrong characters or produced the right ones and Live Preview rendered them.
For structured dictation such as bullet lists, it is generally easier to dictate the prose and add the structure with the keyboard afterwards. Our guide to dictating in Obsidian goes through the workflow patterns that hold up over a long note, including where in the process to add links and tags.
Fix 7: Text appears, then reverts, because sync is fighting you
If dictated text lands and then vanishes seconds later, the problem is the file, not the dictation.
Obsidian vaults are plain files in a folder, which is a strength until two things write to that folder at once. Vaults kept in iCloud Drive, Dropbox, or Google Drive can produce conflict files or silently restore an older version while you are actively editing. If your vault lives in a synced folder and the same note is open on a second device, close it there and let sync settle before testing again. Look for conflict-named copies of the note appearing alongside the original, which is the clearest evidence.
Vaults under Git have a similar failure mode when an automatic commit or pull plugin runs on a timer while you are mid-note.
There is also a permissions version of this. If your vault lives in Documents, Desktop, or iCloud Drive, macOS gates access to those folders, and Obsidian needs permission to write there. If writes are being denied, Obsidian will usually complain, but a vault on an external drive that unmounted, or a network share that dropped, can fail more quietly.
Fix 8: The audio chain, not the app
If the TextEdit test failed, this is your section.
Check the input device in System Settings under Sound. Speak and watch the level meter. Bluetooth headsets are the usual problem: a headset connected for playback is not necessarily connected as an input device, and the switch into microphone mode takes a moment, which clips your first words and reads as dictation missing the start of sentences.
Also check whether something else is holding the microphone. A call left running in a background tab, a recording app, or a meeting client sitting idle can claim the input and leave dictation listening to silence. This is especially easy to miss on a Mac that has been awake for days.
If dictation worked yesterday and does not today, and nothing changed, restart the Mac before investigating further. The audio stack can come back from a long sleep in a state that a restart resolves and nothing else does.
Fix 9: Managed Macs and policy restrictions
If the Dictation toggle in System Settings is greyed out or refuses to stay on, the machine is managed. Check System Settings, General, then Device Management. An MDM profile can disable Dictation and Siri as a blanket data-handling policy.
On personal machines, Screen Time content restrictions can do the same thing. Look under Screen Time, then Content & Privacy, for restrictions covering Siri and Dictation.
Neither is overridable locally. Both target Apple's service specifically rather than dictation as a concept, but on a work machine, ask before installing an alternative.
Things that look like bugs and are not
Dictation stops after a pause. Apple's Dictation stops listening after silence. If you compose the sentence in your head and then speak, you will hit that timeout constantly. It is a design decision, not a failure.
Wiki links come out as prose. Dictating a link name gives you the words, not the brackets. Speaking bracket characters usually collides with auto-pairing. Dictate the prose, then add links with the keyboard.
Tags lose their hash. Same reason. Spoken punctuation is inconsistent for symbols that carry structural meaning in markdown.
Names and jargon are wrong. Transcription resolves ambiguous audio toward common words, so unusual surnames and internal project names lose that contest. A vault full of specialist vocabulary makes this worse, not better, because your notes are precisely the words general transcription does not expect.
The version of this that stays fixed
Every fix above is worth doing once. The problem is that Obsidian updates often, plugins update on their own schedule, and the conflicts come back. Two months from now, a plugin update rebinds a key or adds an autocomplete behaviour and you are back in Settings.
The structural fix is to stop using a dictation method that depends on a mode and a shared keymap. Voice Keyboard Pro uses a hold-to-talk gesture: hold your hotkey, speak, release, and the text lands at your cursor in whatever app is in front of you. A hold cannot be mistimed the way a double press can, there is no session to start or forget to end, and there is no silence timeout to run out of mid-thought.
Two things matter for a vault specifically. Smart Vocabulary is a personal dictionary with replacement rules, which is the direct answer to the jargon problem: the project names, people, and domain terms that transcription mangles get spelled the way you spell them. And Meeting Mode, with speaker detection and AI notes, covers the case where the note you are writing is a record of a conversation rather than your own thinking. On privacy, our servers keep only operational pings. No audio and no transcript content is stored.
The free tier has daily limits and Pro is $4.99 a month or $34.99 a year. If your vault is where your thinking lives, it is worth trying against a real note rather than a test one. The mobile side is covered too, which matters if you capture on the move; dictating in Obsidian on mobile goes through that workflow, and the failure modes there are different again.
Frequently asked questions
Does Obsidian have a built-in dictation feature?
No. Obsidian has no dictation of its own. Anything you trigger is either macOS Dictation or a third-party app, which is why there is no Obsidian setting that fixes it.
Why does dictation work in Apple Notes but not in Obsidian?
Apple Notes is a native app with one text context and almost no hotkeys. Obsidian is an Electron app with a large keymap, several focusable panels, and plugins that modify text as it arrives. Three extra layers, three extra ways to fail.
Do I need to give Obsidian microphone permission?
Not for Apple's Dictation, which runs outside the app and will not list Obsidian in Privacy & Security. A third-party dictation app does need microphone access, plus Accessibility permission to insert text.
Why does dictated text insert words from my other notes?
An autocomplete plugin is accepting a suggestion on your dictated space or newline. Turn on Restricted Mode to confirm, then re-enable plugins in halves to find which one, and change its accept key or disable it while dictating.
Dictation scrambles my note. What is happening?
Almost certainly Vim mode in normal mode, where each dictated letter runs as a command. Command-Z repeatedly will recover the note. Confirm insert mode first, or use a tool that inserts at the cursor rather than simulating keystrokes.
Can I dictate into Obsidian Canvas?
Yes, but the card has to be in edit mode, not merely selected. Selecting a card gives it focus without giving it an insertion point, so dictated text has nowhere to land.
Will reinstalling Obsidian fix dictation?
Rarely worth it. Since Obsidian contains no dictation code, reinstalling changes nothing about transcription. The exception is a stale permission entry after an update, and for that, removing and re-adding the permission entry is the faster fix.
Is this different from dictation problems in Notion?
The focus and Electron issues are shared, but the text-rewriting layer is not. Notion's blocks behave differently from markdown plus plugins. See Mac dictation not working in Notion for that version of the problem.
The words land at your cursor in whatever app you are already in — Mail, Slack, Word, a browser form. No dictation window, nothing to copy across.
Free forever for casual use · Apple Silicon & Intel