🔧🎙️
Wispr Flow Not Working on Mac
Most common: Update the app first
No recording: Mic permission
Connection lost: VPN / network
After sleep: Wait 5-10 seconds
TL;DR: Most Wispr Flow problems on Mac fall into four buckets: it won't launch or crashes (update to the latest version first, then force-quit and relaunch), it isn't recording your voice (grant Microphone permission in System Settings), it shows "connection lost" (a VPN or security tool is blocking it, or your network dropped), or it's sluggish after your Mac woke from sleep (wait 5–10 seconds for it to recover). Several of these — connection lost, network errors, post-sleep lag — trace back to one root cause: Wispr Flow is cloud-dependent, so it fails when the network does. The fixes below come from Wispr Flow's official help center. Disclosure: I build a competing on-device app (MetaWhisp); I've kept the fixes accurate and flagged where the cloud architecture is the underlying issue.
Troubleshooting flowchart for Wispr Flow not working on Mac showing four branches crashes no recording connection lost and sluggish after sleep with fixes

Why Is Wispr Flow Not Working on My Mac?

Wispr Flow failures on Mac cluster into a few categories, and knowing which one you're hitting points to the fix: A useful thing to notice up front: Wispr Flow is a cloud app — it uploads your audio to its servers for transcription. That means a whole class of its failures ("connection lost," network errors, post-sleep reconnection lag) come from the network layer, not from anything you did wrong. The official fixes below address each category, sourced from Wispr Flow's troubleshooting help center.
The single most useful diagnostic question for Wispr Flow problems is "does this involve the network?" Because Wispr Flow processes audio in the cloud, it depends on a working connection to its servers for every dictation. When you see "connection lost," when it lags after your laptop wakes, when a corporate VPN silently blocks it — those aren't bugs in the traditional sense, they're consequences of the cloud architecture. Roughly half of the official troubleshooting steps exist to manage that network dependency. The other half (mic permission, app updates, force-quit) are standard for any Mac app. Understanding which category your problem falls into saves time: network-class issues are fixed by changing your connection or VPN, app-class issues by updating or restarting. If network-class failures keep recurring, that's the architecture telling you something an on-device tool wouldn't.

Fix 1: Update Wispr Flow to the Latest Version

Several crash and launch bugs were fixed in recent Wispr Flow releases, so this is the first thing to try. An outdated version is the most common cause of crashes-on-launch.
  1. Open Wispr Flow
  2. Check Settings for an update prompt, or download the latest version from wisprflow.ai
  3. Install the update and relaunch the app
  4. Test dictation
If the app won't open at all to check for updates, download the latest installer directly from Wispr's site and install over the existing version.

Fix 2: Force Quit and Relaunch

If Wispr Flow is frozen or unresponsive, force-quit all its processes and relaunch. Per Wispr's official guidance (help center):
  1. Press Command + Space to open Spotlight
  2. Type "Activity Monitor" and press Return
  3. In the search bar (top right), type "Wispr"
  4. Select each process with "Wispr" in the name
  5. Click the X (stop) button in the toolbar, then Force Quit
  6. Relaunch Wispr Flow
This clears any stuck state. It's the dictation-app equivalent of "turn it off and on again," and it resolves a surprising share of temporary glitches.

Fix 3: Grant Microphone Permission

If Wispr Flow launches but isn't capturing your voice, it almost certainly lacks Microphone permission. Per Wispr's "why isn't Flow recording my voice" guide:
  1. Open System Settings
  2. Go to Privacy & Security → Microphone
  3. Confirm microphone access is on and Wispr Flow is in the allowed list, toggled on
  4. If it was already on, toggle it off and back on, then relaunch Wispr Flow
  5. Test dictation
