Discord Mac app: what changes when macOS 12 support ends

The Discord Mac app is a free download from the Discord download page: click Download for Mac, open Discord.dmg, and drag the Discord logo onto the Applications folder. The part that changed this autumn is which Macs can keep it updated. Since September 17, 2026, Discord no longer supports the desktop client on macOS 12 Monterey, so a Mac needs macOS 13 Ventura or later to keep receiving updates. A Mac that cannot move past Monterey still has a supported route: the browser version of Discord. This guide, checked against Discord's and Apple's help pages on October 18, 2026, covers what the installed client does that the browser cannot, what the browser does that the client cannot, and how to pick a setup for an older or newer Mac.

Where the Discord Mac app comes from

There are three places a Mac user tends to look, and only one of them is the desktop client.

The official source is the download page on discord.com. Discord's own Desktop Installation Guide gives the macOS steps in three lines: press Download for Mac, open the Discord.dmg file, and drag the Discord logo over the Applications folder in the window that appears. After that, the first launch asks for a sign in or a new account. There is no charge for the client. Nitro is a separate subscription and is not required to install or use the app.

The second place is the App Store. The Discord listing on the App Store, checked on October 18, 2026, is labeled for iPhone and iPad, requires iOS 16.0 or later, and is listed as free with in-app purchases. It is the mobile app. Searching the Mac App Store for Discord does not produce the desktop client, and that confusion is the source of a lot of forum threads that start with "the App Store version looks wrong".

The third place is a third party mirror that hosts older builds. These pages exist because people on older macOS versions go looking for a build that still launches. Discord itself addresses that need directly, which is covered in the next section, so there is no reason to take an installer from anywhere other than Discord.

The download page also offers a Public Test Build under the heading Feeling experimental. It installs as a separate app and receives features before the regular client. It follows the same macOS requirements as the main build, so it is not a way around the version floor.

The macOS floor moved twice in 2026

Discord publishes a page titled What are the OS/system requirements for Discord? and separate known issue notices for each macOS version it retires. Read together, they show a floor that rose twice this year.

macOS version	Status of the Discord desktop client
macOS 10.15 Catalina	Support ended earlier, per a separate known issue notice
macOS 11 Big Sur	Support ended June 15, 2026
macOS 12 Monterey	Support ended September 17, 2026
macOS 13 Ventura and later	Supported, receives updates

The macOS 12 notice is short and specific.

As of September 17, 2026, Discord will no longer be supported on macOS 12. Source: support.discord.com

One detail is worth knowing before reading the requirements table. On October 18, 2026, the desktop table on the requirements page still read "MacOS 12+ (Monterey)" for Mac. The known issue notice is the newer statement, and it says plainly that updates and support now require at least macOS 13. When the two disagree, the dated notice is the one that describes the current state.

The macOS 11 notice follows the same pattern with a June 15, 2026 date and macOS 12 as the then minimum. Anyone who skipped the first change and is still on Big Sur is now two steps below the floor.

What happens to the installed client on macOS 12

The notice answers the obvious question in its own FAQ. A client installed before the cutoff may keep its basic functions, but functionality and stability are not guaranteed because it no longer receives updates.

That has a practical consequence that catches people out. Discord ships updates through the client itself. On an unsupported macOS, the risk is not that the old app stops instantly. The risk is that a newer build gets installed over it and then refuses to launch. Discord addresses exactly this case in a note at the top of both the macOS 11 and macOS 12 notices: if Discord no longer launches, install the specific version linked in the notice. That build keeps working without updating, and installing anything newer on top of it prevents Discord from launching again.

So there are three states a Monterey Mac can be in today.

The client still opens and updates have stopped. It works for now, with no guarantee about how long or how well. Voice and video are the parts most exposed, since they depend on server side changes that an old client never receives.

The client fails to launch after an update. The fix Discord gives is the pinned build linked from the notice, followed by not reinstalling from the regular download page.

The client was never installed. Discord now ties updates and support to macOS 13 or later, so starting fresh on Monterey means starting on an unsupported client. The browser route is the realistic starting point.

The same notice gives the supported way out in its second FAQ entry: if the computer cannot be upgraded right now, the browser version of Discord can be used, as long as the browser meets the minimum requirements. For a Mac that Apple no longer offers newer macOS versions for, that line changes the question from keeping the old client alive to choosing which browser setup should hold Discord.

What only the desktop client can do

Moving Discord to a browser is a fair trade for some uses and a poor one for others. Three capabilities decide which.

Custom keybinds. Discord's Commands, Shortcuts, and Navigation Guide separates ordinary keyboard shortcuts, which work in the browser and desktop versions, from custom keybinds, which it states are only available on the desktop version. Push to talk bound to a key that works while another app is in front is a custom keybind. In a browser, a key only reaches Discord while that window has focus.

