How to uninstall Origami Studio on Mac
Before removing Origami Studio, save and copy your Origami prototypes, imported assets and recordings to a separate backup, then open the copy. This guide covers the official Mac download; Homebrew-specific removal is separate below.
Preserve prototype documents and the media they reference. The official documentation describes the desktop tool separately from the mobile Origami Live Viewer; uninstalling the Mac app does not remove that mobile app or prove your prototypes were backed up.
Quit and remove the app
Finish current work and quit Origami Studio. Check Activity Monitor for its process before removing the app in Finder. In Applications, move Origami Studio.app to the Trash; if you keep it elsewhere, use its actual location. Keep the Trash until your backup has been checked. Official documentation
Review local data
The locations below come from the test record or the live cask; their individual treatment is explained below. Open them through Finder’s Go › Go to Folder. Copy wanted contents first; leave them if you want to keep settings or cannot establish ownership. They are optional data removal, not a prerequisite for removing the app.
~/Library/Application Support/com.facebook.Origami-Studio
Check the result
This read-only check searches full process command lines, not disk contents.
pgrep -ifl 'Origami Studio'
No output with exit status 1 means no matching command line was found. A printed entry needs inspection in Activity Monitor because names can match unrelated processes. An error is not proof of removal. Also check that the app is absent from its original Finder location; a retained data folder or independent component does not mean the app is still installed.
If you installed it with Homebrew
Use the installed cask receipt and uninstall without zap.
brew uninstall --cask origami-studio
The command removes the cask’s managed application artifacts without running zap. The live cask additionally names these zap targets, which can erase settings, local data or integration files; this is Homebrew’s list, not a vendor data-location claim.
~/Library/Application Support/com.facebook.Origami-Studio~/Library/Caches/com.facebook.Origami-Studio~/Library/HTTPStorages/com.facebook.Origami-Studio~/Library/Logs/com.facebook.Origami-Studio~/Library/Preferences/com.facebook.Origami-Studio.plist~/Library/Saved Application State/com.facebook.Origami-Studio.savedState
A direct brew uninstall --cask --zap origami-studio runs its own zap scope without consulting Mole’s checkboxes. Mole uses zap only when the complete scope passes its gate; unchecked or shared paths, paths outside the review boundary, unknown stanzas and unsupported directives suppress it. Selected remnants still use Mole’s deletion path.
What Mole lists
~/Library/Application Support/com.facebook.Origami-Studio is selected by default when present and not protected, so inspect and back it up first. A QuickLook extension container needs its own permission and ownership checks; do not bypass a failure.
These defaults assume “Remove data and settings with apps” is off. Opting in also selects eligible reviewed app data; shared stores and protected data retain individual review or stay locked.
What this test covered
The September 21, 2026 record covers the following test. The app from the official DMG was launched and removed with its reviewed support files, preferences and caches. A QuickLook container remained after a permission failure. Prototype editing, sharing and project restoration were not tested.