Slack Mac App Store listing: what it is and what it needs

Yes, Slack is on the Mac App Store, the listing is the real one, and it is free. It appears as Slack for Desktop, sold by SLACK TECHNOLOGIES L.L.C., and on October 18, 2026 it showed version 4.52.178 with a requirement of macOS 13.0 or later. Slack's own download page offers the same version number in two forms: a direct download, and a button that leads to that App Store listing. The two copies run the same app. What differs is how updates arrive, what an organisation can manage, and what happens when the Mac falls behind Slack's support schedule, which for macOS 13 ends on November 9, 2026.

The rest of this page sets out the listing's details, the practical differences between the two copies, and the options for a Mac that can no longer run either.

What the listing actually shows

Three Slack listings turn up when searching the App Store, and only one of them is the Mac app. The Slack for Desktop listing is the Mac version. The listing simply called Slack is the iPhone and iPad app, and Slack for Intune is a separate iPhone and iPad build for organisations that manage devices with Microsoft Intune. Landing on either of the last two from a Mac is a common reason people think the Mac app is missing.

The Mac listing, as checked on October 18, 2026:

Field	Value
Name	Slack for Desktop
Seller	SLACK TECHNOLOGIES L.L.C.
Price	Free
Category	Business
Version	4.52.178, released October 6, 2026
Size	About 169 MB
Requirement	macOS 13.0 or later

The version number is the useful detail. The Slack for Mac download page listed the same version, 4.52.178, on the same day. That is the clearest sign that the store copy is maintained in step with the direct download rather than left behind. Some large services keep a store listing that trails the direct download by months. On the day checked, this one did not.

The listing shows no in app purchases. Paid Slack plans belong to the workspace and are billed by Slack, so the store copy is just the client. Signing in to a workspace on a Pro or Business plan works the same way from either copy.

Two copies, one app: the differences that matter

Slack's help article on updating the desktop app states it directly: Slack has two versions of the desktop app for Mac, the direct download and the App Store version. The features are the same. The plumbing around them is not.

	App Store copy	Direct download
Where it comes from	Mac App Store	slack.com
How updates arrive	Through the App Store, under Updates	From inside Slack, with Check for updates and Restart to apply update
Sign in to the App Store needed	Yes, an Apple Account	No
Beta builds	Not mentioned on the listing	Linked from the download page as "Get the beta"
Enterprise deployment options	Store based distribution	Linked from the download page as "Enterprise deployments"
Sandboxing	Required by Apple for every Mac App Store app	Not subject to that store rule

Two of those rows come from Apple's rules rather than Slack's choices. Apple's App Review Guidelines, section 2.4.5, require Mac App Store apps to be appropriately sandboxed and to use the Mac App Store to distribute updates, with other update mechanisms not allowed. That is why the store copy never shows its own update prompt and waits for the App Store instead.

In day to day use, the update path is the difference people notice. The direct download badges its help icon when an update is ready and restarts itself to apply it. The store copy updates whenever the App Store does, which is automatic on most Macs and invisible. Neither is wrong. The store copy suits a Mac where everything else also comes from the App Store and updates on its own. The direct download suits anyone who wants to apply an update immediately, or wants to try beta builds.

How to tell which copy is installed

The question comes up most often when an update seems stuck. Slack's help article gives the check:

1. Open Slack.
2. Click Slack in the menu bar at the top of the screen.
3. Choose About Slack. If the window mentions the App Store, the store copy is installed. If it does not, it is the direct download.

From there the update route follows. For the store copy, open the App Store, choose Updates in the sidebar, and click Update next to Slack if it is listed as pending. For the direct download, click Slack in the menu bar, choose Check for updates, then Restart to apply update.

Switching from one copy to the other is not complicated, but it is worth doing deliberately. Quit Slack, move the existing app to the Trash, and install the other copy. Workspaces may need to be signed in again, so it helps to know the workspace URLs and to have any single sign on details ready. Having two copies installed at once is a reliable way to end up with two icons and confusion about which one is updating.

Keeping the store copy from falling behind

