Mac Dictation Not Working in LinkedIn? 9 Fixes That Work

Short answer: LinkedIn has no dictation feature of its own, so failures trace back to macOS or your browser. Check the browser's microphone permission in System Settings, click directly inside the post or message box so it holds focus, confirm the right input device is selected, and watch for the dictation timeout on long posts.

You press the dictation shortcut, the microphone indicator appears, you say a full sentence about a hiring update, and the LinkedIn post box stays empty. Or worse: the first four words land, then nothing. Or the text appears in the search bar at the top of the page instead of the composer you were looking at.

This is one of the more confusing dictation failures to diagnose because LinkedIn itself has no dictation setting anywhere in its interface. There is no toggle to flip, no permission LinkedIn asks for, no microphone button in the post composer on desktop. Everything that can break is either in macOS or in the browser sitting between macOS and LinkedIn. That is good news, because it means the list of possible causes is short and testable.

Below is that list, ordered so the fastest checks come first. Work down it and stop when your text lands.

First: the thirty-second test that tells you where the fault is

Before changing any setting, find out whether the problem is LinkedIn-shaped or Mac-shaped. Open TextEdit, or Notes, or Spotlight. Press your dictation shortcut. Say a sentence.

• Text appears in TextEdit but not in LinkedIn. macOS dictation works. The problem is the browser or the LinkedIn page itself. Go to fixes 2, 3, 5, 6, and 8.
• Text does not appear in TextEdit either. This is a system-level failure, not a LinkedIn one. Go to fixes 1, 4, 7, and 9.
• Text appears in both but LinkedIn drops words partway through. Almost always the timeout or the composer losing focus. Go straight to fixes 3 and 6.

Thirty seconds of testing saves twenty minutes of poking at settings that were never the cause. It also stops you from disabling browser extensions one by one when the real problem was that the microphone was set to a headset that went to sleep.

Fix 1: Give your browser microphone access in System Settings

macOS gates the microphone per application, and a browser is one application no matter how many tabs are open. If Safari, Chrome, Arc, Brave, Edge, or Firefox does not hold the microphone permission, nothing you dictate into any web page will land.

Open System Settings, go to Privacy & Security, then Microphone. Find your browser in the list and confirm the toggle is on. If the browser is not in the list at all, macOS has never been asked for the permission, which usually means the browser needs a restart after you grant it.

One detail that trips people up: granting the permission while the browser is running does not always take effect until the browser is fully quit and relaunched. Not closing the window. Quit with Command-Q, then open it again. Web apps that were already loaded keep the old permission state until the process restarts.

The separate in-browser permission

Chromium browsers keep their own microphone permission layer on top of the macOS one, scoped per site. This layer matters if you use LinkedIn's video or audio message features, or if you dictate through a browser extension rather than through macOS dictation. Click the icon at the left edge of the address bar while LinkedIn is open, find the microphone entry, and set it to Allow. If the entry is missing, the page has never requested microphone access, which is normal for plain text dictation and nothing to worry about.

Fix 2: Click inside the box before you press the shortcut

This sounds too obvious to list, and it is the single most common cause.

macOS dictation inserts text wherever the system thinks the text cursor is. LinkedIn's post composer is a rich text region that opens in a modal over the feed. If you clicked the "Start a post" button and the modal opened, the cursor may not actually be inside the writing area yet even though the placeholder text is showing and the cursor looks like it is blinking there. Some browsers place initial focus on the modal container rather than the editable region inside it.

Click once directly on the placeholder text, see the caret appear, type a single character to confirm the field is live, delete it, then start dictating. If the character does not appear when you type it, dictation was never going to work either. That one keystroke is the fastest focus test there is.

The same applies to the messaging box at the bottom right of the screen, to comment fields under posts, and to the headline and About fields in profile editing. Each one is a separate editable region and each one needs an explicit click.

Fix 3: Watch for focus being stolen mid-sentence

LinkedIn's feed is a live surface. New posts load, notification counts update, suggested connections slide in, and the messaging panel can pop open when someone replies to you. Any of these can move browser focus out of the composer while you are mid-sentence. Dictation keeps listening, the words keep being recognized, and they land somewhere you are not looking. Sometimes nowhere at all.

Three things reduce this:

