Workflows

Slack Notification Won't Go Away? Fix the Stuck Badge

Seven checks in the order that finds the cause fastest, each with a ten-second test, and what to do before you mark everything as read

M
Murali
Nov 20, 202615 min read
TL;DR

A Slack badge that will not clear is usually one of seven things, and you can test each in about ten seconds. Check them in this order: another workspace, thread replies counted in the Activity badge, an overdue reminder or Slack Connect invite, a stale operating-system badge on the dock or taskbar, a plain out-of-sync client, a known Slack incident, and last the notification diagnostic. Slack's own help says that a badge on a conversation you have already read means something may be out of sync on its side, and its first fix is Shift+Esc in the affected workspace. Before you press it, spend two minutes capturing real requests, because it clears everything, including messages you never read.

Picture the version of this that most people live with: a red dot on the Slack icon that stays after every channel is read, every thread is cleared, and the laptop has been restarted. The number sits at 1. You click around the sidebar hoping to stumble on the culprit, give up, and learn to ignore it. That is the real cost of a stuck badge. Within a week your eye stops reading the badge at all, and the one time it is real, a teammate who needs an answer, you miss it.

If you searched "Slack notification won't go away", you have probably already tried the advice in most guides, which is about reducing how many notifications you get. That is a different problem. This guide is about a badge, a dot, or a bold thread that stays after you have read everything, and it is organized as a diagnostic: seven checks in the order that finds the cause fastest, each with a test you can run in seconds.

A note on sources. I lean on Slack's own help center and its public status page for every claim about how Slack behaves, and I say so where I do. Where a menu path changes between desktop and mobile, or where I could not confirm the current wording, I tell you rather than guess. Slack changes its interface often, so if a label differs on your screen, search for the nearby setting instead.

Why Does a Slack Badge Stay After You Read Everything?

A badge is a count, and a count is computed from more places than the channel you are looking at. Slack's help center lists what raises the badge: direct messages, keywords, mentions, app notifications, thread replies, Slack Connect invitations, and overdue reminders. Several of those never appear in a channel you would scroll. So a stuck badge usually has one of two causes. Either something countable is hiding somewhere you did not look, or the number on screen no longer matches what Slack's servers think, which is a sync problem.

That split is useful, because the two causes have different fixes. A hidden item needs you to find it and clear it. A sync problem needs a refresh or a forced re-read of your state. The first four checks below hunt for hidden items. The last three deal with sync and with Slack itself.

Check 1: Is the Badge Coming From Another Workspace?

Slack's help center says that if you belong to several workspaces, you can pick which ones show badge notifications. The flip side is that a workspace you rarely open, a client's or an old employer's, can keep adding to the icon count while you stare at the one you use.

The ten-second test: look at the workspace switcher on the left edge of the desktop app. Each workspace icon carries its own dot or number. If a different workspace has one, that is your badge. Open it, clear it, or, if you do not want badges from it at all, turn its badge notifications off in your notification preferences. Do this one first because it is the most common cause and the cheapest to rule out.

Check 2: Are Thread Replies Inflating the Activity Count?

Thread replies count toward the badge by default, according to Slack's notification help. The Activity view collects them, along with mentions and reactions, and a reply deep in a thread you once joined can sit there unread while the channel itself looks clean. Slack also documents a preference, under Notifications in your preferences, that lets you exclude thread replies that do not mention you from the numbered badge. If your badge is always a little above zero for no visible reason, this setting is a strong suspect.

The ten-second test: open Activity and look for a bold or unread item. In Slack's keyboard help, R marks a notification as read there, so you can clear them one at a time with the keyboard. Then check the same preference and decide whether replies to threads you follow deserve a number on your icon. For most people they do not.

Check 3: Is an Overdue Reminder or Slack Connect Invite Counting?

This is the cause almost nobody thinks of, because neither shows up in a conversation. The same Slack help page that lists the badge triggers includes overdue reminders and Slack Connect invitations. A reminder you set with the /remind command and never marked complete can keep counting. So can an invitation to a shared channel with another company that sits unanswered.

