Running multiple Discord accounts on a Mac

Two accounts, one Mac, and a client that shows one of them at a time. That is the situation almost everyone lands in: a personal account built up over years, and a second one that exists for a job, a client server, a moderation role, or a community that should not see the first. The desktop client has a feature for this, it has had one for years, and it does not do the thing most people assumed it did. Knowing exactly where its line sits saves a lot of guessing about why a message went to the wrong place.

What the built in switcher actually does

The Account Switcher lives behind the avatar at the bottom left of the client. Clicking it and choosing Switch Accounts moves the whole window to another logged in account.

The capacity is fixed and documented.

You can log into five accounts using the Account Switcher. Source: support.discord.com

Five stored logins, one of them active. The switch happens inside the same window, so the second account replaces the first rather than sitting beside it. Two things get discarded on the way across. Appearance preferences such as font scaling reset, and any message typed but not sent is gone. Neither is a bug report worth filing; both are documented behaviour of the feature.

There is a policy detail attached to it as well. Discord states that when enforcement action is taken against a user for a Terms of Service or Community Guidelines violation, that action can extend to any account the company can determine belongs to the same person, including accounts entered into the switcher. That is worth reading before deciding that a throwaway account is genuinely separate from a main one. It is not a reason to avoid a second account, which is ordinary and common. It is a reason to treat both as belonging to the same person, because that is how they are treated on the other side.

The switcher also does not advertise itself. Other users are not shown which accounts sit behind it, and privacy settings chosen per account stay as they were set.

Serial switching is not what most people mean

The gap between the feature and the request is one word: simultaneous.

Switching solves the problem of typing a password four times a day. It does nothing for the problems that come from two accounts being live at the same time. A moderator watching a report queue on one account while answering direct messages on another is doing two jobs at once, not alternating between them. A freelancer sitting in a client server has to notice a mention there while working in a personal server. A translator moving text between two communities needs both windows visible to copy anything across.

There is also a quieter cost. Notifications belong to whichever account is currently loaded. Everything arriving for the other four is invisible until a switch happens, and after the switch the first account goes quiet in turn. For an account that only matters once a week that is fine. For an account that carries work, it means the client has become a thing to remember to check, which is exactly the failure mode a notification is supposed to prevent.

Anyone whose real requirement is two live windows has to leave the switcher behind, because the constraint is structural. One process, one window, one session.

The second account cannot borrow the first one's phone number

This is the constraint that catches people after the windows are already set up, and it is worth handling before rather than after.

Phone numbers on Discord exist for login and anti abuse verification, and the pairing is exclusive.

Only one number can be connected to an account at a time. Once a number has been removed, there is a waiting period before the number can be used on an account again. Source: support.discord.com

Two consequences follow. A number attached to a main account cannot also verify a second one, and moving it across is not instant, because removing it starts a waiting period before it can be attached elsewhere. Bouncing a single number back and forth between a personal account and a work account is therefore not a workable routine.

That matters because plenty of servers require phone verification before a new member can post. An account that reads fine may turn out to be unable to write in exactly the server it was created for, and the discovery usually happens at the worst moment. Deciding which of the two accounts holds the number, based on which one has to post in verified servers, is a two minute decision that prevents a long support conversation later.

Email addresses behave differently and are the easier half of the problem. Each account needs its own, and a plus suffix on an existing address is usually enough to keep the inbox in one place while keeping the accounts distinct.

The support line under the desktop client is moving

There is a second reason to look at this now, unrelated to accounts.

The current minimum for the Mac client is macOS 12, listed on the official requirements page alongside Windows 10 and the supported Linux distributions. That floor is being lifted.

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

The existing installed client may keep working after that date, but it stops receiving updates, and stability past that point is not guaranteed. The stated route for anyone who cannot move to macOS 13 or later is not a patched build. It is the browser.

