Is It Safe to Delete Slack, Teams & Discord Cache on Mac? What Happens

If your Mac's storage meter is creeping into the red, communication apps are a surprisingly large culprit. Whether it is safe to delete Slack cache on Mac is a question that comes up constantly — and the short answer is yes, for the most part, though there are a few folders inside each app's data footprint that you should handle more carefully. This guide covers Slack, Microsoft Teams, and Discord: where each app stores its cache on macOS Sequoia and Tahoe (Apple Silicon and Intel), what happens when you delete it, and the step-by-step process to do it safely.

Why Communication Apps Accumulate So Much Cache

Slack, Teams, and Discord are all built on the Electron framework, which means each app bundles a full Chromium browser engine. That engine caches images, JavaScript modules, fonts, and media files the same way a web browser does — aggressively and continuously. On top of the standard browser cache, these apps also store:

• Message and channel avatars
• Inline image and video previews
• Emoji packs and custom emoji assets
• Workspace icons and theme assets
• GPU shader caches
• IndexedDB and LevelDB databases (message history stored locally)

The combination can grow to several gigabytes on a machine used daily across multiple workspaces or servers. Understanding which of those folders is safe to delete — and which ones hold data you actually care about — is the key to reclaiming space without breaking anything.

Where Slack, Teams, and Discord Store Cache on macOS

All three apps store their data under ~/Library/Application Support/ and ~/Library/Caches/. Here is a breakdown of the most important paths:

The ~/Library/Caches/ subfolders are the pure cache — reconstructed automatically by the app on next launch. The ~/Library/Application Support/ folders are more nuanced: they contain both recoverable caches and non-recoverable local databases.

What Is Actually Safe to Delete

Inside each app's Application Support directory there are subfolders with names that reflect their Chromium heritage. The folders below are purely derived data and can be deleted without losing messages, preferences, or login state:

Slack

• ~/Library/Application Support/Slack/Cache/ — HTTP cache (images, JS)
• ~/Library/Application Support/Slack/Code Cache/ — V8 JavaScript bytecode cache
• ~/Library/Application Support/Slack/GPUCache/ — GPU shader cache
• ~/Library/Caches/com.tinyspeck.slackmacgap/ — top-level app cache

Microsoft Teams

• ~/Library/Application Support/Microsoft Teams/Cache/
• ~/Library/Application Support/Microsoft Teams/Code Cache/
• ~/Library/Application Support/Microsoft Teams/GPUCache/
• ~/Library/Caches/com.microsoft.teams2/

Discord

• ~/Library/Application Support/discord/Cache/
• ~/Library/Application Support/discord/Code Cache/
• ~/Library/Application Support/discord/GPUCache/
• ~/Library/Caches/com.hnc.Discord/

To understand the broader picture of what macOS counts as "cached" storage versus system data, the article on what cache files are on a Mac is a useful companion read.

What You Should NOT Delete

Inside the Application Support folder for each app, several subdirectories store data that is not automatically regenerated:

• IndexedDB/ and LevelDB/ — local message databases. Deleting these means the app has to re-sync all message history from the server. On large workspaces this can take several minutes and may fail if your plan does not retain full history.
• Local Storage/ — stores user preferences, notification settings, and sidebar state.
• Cookies — your login session tokens. Delete this and you will be signed out of every workspace or server.
• databases/ — WebSQL databases used by older Electron versions of Slack and Discord; contains workspace metadata.

As a rule: delete only folders whose names contain "Cache". Leave everything else unless you are doing a full uninstall.

What Happens When You Delete the Cache

When you trash the cache folders and reopen the app, here is what actually occurs:

1. The app launches normally — no crash, no data loss.
2. Images, avatars, and emoji take a moment to reload as the app re-fetches them from CDN servers.
3. The first few minutes may feel slightly slower as the JavaScript bytecode is recompiled and the GPU shader cache is rebuilt.
4. After a few minutes of use, the cache folders start growing again — this is expected and healthy behavior.

You will not lose messages, contacts, workspace memberships, server memberships, pinned items, notification preferences, or custom themes. Those live in the databases and Local Storage folders, which you left untouched.

How to Safely Clear Communication App Cache on Mac (Step-by-Step)

1. Quit the app completely. Use Cmd+Q or right-click the Dock icon and choose Quit. Do not just close the window — Electron apps continue running in the background.
2. Open Finder and navigate to the cache. In Finder, press Cmd+Shift+G to open Go to Folder, then type the path — for example ~/Library/Application Support/Slack/ for Slack.
3. Identify the safe subfolders. Look for folders named Cache, Code Cache, and GPUCache. Do not touch anything else at this step.
4. Move them to Trash. Select each cache folder and press Cmd+Delete. Do not empty the Trash yet.
5. Repeat for ~/Library/Caches/. Navigate there and delete the app-specific subfolder (e.g., com.tinyspeck.slackmacgap).
6. Relaunch the app and verify it works normally. Sign-in should be preserved, messages should appear, and your workspaces should load. Once confirmed, empty the Trash.

If you prefer a terminal approach, the equivalent commands (run with the app closed) look like this for Slack:

rm -rf ~/Library/Application\ Support/Slack/Cache
rm -rf ~/Library/Application\ Support/Slack/Code\ Cache
rm -rf ~/Library/Application\ Support/Slack/GPUCache
rm -rf ~/Library/Caches/com.tinyspeck.slackmacgap

Substitute the appropriate paths for Teams and Discord.

How Much Space Can You Realistically Recover

Results vary considerably based on how long you have been using each app, how many workspaces or servers you belong to, and whether you exchange a lot of media files in chat. A developer who has been using Slack for two or three years across five workspaces can easily see 2–3 GB in cache alone. Discord users who belong to large gaming or community servers with heavy image and video traffic sometimes accumulate over 1 GB in the Cache folder within a few months.

If you want a broader picture of what else is eating into your Mac's storage, the guide on what is taking up space on your Mac walks through the full storage breakdown macOS provides and what each category means. A tool like Crumb can audit all of these app cache folders at once and show what is safe before you delete, which is helpful when you have five or six Electron apps accumulating cache simultaneously.

Frequently Asked Questions

Does clearing the cache affect Slack's performance long-term?

No. Cache deletion gives a temporary fresh start — the first launch is slightly slower while assets re-download, but day-to-day performance returns to normal within minutes. Keeping an oversized cache does not improve performance; most Electron apps re-validate cached assets anyway.

Will Teams lose my meeting recordings if I delete its cache?

Meeting recordings are stored in the cloud (OneDrive or SharePoint, depending on your org's settings), not in local cache folders. Deleting the Teams cache on your Mac has no effect on recording availability.

Can I automate this cleanup on a schedule?

Yes, using a launchd plist or a periodic maintenance script. However, make sure the script only runs when the app is not open, since deleting cache files while Electron is running can occasionally cause the app to write corrupted replacement files. The safest approach is to run the cleanup at login before the app launches, or at shutdown.