How to Log Into Multiple Google Accounts on a Mac

Adding a second Google account takes about four clicks. The account menu opens, Add account appears, credentials go in, and the second inbox loads. The part that goes wrong comes later: a calendar invite opens under the wrong identity, a shared Drive folder returns a permission error that makes no sense, or an admin console refuses to load at all. None of that is a sign-in failure. It is the result of what a second sign-in does to the session that was already there.

Understanding that difference is the whole job. Signing in twice does not give a browser two identities. It gives one browser session a list of accounts, plus a rule for which one to use when nothing in the request says otherwise.

What the second sign-in actually adds

Google's own instruction for adding an account is short. From the account picture at the top right, choose Add account, then sign in. The result is not a separate browsing context. Both accounts now share the same cookie jar, the same extensions, the same saved passwords, and the same download folder. What changes is that Google's servers now know that two authenticated identities are attached to this browser, and every Google property gets to pick between them.

Picking is the problem. Google states the rule plainly on its multiple sign-in help page:

Google might apply settings from your default account.

That default is not something chosen deliberately. As the same page puts it, in many cases the default account is the one signed in with first. So the account that happens to be first in a browser on a Monday morning quietly becomes the arbiter for every ambiguous request that follows, for as long as that browser session lives.

Three categories of request are ambiguous in practice. Links opened from outside the browser, such as an email client or a Slack message, carry no account hint. Downloads and print jobs started from a Google surface inherit the session rather than the tab. Third-party sites using Sign in with Google present the account chooser, but pre-select the default. Each is small. Together they are the reason people describe multi-account browsing as unpredictable.

Where the number in the URL comes from

Once a second account is signed in, Google addresses each one by position rather than by name. The first account signed in becomes index 0, the next becomes 1, and so on, which is why a Gmail address looks like mail.google.com/mail/u/0/ and a second inbox looks like /u/1/.

Two things about that index matter for anyone bookmarking or scripting.

The index is per browser session, not per account. It reflects the order of sign-in in this browser, so the same work address can be /u/1/ on a laptop and /u/2/ on a desktop. A bookmark that hard-codes an index will open the wrong mailbox on the other machine.

The index also shifts. Signing out of one account and back in re-orders the list. Bookmarks built the week before then point at a different person's inbox, which is harmless for reading and less harmless for replying. The safer bookmark form uses the address itself rather than the position, so that Google resolves the account instead of the browser guessing at it.

The index also explains a failure that reads as a bug. Opening an indexed link while that position is empty, which happens after signing out of one account, sends the browser to whichever account currently occupies the slot rather than to an error page. Nothing warns the reader, because from Google's point of view the request was valid. The first sign that something is wrong is usually a reply sent from the wrong address, which is why indexed links are worth removing from shared documents and calendar entries as well as from bookmarks.

Where the second sign-in refuses to finish

Not every account will complete a second sign-in in a browser that already holds one. Four causes account for most of it.

A managed account can require its own profile. Chrome Enterprise administrators can force this. Google's documentation for the setting describes the outcome as a hard boundary: "No data or content is shared between profiles." When that policy is on, a work account signed in on an unmanaged Mac triggers a prompt to create a separate Chrome profile, and declining ends the sign-in.

Single sign-on adds a second layer. Organisations that route Google sign-in through an identity provider often set a session lifetime measured in hours, so the work account drops out of the shared session on its own schedule while personal accounts stay put. The account list then shows an account that looks signed in but returns an authentication redirect on the next click.

Passkeys are stored per profile in the browser's own credential store or in the system keychain, so an account enrolled with a passkey on one Mac profile will fall back to a password and a second factor elsewhere. Nothing is broken, but the second sign-in stops being four clicks.

Finally, embedded webviews and older app frameworks can trigger Google's blocked sign-in flow, which is why an account that signs in fine in a browser fails inside a wrapper app that has not been updated.

Four places an account can live on one Mac

Signing in is only one of the arrangements available. The realistic set looks like this.

Arrangement	Accounts held at once	What is shared	Where it breaks
Multiple sign-in in one browser session	Many	Cookies, extensions, downloads, passwords	Default account decides ambiguous requests
Separate browser profile per account	One per profile	Nothing between profiles	Every profile is its own window stack in the Dock
A second browser for the second account	One per browser	Nothing	Two update cycles, two extension sets
A browser that gives each account its own window	One per space	Chosen per space	Requires moving off the default browser