The ten-second test: open your reminders list and look for anything overdue, then look for any Slack Connect invitation you have not answered. Mark the reminders complete or delete them, and accept or decline the invite. If you want to understand why reminders go stale in the first place, I wrote about it in Slack reminders and scheduled messages.

Check 4: Is It the Operating System Badge, Not the Slack Badge?

There are two separate badges, and people confuse them. One lives inside Slack: the dots and numbers on workspaces, Activity, and threads. The other lives on the app icon in the macOS dock or the Windows taskbar. Both are drawn from Slack's counts, but they are not the same object, and the second one can lag behind or get stuck on its own.

Slack's help says the icon badge is a desktop preference. In the preferences under Sound and appearance, there is an option to show a badge on Slack's icon to indicate new activity, and you can untick it. On Windows, Slack says badges appear in two places, the taskbar and the notification area, and that turning off the option to keep the app running in the notification area removes the icon and its badges from that area.

There is also a documented history. Slack's release notes for the Mac app list a fix for badges that lingered on the dock icon after the messages had been read. If you are on an old build, updating the app is a legitimate first step, not a superstition.

The ten-second test is a comparison. If the dock or taskbar icon shows a number but the Slack window shows no dots anywhere, including in the workspace switcher, Activity, and Threads, the problem is the operating system badge. Quit Slack completely, not just the window, then reopen it. If the icon number returns, toggle the badge preference off and on once so Slack redraws it.

Check 5: Is Your Client Simply Out of Sync?

If the in-app badges are also stuck and none of the earlier checks found anything, treat it as a sync problem. Slack's troubleshooting article is direct about this. It says that if you see notification badges for conversations you have already read, or your Threads view will not unbold, something might be out of sync on Slack's end. Its first step is to open the affected workspace in the desktop app or the browser and press Shift+Esc.

Shift+Esc is Slack's marking-all-as-read shortcut, listed on its keyboard shortcuts page, while plain Esc marks only the conversation you are viewing. One detail from that help is easy to miss: Esc only works when you are not typing a message and no menu is open, so an unsent draft or an open menu can make the shortcut look broken. There is also a Mark All Messages Read control at the bottom of the Unreads view if you prefer a button.

Do not press it yet, though. It is a bulk action, and I explain the risk in the section after the checks. First run the cheaper tests.

01

Hard reload the web version

In the browser version of Slack, a hard reload with Cmd+Shift+R on Mac or Ctrl+Shift+R elsewhere forces a fresh copy of the client. Slack suggested exactly this as a workaround during a badge incident in September 2025, so it is a reasonable first test of whether the problem is in the client or in your account state.

02

Compare desktop and browser

Open the same workspace in the browser. If the browser shows no badge but the desktop app does, the desktop client or its cache is stale. If both show it, the count is coming from Slack's side, which points to Check 6.

03

Compare phone and desktop

A badge on your phone that your desktop does not show can be a mobile-only state. Slack's help describes a mobile cache reset under Preferences, then Debug and Reset Cache. Be careful: it logs you out of every workspace you are signed in to, so have your sign-in details ready.

Check 6: Is Slack Having a Known Incident?

Sometimes the bug is not yours. Slack publishes incidents on its public status page at slack-status.com, and badge bugs have appeared there before. In September 2025 there were at least two. Slack's status page described a window from September 9 to September 12 in which the Activity tab showed an unread count badge even when there was no new activity. A separate post described problems from about September 15 into September 18, where the unread badge in Activity would not disappear after items were read, which Slack tied to a recent change in how its client handles the item row in that view. Slack's stated workaround was the hard reload above.

I am not saying that is your bug today. I am saying the status page takes a minute to check, and if there is an open incident, no amount of clearing on your side will help, so you can stop spending time on it. Search the page for "Activity" or "notifications" before you do anything destructive.

Check 7: Run Slack's Notification Diagnostic

