Your Dictation App Goes Deaf After Sleep. Here's Why — and the Fix

You press the hotkey. The overlay pops up, the app says it's listening, you talk — and nothing lands. Two minutes ago your Mac was asleep; now your dictation app is deaf. Users across every major dictation tool describe this the same way: the app goes deaf. It looks alive, it just stopped hearing.

When a dictation app stops working after sleep, the cause is almost always the same: macOS tore down and rebuilt its audio stack during the sleep/wake cycle, and the app is still holding a connection to a microphone that no longer exists. Quitting and relaunching the app fixes the majority of cases in about 10 seconds. The rest come down to five other links in the chain:

1. Quit and relaunch the dictation app (10 seconds — fixes most cases)
2. Check which microphone macOS actually woke up with (30 seconds)
3. Restart Core Audio with sudo killall coreaudiod (1 minute)
4. Rule out a Bluetooth microphone handoff (1 minute)
5. Check login items and permissions (2 minutes)
6. Update the app — vendors have shipped wake-resilience fixes (5 minutes)

This guide covers third-party dictation apps like Wispr Flow, Superwhisper, and Voibe. If built-in Apple Dictation is what died, most of these fixes still apply, but start with our dedicated guide to fixing Mac dictation.

Work down this table in order. Each fix takes longer than the one before it, and the early ones resolve the large majority of wake-from-sleep dictation failures.

Dictation apps go deaf after sleep because waking a Mac is not a resume — it is a partial rebuild, and audio is one of the things rebuilt. We call the sequence the Wake Chain, and it has four links:

1. Audio hardware re-registers. Built-in mics come back quickly; USB interfaces and Bluetooth headsets can take several seconds to re-register with the system.
2. Core Audio rebuilds its device list. The coreaudiod daemon re-enumerates every input and output. Device identifiers can change in the process.
3. Your dictation app re-attaches its microphone tap. This is the link that breaks. An app that held an audio capture session open from before sleep may keep reading from a device reference that Core Audio has already replaced. The app's UI reports “listening”; the pipeline underneath is attached to nothing.
4. Text lands at your cursor. Only happens if links 1–3 reconnected.

This is not one vendor's bug — it is a structural weak point of always-running audio software on macOS. Wispr Flow's own troubleshooting docs say their “Unable to access mic” error appears “most often after your Mac wakes from sleep or is under heavy load,” and the same wake-and-nothing-happens pattern fills Apple Support Community threads going back years. Once you know which link broke, the fix is mechanical.

A full relaunch forces the app to request the microphone fresh from the rebuilt audio stack — new device list, new capture session, no stale reference. It resolves most wake-from-sleep dictation failures, which is why vendors list it first in their own docs.

1. Click the app's menu bar icon.
2. Choose Quit — actually quit; closing a window leaves the background process (and its dead audio tap) running.
3. Reopen the app from Applications or Spotlight.
4. Dictate a test phrase into any text field.

If the app has hung completely, force-quit it: open Activity Monitor, search the app's name, select it, and click the X button. macOS treats the next launch as a clean start.

After a sleep/wake cycle, macOS sometimes reassigns the system input device — especially when a Bluetooth headset or external interface reconnects late. Your dictation app may be listening, attentively, to a microphone that isn't in the room.

1. Open System Settings → Sound → Input.
2. Speak normally and watch the input level meter. If the bars move, the selected mic is live.
3. If the bars are flat, select a different device — MacBook Pro Microphone (the built-in mic) is the reliable baseline.
4. Now check the app's own microphone setting. Most dictation apps have a device picker in their settings; if it offers “Auto-detect” or “System default,” switch it to the specific microphone you actually use.

Pinning the app to a named device removes the ambiguity that the wake-up reshuffle exploits. Wispr Flow's docs make the same recommendation: choose your specific mic instead of auto-detect.

If the input meter itself is dead — no bars for any device, or the mic produces static in every app — the problem is a link earlier in the Wake Chain: the Core Audio daemon came back from sleep in a bad state. Restarting it rebuilds the whole audio stack without rebooting the Mac.

1. Open Terminal (Applications → Utilities).
2. Run:
   

   sudo killall coreaudiod

