Why Discord Notification Badge Shows Wrong Count After Marking Read

You mark a Discord server or direct message as read, yet the notification badge on the app icon or within the channel list still shows a number, often a smaller count like 1 or 2. This happens because Discord separates notification counts into two categories: unread messages and unread mentions or activity summaries. The badge may persist due to cached notification data, delayed sync between the client and server, or specific notification settings that treat mentions differently from general unread messages. This article explains the root cause of the mismatch and provides clear steps to reset the badge count and prevent it from recurring.

Why Discord Notification Badges Get Stuck After Marking Read

Discord uses two separate notification counters. The first is the unread message counter, which shows the total number of messages you have not read in a server or DM. The second is the mention counter, which tracks @mentions, @everyone, and @here pings. When you mark a server as read, Discord clears the unread message counter for that server. However, the mention counter may not reset if the mention was in a thread, a forum post, or a channel you have not opened.

A second factor is client-side caching. The Discord desktop app stores notification state locally to reduce server requests. If the cache becomes outdated, the badge count can remain at an old value even after the server has confirmed the messages are read. This is especially common on Windows 10 and Windows 11 after the computer wakes from sleep or the network reconnects.

A third cause is the Unread Messages Badge setting in User Settings > Notifications. When this setting is enabled, Discord shows a badge for any unread message, not just mentions. If a thread or forum channel contains an unread reply, the badge persists even after you mark the parent channel as read. The app treats each thread as an independent conversation.

Steps to Reset the Discord Notification Badge Count

Follow these steps in order. Stop after each step and check if the badge count corrects itself.

1. Mark All Servers as Read
   Right-click the Discord icon in the system tray or taskbar. Select Mark All Servers as Read. This clears all unread indicators across every server and DM. If the badge remains, proceed to the next step.
2. Check Unread Threads and Forums
   Open the server that shows the wrong badge. Look for channels with a thread icon or a forum icon that has a small number next to it. Click into each such channel and scroll to the bottom to load all threads. Right-click each thread and select Mark as Read.
3. Toggle the Unread Messages Badge Setting
   Go to User Settings > Notifications. Find Unread Messages Badge. Toggle it OFF, then toggle it ON again. This forces the app to recalculate the badge count from the server.
4. Clear the Discord Cache
   Press Ctrl + Shift + I on Windows or Cmd + Shift + I on Mac to open Developer Tools. Click the Application tab. In the left panel, expand Storage and select IndexedDB. Click Clear site data. Restart Discord. The cache rebuilds from the server, which usually corrects the badge count.
5. Restart Discord Completely
   Right-click the Discord icon in the system tray and select Quit Discord. Wait 10 seconds. Launch Discord again. This ensures the app reloads all notification data from the server instead of using a cached state.
6. Reinstall Discord
   If the badge is still wrong, uninstall Discord from Settings > Apps > Installed apps on Windows 11. Download the latest installer from discord.com and reinstall. This clears all persistent local data, including corrupted notification cache.

If Discord Still Shows Wrong Badge Count After the Main Fix

Badge Shows 1 After Reading All Messages

This usually means a thread or forum post contains an unread reply. Open the server, click the channel list icon at the top left (the hamburger menu on mobile or the server name on desktop). Look for any channel that has a small number next to the thread icon. Click into that channel and mark each thread as read individually.

Badge Count Is Stuck on a Number Higher Than Actual Unread Messages

This happens when the notification cache is out of sync. Use the cache clearing step with Developer Tools as described above. If that does not work, disable the Unread Messages Badge setting in User Settings > Notifications, restart Discord, then re-enable it. This forces a full re-sync.

Badge Appears on the Wrong Server

Discord groups notifications by server. If you see a badge on a server you already read, check if you have a friend request or a pending server invitation. Open the Home tab (the Discord logo at the top left) and look at the Pending Friend Requests section. Accept or decline any requests, then the badge should disappear.

Discord Notification Badge Settings: Unread Messages vs Mentions

Item	Unread Messages Badge	Mention Badge
Purpose	Shows total unread messages across all servers and DMs	Shows only messages where you were @mentioned or the channel used @everyone
Default state	Enabled on desktop, disabled on mobile	Enabled on all platforms
Clears when	You mark the server or DM as read, or read all messages in a channel	You open the channel where the mention occurred and view the message
Can cause wrong count	Yes, if threads or forums have unread replies	No, because mentions clear immediately when the channel is opened

The Unread Messages Badge setting is the most common source of a wrong count. If you primarily want to see only mentions, disable this setting in User Settings > Notifications. The app icon will then show a badge only when someone pings you.

After applying the steps above, the notification badge on Discord should reflect the correct number of unread messages and mentions. To avoid future mismatches, mark threads as read individually after reading them, and clear the Discord cache every few weeks using Developer Tools. If the issue returns frequently, switch to the Mentions Only badge mode by disabling the Unread Messages Badge setting.