Stream quality controls. The Go Live and Screen Share article carries a tip that when streaming through a browser, the stream quality cannot be adjusted. Resolution and frame rate stay where the browser puts them.

Audio during a screen share. The same article lists where audio can be captured: the Windows desktop app, the macOS desktop app, the Chrome browser, and the mobile clients. It adds that application audio cannot be shared on other browsers or on Linux. Safari and Firefox are not on that list, and Chrome is.

One feature people expect to lose was never available on a Mac. Discord's Game Overlay 101 states that the overlay is compatible with Windows 10 and 11 only and does not function on macOS or Linux. Leaving the Mac client does not cost an overlay.

The split that follows is fairly clean. A Discord used with a headset during games, with push to talk held down in another app, belongs in the desktop client on a supported macOS. A Discord used for a work community, a study group, a client server, or a hobby server that runs mostly on text and the occasional call loses very little in a browser.

What the browser route offers on an older Mac

The browser minimums on Discord's requirements page, checked on October 18, 2026, are Google Chrome 108 or later, Firefox 142 or later, Opera 72 or later, Microsoft Edge 86 or later, and Safari 15.4 or later. The same page notes that older browsers may lack newer features, and that running Discord in a mobile browser is not supported.

The point of those numbers is that a browser updates on its own schedule, separately from Discord's installer. A Monterey Mac can often keep a current Chrome, Edge, or Firefox for longer than Discord keeps accepting the operating system. That is why the browser route works for the machines the client has left behind.

Before choosing, check two things. Open the Apple menu and choose About This Mac to read the macOS version. Then check whether that Mac can move to macOS 13 at all. Apple's guide to upgrading macOS covers how to see which versions a given Mac can install. If the Mac can upgrade, upgrading and staying on the official client is the simplest answer, especially for anyone who relies on custom keybinds. If it cannot, the browser route is the long term setup rather than a stopgap, and it is worth setting up properly.

Text chat, threads, file uploads, reactions, and notifications behave the same in the browser as in the client. Voice calls work too. The differences sit around the edges of voice and streaming, as the previous section listed.

Four ways to hold Discord on a Mac

Once the browser version is on the table, the real question is what window it lives in. The options behave differently.

Setup	Custom keybinds	Audio in screen share	Works on macOS 12	Separate login from the browser
Official desktop client	Yes	Yes	No longer supported	Yes
Tab in Chrome	No	Yes	Yes, with a current Chrome	No
Safari web app (Add to Dock)	No	No	No, needs macOS Sonoma 14	Yes
Standalone app built on an installed Chrome	No	Yes, on the Chrome engine	Yes, if the tool supports macOS 12	Yes

The Safari option deserves a fair description. Apple's page Use Safari web apps on Mac says the feature starts with macOS Sonoma 14, that a web app shares no browsing history, cookies, or website data with Safari, and that the Dock icon can show a badge for unread notifications. Those are real advantages on a newer Mac. The Sonoma requirement rules it out on exactly the Monterey machines this article is about, and Safari is not on Discord's list for capturing audio in a screen share.

A tab in Chrome is the zero setup answer. It meets the browser minimum and carries audio in screen shares. It also disappears when the browser quits, sits among every other tab, and does not appear on its own in Cmd+Tab.

The fourth row is a site to app tool that builds a standalone Mac app around one URL using a browser already installed on the Mac. Built on Chrome, the window gets Chrome's engine, so it stays on the supported side of Discord's audio list, while behaving like an app: its own Dock icon, its own place in Cmd+Tab, and a window that stays open when Chrome is quit. What it cannot add is custom keybinds, because those belong to the desktop build and not to any window around the web version.

Setting up the browser route without losing notifications

The most common complaint about Discord in a browser is that it goes quiet. That is usually a permission, not a fault.

The web version asks for notification permission the first time. If that prompt is dismissed or denied, desktop alerts stop until the permission is granted again in the browser's site settings, and macOS also has to allow notifications for whichever app is showing them, in System Settings under Notifications. With a Safari web app or a standalone app, respond to the prompt inside that app's window rather than in the main browser, so the alerts carry that app's name and settings.

Two other details save time. Discord's guidance for the browser route assumes the browser is kept current, so leave automatic updates on. And because the web version signs in through the browser's cookies, a separate window with its own profile keeps a work Discord account and a personal one apart without signing either out.

That last point is where a site to app tool earns its place for people who run more than one community. The tool described on the features page gives each app its own browser profile, so two Discord apps made from the same URL hold two separate sessions side by side. Discord is already one of the supported services, with the URL, icon, and name filled in, and the pricing section lists a free plan for up to three apps, which is enough to try a Discord window before deciding anything.

What to change first

Check the macOS version first. On macOS 13 or later, keep the official client and nothing needs to change. On macOS 11 or 12, move Discord to the web version now, in a current Chrome, and give it a window of its own with Kagemusha if it should behave like an app instead of a tab.