Why is Slack using so much CPU and memory on my Mac?
Last reviewed: 19 November 2026.
Slack's desktop app is an Electron app: it wraps Slack's web app in a copy of Chromium, so it runs a main process plus Slack Helper processes for pages, graphics and services. Memory grows with the number of workspaces you are signed in to and the channels you have open, and CPU rises during huddles with video, noise suppression or screen sharing. Turning off video in large huddles and using Help > Troubleshooting > Clear Cache and Restart are Slack's own suggestions.
What are the Slack processes in Activity Monitor?
Slack's engineering team describes the desktop app as an Electron container around Slack's web app. On a Mac you see the Slack app plus several helpers: Slack Helper (Renderer) runs the Slack interface itself, a GPU helper draws it, and other Slack Helper rows handle networking and audio.
Older versions ran a separate process for each workspace. Slack later rebuilt the app so that signed-in workspaces share processes, which reduced memory for people in several workspaces, but each workspace still keeps its own data loaded.
Why does Slack use CPU when you are not typing?
Slack keeps a live connection to its servers and updates channels, unread counts and presence in real time. Busy channels with frequent messages, animated GIFs and emoji, and link previews make the renderer redraw often.
Huddles add audio and video processing. Slack's help says lag in huddles with many participants may be due to high CPU usage, and that turning off your video or noise suppression may help.
How do you reduce Slack's CPU and memory use?
- Turn off video or noise suppression in big huddles. During a huddle with many people, switch your camera off and turn off noise suppression; both use CPU continuously.
- Clear the cache. Click Help in the menu bar, choose Troubleshooting, then Clear Cache and Restart. Slack restarts with a fresh local cache.
- Sign out of workspaces you no longer use. Each signed-in workspace keeps its channels and messages loaded. Removing ones you do not need reduces memory.
- Quit Slack when you do not need it. Slack runs until you quit it with Command-Q. Closing the window leaves its processes running so notifications keep arriving.
When is Slack's CPU or memory use a problem?
A Slack Helper (Renderer) row that stays high with no huddle running and Slack in the background is not typical. Try Clear Cache and Restart first. If huddle audio or video breaks up, Slack's own troubleshooting covers the network side (wired connection, distance to the router) as well as CPU load.
How can Thrum help with Slack?
Thrum's Memory tab shows memory pressure, swap, and the eight processes using the most memory, so you can see how much Slack holds and whether the Mac is short of memory. An optional alert tells you when memory pressure turns critical. Click Slack in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions
Is Slack an Electron app?
Yes. Slack's engineering team describes its desktop app as an Electron container around the Slack web app, which is why its helper processes look like a browser's.
Does closing the Slack window quit Slack?
No. Slack keeps running in the background to deliver notifications. Choose Slack > Quit Slack or press Command-Q to quit it.