• Write in the full-screen composer. The expanded post editor is less prone to interruption than the small inline box, because fewer live elements sit inside it.
• Collapse the messaging panel before you start. An incoming message that expands the panel is a common focus thief.
• Dictate in shorter runs. Two or three sentences, release, check, continue. If focus is stolen you lose a fragment instead of a paragraph.

If you are writing anything longer than a short comment, there is a stronger version of this advice: do not write it in LinkedIn at all. Draft in a plain text editor where nothing can steal focus, then paste. That is also the approach recommended in our guide to voice typing LinkedIn posts, for the same reason.

Fix 4: Confirm the right microphone is actually selected

macOS picks an input device, and it does not always pick the one you expect. Plug in a headset, join a call, unplug the headset, and the system can be left pointing at a device that is no longer there or that has switched into a mode with a different input.

Open System Settings, then Sound, then the Input tab. Speak normally and watch the level meter. If the bars do not move, the selected device is not hearing you. Switch to the built-in microphone and test again.

Bluetooth headsets deserve special suspicion. Many of them run in a high-quality listening mode by default and switch to a lower-quality two-way mode only when an application requests the microphone. That switch takes a moment, and if you start speaking immediately after pressing the shortcut, the first words go missing. Press the shortcut, pause for a beat, then speak. AirPods are particularly prone to this, and we cover the pattern in more depth in the post on Mac dictation not working with AirPods.

Fix 5: Secure Input may be holding the keyboard hostage

macOS has a protection called Secure Input. When an application turns it on, it blocks other processes from observing keystrokes. It exists so password fields cannot be logged, and it is the correct behavior. The problem is that applications sometimes enable it and fail to turn it off, leaving the whole system in a state where dictation shortcuts and text insertion behave strangely.

Password managers, terminal emulators, remote desktop clients, and video conferencing apps are the usual culprits. LinkedIn's own sign-in page can trigger it too: if you loaded LinkedIn, landed on the login screen, clicked the password field, and then signed in, the flag can linger.

The quickest diagnosis is to quit your password manager and any terminal windows, then try dictating again. If that fixes it, you have found your source. Logging out and back in clears the state reliably when you cannot identify which application is responsible.

Fix 6: The dictation timeout is cutting your post in half

If your first two sentences land and the rest evaporates, you are probably hitting a listening timeout rather than a permission problem.

Built-in dictation on macOS is designed around short bursts. It listens, transcribes, and stops. For a search box or a chat reply that is fine. For a LinkedIn post of three hundred words it is not, because the session ends before you finish the thought and you are left mid-paragraph wondering what broke.

Two workarounds. First, dictate in deliberate chunks: one paragraph, release, breathe, start again. Second, and better for anyone posting regularly, use a dictation tool that is built around holding a key for as long as you are speaking rather than starting a timed session. That is how Voice Keyboard Pro works on the Mac: you hold your hotkey, speak for as long as you need, release, and the finished text appears at the cursor in whatever application is in front of you. There is no session to expire mid-sentence.

Fix 7: A shortcut conflict is swallowing the trigger

If pressing the dictation shortcut produces no microphone indicator at all, something else has claimed that key combination.

Open System Settings, then Keyboard, then Dictation, and look at the shortcut assigned. The common defaults involve pressing a modifier key twice or pressing the microphone key. Both are easy to collide with: screen recording tools, window managers, clipboard managers, and note-taking apps all like to grab global shortcuts, and some of them do it silently on install.

Set the dictation shortcut to something deliberately unusual and test it. If it works, you have a conflict and can go hunting for the offender at your leisure. If it still does nothing, the problem is not the shortcut. Our guide to a Mac dictation shortcut not working walks through the full elimination process.

Fix 8: Browser extensions interfering with the page

Content blockers, privacy extensions, grammar assistants, and social media "focus" extensions all modify LinkedIn's page in ways the site did not anticipate. Grammar extensions in particular inject their own editing layer over text fields, and that layer can intercept the text being inserted or confuse which element holds the cursor.

Open a private browsing window, where most extensions are disabled by default, load LinkedIn, and try dictating into a comment. If it works there, an extension is the cause. Re-enable them in batches rather than one at a time to narrow it down faster.

Privacy-focused browsers apply some of this behavior by default rather than through an extension, which makes the same symptom harder to trace. If you are on one of them, the browser-specific notes in Mac dictation not working in Brave and Mac dictation not working in Chrome apply directly to LinkedIn too.

