In-store advertising
BannerBanner

How to Clear the Discord Cache on Desktop and Mobile

How to Clear the Discord Cache on Desktop and Mobile

On Windows, quit Discord completely from the tray icon, press Win + R, type %appdata%\discord and delete the Cache, Code Cache and GPUCache folders. The app recreates them on the next launch. Your account, servers and messages are unaffected: all of that lives on Discord's servers, not in the cache.

Below are the same steps for macOS, Linux, the mobile app and the browser, plus a list of folders to leave alone and a look at when clearing the cache actually fixes something.

What the cache holds and when to clear it

The cache is a set of local copies the app keeps so it doesn't re-download the same data every time: avatars, image previews, emoji, stickers, interface elements and parts of the client's code. Over time the folder grows and can take up a noticeable amount of disk space.

Clearing it helps in specific situations:

  • avatars, images and emoji don't load and show up as blank squares;
  • the interface renders incorrectly after an update;
  • the client gets stuck on the update-checking screen or shows a white window;
  • the app has become noticeably slower to open;
  • you need to free up space on the system drive.

There's no point doing it routinely as "maintenance": the cache exists for speed, and right after clearing it, images will have to load from scratch again.

How to clear the Discord cache on Windows

  1. Shut the app down completely. The X button only minimises it to the tray, so right-click the Discord icon near the clock and choose to quit.
  2. Press Win + R, type %appdata%\discord and confirm.
  3. In the folder that opens, delete the Cache, Code Cache and GPUCache directories.
  4. Optionally delete blob_storage as well — it's recreated automatically too.
  5. Empty the Recycle Bin and launch Discord.

If Windows refuses to delete the contents and says the files are in use, the process is still running: open Task Manager, end any remaining Discord tasks, and try again.

Which folders to leave alone

The same directory holds the data responsible for your login session and settings. Deleting it will log you out and reset your local preferences:

  • Local Storage — where the login session is stored;
  • sessionStorage and databases — the client's service data;
  • settings.json — the app's settings file.

Deleting the whole discord folder only makes sense for serious failures — and you'll need to be ready to sign in again. If two-factor authentication is enabled, keep your authenticator app or backup codes at hand.

How to clear the cache on macOS

  1. Quit Discord completely (Cmd + Q).
  2. In Finder, open GoGo to Folder.
  3. Enter the path ~/Library/Application Support/discord.
  4. Delete the Cache, Code Cache and GPUCache folders, then empty the Trash.

The user Library is hidden by default, so going straight to the path is the fastest way to get there.

How to clear the cache on Linux

For a package installation the path is usually ~/.config/discord. Delete the Cache, Code Cache and GPUCache directories from it — with a terminal command, or through a file manager with hidden files shown.

The Flatpak build keeps its data in a separate sandbox, at a path like ~/.var/app/com.discordapp.Discord/config/discord. A Snap build has its own structure, so look for the app's directory in your home folder.

How to clear the cache in the mobile app

On Android the most reliable route is through the system: SettingsApps → Discord → StorageClear cache. Leave the neighbouring Clear data button alone — it resets the app to a freshly installed state and signs you out.

Current versions of the app also manage storage internally: the settings section covering storage and downloads lets you remove downloaded media. The wording changes from release to release, so search for "cache" or "storage".

On iOS there's no separate cache-clearing button in the system. If the app takes up too much space, offload it in your iPhone settings or reinstall it — messages and servers aren't lost, you'll just need to sign in again.

The browser version

If you use Discord in a browser, the cache belongs to the browser rather than the app. The quick fix is a cache-bypassing reload with Ctrl + F5. For a full clean-up, open your browsing data settings, choose to remove cached images and files, and where possible limit it to discord.com so you don't wipe data for other sites.

Multiple clients and accounts

The test builds have their own directories: PTB stores its data in discordptb, Canary in discordcanary. They have to be cleared separately — the builds share no cache.

The same goes for different profiles: if you keep a personal and a work account in separate clients or browser profiles, each accumulates its own cache. Community admins who split their Discord accounts by task find it worth knowing upfront which folder belongs to which client.

If clearing the cache didn't help

When the problem persists, work down this list:

  1. Reload the client with Ctrl + R — it refreshes the interface without a full restart.
  2. Update the app to the latest version.
  3. Turn off hardware acceleration in the advanced settings if you're seeing graphical artefacts.
  4. Check whether an antivirus, VPN or corporate firewall is blocking the connection.
  5. Reinstall Discord, removing the app folder in AppData first.

Some faults have nothing to do with local data at all: if messages won't send or a voice channel isn't working, check Discord's service status first.

Common mistakes

  • Clearing the cache while the app is running. The files are locked by the process, some folders won't delete, and nothing changes.
  • Deleting Local Storage along with the rest. The result is being logged out, plus extra hassle signing back in if two-factor authentication is on.
  • Mixing up the AppData folders. Roaming holds the client's data, Local holds the installed app versions — leave the latter alone.
  • Expecting higher FPS in games. The cache affects the client itself, not game performance.
  • Clearing the cache instead of fixing the actual problem. Missing notifications or lost audio usually come down to settings, not local files.

FAQ

Will my messages be deleted when I clear the cache?

No. Messages, servers, roles and account settings live on Discord's side; the cache only holds temporary copies that speed up loading.

Will I have to log in again?

Not if you only deleted Cache, Code Cache and GPUCache. Being logged out happens when you delete the login data or the entire app folder.

How much space does the Discord cache take up?

There's no fixed figure: it depends on how heavily you use the app and how many images you view. You can check the current size in the folder's properties.

How often should I clear it?

Only as needed — when display glitches appear or the disk is filling up. Scheduled clean-ups just slow the interface down for a while.

Is there a built-in clear-cache button on desktop?

The desktop client has no dedicated button for a full clean-up, which is why the folders are deleted manually. The mobile app and your phone's system settings do offer one.

Is it safe to delete these folders?

Yes — the folders listed above are meant for temporary files and are recreated at launch. The risk only comes from deleting login data and settings.

Will it help if Discord is stuck on an update?

Often, yes: corrupted files in Cache and Code Cache are a common cause of hanging on the update-check screen. If it doesn't help, a reinstall is the next step.

Does clearing the cache affect voice quality?

Not directly. Call quality depends on your voice settings and network conditions, not on local temporary files.

In short

Clearing the Discord cache comes down to three steps: close the app completely, open its data folder, and delete the Cache, Code Cache and GPUCache directories. The logic is the same on macOS and Linux with only the path changing, and on a phone the system app settings are the easier route. The key points are to leave the login data untouched and not to expect a cache clean-up to fix problems that come from your network or your client settings.

BannerBanner