Second Discord account on a Mac: running both without logging out

The reason for a second Discord account is almost always the same: one identity belongs to a job, a client community or a project people can find, and the other belongs to everything else. Keeping them in one account is not really an option once a username has been given out professionally.

Discord supports this officially, and the feature is easy to miss because it sits behind an avatar rather than in settings. What it does not do is run two accounts at once, and that distinction is the whole subject. The switcher solves signing in. It does not solve being present in two places at the same time, and the difference matters if the second account is the one that gets messaged during working hours.

What the account switcher does

Discord's own support material is short and specific. The Account Switcher lets a user with multiple accounts access and switch between them on desktop. To reach it, click the avatar image at the bottom left of the Discord app, then select Switch Accounts.

The published limit is five accounts. Discord states that five accounts can be logged into using the Account Switcher, which is well beyond what most people need and worth knowing before assuming the ceiling is two.

Two things it does not do are stated just as plainly. It does not reveal to other users which accounts are being switched between, so there is no visible link created by using it. And it does not change the Privacy and Safety settings chosen for each account, which stay as they were set.

That is the feature in full. Everything else people want from a second account is outside it.

Switching is not the same as running both

Three consequences of switching are documented, and together they explain why the switcher feels insufficient to some people and perfectly adequate to others.

Some preferences reset when switching between accounts. Discord names appearance settings such as font scaling as examples. On a Mac where the interface has been tuned once and left alone, that is a small recurring irritation rather than a problem.

Drafted messages are not stored when switching accounts. This one is sharper than it looks. A half written reply in one account disappears on switching to the other, which turns every switch into a decision about whether the current message is finished.

And only one account is present at a time. The switcher changes which account the app is signed in as, so notifications, mentions and direct messages for the other account arrive at an app that is not currently showing them. Anyone whose second account is the professional one will discover this the first time a client message waits four hours.

If the second account is for reading occasionally, the switcher is the whole answer. If the second account needs to be reachable while the first one is in use, the switcher is the wrong tool and nothing in Discord's settings changes that.

Making the second account: one email each

The practical blocker when creating the second account is an error message rather than a setting, and it is worth knowing in advance.

Discord allows exactly one email address per account. Its support documentation on the "Email is Already Registered" error states that the system only allows one email address to be tied to an account, which means multiple Discord accounts cannot share one email address. Attempting to register an address already in use returns that error, and the advice is to log into the existing account rather than to keep trying.

So the second account needs its own address. On a Mac there are two tidy ways to get one without creating another mailbox to check. A Gmail address accepts a plus suffix, giving a distinct address that delivers to the same inbox. An iCloud account can generate a Hide My Email address, which is a real forwarding address rather than an alias. Either produces an address Discord will accept, while keeping the number of mailboxes the same.

One thing not to do is reuse a work address for a personal account. The account that outlives the job should not depend on a mailbox that stops existing when the job does.

The part worth reading before creating an alt

Discord publishes one answer in its switcher documentation that deserves more attention than it usually gets, because it changes the risk calculation for anyone making a second account to get around something.

If a user violates Discord's Terms of Service or Community Guidelines and the Trust and Safety team decides to act, action may be taken on any account the team can determine belongs to that user. The documentation says explicitly that this could include accounts entered into the Account Switcher, and that the more severe the violation, the more likely action is taken across a user's accounts.

Read plainly, that means the switcher is a convenience feature rather than a separation feature. Two accounts used for two legitimate contexts have nothing to worry about. A second account created to continue after a ban on the first is not a fresh start, and putting both into the same switcher is the opposite of hiding the connection.

This is also the clearest reason to think about what each account is for before setting either of them up. Separation of identity for the benefit of other people is what Discord supports. Separation from Discord itself is not on offer.

Running both at once on a Mac

Because Discord holds one session per app instance, having both accounts live at the same time means giving each one its own session store. There are three ways to do that on a Mac, and they differ in how much work they create.

The quickest is the desktop app for one account and the browser for the other. Discord runs as a web application, so signing in at a browser gives a second live session immediately, with no installation. Its weaknesses are the ones every browser tab has: the session sits behind whatever else is open, and closing the window closes the presence.

Two browser profiles is the next step up, since each profile has its own cookie store and can therefore hold its own Discord session. That works, and it is tiring for the reason every profile based workaround is tiring. Two identical icons in the Dock, notification permissions granted twice, and no reliable way to tell which window belongs to which account at a glance.

The third is a browser built around the limit rather than working against it, loading each application in its own container so that two Discord sessions sit side by side as separate windows with separate notifications.

Approach	Both accounts live at once	Notifications per account	Cost
Account switcher	No, one at a time	No, only the active account	Free and built in, drafts lost on switch
Desktop app plus browser	Yes	Partly, depending on the browser	Free, the browser session is easy to lose
Two browser profiles	Yes	Yes	Two icons, everything configured twice
A browser that keeps each web app in its own window	Yes	Yes, per window	A tool to install, sessions stay separated by design

The last row exists specifically because one browser profile holds one signed in session per service. Tools in that category give each application its own cookie container, which is how the same service stays signed in twice. What that involves is on the Features page, grouping containers by role rather than by service is covered under Workspaces, and which services load cleanly that way is listed on Supported apps.

Decide which account owns what before splitting

The setup that goes wrong is not the one with the wrong tool. It is the one where both accounts end up half responsible for the same things.

Server ownership is the clearest example. A server created by the personal account and later used for client work is permanently tied to an identity that was not meant to be professional, and moving it means transferring ownership rather than renaming anything. Deciding which account creates a server is a one time choice that is awkward to reverse.

Direct messages behave the same way. A conversation started from one account stays with that account, so a contact who first messaged the personal identity will keep arriving there no matter which account is nominally the work one. That is an argument for giving out one username deliberately rather than whichever was signed in at the time.

Paid features and per account settings follow the account too, not the machine. Anything configured once on one account has to be configured again on the other, which is a reason to keep the second account deliberately minimal rather than a mirror of the first.

The test worth applying is simple. If a thing needs to survive a change of job, it belongs to the personal account. If a thing needs to be handed over when a job ends, it belongs to the work one. Anything that fails both tests probably does not need a second account at all.

Notifications are the last piece, and they are the reason this question usually gets asked in the first place. macOS delivers notifications per application, so an account living in a browser window competes with every other tab in that window, while an account living in its own window can be muted or surfaced on its own. Two accounts sharing one app share one notification stream, whatever the arrangement behind it.

Discord is rarely the only account that doubled

It is worth checking whether Discord is the whole problem before changing anything, because it usually is not.

Anyone with two Discord accounts for work and personal reasons tends to have the same split elsewhere: two Google accounts, two chat workspaces at a second service, two project tools, sometimes two sign ins to the same dashboard. Each of those hits the same limit, because identity in a browser is held in cookies and one profile keeps one session per service.

Solving it once per service produces a collection of workarounds that each need maintaining. Solving it at the level of the window solves it for every service at once, which is the only real argument for changing tools rather than adding another browser profile.

There is also a quieter cost to the switcher approach that only shows up after a few weeks. Every switch is a small decision, and small decisions made dozens of times a day are where attention actually goes. The reason two live windows feel better is not that they save clicks. It is that they remove the decision entirely.

What to change first

Start with the switcher, because it is free, built in, and enough for a second account that is read rather than answered. Give that account its own email address using a plus suffix or a Hide My Email address, and keep both accounts to their own contexts.

If the second account needs to be reachable while the first one is in use, the switcher cannot do it and the unit that has to change is the window, which is what SpaceDeck is built around. The Pricing page is the quickest way to judge whether that step is worth taking.