Slack in the browser: what it does and where it breaks down

Running Slack in a browser tab is not a reduced version of Slack. It is the same client, reached through a different door. Messages, channels, search, threads, and files all behave the way they do in the desktop application, because the work is happening on the same servers either way.

What changes is everything around that client: which browsers are allowed to open it, which features the browser is permitted to run, where the notification permission lives, and what happens on the day a version falls out of support. Those conditions are published, they are specific, and several of them have dates attached. This is a walk through them, aimed at someone deciding whether a tab is a reasonable permanent home for Slack or a temporary arrangement that should be replaced.

Three doors into the same workspace

On a Mac there are three ways in. The desktop application from Slack's download page, the same application from the Mac App Store, and the browser. All three connect to the same workspace and show the same conversations.

The difference is what ends up on the machine. The desktop application installs, occupies a Dock slot, and carries its own update mechanism. The browser route installs nothing. Authentication state lives in the browser's storage, and there is no uninstall step, because there is nothing to uninstall.

That distinction matters most when the machine is managed by someone else. On a laptop where software installation is restricted, the browser is often the only route available. It also matters when the hardware is old: Slack lists macOS 13 or later and application version 4.44 or later as the requirement for the desktop client, so on anything older the desktop door is simply closed and the browser is what remains.

Browsers have a floor, and it moves twice a year

The browser route is not open to every browser. Slack publishes a minimum version for each supported one.

Browser	Minimum version
Chrome	137
Firefox	139
Safari	26
Microsoft Edge	136

The Safari row behaves differently from the others. Chrome, Firefox, and Edge update themselves on their own schedule, independent of the operating system, so those numbers get cleared without anyone thinking about it. Safari updates arrive with macOS. Requiring Safari 26 therefore amounts to requiring a recent macOS, which is the same constraint that pushed some people toward the browser in the first place.

The floor itself is not fixed. Slack states that system requirements are refreshed twice a year, in May and November, and notes that this cycle changed in May 2025 from the previous March and September schedule. Anyone planning around these numbers should treat them as a moving line rather than a permanent one, and should expect two adjustments per year.

Only one feature is gated by browser choice

Very little functionality is formally restricted in the browser, but there is one line, printed as a note directly under the browser table:

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

Whether that matters depends entirely on how a team communicates. Where calls happen in a scheduled meeting tool and Slack carries text, Safari and Edge are perfectly adequate. Where people drop into huddles several times a day to sort something out in ninety seconds, that single sentence removes two of the four supported browsers from consideration.

The efficient way to use this is to decide in the other order. Settle whether huddles are part of the daily routine first, then pick the browser. Teams that use them are choosing between Chrome and Firefox. Teams that do not can use any browser that clears the version floor above.

Notifications reach one workspace, and the permission lives elsewhere

The most common surprise in the browser is notification behavior, and it is documented plainly. Slack's notification troubleshooting page ends its browser section with a note stating that notifications will only be received for the workspace open in the browser.

This is the behavior that separates a tab from an application. The desktop client holds several workspaces at once and raises a banner for whichever one has activity. The browser knows about the one currently loaded. A mention in the other workspace waits silently until someone goes looking.

The permission itself also sits outside Slack. In Chrome it is under Privacy and security, then Site settings, then Notifications. In Edge it is under Cookies and site permissions, then All permissions, then Notifications, where Slack has to appear in the allowed list. Firefox keeps it under Privacy and security, in the permissions section next to Notifications. Safari keeps it in preferences under Websites, then Notifications. Four browsers, four locations, and switching browsers means setting it again.

Above all of that sits macOS, where the browser itself must be allowed to post notifications and Do Not Disturb must be off. A browser notification therefore depends on three layers agreeing: the Slack preference, the browser permission, and the system setting. Three layers means three places where a silent failure can hide, which is why "notifications stopped working" is rarely one problem.

What happens at end of support is not the same for every door

Versions have published end dates, and the consequence differs depending on which component expired.

