How to uninstall Wispr Flow on Mac
Wispr Flow keeps your dictation history, meeting notes, recordings and transcripts, settings and signed-in session locally, and its own removal guide warns that deleting Flow's data folders can permanently remove local transcripts and other unsynced content. Save anything you need before going beyond removing the app. This covers the official Mac download from wisprflow.ai, plus a Homebrew section for the wispr-flow cask.
Quit Flow and remove it
These steps follow Wispr Flow's removal guide.
- Quit Flow from its menu bar icon and let it finish closing.
- Open Activity Monitor, search for Wispr Flow, and end any process still running, including Wispr Flow Helper.
- In Finder's Applications folder, move Wispr Flow to the Trash.
- Open System Settings, then General, then Login Items, and remove any Wispr Flow entry.
- If you no longer want Flow to keep its permissions, open System Settings, then Privacy & Security, and remove the entries for Wispr Flow and its helper under Accessibility, Microphone, Screen Recording and Full Disk Access.
Where Wispr Flow keeps its data
Press Shift + Command + G in Finder and open each path that exists. These are the paths the Homebrew cask lists for Wispr Flow.
| Location | What it holds | What to do |
|---|---|---|
~/Library/Application Support/Wispr Flow |
Local dictation history, meetings, recordings and transcripts, settings and your signed-in session | Copy out what you need first; the vendor warns deletion can be permanent |
~/Library/Logs/Wispr Flow |
App logs | Safe to remove |
~/Library/Caches/com.electron.wispr-flow |
App cache | Safe to remove |
~/Library/Caches/com.electron.wispr-flow.accessibility-mac-app and ~/Library/Caches/com.electron.wispr-flow.ShipIt |
Caches for Flow's accessibility component and its updater | Safe to remove |
~/Library/Caches/SentryCrash/Wispr Flow |
Crash reports | Safe to remove |
~/Library/HTTPStorages/com.electron.wispr-flow |
Web storage | Remove with the app |
~/Library/Preferences/com.electron.wispr-flow.plist |
App preferences | Remove with the app |
Check the result
pgrep -il wispr
mdfind "kMDItemCFBundleIdentifier == 'com.electron.wispr-flow'"
ls -d ~/Library/Application\ Support/Wispr\ Flow
No output from pgrep means no Wispr Flow process is running; a listed process means one is still open, so end it in Activity Monitor. No output from mdfind means Spotlight finds no remaining copy of the app. For ls, "No such file or directory" means that folder, and the local history inside it, are gone; the path printed back means it is still there, which is expected if you left that row unticked.
If you installed it with Homebrew
The wispr-flow cask's zap list covers every path in the table plus Flow's Recent Documents record. Running brew uninstall --cask --zap wispr-flow yourself moves all of them to the Trash, dictation history included, whatever you selected in Mole. To remove only the app:
brew uninstall --cask wispr-flow
Mole runs --zap only when every path in the stanza is under ~/Library, is a row you ticked, is not claimed by another installed app, and uses directives it can review. Leave the Application Support folder unticked and Mole drops --zap, while still removing the rows you ticked.
What Mole lists
Mole selects by default the logs folder and crash report folder named after the app, and the cache, web storage and preferences named after Flow's bundle ID. ~/Library/Application Support/Wispr Flow, which holds your dictation history and settings, is listed for review and is not selected by default.
What this test covered
On September 22, 2026, Wispr Flow 1.6.897 from the official Mac download was copied into Applications and removed with Quit and Remove, using a development build of Mole. Status showed one Wispr Flow row while it ran. The 600 MB app and its Application Support folder went to the Trash. Before the removal, the only startup entries were the temporary ones macOS creates for a running app, and no new user LaunchAgent appeared. Mole found a Squirrel updater but no readable update feed for Flow. Signing in and dictation were not tested.
