Slack in the browser not working: what to check, in order

Slack running in a browser tends to fail quietly. Nothing crashes. A message simply never announces itself, a button does nothing when clicked, or a badge sits there claiming three unread items that were read an hour ago. Because there is no error text to search for, the usual response is to try random fixes: reload, sign out, clear everything, reinstall something. That works occasionally and teaches nothing. A fixed checking order is faster, because each step rules out a whole category and the categories do not overlap.

Sort the symptom into one of four buckets first

Before checking anything, decide which of these describes what happened. The rest of this article is organised the same way.

Nothing loads, or sign in refuses to complete. Something is wrong at the version or session level.

Messages arrive but notifications do not. The delivery chain has a break in it, and the chain has five links.

A specific feature refuses to start while everything else works. That is a support boundary, not a fault.

Something that was read keeps looking unread. That is state getting out of sync, and it has a documented fix.

Guessing which bucket applies is not necessary. The symptom names the bucket. Working out of order is what makes these take an afternoon.

First check: is this browser still allowed in

This one goes first because it invalidates every other test. Slack removes support from browser versions on a schedule and the result is not a warning banner.

The published schedule lists Chrome 142 and below, Firefox 144 and below, and Edge 142 and below as reaching end of support on 9 November 2026. Safari 18 and below ended on 18 May 2026. The current floor given in the system requirements is Chrome 137 or later, Firefox 139 or later, Safari 26 or later, and Edge 136 or later. Support lasts 12 to 18 months from a browser's release, and the requirements themselves are refreshed every May and November.

The symptom to match is being blocked at sign in, or a workspace that will not open at all while the same account works fine on a phone. Checking takes a few seconds in the browser's about screen. If the version is below the floor, stop here: nothing further down this list is the cause. On a managed machine where the browser version is controlled centrally, this is also the check that has to be escalated rather than solved locally.

Notifications that never arrive: five links in the chain

This is the most common complaint and the one with the most places to go wrong. Check them in this order, because each one is cheaper to verify than the next.

Link one: is the workspace actually open. Browser notifications only exist for a workspace loaded in that browser. Close the tab and the workspace goes silent. This single fact explains most missing notifications, and it is the reason the complaint so often takes the form of finding out about something hours later.

Link two: browser permission. Slack's troubleshooting documentation gives a separate path per browser. Chrome: settings, then privacy and security, then site settings, then notifications. Edge: cookies and site permissions, then notifications, with the Slack workspace in the allow section. Firefox: privacy and security, then the settings button beside notifications. Safari: the websites tab, then notifications. A permission dismissed once months ago stays dismissed silently.

Link three: the operating system. On macOS, notifications must be allowed for the browser itself, with an alert style of banners or alerts rather than none. Focus modes and Do Not Disturb sit at this level too, and a Focus left running after a meeting is a common cause of an afternoon of silence.

Link four: Slack's own pause. Notifications can be paused inside Slack, which shows as a snooze icon next to the name. This is easy to trigger by accident and easy to forget.

Link five: power saving. Slack's documentation notes that power saving modes and performance optimisation utilities can prevent notification delivery, and suggests disabling them or adding Slack to their allow list. Browsers also suspend background tabs to save memory, which is the same problem arriving from a different direction.

Four of these five links do not exist when Slack runs in a window registered with the operating system. That is the practical reason this category of complaint mostly disappears after moving out of a tab.

Badges that will not clear

A conversation that stays bold after being read, or a threads view that will not unbold, is a synchronisation problem rather than a settings problem. Slack documents the fix for the desktop app and for Slack in a browser identically: open the affected workspace and press Shift and Escape to mark everything as read. If that does not clear it, the documentation directs the issue to Slack support with the workspace URL attached, which is a way of saying that local troubleshooting has been exhausted.

Worth noting before spending time on it: an unread count that reappears immediately after being cleared is usually a muted channel or an app posting into a conversation that is still counted. That is expected behaviour and not the same symptom.

A feature refuses to start: where the boundaries are

When one thing fails while everything else works, the answer is almost always a documented boundary rather than a bug.

Huddles are the clearest case.

