Slack Red Dot Won't Go Away? What It Counts and How to Clear It

If the red dot on the Slack icon will not go away, press Shift+Esc in the Slack app to mark every message as read. In our test it also cleared the Activity badge, after a confirm dialog (Slack all unreads). That clears most stuck badges. If it comes back, the unread is somewhere the channel list does not show in bold: a reply in a thread you follow, a mention inside a muted channel, a due reminder in To-dos (called Later until October 2026), or a message in another workspace you are signed in to. If you have checked all of those and the badge is still there, the count is out of sync: clear Slack's cache, then reset the badge in your operating system. To remove the red dot for good, turn off the badge in Slack's notification preferences or in your system's notification settings. The red dot is separate from the green presence dot, and Slack Green keeps that one green from a server with the laptop closed, free for 7 days with no card.

What the red dot and the number mean

Slack puts two kinds of badge on its icon, and they count different things. Slack's own Guide to Slack notifications spells it out per system:

So a plain dot with no number on a Mac is ordinary unread channel traffic. It clears when you read those channels or press Shift+Esc. A message you marked unread yourself keeps it lit too; Slack mark as unread shows what clears that marker. A number means something was addressed to you, and it usually hides in one of the places below.

Why the Slack red dot stays after you read everything

These are the places that keep the badge alive while every channel in your sidebar looks read:

• • Threads. Replies in a thread you follow count toward the number but never appear in the channel. Open Threads at the top of the sidebar and scroll through each one. The full walk-through is in Slack keeps showing unread messages.
• • Mentions in muted channels. Muting stops channel traffic from counting, but an @mention of you inside a muted channel still does, and it brings a hidden muted channel back into the sidebar (our test). Open Activity and filter to unread.
• • Due reminders. A reminder that has come due puts a badge on To-dos (the Later tab in our test below) and adds 1 to Activity. Complete or reschedule it; see Slack Saved for later.
• • Another workspace. On desktop, the badge on the Dock or taskbar covers every workspace you are signed in to. Look for the numbered badge on a workspace icon and switch to it. Managing several at once is covered in using multiple Slack workspaces.
• • Collapsed sidebar sections. A collapsed section can hide a bold DM. Expand every section once, or switch the sidebar to show unreads only.

What a due reminder does to the badges: our test

Reminders are the badge source people forget, because they never make a channel bold. We set one on 2 October 2026 in Slack's web app with /remind me sg1002 red dot test in 1 minute and watched the sidebar and Slack's client.counts method, which returns the numbers behind each badge.



Time (UTC)	Later badge	saved_reminder in Activity	Later list
01:29, reminder set	none	0	1 in progress, not due
01:30, reminder due	1	1	1 overdue
01:31, Mark complete	none	0	0 in progress, 1 completed

So a reminder that comes due adds 1 to both Later and Activity, and nothing in your channel list changes. What else lands in Activity, and which of it you can turn off, is in Slack Activity tab. On 8 October 2026 the same badge showed on To-dos, the tab that replaced Later. Open To-dos, hover the reminder and click the tick (Mark complete), or the clock to snooze it.



The Activity number in our screenshot stayed at 7 after we completed the reminder because another channel item arrived in the same minute; client.counts showed saved_reminder back at 0 and the channel count up by one.

Clearing the red badge does not touch your presence dot, which Slack turns away 10 minutes after your last keyboard or mouse input. A server-side tool keeps your Slack dot green with no input, even with the laptop closed or the phone locked.

How to clear a stuck Slack badge

Slack's troubleshooting article says a badge that stays after you have caught up means "something might be out of sync on our end". Work down this list and stop when the dot is gone.

• Mark everything as read. Open the affected workspace in the desktop app or a browser and press Shift+Esc. Do it in each workspace you are signed in to.
• Read Threads, Activity and To-dos. These three hold the unreads that never turn a channel bold.
• Reload. Press Ctrl+R on Windows or Cmd+R on a Mac. A read marker that did not sync often catches up on reload.
• Clear the cache. On desktop, open the Help menu, then Troubleshooting, then Clear Cache and Restart. On iPhone, tap your profile picture, Preferences, Debug & Reset Cache, Reset Cache. On Android, tap your profile picture, Preferences, Reset Cache. More detail is in how to clear Slack cache.
• Reset the badge in your operating system. If Slack shows no unreads but the icon still does, the stale badge belongs to the OS. See the next section.

If none of this clears it, Slack asks you to contact support with a short summary, your workspace URL and your email address.

Slack badge stuck on Mac, Windows, iPhone or Android

Mac. The Dock sometimes keeps the last badge after Slack has cleared it, or after you quit Slack. Restart the Dock from Terminal. Your windows and apps stay open:

killall Dock

Windows. Restart Windows Explorer, which redraws the taskbar and the notification area. From Command Prompt:

taskkill /f /im explorer.exe && start explorer.exe

Or open Task Manager, find Windows Explorer, and choose Restart.

iPhone. The number on the home screen icon comes from push notifications. Open Slack and let it load so it can send a fresh count. If it still sticks, turn Badges off and on again under Settings, Notifications, Slack.

Android. Notification dots belong to your launcher. Open Slack, clear any Slack notifications in the shade, then turn the app icon badge off and on in the phone's notification settings. The menu path differs by maker.

Slack not showing the red dot

The opposite problem starts with one check. On a Mac, Terminal can print the badge Slack is asking the Dock to draw:

lsappinfo info -only StatusLabel Slack

On our Mac (macOS 26.5.2, Slack desktop 4.52.171) on 7 October 2026 it printed:

"StatusLabel"={ "label"="13" }

The 13 is the badge Slack set on its Dock icon at that moment. Finder, which had no badge, printed "StatusLabel"=[ NULL ] from the same command. So if Slack prints a number and you see no red badge, Slack is counting and the next place to look is macOS: System Settings, Notifications, Slack, Badge application icon. If it prints NULL, Slack has not set a badge at all, so look in Slack's own notification preferences on the desktop app.

A missing number with a dot still showing is expected. Slack shows a number only for DMs, mentions, keywords and replies in threads you follow, as the table at the top of this page says. Ordinary channel messages only ever give the dot, so a busy channel will not show a count on the icon.

How to turn off the red dot in Slack

If you would rather not see the badge at all:

Two limits. The Windows setting removes badges from every taskbar app, and the Slack icon in the notification area still shows its blue or red badge. You can drag that icon into the hidden icons tray. On phones, setting mobile notifications to Nothing in Slack also stops new badges, but it stops the push notifications with them. If you only want quiet time, pause notifications instead.

FAQ

Why is the Slack badge count wrong?

The number counts DMs, mentions, keywords and followed thread replies across every signed-in workspace, not only the one on screen. If it is higher than what you can find, check other workspaces, then clear the cache.

Does muting a channel stop the red dot?

It stops ordinary messages in that channel from counting. A direct @mention of you still counts.

Why do I not get the notifications behind the badge?

That is a separate problem with its own fixes: Slack notifications not working.