Your Bluesky app shows a notification badge with a number that does not go away even after you read all new posts, replies, and likes. This is a known display glitch where the badge counter fails to reset after the notification server clears the actual unread count. The problem can affect the mobile app, the web app, or both at the same time. In this article, you will learn why the badge gets stuck and how to force a reset using four proven methods.
Key Takeaways: Resetting a Stuck Bluesky Notification Badge
- Web app: Refresh the page or log out and back in: Clears the cached badge counter from the browser session.
- Mobile app: Force stop and reopen the app: Terminates the background process that holds the stale badge number.
- Mobile app: Clear the app cache from system settings: Removes corrupt local notification data without deleting your account.
- Web app: Open Bluesky in a private or incognito window: Loads a fresh session that bypasses cached badge state.
Why the Bluesky Notification Badge Gets Stuck on a Non-Zero Number
Bluesky displays a notification badge on the app icon and in the in-app navigation bar to show how many unread interactions you have. The badge number comes from a server-side notification queue. When you open the app, Bluesky sends a read-receipt request to the server. The server then decrements the unread count and sends back an updated number.
A stuck badge occurs when one of these events fails:
Delayed or Dropped Read-Receipt
If your device loses network connectivity right after you view new content, the read-receipt never reaches the server. The server still thinks you have unread items. The badge stays at the old number until the server receives a new read-receipt from a subsequent session.
Corrupt Local Cache
The Bluesky mobile app stores the last known badge count in a local cache file. If the cache becomes corrupted due to an app crash or incomplete update, the app continues to display the stale number even after the server resets the count.
Browser Session State
On the web version, Bluesky uses the browser\’s localStorage to persist the badge number across page loads. If the browser does not sync correctly with the server, the badge value remains frozen. This is more common when you keep the browser tab open for many hours without a refresh.
Steps to Fix a Stuck Notification Badge on Bluesky
Try these methods in order. Each method addresses a different cause. Test the badge after each step before moving to the next one.
Method 1: Refresh the Bluesky Web Page or Restart the Mobile App
- On the web: Press F5 or click the browser refresh button
This reloads the entire Bluesky interface and forces the app to request a fresh badge count from the server. Wait 5 seconds after the page reloads to see if the number changes. - On iOS: Swipe up from the bottom and swipe the Bluesky app card away
Fully close the app. Wait 10 seconds, then tap the Bluesky icon to relaunch it. The app will re-fetch the badge count from the server during startup. - On Android: Open Settings > Apps > Bluesky > Force Stop
Tapping Force Stop kills all app processes. After the button turns gray, tap Open to restart the app. The badge should update within 15 seconds.
Method 2: Log Out and Log Back In
- On the web: Click your avatar in the top-right corner > Settings
Scroll to the bottom of the Settings panel and click Sign Out. The page returns to the login screen. - On mobile: Go to Settings > Account > Sign Out
Tap Sign Out and confirm. The app closes the current session and clears the local badge cache. - Sign back in with your handle and app password or email
Use your regular login credentials. Do not use a one-time code from a previous session. After login, the badge should show zero or the correct unread count.
Method 3: Clear the App Cache on Mobile
- On Android: Open Settings > Apps > Bluesky > Storage > Clear Cache
Tap Clear Cache. Do not tap Clear Data or Clear Storage. Clearing the cache removes only the temporary notification files. The badge number resets the next time you open the app. - On iOS: Offload the app via Settings > General > iPhone Storage > Bluesky > Offload App
Offloading removes the app but keeps your documents and data. After offloading, tap Reinstall App from the same screen. iOS downloads a fresh copy of Bluesky. Log in again and the badge will reflect the server count.
Method 4: Use a Private or Incognito Browser Window
- Open a private browsing window in your browser
In Chrome, press Ctrl+Shift+N. In Firefox, press Ctrl+Shift+P. In Safari, press Shift+Command+N. - Navigate to bsky.app and log in
The private window does not share localStorage or cache with your regular browsing session. This gives Bluesky a completely clean slate for the badge counter. - Check the badge number in the navigation bar
If the badge shows the correct count in the private window, the issue is isolated to your regular browser session. Close the regular browser tab and continue using Bluesky in the private window until you clear the normal browser cache.
If Bluesky Still Shows a Stuck Badge After All Fixes
The Badge Number Changes but Never Reaches Zero
This means you have unread notifications that you have not viewed. Open the Notifications tab by tapping the bell icon at the bottom of the screen. Scroll through every notification until you reach the oldest one. The badge should reset to zero after you have scrolled past all items.
The Badge Shows a Number That Is Lower Than Before but Still Not Zero
A partially updated badge indicates that the server processed some read-receipts but missed one or more. Repeat Method 2 (log out and log back in). This forces a full sync of all notification states.
The Badge Appears Only on the Mobile App but Not on the Web
The mobile app stores the badge count in the iOS or Android notification system, which is separate from the Bluesky in-app badge. Go to your device notification settings and disable then re-enable notifications for Bluesky. On iOS, go to Settings > Notifications > Bluesky > toggle Allow Notifications off, wait 10 seconds, then toggle it back on. On Android, go to Settings > Apps > Bluesky > Notifications > toggle all categories off and on again.
Bluesky Notification Badge Stuck: Web vs Mobile Behavior
| Item | Web Version | Mobile App |
|---|---|---|
| Badge location | In-app navigation bar only | App icon badge and in-app navigation bar |
| Data source | Browser localStorage | Device notification cache and local app storage |
| Most common fix | Page refresh or private window | Force stop or clear app cache |
| Persistence after logout | Cleared when session ends | May persist until cache is cleared |
The web version relies entirely on the browser session. The mobile app stores badge data in two separate locations: the app\’s internal cache and the operating system\’s notification system. This is why the mobile badge sometimes requires a device-level fix such as clearing the app cache or resetting notification permissions.
A stuck notification badge on Bluesky is a display glitch, not a sign of missed messages or account problems. The four methods listed above will resolve the issue in nearly every case. If you use Bluesky on multiple devices, check the badge on each device separately because the cached count is stored locally per device. For persistent problems, submit a support request through Bluesky’s in-app feedback option under Settings > About > Report a Problem.