Slack Mac download: three routes, one right answer

The Slack download page for Mac shows two buttons where most vendors show one. There is a direct download and a Mac App Store link, sitting next to each other with no explanation of the difference. Underneath that choice is a third route nobody advertises, which is not downloading anything and using the browser. All three lead to a working Slack. They differ in what happens on the machine, what happens at update time, and in one specific case, what happens when a call starts.

Two buttons and a browser

The direct download delivers a .dmg from Slack's own servers. As of early September 2026 the version offered is 4.52.155. That page also links to a beta channel and to enterprise deployment documentation, which is a good signal that this is the route Slack expects most people and most IT departments to take.

The Mac App Store route delivers the same application through Apple's distribution system. The listing is published by SLACK TECHNOLOGIES L.L.C., carries a download size of 168.1 MB, is rated 16+, and lists 52 interface languages. It was last updated on 1 September 2026 at version 4.52.155, matching the direct download.

The third route is app.slack.com in a browser tab. No installation, no disk space, no update to manage.

Route	Update mechanism	Admin rights needed	Sandboxed
Direct .dmg	Slack's own updater	For /Applications	No
Mac App Store	Apple's store queue	No	Yes
Browser tab	Follows the browser	No	Browser sandbox

The practical difference between the first two shows up in managed environments. A Mac where the user cannot install to /Applications can still install from the App Store, because store installs go into the user's own library. Conversely, an organisation that blocks the App Store entirely has to use the direct download or a managed deployment package. For a personal Mac, the two are close enough that the choice hardly matters.

The floor, and the fact that it moves

Both installable routes require the same macOS version. The published requirements list it plainly.

OS	OS version	App version
macOS	MacOS 13 or above	4.44 or above
Windows	Windows 11 version 23H2 or above	4.44 or above
Linux	Ubuntu LTS 22.04 or above, RHEL 9.0 or above	4.44 or above

The Mac App Store listing states the same floor independently, requiring macOS 13.0 or later. So a Mac on Ventura qualifies and a Mac on Monterey does not, regardless of which button gets clicked.

More important than the current number is that the number is scheduled to change.

Slack updates these system requirements twice per year in May and November. Source: slack.com

That is unusually explicit, and it is useful. Most vendors raise their floor without warning. Knowing the cadence means a Mac sitting one macOS version above the current minimum has a predictable window before the question comes up again. It also means an article stating a requirement is only reliable until the next revision, so checking the source rather than a summary is worth the thirty seconds.

The mobile and browser floors move on the same schedule. Currently iOS 17 and Android 11 on the mobile side, and Chrome 137, Firefox 139, Safari 26, and Edge 136 on the browser side.

What the browser route actually costs

The web version of Slack is close to complete. Messages, threads, channels, search, file uploads, notifications, keyboard shortcuts, and the entire application ecosystem work in a browser tab. For a long time the honest summary was that the desktop application offered better system integration and nothing else functionally.

There is now one documented exception, and it is the one that matters most in a working day.

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

Huddles are the lightweight audio and video calls that start from inside a channel. In Safari, they are not available. In Chrome or Firefox at a current version, they are. This single line decides more about the browser route than anything else on the requirements page, because a Mac user who defaults to Safari and switches to Slack in the browser will discover the gap during a call rather than before one.

The other cost is not functional but ergonomic. Slack in a tab looks like every other tab. It does not appear in the Command Tab switcher, it cannot hold a fixed position in the Dock, and its notifications arrive attributed to the browser rather than to Slack, so silencing browser notifications silences the ones that matter along with the ones that do not.

On a Mac that cannot install it

A Mac running macOS 12 or older cannot install the desktop application from either route. This is a growing group, because the floor moved to macOS 13 and Apple's own support window has moved with it. The machines themselves are frequently fine.

The route that remains is the browser, and it is a genuine route rather than a consolation. Everything except huddles works, and huddles work too as long as the browser is Chrome or Firefox at a supported version. The setup takes no installation and no administrator approval, which on a locked down machine is sometimes the deciding factor.