When the earlier checks find nothing, Slack has a built-in test. Its help center says that if restarting your device did not fix a notification problem, you can run a diagnostic from the app. The path it gives is profile picture, then Notifications, then Troubleshoot Notifications. That wording reads as the mobile path, and I could not confirm an exact desktop equivalent, so on desktop look in your preferences under Notifications for a troubleshooting option. The diagnostic checks your settings for the usual conflicts, such as a do-not-disturb schedule or an operating system setting that blocks Slack.

If nothing works, Slack's article says you can contact support. It asks for a short summary of the issue plus your workspace URL and email address, and one version of the article asks you to collect logs from the app. Send those details in the first message and you will skip a round of back and forth.

What Order Should You Check in?

The order matters more than any single fix, because it keeps you from using a bulk action when a cheap test would do. Here is the sequence as a checklist.

  • Workspace switcher. Does another workspace have its own dot or number? Ten seconds.
  • Activity and Threads. Any bold or unread item, especially an old thread reply? Press R in Activity to clear one.
  • Reminders and invites. Any overdue reminder or pending Slack Connect invitation?
  • Dock or taskbar versus window. Icon number with no dot anywhere inside Slack means the operating system badge is stale. Quit and reopen.
  • Hard reload or browser comparison. If the badge is gone in the browser, the desktop client is stale.
  • Status page. Is there an open Slack incident about Activity or notifications?
  • Diagnostic, then support. Run Troubleshoot Notifications, then contact Slack with your workspace URL.

Stop at the first check that explains your badge. The usual mistake is skipping straight to the last item or to mark-all-as-read, which clears the number and teaches you nothing about why it came back.

What Is the Risk of Marking Everything as Read?

Shift+Esc is the fix Slack itself recommends for a badge that is out of sync, and it works. The risk is what it clears. A stuck badge is often sitting on top of real, unread messages: a request from a manager in a thread you never opened, a question in a channel you skim, a file someone asked you to look at. Marking everything as read does not distinguish between a ghost and a real ask. It removes the signal for both.

A badge you cannot trust and a badge you cleared without looking are the same problem: you no longer know what is waiting for you.

Mark-all-as-read is also quietly lossy for one more reason. Once the unread state is gone, Slack no longer shows you where you stopped. If you are drowning in a busy workspace, that bookmark was the only map you had.

So before you press it, spend two minutes capturing. This is the habit I would keep even after the badge is fixed.

The Two-Minute Capture Before You Clear

Open the Unreads view, which Slack's help describes as the place to view all your unread messages in one list. Scan it once, quickly, and sort every item that is aimed at you into one of three buckets.

  • Answer now. Anything you can reply to in under two minutes. Do it, then it is gone.
  • Needs a time. Anything that needs real work or a decision. Make it a task with a due time right now, not "later". A line like "send the revised quote to Priya" with a time attached is a commitment. A message sitting unread is a hope.
  • Not for me. Announcements and chatter. Leave them.

Then press Shift+Esc. You have not lost anything, because everything that mattered now lives somewhere with a time on it, and the badge can start from zero. I wrote about why "I will reply later" fails so often in the reply-later piece, and the same logic applies here: an unread message is not a plan.

If you want a deeper system for turning Slack requests into tracked work, turning Slack messages into tasks walks through the options by tool. And if your real problem is the volume, not the stuck badge, managing excessive Slack notifications covers muting, keywords, and schedules.

How Do You Stop the Badge From Getting Stuck Again?

You cannot prevent a Slack-side bug, but you can remove most of the causes that are in your control.

  • Leave or mute workspaces you do not use. An old workspace is a permanent source of stray counts, and you can switch off badge notifications for it.
  • Decide on thread replies. If you do not want a number for every reply in threads you follow, use the preference that excludes thread replies that do not mention you.
  • Close the loop on reminders. Mark reminders complete or delete them. An overdue one keeps counting.
  • Answer or decline invitations. A pending Slack Connect invite is a stuck badge waiting to happen.
  • Keep the app updated. Slack's Mac release notes show badge fixes shipped in updates, so an old build can carry an old bug.
  • Check the status page first. If the badge acts strangely on several people's machines at once, it is probably not you.

None of this is glamorous. A badge is a very small thing, and the point of fixing it is not tidiness. It is that the badge is the only signal Slack gives you from outside the app, and a signal you have learned to ignore is worse than no signal.