The middle two rows solve the default account problem completely, because there is no shared session left to be ambiguous about. They also introduce the cost that sends people back to multi-login: macOS treats every Chrome profile window as the same application, so Command+Tab, the Dock, and notification grouping cannot tell the work window from the personal one. The isolation is real and the addressability is not.

That gap is what a workspace model is for. Giving each account a named space with its own storage means the boundary and the way to reach it are the same object, and switching is a deliberate action rather than a guess. The Workspaces page describes how that unit is defined, and the list of Supported apps shows which services are set up to run that way without extra configuration.

Signing in outside the browser

The browser is only one of the places a Google account gets authenticated on a Mac, and the others do not share the browser's account list at all. Adding an account in Chrome does nothing for Apple Mail, and adding it in Apple Mail does nothing for Chrome. Each surface holds its own tokens.

There are four of them on a typical machine. The browser session holds the accounts added through the account chooser. macOS Internet Accounts holds the ones added in System Settings, which is what feeds Mail, Calendar, and Contacts. Any installed web app created from a page holds whichever session existed in the profile it was installed from. Native desktop clients hold their own OAuth grants issued at first use.

Two consequences follow. Revoking access in one place does not revoke it in the others, so an account removed from a browser can still be delivering mail to a desktop client weeks later. And a second factor prompt can arrive from a surface that was set up months earlier and forgotten, which is the usual explanation for a verification request that appears to come from nowhere.

The other detail worth knowing is what an installed web app inherits. When a page is installed as an app through Chrome, the resulting window is bound to the profile it was created in, and it carries that profile's session including its default account. Installing a Gmail window from a profile holding three accounts produces a window that still has three accounts and the same ambiguity, not a single-account window. Getting one account per window requires one profile per account first, and the install second.

Auditing this once is worth the fifteen minutes. The security section of a Google account lists every third-party app and device with access, which is the fastest way to find sign-ins that outlived their purpose. Anything on that list that cannot be explained should be removed before adding more accounts anywhere.

A work account is not simply another account

Personal accounts fail softly. Work accounts fail in ways that create tickets.

Google Cloud Console, the Google Workspace Admin console, and the developer console are the surfaces where mixed sessions cause the most confusion, because their permission model is tied to the account that opened the console rather than the tab it was opened from. An administrator who signs in with a personal account first can end up seeing an access error that reads as a permission problem inside the organisation.

Data handling is the other half. In a shared session, a file downloaded from a corporate Drive lands in the same Downloads folder as everything else, and a password saved during a work sign-in is stored in the same profile as personal credentials. Neither is a policy violation on its own. Both are the reason security teams write the separate-profile policy in the first place.

The practical read: if one of the accounts belongs to an employer, the question is not how to log into multiple Google accounts in one place. It is where the boundary between them should sit, and whether it should be something the browser enforces rather than something a person remembers.

Habits that keep the wrong account from opening

Three changes remove most of the recurring failures without any new software.

Check the avatar before typing, not after sending. The account picture at the top right is the only reliable indicator of which identity a Google surface is using, and it is small enough to be ignored for months.

Give each account a different Chrome profile colour and name. Profiles apply a colour to the window frame, which turns identity into something visible in peripheral vision rather than something to verify.

Stop bookmarking indexed URLs. Bookmarks that encode /u/1/ will eventually point somewhere else. Bookmarks that encode the account address will not.

There is a limit to what habits fix. Google's help documentation is direct about what a profile is not: "If someone has your device, they can switch to any other Chrome profile on it."

If someone has your device, they can switch to any other Chrome profile on it. Source: support.google.com

Separation is an organising tool, not a lock. Treating it as a lock is how client data ends up in a personal browser.

What to change first

Decide which single account should be default, sign that one in first in a fresh browser session, and let the rest follow. If two of the accounts belong to different organisations, stop adding them to the same session and give each one its own space with its own storage instead, which is the arrangement SpaceDeck is built around. The setup takes an afternoon and removes a class of mistakes that habits alone do not.