Slack Mac App Store listing: what it is and what it needs
Searching the Mac App Store for Slack returns one result from the company itself, sitting above a long tail of unrelated apps. That is unusual enough to raise a question. Plenty of large services have quietly abandoned their store listings, leaving a stale build in place while development moved to a direct download. Slack has not. The listing is current, it is free, and the build number on it matches what the company ships elsewhere. The real decision is not whether the listing is real. It is whether that copy, the copy from slack.com, or no installed app at all is the right fit for the Mac in question.
What the listing actually says
The fields on the listing answer most of what people arrive wanting to know.
| Field | Value |
|---|---|
| Name | Slack for Desktop |
| Seller | SLACK TECHNOLOGIES L.L.C. |
| Price | Free |
| Category | Business |
| Size | 168.1 MB |
| Requirement | Requires macOS 13.0 or later |
| Version | 4.52.155, released 1 September 2026 |
| First released | 23 January 2014 |
Two of those rows deserve a second look.
The release date on the current version is the point. A store listing that has been left behind shows a version number months or years behind the vendor's own download page. This one does not. The listing has also been in place since January 2014, which makes it one of the longer running business listings on the store rather than a recent experiment.
The requirement line is the other one, and it is where most of the trouble on this topic comes from.
App Store or slack.com
Slack offers both, and says so on its own download page for Mac, where a direct download button sits alongside a link to the Mac App Store. Neither is the unofficial route.
What differs is the plumbing around them rather than the application.
An App Store copy updates through the App Store, tied to an Apple Account, and appears in the purchase history of that account. On a Mac where the person using it does not have permission to run installers, or where software is expected to arrive through the store for auditing reasons, that is the practical choice, and often the only one.
A copy from slack.com updates itself. There is no Apple Account involved, the download is a disk image dragged to the Applications folder, and updates arrive from Slack's own update mechanism rather than being queued behind everything else waiting in the store.
Both land on the same requirement floor, so neither is a way around an old macOS. Choosing between them is a question about how the machine is administered, not about the software.
Why the floor moves, and on a schedule
Slack publishes its system requirements and states how often that page changes. The desktop entry currently reads macOS 13 or later, paired with Slack app version 4.44 or later. The cadence is the part worth writing down.
Slack updates these system requirements twice per year in May and November. Source: slack.com
A fixed schedule changes how to plan around it. This is not a vendor that raises its minimum without warning when a release happens to need it. There are two dates in the year on which the floor can rise, and a Mac sitting one major version above the current minimum has, at most, a predictable amount of time before the question returns.
For anyone maintaining a small fleet of Macs, that turns into a simple habit: check the requirements page after each of those two months, rather than discovering the change when someone's Slack stops updating.
The date already on the calendar
The schedule is not abstract. Slack publishes a support life cycle page listing which versions have reached, or are about to reach, the end of support, and the Mac column has a date on it.
macOS 13 and below reaches end of support on 9 November 2026. That is the same date on which Slack desktop app version 4.47.59 and below stops being supported. The two together describe exactly what happens on a Mac running Ventura after that day.
What follows is documented and differs between the two cases, which is the part people get wrong.
An operating system reaching end of support does not lock anyone out immediately. Slack states that access continues as long as a supported app version is in use, but app updates stop arriving, and Slack will no longer be available to download from the App Store. So the listing that prompted this search will simply not offer itself to that Mac any more.
An app version reaching end of support is stricter. Slack states that a notification appears prompting an upgrade, and that access is blocked until the upgrade happens. Since updates have already stopped on an unsupported operating system, the two conditions eventually meet, and a Mac that cannot move past macOS 13 loses access rather than degrading gracefully.
The underlying policy explains the pattern.
Slack desktop and mobile apps: 12 to 18 months from release. Browsers: 12 to 18 months from release. Mac, Windows and Linux: at least three months from the time the manufacturer stops OS support. Source: slack.com
Read alongside the store listing, that reframes the requirement line. Requires macOS 13.0 or later is true on the day of installation and has an expiry attached to it. For a Mac already on macOS 14 or later, none of this is urgent. For one on Ventura, the choice between the store copy and the direct download is much less important than the question of what happens in November.
When the Mac cannot run the app
This is the situation that sends people to the App Store listing in the first place, hoping the store copy has a lower requirement than the download. It does not. Both need macOS 13.
What remains is the browser, and Slack supports it explicitly rather than tolerating it. The published browser minimums are Chrome 137 or later, Firefox 139 or later, Safari 26 or later, and Microsoft Edge 136 or later.
There is one documented exception, and it is significant enough to decide the choice of browser.
Google Chrome and Firefox are the only browsers that support huddles. Source: slack.com
For a team that uses huddles daily, that sentence removes Safari and Edge from consideration on a Mac that cannot run the desktop app. Chrome or Firefox is the browser, and everything downstream follows from that.
The browser floor is worth reading carefully too, because it is higher than people expect. Safari 26 or later is a recent release, and Safari on a Mac is upgraded with the operating system rather than on its own. That means the browser route through Safari inherits exactly the macOS problem it was supposed to avoid. Chrome and Firefox update themselves independently of macOS, so on an older machine they reach a supported version when Safari cannot, which is a second and quite separate reason the answer lands on those two.
Slack applies the same 12 to 18 month support window to browsers as it does to its own apps, so these numbers move as well. The difference is that a self updating browser crosses each new floor without anyone noticing, while an operating system does not.
Supported in a browser is not the same as being an app
Running Slack in a tab solves the compatibility problem and creates a different one. A tab has no Dock icon, no place in Command+Tab, and no protection from being closed with everything else at the end of the day. For a tool that is checked dozens of times a day, that is a real cost rather than an aesthetic complaint.
The obvious fix is to install the site as an app, and here Slack's web client behaves differently from most services. It does not publish a web app manifest, which is the file browsers read to decide a site can be installed as a standalone application. Reddit publishes one. Slack does not.
The consequence is narrow but worth knowing. No browser will offer an install prompt in the address bar for Slack, because there is nothing to prompt from. The generic commands still work: Chrome installs any page as an app from the More menu under Cast, save, and share, and Edge does the same from More tools, then Apps. What comes out is assembled from the favicon and the current URL rather than from anything the site declared, so the icon and the launch page are worth checking afterwards rather than assuming.
| Route | Works without macOS 13 | Huddles | Dock icon |
|---|---|---|---|
| Slack for Desktop, App Store | No | Yes | Yes |
| Slack for Desktop, slack.com | No | Yes | Yes |
| Chrome or Firefox tab | Yes | Yes | No |
| Chrome window installed as an app | Yes | Yes | Yes |
| Safari web app added to the Dock | Yes, macOS 14 or later | No | Yes |
The case for a window even when the app runs fine
The browser route is not only a fallback. Two situations make it the better arrangement on a Mac that meets every requirement.
The first is more than one workspace under separate accounts. The desktop app handles multiple workspaces on one account well, but a contractor signed in to several clients under different email addresses ends up switching rather than seeing both. Separate app windows built on separate browser profiles keep each session in its own icon.
There is also the case of a Mac that has aged past the desktop app but is otherwise fine. Rather than treating the browser as a temporary indignity, giving the web client a permanent window turns it into the arrangement it is going to be for the rest of that machine's life. Nothing about that setup expires on a fixed date, because the browser underneath keeps updating on its own schedule.
The second is a machine where the desktop app is not permitted but the browser is, which is a common shape for managed laptops and shared workstations. A site to app tool produces the window without installing anything the policy is aimed at, since what it creates is a launcher pointed at a browser that is already approved. Which profile it uses is the only decision that matters, and the setup guide covers it.
What to change first
Check the macOS version before anything else, because both installed copies need macOS 13 and neither store nor download changes that. If the Mac qualifies, take whichever copy fits how the machine is administered, since the version on the App Store listing is current. If it does not qualify, use Chrome or Firefox so huddles keep working, then give that tab its own window and Dock icon with Kagemusha rather than leaving it among forty others.
Frequently asked questions
Is the Slack app on the Mac App Store the official one?
Yes. The listing is published by SLACK TECHNOLOGIES L.L.C., it is free, and Slack's own Mac download page links to it alongside the direct download. The version on the store matches what Slack ships elsewhere, so it is not an abandoned build.
What is the difference between the App Store version and the download from slack.com?
Mainly how updates arrive and how the machine is administered. The store copy updates through the App Store and is tied to an Apple Account, while the direct download updates itself. Both have the same macOS requirement, so neither runs on an older system than the other.
What macOS version does Slack for Desktop need?
macOS 13 or later, paired with Slack app version 4.44 or later. That floor is dated: Slack's support life cycle page lists macOS 13 and below as reaching end of support on 9 November 2026, so a Mac on Ventura should be planned around rather than installed on.
Can Slack be used on a Mac that is below macOS 13?
Yes, in a browser. Slack supports Chrome 137 or later, Firefox 139 or later, Safari 26 or later, and Edge 136 or later. Huddles are supported only in Chrome and Firefox, so pick one of those if calls matter, and consider putting it in its own window so it is not buried in tabs.