macOS updates sometimes reset privacy permissions, so this is worth checking after any system update even if it worked before.
Microphone and Accessibility permissions resetting after macOS updates is the single most common "it stopped working for no reason" cause across every Mac dictation app, not just Wispr Flow. Apple's update process occasionally re-applies privacy defaults, which silently revokes app permissions. The symptom is confusing because the app looks installed and signed-in but simply produces nothing — no error, no prompt. The fix is always the same: re-check System Settings → Privacy & Security for both Microphone and Accessibility after any macOS update. A useful habit is to toggle the permission off and back on rather than just confirming it's on, because the underlying grant can be in a stale state that the toggle refreshes. This applies to Wispr Flow, MetaWhisp, MacWhisper, and Apple's own Dictation equally.

Fix 4: Reset and Restart the App

Wispr Flow has a built-in reset that clears local app data without uninstalling. Per their reset guide:
  1. Click the Settings icon in Wispr Flow
  2. Select System → Data
  3. Click "Reset & restart"
  4. Confirm by clicking "Reset & restart" again in the dialog
This is more thorough than a force-quit — it clears local state that may have become corrupted. Use it when force-quit and relaunch didn't fix the problem.
Five step fix sequence for Wispr Flow on Mac update app force quit microphone permission reset restart and check VPN network

Fix 5: Check for "Connection Lost" — VPN and Security Tools

If you see "connection lost" or network errors, a VPN, firewall, or security tool is likely blocking Wispr Flow's connection to its servers. Per Wispr's VPN/security troubleshooting: This category of failure is unavoidable with a cloud dictation app — if Wispr can't reach its servers, it can't transcribe. There's no offline fallback. This is the clearest case where the cloud architecture directly causes the problem.
Diagram showing why Wispr Flow connection lost error happens when VPN firewall or network blocks the cloud server versus on-device dictation that needs no connection
The difference between a force-quit (Fix 2) and a Reset & Restart (Fix 4) is worth understanding so you don't waste time. A force-quit just kills the running processes and starts fresh — it fixes temporary stuck states, frozen UI, and most "it's not responding" moments. It changes nothing on disk. The Reset & Restart goes further: it clears Wispr Flow's local app data, which fixes problems caused by corrupted settings, a bad cache, or a broken local state that survives a normal restart. The rule of thumb: try force-quit first because it's faster and loses nothing; escalate to Reset & Restart only if force-quit didn't help and the problem feels persistent rather than momentary. A full reinstall (Fix 9) is the last step, for when even the in-app reset doesn't clear the corrupted state.

Fix 6: Wait After Waking from Sleep

If Wispr Flow is sluggish or unresponsive right after your Mac wakes from sleep, it's reconnecting to its servers. Per Wispr's guidance, wait 5–10 seconds — it often recovers automatically. If it doesn't recover after 10 seconds, force-quit and relaunch (Fix 2). This post-sleep lag is another symptom of cloud dependency: the app has to re-establish its server connection after the network stack wakes up. On-device tools don't have this delay because there's no connection to re-establish.

Fix 7: App Won't Start After Sign-In

If you sign in, click "Open Wispr Flow," and nothing happens, there's a specific fix in Wispr's startup troubleshooting:
  1. Force-quit any Wispr processes (Fix 2)
  2. Relaunch the app directly from your Applications folder, not from the browser sign-in link
  3. If it still won't start, reinstall the latest version
This edge case usually comes from the browser-to-app handoff failing; launching directly from Applications bypasses it.

Fix 8: Check Accessibility Permission

Wispr Flow needs Accessibility permission to insert text into other apps. If dictation transcribes but text doesn't appear where you're typing:
  1. Open System Settings → Privacy & Security → Accessibility
  2. Confirm Wispr Flow is listed and toggled on
  3. Toggle off and on if it was already enabled, then relaunch
Like Microphone permission, this can reset after macOS updates.

Fix 9: Reinstall as a Last Resort

If nothing above works, do a clean reinstall:
  1. Quit Wispr Flow and force-quit any processes (Fix 2)
  2. Move Wispr Flow from Applications to Trash
  3. Download the latest version from wisprflow.ai
  4. Install fresh and sign in again
  5. Re-grant Microphone and Accessibility permissions
