Grey screen? Blank window? Stuck updating?

Discord got stuck.
Again.

Download it, open it, click one button. Discord closes, the gunked-up caches get yeeted, and it reopens — usually in about three seconds. You stay logged in.

macOS.dmg Windows.exe Linux.AppImage

Free · MIT · ~6 MB · no installer · no account · no terminal required

Discord

Checking for updates…

for the last 11 minutes

Fixed.

Freed 287 MB · you're still logged in

↑ go on, it's just a demo. The real one is one download away.

You are not alone.

—

…people have watched Discord fail to open.

You know this dance

Discord is an Electron app, and Electron apps hoard corrupt caches like a dragon hoards gold. Eventually the client just… gives up. It always looks like one of these:

The grey void

A featureless grey rectangle that stares back at you and does nothing.

The blank window

It opened! Technically. There is simply nothing inside it.

The forever update

"Checking for updates…" — a promise it has no intention of keeping.

The fix has always been the same: close Discord, delete some cache folders, open it again. You've looked that up forty times. This is a button.

One button. Three moves.

Stops Discord

Politely (SIGTERM), then firmly (SIGKILL). It waits for Discord to let go of its files before touching anything.

Clears the caches

The dozen-odd cache directories that actually cause the hang — gone. Your login and settings are on a hard no-touch list.

Reopens it

Right where you left off. Only reopens what it closed — it won't barge in on a Discord you quit on purpose.

Discord Stable, PTB, Canary & Development are each detected separately. Got more than one? Pick which to fix.

You stay logged in.
Yes, really.

Your session token lives in two files — Local Storage and Cookies. They sit on a hard-coded deny list that neither cleaning mode can touch. And if some future edit ever tried to sneak them onto the delete pile, a test fails the build. The code literally refuses to ship.

Your messages? Those live on Discord's servers. This app never goes anywhere near them.

Always cleared

Cache
Code Cache
GPUCache
Shader caches
blob_storage
Crashpad
logs · sentry

pure junk

Deep clean also

Service Worker
Session Storage
WebStorage
Trust Tokens
the big modules dir

regenerated on launch

Never. Touched.

Local Storage ← your login
Cookies ← your login
settings.json
quotes.json

off limits

The old way vs. the button

Before

$ pkill -f Discord
# also killed your editor, which
# happened to have a file named
# discord_notes.md open. oops.
$ rm -rf ~/Library/Application\ …
# wait, was that the right folder?
$ ▋

Googling the incantation. Praying you deleted the right thing. Hoping -f didn't take a hostage.

After

Fix Discord

It matches Discord by its actual executable path, never by a command line that merely mentions the word "Discord." Your editor lives.

Stuck on that endless update? Flip one checkbox.

Deep clean also removes Discord's downloaded native modules — often 200–300 MB — which is the thing that actually breaks a client out of an update loop. Discord re-downloads them on the next launch. Takes a moment longer. Still keeps you logged in.

~6 MB

Written in Rust

No Electron (unlike the thing it fixes)

Starts instantly

macOS · Windows · Linux

MIT & open source

Don't trust a button? Fair.

The same binary runs headless. See exactly what it would delete — down to the byte — before it touches a thing.

$ discord-desktop-fixer --dry-run
Would clear 13 items (241.8 MB)
# deletes nothing. just tells you.

--cliRun in the terminal instead of a window

--dry-runShow what would go, delete nothing

--deepAlso clear stored modules & web storage

--no-relaunchDon't reopen Discord afterward

Go on. Un-stick it.