3. Enter your password. macOS relaunches the daemon automatically within a few seconds.
4. Test the input meter in System Settings → Sound, then test dictation.

This is the microphone-side sibling of the killall corespeechd trick that revives Apple's speech recognition — we've covered what killall corespeechd actually does separately. coreaudiod resets the audio devices; corespeechd resets Apple's transcription engine. Wake-from-sleep deafness is usually the former.

Bluetooth is the most common trigger hiding behind “it broke after sleep.” AirPods re-pair a few seconds after wake, and when they do, macOS may yank the system input over to them mid-dictation — or leave the input pointed at a headset that is still negotiating its connection and delivering silence.

1. Open Control Center → Bluetooth and disconnect the headset (or toggle Bluetooth off).
2. Test dictation with the built-in microphone.
3. If dictation works, you've found the culprit: the handoff race, not the app.

Two permanent options: pin your dictation app's input to the built-in microphone (Fix 2) so headphones stay for listening only, or accept the handoff and wait the few seconds after wake before dictating. For long dictation sessions, the built-in mic array on Apple Silicon MacBooks is also simply more consistent than a Bluetooth mic that compresses your voice — a pattern we hit repeatedly while testing apps for our offline dictation roundup.

If dictation is dead not after every sleep but after every login or restart, the app's background process isn't coming back at all — a different failure with the same symptom. Users of several dictation tools report exactly this “won't launch at login” pattern on public feedback boards.

1. Open System Settings → General → Login Items & Extensions and confirm the app is listed under “Open at Login.”
2. Open System Settings → Privacy & Security → Microphone and confirm the app is toggled on.
3. Check Privacy & Security → Accessibility too — dictation apps need this permission to type text at your cursor, and macOS occasionally revokes it after major OS updates.
4. If a permission looks enabled but the app still fails, toggle it off and on, then relaunch the app.

Permission state, unlike the audio stack, survives sleep — but a macOS update in between can silently reset it, and the first symptom you notice is a dictation session that produces nothing.

Wake-from-sleep failures are known bugs, and vendors patch them. Wispr Flow's changelog notes that Flow “now monitors lid open/close, sleep/wake, and device connect/disconnect events in real time” and “automatically recovers audio capture if it's interrupted during an active recording,” per their troubleshooting documentation. Superwhisper's troubleshooting guide walks through audio capture checks — if the recording window's waveform stays flat, audio isn't being captured — and the fix for a known capture bug is often simply the next release.

1. Open the app's settings and run Check for Updates (or redownload from the vendor's site).
2. Read the release notes for words like “wake,” “sleep,” “audio capture,” or “microphone.”
3. Update, relaunch, and re-test after the next sleep cycle.

If an app has needed the relaunch ritual for months across updates, that is data too. We track reliability patterns across dictation tools — see our notes on whether Wispr Flow is reliable for how one vendor's track record looks over time.

Built-in Apple Dictation fails after sleep for related but distinct reasons — its speech daemon (corespeechd) can hang, its shortcut can conflict with third-party apps, and it stops on its own after 30 seconds of silence by design, per Apple's dictation documentation. Three resources:

• Dictation not working on Mac: 8 proven fixes — the full troubleshooting ladder for Apple's built-in dictation, including Voice Control conflicts and cache resets.
• Mac dictation keyboard shortcuts — for when the trigger key is what stopped responding.
• Apple's official troubleshooting page — the vendor checklist.

And if you use Dragon on a Mac, its microphone issues are their own category — covered in our guide to Dragon Dictate microphone problems.

The difference is architectural, and it comes down to when the app holds the microphone.

Apps with a persistent audio tap keep a capture pipeline open continuously so they can react the instant you speak. That pipeline is a standing bet that the audio stack underneath it never changes — and sleep/wake, Bluetooth handoffs, and device switches break that bet several times a day. These apps need wake-monitoring code (the kind Wispr Flow added) to detect the break and rebuild, and when that code misses a case, the app goes deaf.

Apps with per-dictation capture open the microphone when you press the hotkey and release it when you stop. Every dictation attaches to the audio stack as it exists right now, so there is no long-lived connection to go stale. There is nothing to recover because nothing persisted.

