Discord is eating your RAM
Discord is built on a whole web browser — so it can burn 1 GB+ of RAM just to show chat. Here's how to claw it back, from 2-second wins to the big one.
Open Task Manager mid-game and Discord is often using more memory than the game you're playing. On a lot of Windows PCs the normal client sits well above 1 GB of RAM — just to show a chat window. Here's why, plus seven things you can actually do about it.
🔍 Why Discord eats so much RAM
Discord runs on Electron — basically a full copy of Chrome bundled into the app. Before you've read a single message it's already running several Chromium processes, each with its own chunk of memory. Then these pile on:
- Hardware acceleration spins up a GPU process that can leak memory over a long session.
- Animated avatars, emojis, and stickers get decoded and held in memory as you scroll.
- Big, busy servers mean more cached members, channels, and media.
- Background telemetry and experiments add overhead you never see.
🛠 7 ways to cut Discord's memory use
Toggle hardware acceleration
Settings → Advanced → Hardware Acceleration. CPU-bound? Leaving it on shifts work to the GPU. GPU maxed in-game? Turning it off frees VRAM and stops a slow memory creep. Test both — the right answer depends on your rig.
Cut the animation load
Settings → Accessibility → turn on Reduced Motion and switch off animated emoji and stickers. Fewer things looping = less memory used.
Leave servers you don't use
Every server you're in is stuff Discord keeps loaded. Leaving dead ones is the easiest way to shrink those cached member and channel lists.
Clear the cache
Fully quit Discord, then empty %AppData%\discord\Cache and Code Cache.
A bloated cache costs startup memory, not just disk space.
Actually quit it (don't just minimize)
Hitting X just minimizes Discord to the tray — it keeps running. Not in a call? Right-click the tray icon → Quit. Relaunching takes two seconds and resets the memory baseline.
Turn off launch-on-startup
Settings → Windows Settings → turn off "Open Discord" on startup. No reason for a 1 GB process to load before you've even opened a game.
Run a lighter client — the big one
The fixes above help, but you're still running a full browser just to read text. The biggest single win is swapping the client itself — a trimmed build strips the browser-like parts (telemetry, crash beacons, ad-tech, growth experiments) and idles far lower. Same servers, same friends, same pings.
Bottom line: quit instead of minimize, clear the cache, leave dead servers for the quick wins. The bigger win is a client that wasn't built to spy on you — same Discord, hundreds of MB lighter.