Note: Google Chrome and Firefox are the only browsers that support huddles. Source: slack.com

On Safari or Edge, the headphone icon leads nowhere. Nothing is broken and no amount of clearing caches changes it. The fix is a different browser, the desktop app, or the mobile app.

Screen sharing has its own edges. Two people can share at the same time, and drawing on a shared screen is documented as working in the Slack desktop app on Mac and Windows only. A missing pencil icon in a browser is the documented state, not a rendering failure.

Keyboard shortcuts that do nothing belong here as well. Slack's shortcut reference marks desktop only entries with a double asterisk, covering opening preferences, uploading a file, browsing channels, opening the threads view, and quitting. In a browser those key combinations get intercepted by the browser before Slack sees them, so the result is either nothing or something unrelated. Custom shortcut remapping is not currently available, so there is no configuration route around it.

Finally, huddle capacity: two participants on the free plan, up to 50 on paid plans with video limited to 25 at a time. A huddle that refuses a third person is behaving as documented.

Things that look like faults but are plan limits

Two symptoms get reported as browser problems every time and belong to the account instead.

Older messages that cannot be found are a history limit. The free plan makes 90 days of messages searchable, with access to the past 12 months requiring an upgrade. The same limit applies in the desktop app, so reinstalling changes nothing.

An integration that will not connect may be hitting the free plan's maximum of 10 apps. Slack Connect on the free plan is likewise limited to one to one direct messages with people outside the workspace.

Checking the plan before checking the browser saves the most time of any step here, and it is the one most often skipped.

When the container is the problem

A last category deserves separating out, because the fixes are different in kind. These are faults caused by how the page is being hosted rather than by Slack.

Content blockers and privacy extensions occasionally break parts of the interface, and testing in a private window with extensions disabled isolates that in under a minute. Multiple accounts signed in through one browser profile can produce confusing session behaviour, where opening one workspace logs out another. Aggressive tab discarding returns a stale page that looks loaded but has stopped receiving events, which reads exactly like Slack having gone quiet.

All three follow from the tab being a shared, crowded place. A window of its own removes them structurally rather than fixing them one at a time, which is why persistent flakiness is a stronger argument for changing how Slack is opened than any single missing feature is.

Splitting the fault with a second device

When the checks above all pass and the behaviour continues, one test separates a local problem from an account problem faster than any further configuration work. Open the same workspace on a phone, or on any second machine, and watch whether the same thing happens there.

If a message notifies the phone but not the browser, the account and the workspace are fine and the fault is local: permissions, Focus, an extension, or a discarded tab. If the phone is equally silent, the cause sits with notification preferences on the account, a muted channel, or a paused state, none of which can be fixed by touching the browser.

The same split works for features. A huddle that fails in one browser and succeeds in another is a support boundary. A huddle that fails everywhere on the same account points at plan capacity or a permission set by the workspace administrator.

What to have ready before asking anyone

If escalation becomes necessary, five details turn a long exchange into a short one, and four of them come out of the checks already performed.

The browser name and exact version number. The workspace URL. The time a specific missed message was sent, ideally with the channel name. Whether the behaviour also occurs in a private window with extensions disabled. Whether a second device saw the same thing.

Slack's own troubleshooting guidance asks for a short summary of the issue along with the workspace URL and the account email address when marking everything as read fails to clear stuck badges, which is the same shape of information. Internal IT teams ask for it too, and on a managed machine they are usually the correct first contact rather than the second, since browser versions and notification policy are often set centrally.

Writing these down also has a side effect worth having: the act of listing them frequently surfaces the answer. A version number that turns out to be two years old, or a private window that behaves perfectly, ends the investigation on the spot.

What to change first

Run the checks in the order above and stop at the first one that matches, because the categories do not overlap and continuing past a match wastes the afternoon. If the answer turns out to be a version floor or a plan limit, no change to the window will help. If instead the pattern is notifications arriving late or not at all, and tabs being closed during the day, the fix is structural: give Slack a window that the operating system knows about. The guide covers building one in the right order, including where notification permission gets granted, and Kagemusha answers the questions that usually come up straight afterwards.