Voibe — the app we build — uses the per-dictation model: hold the key, speak, release, and the mic is only active during the dictation itself. That design choice was made for privacy (the microphone is verifiably off between dictations), but it buys wake-resilience for free: the stale-tap failure mode of the Wake Chain's third link doesn't exist. It runs as a lightweight native menu bar process, on-device on Apple Silicon, at $7.50/mo, $59/yr, or $149 lifetime. If you're doing the quit-and-relaunch ritual every morning, try Voibe for free and see whether the ritual just disappears.

Prevention beats the morning ritual. Four habits eliminate most recurrences:

• Pin the input device. Set your dictation app to a specific microphone — usually the built-in mic — instead of “auto” or “system default,” so Bluetooth handoffs can't hijack capture.
• Keep the app current. Wake-resilience fixes ship in point releases; check release notes for “sleep,” “wake,” and “audio capture.”
• Confirm the login item. The app should start with your Mac so every session begins with a fresh process, not yesterday's.
• Know your 10-second fix. Menu bar → Quit → relaunch. When everything else is fine, this is the reset that works.

And if the ritual keeps coming back regardless: the failure mode is architectural, so the durable fix is choosing an app whose architecture doesn't have it. That reasoning — reliability as a function of design, not luck — is the same reason we argue offline dictation matters beyond privacy alone.

Quick Fixes

What's the fastest fix when dictation stops working after sleep?

Fully quit the dictation app from its menu bar icon and relaunch it — about 10 seconds. A relaunch forces the app to attach to the rebuilt audio stack fresh. Wispr Flow's docs recommend exactly this for post-wake mic errors.

Is sudo killall coreaudiod safe to run?

Yes. macOS relaunches the Core Audio daemon automatically within a few seconds. Expect a brief audio dropout in every app — finish calls and recordings first. No settings or data are affected.

Do I need to restart the whole Mac?

Rarely. A full restart fixes wake-related dictation failures because it rebuilds everything, but it is the slow version of Fixes 1 and 3. Try the app relaunch and the Core Audio restart first; reboot only if both fail.

Root Causes

Why does my dictation app show it's listening but type nothing?

Because the interface and the audio pipeline are separate. The UI survived sleep; the microphone connection underneath it went stale when macOS rebuilt the audio device list. The app reads silence from a device reference that no longer maps to real hardware.

Why does it break specifically when my AirPods reconnect?

AirPods re-pair a few seconds after wake, and macOS often moves the system input to them automatically. Dictation apps pointed at “system default” follow the input to a headset that is still mid-handshake and delivering nothing. Pinning the app to the built-in microphone prevents the race.

Is my microphone hardware failing?

Almost certainly not. Hardware failures are consistent — the mic dies everywhere, all the time. A mic that works fine except after sleep is a software state problem. Test in Voice Memos after a restart to confirm the hardware baseline.

Specific Apps

Why does Wispr Flow say “Unable to access mic” after my Mac wakes?

Wispr Flow's troubleshooting docs state this error appears when the mic is slow to respond, “most often after your Mac wakes from sleep or is under heavy load.” Their fix order: click Restart App on the notification, quit and reopen from the menu bar, and keep the app updated for the automatic capture-recovery added in recent versions.

What about Superwhisper after sleep?

Superwhisper's troubleshooting guide has you verify audio capture by watching the waveform in the recording window — a flat line means no audio is arriving. The same relaunch, input-device, and Core Audio fixes in this guide apply; the guide's steps are app-agnostic.

Does Apple Dictation have the same problem?

Apple Dictation fails after sleep too, but through its own daemon (corespeechd) and settings rather than a third-party audio tap. Follow our dedicated Mac dictation troubleshooting guide for the Apple-specific ladder.

Wake-from-sleep dictation failures feel random, but the Wake Chain makes them legible: the audio hardware, Core Audio, and your app must reconnect in order, and the app's microphone tap is the link that snaps. Relaunch the app, verify the input device, restart Core Audio if the whole stack is wedged, and pin your microphone so Bluetooth can't steal it. Update the app because vendors genuinely fix these bugs — and if a tool needs the ritual every morning anyway, switch to one whose capture model starts fresh with every dictation.

Related reading: the complete Mac dictation fix list, what killall corespeechd actually does, and the best offline dictation apps for Mac.