That is a notable thing for the company itself to recommend, because it settles a question people often argue about. The browser version is not a degraded fallback that support staff steer people away from. It is the supported path for a Mac that has aged out of the client. On a 2017 iMac or an Intel MacBook Air that stopped at macOS 12, the browser is the whole answer, and account separation there works differently and rather better than in the client.

What the browser gives up, and what it does not

Being honest about the trade is the only way to make this decision once.

The published browser minimums are Chrome 108 or later, Firefox 142 or later, Edge 86 or later, Opera 72 or later, and Safari 15.4 or later. Discord also states plainly that running it in a mobile browser is not supported, so this route is a desktop route only.

Text, voice, servers, threads, roles, and direct messages all behave normally. The differences show up at the edges. Push to talk cannot listen to a key press while another application is in front, because a web page does not get global keyboard access. Rich presence, the line that shows a game or an editor on a profile, comes from the desktop client. Screen sharing with application audio is the fussiest area: audio capture is supported on the Windows and macOS clients, in Chrome, and on mobile, and is not available in every browser, so a workflow built on sharing a window with its sound needs testing rather than assuming.

For a second account that exists to read announcements, answer clients, or moderate a channel, none of those limits touch the daily work. For a primary gaming account, several of them do. That split, rather than any general verdict, is what decides which account belongs where.

Four routes to two accounts open at once

Route	Both accounts live at once	Logins stay separate	Notifications for both	Needs the client
Account Switcher	No	Yes	Active account only	Yes
Private browsing window	Yes	Yes, until it closes	Yes, while open	No
Second browser profile	Yes	Yes	Yes	No
One site app per account	Yes	Yes	Yes, per app	No

Private browsing is the zero setup option and the worst daily one, because the login goes away with the window. It is right for a one hour visit to a server and wrong for anything recurring.

A second browser profile keeps the login and separates cookies properly. Its weakness is navigation. Both profiles open browser windows that look alike in the app switcher, both carry the same icon, and finding the right one becomes a small hunt several times a day.

Building one standalone app per account fixes the navigation problem, because each account becomes its own entry in the Dock with its own icon, its own window, and its own isolated profile underneath. The Features page covers the profile isolation that makes this work: cookies, session, history, and cache stay inside the app that owns them, which is the same mechanism a second browser profile uses, wrapped in something that can be clicked directly.

Which accounts earn their own window

A separate window is not free. It occupies a Dock slot, it fetches messages in the background, and it is one more thing to update. Three questions sort the accounts worth it from the ones that are not.

Does anything arrive on this account that needs to be seen within the hour? An account that carries client messages or on call escalations does. A community account followed out of interest does not, and belongs behind the switcher.

Would mixing it with the main account cause an actual problem? Posting from a personal handle in a client server is the classic version of this. Where the two identities must not be confused, the separation should be physical rather than a habit of checking the avatar before pressing send.

Is it opened most days? Anything opened weekly is better served by the switcher and its five slots. Daily use is where the cost of switching, and of losing an unsent draft on the way across, adds up into something worth spending a Dock slot on.

Most people end with two: a main account in the client, and one work or moderation account in its own window. The Supported services list shows how common that shape is across chat services generally, since the same account separation problem appears in every one of them.

Setting up the second window once

Each account window is an independent session, so it needs its own five minutes.

Grant notification permission inside that window rather than assuming it inherited it, because permission is stored per profile and a silent second account is the most common complaint after this setup. Sign in and turn on the setting that keeps the session, so the login survives a restart. Give the window a name and an icon that distinguish it at a glance, since two identical icons in the Dock rebuild the problem the separation was meant to solve.

If a password manager or a translation extension is part of the workflow, install it in that profile too. Extensions are per profile, and the second window starts empty. That is a one time cost and worth paying deliberately, rather than discovering it mid conversation.

What to change first

Pick the account that causes the most switching in a week and give that one its own window, leaving everything else where it is. Run it for a few days before adding a third, because the pattern of what actually arrives on each account is more useful than any plan made in advance. When the count grows past two, a builder such as Kagemusha handles the icon, profile, and notification setup that stops being quick to repeat by hand.