Fix 9: Restart the dictation service, then the Mac

If everything above checks out and dictation still refuses to work anywhere, the service itself may be stuck. This happens most often after a macOS update, after waking from sleep, or after a period of heavy memory pressure.

Toggle dictation off in System Settings, wait several seconds, then turn it back on. This forces the service to reinitialize. If you are prompted to download a language component, let it finish completely before testing, and stay on a stable network while it does. A partially downloaded language component produces exactly the symptom people describe as "dictation turns on but nothing happens."

If toggling does not help, restart the Mac. This is the fix nobody wants to hear and the one that resolves a genuine share of cases, because it clears stuck Secure Input flags, releases audio devices held by crashed processes, and reinitializes the dictation service in one step.

Why LinkedIn breaks dictation more often than a plain text box

It is worth understanding the shape of the problem, because it explains why the same fixes keep working.

A LinkedIn composer is not a simple text input. It is a rich editable region that supports mentions, hashtags, links, and formatting, wrapped in a page that is constantly updating itself. When you type an "@" character, an autocomplete dropdown appears and takes over keyboard handling until you dismiss it. When you paste a URL, the page fetches a preview and rewrites part of the composer. When a notification arrives, elements shift.

Dictation inserts text as if it were typed, which means it walks into all of the same machinery. Say the word "at" in a sentence and you may or may not trigger mention handling depending on how the text is inserted. Dictate a long stretch and the composer's own autosave may run partway through and reset the caret position.

None of this is LinkedIn behaving badly. It is a rich editor doing rich editor things. But it does mean that the more complex the field, the more value there is in a dictation approach that hands over a complete block of finished text at once, rather than streaming words into a live editor and hoping the editor keeps up.

What actually changes if you dictate differently

Every fix above addresses a symptom of the same structural situation: built-in dictation is a timed session that streams into whatever field it can find, and LinkedIn is a moving target.

Voice Keyboard Pro takes the other approach on the Mac. It sits in the menu bar. You hold your chosen hotkey, speak for as long as you want, and release. The transcription happens, and the finished text is placed at your cursor in whatever application is frontmost, whether that is a LinkedIn composer in Safari, a Slack message, a Word document, or a terminal. Because it inserts once at the end rather than streaming during, it sidesteps most of the mid-sentence focus problems described above.

Two features matter specifically for LinkedIn. Smart Vocabulary is a personal dictionary with replacement rules, which is how you stop your company name, your product names, and the industry acronyms in your posts from being transcribed phonetically every single time. If you write about the same five topics, you teach it those terms once. And Meeting Mode, with speaker detection and AI notes, turns the conversation you just had into material you can actually post about, which is frequently where a LinkedIn post starts.

On privacy, which is a fair question when your posts are professional communication: the server stores only operational pings. No audio, no transcript content.

There is a free tier with daily limits, which is enough to find out whether the approach suits how you write. Pro is $4.99 a month or $34.99 a year.

If you are hitting this on your iPhone instead

The LinkedIn mobile app is a different environment with different failure modes: keyboard permissions, the app's own microphone handling, and the in-app browser all behave differently from the desktop site. We cover those separately in iPhone dictation not working in LinkedIn.

Worth noting for anyone who writes on both: Voice Keyboard Pro on iPhone is a custom keyboard with a built-in mic button, so it works inside the LinkedIn app the same way it works anywhere else in iOS. It also includes Voice Edit, where you speak a change to fix text you have already written, which is unusually useful for the last pass over a post before you publish it.

Quick reference

1. Test dictation in TextEdit to find out whether the fault is systemwide or LinkedIn-specific.
2. Grant the browser microphone access in Privacy & Security, then fully quit and relaunch it.
3. Click directly in the composer and type one character to confirm focus before dictating.
4. Keep the messaging panel collapsed so it cannot steal focus mid-sentence.
5. Check the Sound input device and watch the level meter move while you speak.
6. Pause a beat after pressing the shortcut if you are on a Bluetooth headset.
7. Quit password managers and terminals to clear a stuck Secure Input flag.
8. Dictate in paragraph-sized chunks if sessions are timing out, or switch to hold-to-talk.
9. Test in a private window to rule out extensions, then restart dictation or the Mac.

Nine steps sounds like a lot, but the first three resolve the large majority of cases, and the test at the top tells you which branch to take. Most people are back to writing within two minutes.