The Discord app with multiple accounts on one Mac

The phrase "the Discord app" hides a problem, because there are three of them and they do not agree about multiple accounts. The desktop app has a built in account switcher. The browser client mostly matches it and loses specific features. The mobile app does not officially have the switcher at all. Anyone trying to run two Discord accounts from one Mac is really choosing between those surfaces, and the choice is easier once the documented limits are on the table.

What the account switcher holds, and what it drops

Discord documents the feature narrowly. The Account Switcher lets a user with multiple accounts access and switch between them on desktop, reached by clicking the avatar image at the bottom left of the app and choosing Switch Accounts. Secondary accounts are added through Switch Accounts, then Manage Accounts, then Add an Account, entering the credentials for each.

Three published details matter more than the mechanics.

The ceiling is five. Discord states that five accounts can be logged in through the Account Switcher. That is generous for a work and personal split and restrictive for anyone managing accounts on behalf of several communities.

Some preferences reset on each switch. The documentation names appearance settings such as font scaling among the items that reset. This is the detail that makes frequent switching feel wrong without being obviously broken: the interface subtly changes each time.

Drafted messages are not kept. Discord states plainly that drafted messages will not be stored when switching between accounts. A half written reply in one account does not survive a trip to the other, which is a real cost for anyone who switches mid conversation.

Two things it does not do are worth noting on the reassuring side. The switcher does not show other users which accounts are being switched between, and privacy settings chosen for each account do not change because the switcher is in use.

The rule to read before creating the second account

One paragraph in Discord's own documentation should decide whether a second account is created at all. Asked whether action taken against one account might extend to others, Discord answers yes: if a user violates the Terms or the Community Guidelines, action may be taken on any account that can be determined to belong to that user, and this could include accounts entered into the Account Switcher. The documentation adds that the more severe the violation, the more likely action spreads across a user's accounts.

The practical reading is that accounts linked in the switcher are linked in the eyes of enforcement. A second account is a separation of context, not a firewall against consequences. For a work account that a team depends on, that is an argument for keeping anything risky far away from it rather than for relying on the boundary.

The mobile app is a different situation

Searching for multiple accounts in the Discord app turns up a lot of results that look official and are not. Discord's own article on the Account Switcher describes it as a desktop feature. The pages asking for the same thing on phones are community feedback posts, some of them years old, several of them explicitly noting that the desktop and web clients have the switcher while the mobile app does not.

That matters for a practical reason. Advice written for mobile, including instructions to find an Add Account option under account settings, describes either another platform or an unreleased experiment. On a Mac, the routes that exist are the desktop app, a browser, and combinations of the two.

Switching is a swap, not two sessions

The switcher changes which account the app is showing. It does not run two accounts at once, and the consequences are all about notifications.

One Dock icon carries one badge. A mention in the account that is not currently active does not raise a badge on the Discord icon, because that session is not the one the app is holding. The result is a routine where the switch happens on a schedule rather than in response to anything, which is exactly the behavior that makes people describe Discord as a time sink.

Voice makes it stricter. A voice channel belongs to the session that joined it, so switching accounts leaves the call. For anyone whose second account exists to be present in a community while working in the first, switching is not a workaround at all.

Search is bounded the same way. A message received by the account that is not active cannot be found from the account that is, so the ordinary habit of searching for a phrase and letting the client find it breaks down into remembering which identity received the thing being looked for. That is a small cost on any single occasion and a large one accumulated across a week.

Running two at the same time on a Mac

Two sessions at once requires two containers, and the options differ in what they give up.

Route	Second session runs in	What it loses
Desktop app plus a browser tab	A normal browser window	Keybinds, and push to talk only works while the window has focus
Desktop app plus a second browser profile	A separate browser profile with its own cookies	Same browser limits, plus a second window to manage
Desktop app plus a dedicated single site window	An app style window for one service	Same browser limits, better notification behavior
A second macOS user account	A full second desktop	Fast User Switching, so only one is visible at a time

The browser limits are documented rather than folklore. Discord's note on keybinds states that the feature is only available on the desktop version of the app, and that keybinds cannot be set on the mobile or browser client. Push to talk in a browser also depends on the window having focus, which is the same restriction seen from a different angle: the browser does not hand a web page a global hotkey.

The arrangement that follows from this is straightforward. The account that needs voice, push to talk and hotkeys belongs in the desktop app. The account that mostly needs to be readable and to raise a notification belongs in the second container. Choosing which account gets the desktop app is a more useful decision than choosing a clever tool.

Making the second container behave on macOS

A second session only helps if its notifications arrive correctly, and that takes three settings rather than one.

The browser has to be allowed to show notifications for the site, which is a per site permission granted the first time Discord asks and easy to have refused years ago in a different context. In Chrome that setting sits under Privacy and security, then Site settings, then Notifications, and a domain listed under the blocked heading explains a silent second account better than anything else.

macOS has to be allowed to show them too. Under System Settings, then Notifications, the browser appears as an application, and the alert style chosen there applies to every site running inside it. This is the weak point of the browser route: notifications from the second Discord account and from every other site in that browser are attributed to the browser, styled the same way, and grouped together. A dedicated window for one service, rather than a tab among many, is what separates them again.

Then the account itself has to be configured to send anything. Discord's per server notification settings are stored per account, so a second account added through the switcher starts from defaults, and a server muted in the first account is not muted in the second. Setting the second account to mentions only, server by server, is usually the difference between a useful signal and a reason to turn notifications off entirely.

One more detail catches people who split a work account out of a personal one. Server specific settings, muted channels, folder arrangements and the order of the sidebar all belong to the account, not to the app, so none of it transfers. Rebuilding that arrangement in the second account takes twenty minutes and is worth doing deliberately rather than discovering piece by piece over a fortnight.

Sometimes the cap is the real reason, and a second account is the wrong fix

A second Discord account is often created to get around a limit rather than to separate a persona, and the limits are published. A base account can be in 100 servers, and Nitro raises that to 200. The file sharing limit runs 10MB on a base account, 50MB on Basic and 500MB on Nitro. The sidebar holds 100 direct message conversations, and the friends list holds 1,000 entries.

Reading those numbers changes the decision. Someone who joined a second account because the server list was full is paying for it with a switch several times a day, and a subscription that doubles the cap removes the reason entirely. Someone who created a second account to keep a client community away from a gaming identity has a genuine separation and no cap to raise.

The test is simple enough to apply in a minute. If the second account exists because of a number, check whether the number moves. If it exists because of an audience, it stays, and the question becomes where to put it.

Discord is rarely the only account that doubled

An account that splits in Discord has usually already split elsewhere. The same person tends to hold two Google accounts, two Slack workspaces, two Notion logins, and the switching cost is paid once per service, several times a day, with a different mechanism in each. Slack has workspace switching, Google has account switching, Discord has the switcher described above, and none of them shares state with the others.

That is the point at which the problem stops being about Discord. When each service keeps its own window and its own session, a second account is another window rather than another mode of the same window, and the badge on it means what it says. A browser built so that each web app holds its own session treats a second Discord account as an ordinary case rather than a workaround, and checking which services are covered against the supported app list is faster than assembling separate profiles by hand.

The desktop app still earns its place for voice, screen sharing and hotkeys. Everything that is mostly reading and replying does not need a native application, and treating it as if it did is what forces the switching in the first place.

What to change first

Decide which single account belongs in the desktop app, based on which one needs voice and hotkeys, and put every other account in its own window rather than behind the switcher. Before adding an account at all, check whether the reason is a published cap that a subscription raises. If the switching between windows is what actually costs the day, that is a window arrangement problem, and SpaceDeck is built for that layer.