Slack, Discord, and Teams sit at the top of Task Manager‘s Memory column, and your Windows 11 PC slows to a crawl whenever all three are open. Many popular chat and collaboration apps like these are built with Electron, a framework that bundles its own copy of the Chromium browser engine and Node.js, so the fixes below start with finding the worst offender and then cut its memory use with tools already built into Windows.
Why Electron Apps Use So Much RAM on Windows 11
Electron is a framework that lets developers build desktop programs with web technology. Slack, Discord, Microsoft Teams, Visual Studio Code, and WhatsApp Desktop are commonly cited as Electron-based apps, though the exact framework and version behind any single app can change release to release.
The catch is that every Electron app bundles its own Chromium engine and Node.js runtime. Run four Electron apps and you’re running four private web browsers side by side.
That’s also why one app shows up as many processes in Task Manager. Chromium splits its work into separate pieces, such as a main process, a process for each window, and a GPU process. If one piece crashes, the others keep going. The tradeoff is memory.
Each app also ships its own Electron version. The framework’s latest release is Electron 45, released October 21, 2026, with Chromium 156.0.8078.48 and Node 24.22.0 (Electron blog). Individual apps often lag behind, so check an app’s own changelog before assuming which version it runs.
Before You Begin
- A PC running Windows 11 (most fixes work across supported builds, though Efficiency mode requires version 22H2 or later)
- The Electron apps you want to rein in (Slack, Discord, Teams, and so on) installed and signed in
- Any unsaved messages or drafts sent or saved, since several fixes close the app
- Microsoft Edge or Google Chrome, if you plan to try the web or PWA version in Fix #7
You don’t need admin rights for most of these steps. You don’t need any third-party “RAM cleaner” either.
Quick Reference
| Scenario | Recommended Fix | Lasting or Temporary |
|---|---|---|
| You don’t know which app is the problem | Fix #1: Sort Task Manager by Memory | Diagnosis only |
| Memory stays high after closing a window | Fix #2: Quit from the system tray | Temporary (until next launch) |
| The app is running every time you sign in | Fix #3: Disable startup launch | Lasting |
| You need the app open but want less drag | Fix #4: Turn on Efficiency mode | Temporary (per running process) |
| The app runs in the background all day | Fix #5: Limit background permissions | Lasting (where available) |
| The app’s GPU process is a heavy hitter | Fix #6: Turn off hardware acceleration | Lasting, but test it |
| You only use the app occasionally | Fix #7: Switch to the web or PWA version | Lasting |
Fix #1: Find the Real Memory Hogs in Task Manager
Don’t change any settings until you know which app is actually the problem. This takes about a minute.
- Press
Ctrl + Shift + Esc. Task Manager opens. - Select Processes in the left-hand menu.
- Click the Memory column header. The heaviest apps move to the top of the list.
- Click the arrow next to an app like Slack or Discord to expand it. You’ll see every helper process that belongs to that app.
- For a per-executable view, select Details in the left menu and click its memory column header. Multiple entries with the same name (for example, several
slack.exeorDiscord.exerows) all belong to one app.
Expected result: You now have a short list of the two or three apps using the most RAM. Those are the apps to target in the fixes below.
Is it safe to click End task on one of these processes? It won’t harm Windows, but ending a single helper process can crash or blank out the app’s window. You’ll also lose anything unsaved. Quitting the app properly (Fix #2) is cleaner. Never end processes you don’t recognize as belonging to the app.
Fix #2: Quit Apps Fully From the System Tray
Clicking the X on Discord, Slack, or Teams often just hides the window. The app keeps running in the background, and its memory stays in use.
- Click the Show hidden icons arrow (
^) on the taskbar, next to the clock. - Right-click the app’s icon.
- Choose Quit or Exit. The exact label varies by app.
- Press
Ctrl + Shift + Escand check the Processes list again. The app’s entry should be gone.
Expected result: The app’s processes disappear from Task Manager, and the memory they held is released.
This fix lasts only until the app opens again. If you want the X button to really quit, look in the app’s own settings for an option about closing or minimizing to the tray. Not every app offers one, and the wording differs between apps.
Fix #3: Stop Electron Apps From Launching at Startup
An app that relaunches itself after a reboot is usually registered as a startup app. Turning that off is one of the most reliable fixes here, because the app never loads unless you open it.
- In Task Manager, select Startup apps in the left-hand menu.
- Find the Electron app in the list.
- Right-click it and choose Disable. The Status column changes to Disabled.
You can do the same thing from Settings:
- Open Settings > Apps > Startup.
- Turn off the toggle next to the app.
Expected result: After your next restart, the app doesn’t appear in Task Manager until you open it yourself. Disabling startup doesn’t uninstall anything.
Some apps also have their own “open on login” or “launch at startup” switch. If the app keeps coming back, turn that off inside the app as well.
Fix #4: Turn On Efficiency Mode for Apps You Keep Open
Efficiency mode lowers a process’s priority and applies Microsoft’s EcoQoS behavior. It arrived in Task Manager with Windows 11 version 22H2. Be clear about what it targets. It reins in CPU and power use, so the RAM figure may not drop much. What you get is less slowdown from an app you need to keep open.
- In Task Manager, select Processes.
- Expand the app’s group and right-click its main process.
- Choose Efficiency mode.
- If Windows asks you to confirm, select Turn on Efficiency mode.
- Look for the leaf icon in the Status column. That confirms Efficiency mode is active.
Is it safe? Yes, for apps you install yourself. The worst case is an app that feels sluggish while it’s throttled. Switch it off the same way if that happens. It applies to the running process, so check again after you relaunch the app.
If the option is greyed out, the process is protected or Windows doesn’t allow priority changes for it. Try the app’s main process instead of a helper, or fall back on Fixes #3 and #5.
Fix #5: Limit Background Activity in Settings
Windows has a per-app background setting, but it appears only for some apps. Many traditional desktop and Electron apps won’t show it.
- Open Settings > Apps > Installed apps.
- Select the three-dot menu next to the app.
- Choose Advanced options. If that option is missing, this fix doesn’t apply to the app.
- Under Let this app run in background, choose Never or Power optimized (recommended).
Expected result: The app stops doing work when you aren’t using it. Pick Never only for apps whose notifications you don’t need.
Fix #6: Turn Off Hardware Acceleration in the App
Hardware acceleration hands drawing work to your graphics chip through a separate GPU process. Turning it off can shrink that process on some PCs. It can also push the work onto your CPU and make scrolling choppier. Treat this as a test, not a guaranteed win.
- Note the app’s current memory use in Task Manager’s Processes list.
- Open the app’s Settings, usually through a gear icon.
- Look for an Advanced or similar section. The location and label differ from app to app.
- Turn off the Hardware acceleration toggle.
- Restart the app if it asks you to.
- Use the app normally for a while, then compare its memory in Task Manager.
Expected result: Memory or GPU-process use drops without the app feeling slower. If the app stutters or your CPU usage climbs, turn the toggle back on.
Fix #7: Use the Web or PWA Version Instead
For apps you open once or twice a week, the browser version can be worth trying instead of the desktop app. It runs inside a browser window or tab you may already have open, rather than starting a separate Chromium and Node.js copy.
Whether this actually lowers your total memory use isn’t guaranteed. It depends on how many tabs, extensions, and other processes your browser already has running, so treat the switch as a tradeoff to test rather than an automatic win.
To install a service as a Progressive Web App (PWA) in Microsoft Edge:
- Open the service’s web address in Edge and sign in.
- Select Settings and more (
...) > Apps > Install this site as an app. - Select Install. The app gets its own window and Start menu entry.
- Uninstall the desktop version from Settings > Apps > Installed apps once you’re happy with the web version.
Expected result: One less Electron app running in the background. Check notifications and any features you rely on first, since web versions don’t always match the desktop client feature for feature.
Settings Reference
| Setting | Where to Find It | Default |
|---|---|---|
| Efficiency mode | Task Manager > Processes > right-click a process | Off unless you turn it on |
| Startup launch | Task Manager > Startup apps, or Settings > Apps > Startup | Varies; many apps enable it at install |
| Let this app run in background | Settings > Apps > Installed apps > app > Advanced options | Power optimized, where the control exists |
| Hardware acceleration | Inside each app’s own Settings | Typically on; varies by app |
Tips and Troubleshooting
An app comes right back after End task
A startup entry, updater, or companion service is relaunching it. Disable the app in Startup apps (Fix #3) and switch off any launch-at-login option inside the app.
The app isn’t in the Startup apps list at all
Some launchers drop a shortcut straight into a Startup folder. Press Windows + R, type shell:startup, and press Enter to see your own Startup folder. Then do the same with shell:common startup for the all-users folder. Delete only shortcuts you recognize.
Startup impact says “Low,” but the app uses lots of RAM
Startup impact measures how much an app slows your sign-in. It says nothing about memory use afterward. Judge ongoing RAM use with the Memory column instead.
Do you need to update Windows to see memory improvements?
Mostly, but not entirely. Efficiency mode (Fix #4) needs Windows 11 version 22H2 or later, and background-app controls (Fix #5) only appear for some apps, so exact availability depends on your build and which app you’re adjusting.
Microsoft’s November 3, 2026 Windows blog post also describes separate, ongoing memory improvements Microsoft is rolling out for 8GB Windows 11 PCs through Windows Update, including more efficient background behavior for apps like Teams. For the current version requirements and Microsoft’s own test results, check that blog post directly, since both can change as the rollout continues. Check Settings > Windows Update to see what’s available on your PC.
Conclusion
Fixes #2 and #3 do the heavy lifting for most 8GB PCs. Quitting from the tray and killing startup launch keep these apps from loading when you aren’t using them. Hardware acceleration is a coin flip, so test it per app and revert if things feel worse.
If memory is still maxed out with only one or two apps open, a RAM upgrade such as a Crucial or Kingston laptop memory kit is the honest fix, or a new laptop with 16GB of RAM if yours is soldered. And if Task Manager shows heavy processes you don’t recognize, run a full Microsoft Defender scan before you troubleshoot anything else.
Resources
Sources retrieved November 8, 2026.