What reaches end of support	What follows
The macOS version	Slack remains accessible on a supported application version, but the application stops receiving updates
The desktop application version	A prompt to upgrade appears, and Slack cannot be accessed until the upgrade is done
The browser version	Slack cannot be used in that browser at all, including signing in, creating workspaces, and managing settings

The browser row is the strict one. An aging operating system degrades gradually. An unsupported browser stops the session outright.

The dates are published in advance. Chrome 142 and earlier, Firefox 144 and earlier, and Edge 142 and earlier are listed with an end date of 9 November 2026. Safari 18 and earlier carries an earlier date, 18 May 2026, which has already passed. That gap between Safari and the rest is not arbitrary: a browser that cannot update without the operating system falls out of support faster, and the Safari 26 requirement is the same fact stated from the other side.

For anyone on Chrome or Firefox, these numbers get crossed automatically during normal use. That is a genuine argument for a self updating browser as the home for a tab that needs to keep working without maintenance.

The lengths behind those dates are published as policy rather than left to guesswork, which makes the next expiry predictable instead of surprising.

Component	How long support lasts
Slack desktop and mobile applications	12 to 18 months from release
Browsers	12 to 18 months from release
Mac, Windows, and Linux	At least 3 months after the manufacturer stops supporting the OS
iOS	Two and a half to three years from release
Android	Four and a half to five years from release

Two things fall out of that table. First, browsers get the shortest window of anything on the list, which is worth knowing before treating a browser tab as the stable long term arrangement. Second, the operating system row is not a fixed number at all; it is tied to whatever Apple decides, with a short grace period added. A Mac that stops receiving macOS updates therefore starts a clock that Slack does not control, and the browser on that Mac is caught by the same clock if it is Safari.

Slack also reserves the right to change the lifecycle at its own discretion, with or without prior notice. Treating any of these dates as a permanent guarantee is a mistake; treating them as a reason to check twice a year, when the requirements themselves are refreshed, is proportionate.

Sign-in state belongs to the browser, not to Slack

One more structural point explains several everyday behaviors. Identity in the browser route is held in the browser's own storage rather than inside a Slack application.

That is why signing in through Chrome does nothing for Safari on the same Mac. It is why a private or incognito window shows a signed out screen. It is why clearing site data signs someone out of every workspace at once. None of these are faults; they follow from where the state is kept.

The consequence shows up when two identities are needed at the same time, which is common for anyone who belongs to a client workspace as a guest alongside their own. In the browser, that means separate browser profiles, two different browsers, or one window in private mode. All three work. All three leave the person responsible for remembering which window is which, every time.

Where the friction actually comes from

Most complaints about running Slack in a browser are not about features at all. A tab is a tab. It sits in the same row as documentation being read, an admin console left open since yesterday, and a half finished search, and the row gets narrower every hour.

The specific failures are ordinary: the tab cannot be found when a mention arrives, the window switching shortcut lands somewhere else, the tab gets closed by accident and has to be recovered from history. None of these are fixed by any setting inside Slack, because the problem is the location rather than the software.

The fix is to stop treating a daily tool as a page. macOS includes Add to Dock in Safari. Chrome can install a page as an application from its menu. Both are free and both produce a separate window with its own Dock icon. For an arbitrary URL, or for a list of sites that should all behave the same way, a site to app tool covers the same ground with one consistent method; the Features page lays out what that involves, and the Guide walks through building one.

A useful check before committing: count the number of times Slack gets opened in a day. Fewer than five, and a tab is fine. Twenty or more, and the seconds spent hunting for it are the largest cost in this entire article. It is also worth checking how much of the rest of the daily list could be handled the same way, since internal dashboards and vendor consoles almost never ship a native client. The Supported services list is a quick way to compare that against an actual set of tabs.

What to change first

Decide the constraints in order: whether the browser is mandatory, whether huddles are part of the routine, and how often Slack gets opened. If the answer to the last question is "constantly", move that one address out of the tab strip and give it a window of its own, using Safari, Chrome, or a tool such as Kagemusha, and leave the rest of the browsing where it is.