How to uninstall TradingView on Mac

TradingView Desktop is the Electron app for TradingView's charts, from tradingview.com/desktop. Your account, subscription, chart layouts and alerts belong to tradingview.com, and the test never signed in, so what the app keeps locally after sign-in was not checked. What the test did see is small: preferences, Electron caches and a 2 MB Application Support folder. One thing outside those folders matters if you connected a broker: TradingView's help article says the saved broker login is a "TradingView Desktop" record in Keychain Access, under Local Items, which you delete yourself. Uninstalling does not cancel a subscription or close a broker connection. This guide covers the disk image from tradingview.com and the Homebrew cask tradingview.

Quit and remove the app

1. Disconnect any broker inside the app if you connected one, and note what you want from the account side, such as exported data, because the app itself is not where it lives.
2. Quit TradingView with Command + Q. In the test it ran as 12 processes (the app, Electron helpers and a crash handler) and registered no login item or launch agent. Mole had to force it to quit during the uninstall, so give it a few seconds, and open Activity Monitor if it does not go.
3. Open Finder, go to Applications and drag TradingView.app to the Trash.
4. If you connected a broker, open Keychain Access, find the "TradingView Desktop" record under Local Items and delete it.

Where the data lives

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

Check the result

pgrep -il tradingview
ls -d /Applications/TradingView.app ~/Library/Application\ Support/TradingView ~/Library/Preferences/com.tradingview.tradingviewapp.desktop.plist

• No output from pgrep means TradingView and its helpers are not running. A printed line is a process still alive; quit it and run the command again.
• For ls -d, "No such file or directory" means that path is gone. A printed path is still on disk.

If you installed it with Homebrew

brew uninstall --cask tradingview

The cask only quits the app on an ordinary uninstall, so this removes the app and nothing else. brew uninstall --cask --zap tradingview also trashes ~/Library/Application Support/TradingView, the preferences file, the saved window state and the app's recent-documents entry. A direct brew command does not read Mole's checkboxes. Mole adds --zap only when its whole removal scope passes its zap gate (unchecked or shared paths, paths outside the reviewed boundary, unknown stanzas and unsupported directives suppress it), and otherwise removes the rows you selected itself. The Homebrew install was not tested.

What Mole lists

Mole selects the app, the preferences file, the eight Electron cache and log folders inside ~/Library/Application Support/TradingView and the two temporary cache rows. It lists ~/Library/Application Support/TradingView for review and selects it by default when eligible. Before removing, Mole asks TradingView to quit, then forces it if it stays open.

What this test covered

On November 9, 2026, the test downloaded TradingView Desktop 3.5.0 as a universal disk image from TradingView's package server, whose checksum matched the Homebrew cask, copied the app to Applications without running brew install, launched it once and quit it. A source-built Mole with the review rows ticked asked it to quit, forced it to quit when it stayed open, and moved the app and 12 rows to the Trash; no row failed. Mole's rescan found nothing left; a file listing afterwards still showed the app's recent-documents file, which Mole's scan could not read because the test build ran without Full Disk Access. Status showed one TradingView row with 12 processes. Mole detected an Electron updater, and no update was run. No account was signed in and no broker connected, so the Keychain record, chart layouts and alerts were not tested, nor were the Homebrew install and Mole's notarized release build.