Where Mursa Fits, and Where It Does Not

I build Mursa, so I will be plain about the limit of what it does here. Mursa will not fix a stuck Slack badge. That is a Slack client or account state problem, and the checks above are how you solve it. Where Mursa helps is the thing underneath the badge: the requests that arrive in Slack and get lost between reading them and doing them. It is built for people who lose tasks in Slack, so when you reach the two-minute capture step, a message that needs real work can become a task with a time instead of an unread dot you are afraid to clear.

That is the same idea whichever tool you use. A task manager, a notes app, or a paper list works if it gets the request out of Slack and onto a time. What does not work is leaving the only record of a commitment as a bold line in a thread.

Common Mistakes With a Stuck Slack Notification

  • Pressing mark-all-as-read first. It clears the number and any real unread asks along with it.
  • Fixing the wrong badge. The dock or taskbar number and the in-app dots are different objects. Compare them before you change anything.
  • Ignoring other workspaces. The count on your icon can come from a workspace you have not opened in months.
  • Forgetting reminders and invites. Overdue reminders and Slack Connect invitations count toward the badge, and neither lives in a channel.
  • Blaming yourself for a Slack incident. Slack has had badge bugs of its own, so check the status page before spending an hour on your own settings.
  • Resetting the mobile cache casually. It logs you out of every workspace, so do it last.

What Should You Do Right Now?

Open the workspace switcher and look for a stray dot. Open Activity and clear any old thread reply with R. Check reminders and pending invitations. Then compare the dock or taskbar icon with the Slack window itself. If the badge is still there, hard reload the browser version and glance at slack-status.com. Only after those, run your two-minute capture, press Shift+Esc in the affected workspace, and you should be back at zero with nothing important lost. Total time, about ten minutes, most of it the capture you should be doing anyway.

Common questions

Frequently Asked Questions

Why won't my Slack notification go away?

A badge is a count from several sources, not just the channel you are viewing. It can come from another workspace, thread replies in Activity, an overdue reminder, a Slack Connect invitation, a stale dock or taskbar badge, or a sync problem. Slack's help says a badge on a conversation you have already read may mean something is out of sync on its side, and its first fix is to press Shift+Esc in the affected workspace.

How do I mark everything as read in Slack?

In the desktop app or browser, open the affected workspace and press Shift+Esc, which Slack lists as the shortcut for marking all messages as read. Plain Esc marks only the current conversation, and only when you are not typing and no menu is open. You can also scroll to the bottom of the Unreads view and use Mark All Messages Read.

Why does Slack show a badge on the dock or taskbar when I have no unread messages?

The icon badge is a separate desktop preference from the dots inside Slack, and it can get stuck on its own. Quit Slack completely and reopen it, update the app, and toggle the option to show a badge on Slack's icon, found under Sound and appearance in preferences. Slack's Mac release notes list a past fix for badges that lingered after messages were read.

Do thread replies count toward the Slack notification badge?

Yes, by default. Slack's help lists thread replies among the things that raise the badge, alongside direct messages, mentions, keywords, app notifications, Slack Connect invitations, and overdue reminders. There is a preference under Notifications that lets you exclude thread replies that do not mention you from the badge count.

Can a Slack reminder keep the badge on?

Yes. Slack's help lists overdue reminders among the items that show a badge notification. Open your reminders list, mark anything overdue as complete or delete it, and the count should drop.

Is a stuck Slack badge a Slack bug?

Sometimes. Slack's status page recorded Activity badge problems in September 2025, including a window from September 9 to 12 where an unread count showed with no new activity, and another from about September 15 to 18 where the badge would not disappear after items were read. Slack's suggested workaround was a hard reload with Cmd or Ctrl plus Shift plus R. Check slack-status.com before you spend time on your own settings.

Is it safe to press Shift+Esc to clear all Slack notifications?

It works and Slack recommends it for an out-of-sync badge, but it also clears real unread messages. Spend two minutes in the Unreads view first, reply to anything quick, and turn anything that needs real work into a task with a time. Then clear.