Slack enforces a minimum app version as well as a minimum operating system, which makes the update setting on the Mac more important than it first looks. On Slack's support schedule, desktop app versions 4.47.59 and below reach end of support on November 9, 2026, and an unsupported version stops working until it is upgraded. A store copy that has quietly not updated for months can therefore stop opening workspaces on a specific date, even on a fully supported Mac.

Apple's page on updating apps gives the setting that prevents this. From the menu bar, open App Store, choose Settings, and select Automatic Updates. With it on, the App Store installs Slack updates along with every other store app. With it off, the App Store sends a notification each time an update is released, and the update waits until Update is clicked under Updates in the sidebar. Apple also notes that apps not downloaded from the App Store are updated through their developer, which is the direct download's own Check for updates command in Slack's case.

A short check once a quarter is enough: open About Slack, note the version, and compare it with the version shown on Slack's download page. If the two are far apart, the update path is not working, and switching on Automatic Updates or moving to the direct download fixes it.

The macOS 13 deadline

The listing's requirement line is current today, but Slack revises it on a schedule. Slack's page on its support life cycle explains the policy. Since May 2025, system requirements are updated twice a year, in May and November. On the Mac, an operating system is supported for at least three months after Apple stops supporting it.

The schedule on that page, as read on October 18, 2026:

macOS version	End of Slack support
11 and below	September 1, 2024
12 and below	May 18, 2026
13 and below	November 9, 2026

What end of support means is spelled out on that page too. On an operating system past its end date, Slack keeps working as long as the installed app version is still supported, but no more app updates arrive, and Slack is no longer available to download from the App Store. Separately, when an app version itself reaches end of support, Slack shows a notice asking for an upgrade, and the app cannot be used until that happens.

Put together, a Mac on macOS 13 can install Slack from the store today, will stop receiving updates after November 9, 2026, and will eventually be running an app version that Slack no longer accepts. The listing does not warn about any of this. The requirement line on the listing will simply change when the next update ships.

When the Mac cannot run the current app

For a Mac that is on macOS 13 or older and cannot move to a newer release, there are three practical routes, and none involves an unofficial client.

Use Slack in a browser. Slack's support life cycle page covers browsers alongside operating systems, so the web version is a supported way to use Slack. On an older Mac, the deciding factor is whether the installed browser itself still receives updates for that macOS release, which is worth checking on the browser maker's own page.

Give the browser version its own window. The main drawback of Slack in a browser is that it becomes one tab among many, easy to lose and easy to close by accident. Installing it as its own app gives it a Dock icon, a place in Command Tab, and a window that is not shared with anything else. In Chrome, the menu offers Cast, save, and share, then Install page as app. On macOS Sonoma 14 or later, Safari's File, Add to Dock does the same, although on macOS 13 that Safari option is not available. A tool that turns a website into a standalone Mac app can do it on macOS 12 and later, using an installed Chromium browser, and keeps the window updated along with that browser.

Plan the upgrade. If the hardware supports a newer macOS, moving up removes the problem entirely and restores access to the store copy. Slack's schedule makes it easy to pick a date: the next requirement change is in November, and the one after that in May.

The browser routes have one honest limit. They depend on the browser's notification support rather than on Slack's own desktop notifications, so it is worth sending a test message and confirming that alerts and the Dock badge behave as expected before relying on them.

Which copy to install

For a Mac on macOS 14 or later with no special requirements, the store copy is the simplest choice. It is free, it is current, and it updates alongside everything else from the App Store. For anyone who wants beta builds, immediate updates, or is setting Slack up across an organisation, the direct download and the enterprise options linked from Slack's page are the better fit. For a Mac on macOS 13, either copy works today, but the November 9, 2026 date is the one to plan around, and a browser window of its own is the fallback that keeps working after it.

Slack is also one of the services commonly listed by tools that turn websites into Mac apps; the list of supported services shows which ones come preconfigured with URL and icon, and the guide covers how such an app is created and kept current.

What to change first

Open Slack, choose About Slack from the Slack menu, and confirm which copy is installed and which macOS the Mac is running. If it is macOS 13, set up Slack in its own browser window before November 9, 2026, for example with Kagemusha, so nothing breaks on the day updates stop.