What is lost is the desktop integration listed above. That loss is recoverable without installing Slack's application, which is the part most people do not realise. A tool that turns a website into a standalone Mac app produces a window with its own Dock icon, its own switcher entry, and its own notification identity, while the page inside it remains the ordinary web version. On a Mac below the installable floor, this is the closest available equivalent to the real application.

The important detail is what the window is built on. Built on Chromium, huddles keep working, because the underlying engine is one of the two Slack supports for that feature. Built on Safari's engine, they do not. The requirement page's one line about browsers turns into a hard constraint on which wrapper approach is usable.

Several workspaces, and several identities

The desktop application handles multiple workspaces well. Signing into more than one puts them in a rail down the left edge, with unread badges per workspace, and switching is one click. There is no need for separate windows or separate installations to belong to several communities.

Where the arrangement strains is separate identities rather than separate workspaces. A contractor with a personal Slack account and a client account under a different email, or somebody who keeps a work identity and a community identity deliberately apart, ends up wanting two independently signed in environments rather than two entries in one rail.

The browser answers this the way it answers everything: separate profiles, separate cookie stores, separate sessions. Standalone windows built on top of specific browser profiles inherit that separation, so one window opens the work workspace and another opens the personal one without either one prompting for a sign in. The features overview covers how the profile binding works, and the service catalogue shows the other tools that end up in the same arrangement once the habit starts.

Notifications behave differently on each route

Notification behaviour is the detail people notice on day two, after the novelty of the choice has worn off.

The installed application registers with macOS under its own name. Notification style, banner or alert, grouping, preview visibility, and Focus mode allowances are all set per application in System Settings, so Slack can be allowed through a Focus mode while everything else stays quiet. Badge counts appear on the Dock icon.

Slack in a browser tab registers under the browser's name instead. Every site that has been granted notification permission shares that single identity. Allowing Slack through a Focus mode therefore allows every other site that has permission, and denying the browser silences Slack along with them. There is no per site granularity at the macOS level, only inside the browser's own settings, which Focus modes do not read.

A standalone window built from the tab restores the per application identity. macOS treats it as a separate application because it is one, so notification settings and Focus rules apply to it alone. The messages still arrive from the same web page. Only the attribution changes, and the attribution is what the operating system uses to decide whether to interrupt.

There is a secondary effect worth mentioning. Badge counts on a Dock icon are read at a glance, from across a desk, without switching applications. A count buried in a tab title requires looking at the browser, which requires already being in the browser.

Keeping the download from becoming a maintenance job

Slack does not let old desktop versions run indefinitely. The requirements page points at a support lifecycle document listing versions that will soon be blocked, which means an installation left alone eventually stops connecting rather than merely falling behind on features. The current minimum application version is 4.44 or above, well behind the 4.52.155 currently shipping, so there is room, but the mechanism exists and does get used.

Each route handles this differently. The direct download updates itself in the background and generally stays current without attention. The App Store version updates with everything else in the store queue, which on a Mac with automatic updates disabled can sit untouched for months. The browser route sidesteps the problem entirely, because the web version is whatever Slack is serving that day and there is no client to fall behind.

That last point is the quiet advantage of the browser route in environments where software updates need approval. There is no version to audit, no package to re-approve, and no blocked client to explain. The tradeoff is the notification and window behaviour described above, which is exactly what a standalone window is for.

Deciding in under a minute

Three questions settle it.

Is the Mac on macOS 13 or later? If not, the browser is the route, and the browser should be Chrome or Firefox so huddles remain available.

Does the work involve huddles? If yes and the browser is Safari, either switch browsers for Slack specifically or install the desktop application.

Is more than one Slack identity in play? If yes, one installed application will not hold both, and separate browser backed windows will.

For a single identity on a current Mac with no unusual constraints, the direct download is the simplest thing that works, and the App Store version is equally fine if administrator rights are awkward. The pricing page is relevant only if the standalone window route is the one being chosen.

What to change first

Check the macOS version before clicking either button, because below macOS 13 neither one will complete. If the browser is the route, use Chrome or Firefox so huddles keep working, then give that tab its own window and Dock icon with Kagemusha so it stops behaving like a tab.