How to uninstall Blip on Mac

Blip is a file transfer app from Blip Studio, from blip.net, that sends files and folders directly to another device with no size limit. Its site says transfers resume after interruptions and that files are sent straight to the recipient rather than uploaded to cloud storage, so there is no copy of your files on Blip's side to clean up. Finish or cancel any transfer in progress first: quitting pauses it, and removing the app means it never resumes. Files you received are wherever you saved them and are not touched by anything below. This guide covers the direct download (a zip) and the Homebrew cask blip; an App Store build, if you have one, keeps its files elsewhere and is not covered.

Quit and remove the app

1. Quit Blip from its menu bar icon, since it runs without a Dock icon. In the test, Status grouped two processes under one row.
2. Blip can add itself to your login items. In the test it did so at first launch, and Mole removed that login item during the uninstall; if you remove Blip by hand, also remove it in System Settings › General › Login Items & Extensions. No launch agent appeared.
3. Open Finder, go to Applications and drag Blip to the Trash.

Blip ships a Share extension and a preview extension inside the app. Each one gets its own container, which is why the table below has more rows than a typical app.

Where the data lives

Press Shift + Command + G in Finder to open each path. Skip any path that is not on your Mac.

If macOS refuses to move a container or the group folder with a permission error, it is protecting that data. Quit Blip first, then either grant Mole Full Disk Access in System Settings › Privacy & Security › Full Disk Access and let it try again, or move the folder to the Trash in Finder yourself. Moving the group folder may also bring up a prompt about access to data from other apps; allow it.

Check the result

pgrep -il blip
launchctl list | grep -i blip
ls -d /Applications/Blip.app ~/Library/Containers/net.blip.macos.* ~/Library/Application\ Scripts/net.blip.macos.* ~/Library/Application\ Scripts/AY8UB8KTUX.blip ~/Library/Group\ Containers/AY8UB8KTUX.blip

• No output from pgrep means Blip is not running. A printed line is a process still alive; quit it, or restart the Mac once.
• No output from launchctl means no Blip job is loaded for your user. A line naming net.blip.macos means Blip, or its login helper, is still registered; check Login Items & Extensions.
• For ls -d, "No such file or directory" means that path is gone. A printed path is still on disk; the two containers and the group folder are the ones that can survive.

If you installed it with Homebrew

brew uninstall --cask blip

The cask quits Blip on an ordinary uninstall and removes the app only. Its zap list names the three Application Scripts folders, the two extension containers, ~/Library/Group Containers/AY8UB8KTUX.blip, the cache, the network storage, the preferences file and the recent-documents list for Blip. Running brew uninstall --cask --zap blip yourself deletes all of it and does not read Mole's checkboxes. Mole adds --zap only when its whole removal scope passes its zap gate; while the group folder exists, the list reaches a path Mole does not list, so Mole keeps --zap off and removes the rows you selected itself. The Homebrew install was not tested.

Account

Removing the app does not delete a Blip account you signed in to. Signing in was not tested; for account questions contact Blip through blip.net.

What Mole lists

Mole selects the app, the preferences file, both caches, the network storage, the temporary cache row, both extension containers and, when they exist, the extensions' Application Scripts folders. It lists ~/Library/Application Scripts/AY8UB8KTUX.blip for review and selects it by default. Before removing, Mole asks Blip to quit and removes its login item. Mole does not list ~/Library/Group Containers/AY8UB8KTUX.blip, so it stays until you remove it. With Full Disk Access Mole can move the containers; without it, Mole's report names Full Disk Access and offers a retry.

What this test covered

On November 9, 2026, the test downloaded Blip 1.2.8 (a Universal zip) from Blip's download host, whose checksum matched the Homebrew cask, copied the app to Applications without running brew install and opened it once. It then quit the app and removed it with a source-built Mole with every review row ticked, and repeated the run after a fix. In the repeat, Mole moved the app and six rows to the Trash and removed the login item Blip had added at first launch. The two extension containers stayed because the test build ran without Full Disk Access and macOS refused the move. The group folder stayed because Mole does not list it. Status showed one Blip row with 2 processes. Mole detected a Sparkle update feed, and no update was run. Sending or receiving a file, signing in, the Share and preview extensions in use, a Homebrew-managed uninstall and Mole's notarized release build were not tested.