A clean reinstall clears any corrupted state that the in-app reset didn't catch.
If you find yourself running through this fix list repeatedly, the pattern matters more than any single fix. Occasional glitches are normal for any app. But recurring "connection lost" errors, frequent post-sleep lag, or dictation that works inconsistently depending on your network are signals of the cloud dependency rather than a fixable bug. No amount of force-quitting changes the fact that the app needs a live server connection for every dictation. For users who hit these network-class failures often — people who travel, work on unreliable WiFi, or sit behind strict corporate firewalls — the durable fix isn't another troubleshooting step; it's a dictation tool that doesn't depend on the network at all. On-device Whisper apps transcribe locally, so "connection lost" simply can't happen.

When the Real Fix Is a Different Architecture

Several of the fixes above — VPN exceptions, network switching, post-sleep waiting — exist only because Wispr Flow processes audio in the cloud. If your Wispr Flow problems are network-class and recurring, the underlying issue isn't something you can troubleshoot away. On-device dictation tools work differently. Apps like MetaWhisp, MacWhisper, and Apple's built-in Dictation run the speech model locally on your Mac. That eliminates an entire category of failures: You still get standard app issues (permissions, the occasional restart), but the network-dependent failures simply don't apply. For anyone whose Wispr Flow frustration is mostly network-related, switching to an on-device tool is less a "fix" and more a way to make those problems structurally impossible. MetaWhisp is free and open-source if you want to try the on-device approach.
Comparison of cloud dictation failure modes like connection lost and VPN conflicts versus on-device dictation that works offline with no network failures on Mac

Frequently Asked Questions

❓

Why isn't Wispr Flow recording my voice on Mac?

Almost always a Microphone permission issue. Open System Settings → Privacy & Security → Microphone, confirm Wispr Flow is allowed and toggled on. If it was already on, toggle it off and back on, then relaunch. macOS updates sometimes reset this permission, so check it even if dictation worked before.

❓

Why does Wispr Flow say "connection lost"?

A VPN, firewall, or security tool is blocking Wispr Flow's connection to its servers, or your network dropped. Wispr Flow is cloud-based, so it needs a live server connection to transcribe. Temporarily disable your VPN to test; if that fixes it, add Wispr Flow as an exception. On-device dictation tools don't have this error because they don't use the network.

❓

Why does Wispr Flow keep crashing on Mac?

Most often an outdated version — several crash bugs were fixed in recent releases, so update first. If it still crashes, force-quit all Wispr processes via Activity Monitor and relaunch, then try the in-app Reset & Restart (Settings → System → Data). A clean reinstall is the last resort for persistent crashes.

❓

Why is Wispr Flow slow after my Mac wakes from sleep?

Wispr Flow reconnects to its servers after your Mac wakes, which causes brief lag. Wait 5–10 seconds and it usually recovers automatically. If it doesn't recover after 10 seconds, force-quit and relaunch. This post-sleep delay is a cloud-dependency symptom — on-device dictation tools have no connection to re-establish, so they don't lag after sleep.

❓

Wispr Flow transcribes but text doesn't appear — why?

Wispr Flow needs Accessibility permission to insert text into other apps. Open System Settings → Privacy & Security → Accessibility, confirm Wispr Flow is listed and toggled on. Toggle off and on if it was already enabled, then relaunch. This permission, like Microphone, can reset after macOS updates.

❓

How do I stop Wispr Flow problems from recurring?

If your problems are network-class (connection lost, post-sleep lag, VPN conflicts), they recur because Wispr Flow depends on a live server connection. No troubleshooting step changes that. For travelers, weak-WiFi users, or those behind strict firewalls, the durable fix is an on-device dictation tool (MetaWhisp, MacWhisper, Apple Dictation) that transcribes locally — eliminating network-class failures entirely.

About the Author

Andrew Dyuzhov is the solo founder and CEO of MetaWhisp, a free, open-source, on-device voice-to-text app for macOS that runs Whisper large-v3-turbo locally via WhisperKit. He builds a competing on-device tool, which is why this guide leads with that disclosure, sources every fix from Wispr Flow's own help center, and flags where the cloud architecture — not a fixable bug — is the underlying issue. Connect on X or GitHub.

Related Reading