How many Gmail addresses one person can hold

The question is usually asked after something small goes wrong. A second address is needed for a client, or for invoices, or for a side project, and the obvious move is to add it to the account that already exists. The switcher in the top right corner shows several accounts, so it looks like one Google Account can carry several inboxes. It cannot, at least not in the way the question implies, and knowing exactly where the line sits saves a lot of unnecessary account creation.

The short version: a consumer Google Account has exactly one Gmail mailbox, but that mailbox answers to more addresses than most people realise, and a single person may hold as many separate Google Accounts as they can actually maintain. Those are three different limits, and only one of them is set by Google.

One account holds one mailbox and many addresses

For a personal account, the @gmail.com address is not a feature of the account. It is the account name. Creating a second @gmail.com address means creating a second Google Account, with its own password, its own storage, its own Drive, and its own place in the switcher. There is no setting anywhere that adds a second inbox to an existing personal account.

What does exist is a set of ways to make one mailbox accept mail sent to different strings.

Dots in the local part of a Gmail address are ignored. Mail addressed to [email protected], [email protected], and [email protected] all lands in the same inbox, and the address printed on a business card with dots in it is not a separate account.

If someone accidentally adds dots to your address when emailing you, you'll still get that email. Source: support.google.com

Plus addressing does the same thing with a tag attached. Mail to [email protected] arrives in the same inbox carrying a string that a filter can match on. Using a tagged address when signing up for a service gives per service sorting for free, and it also shows later which service leaked the address when unexpected mail starts arriving.

The important distinction is between an address and a mailbox. Extra addresses are cheap and cost nothing to maintain. Extra mailboxes are extra accounts, and every one of them has to be secured, backed up, and watched.

The limits Google actually sets

Google does not publish a number for how many accounts one person may create. The practical throttles are elsewhere, and they are worth knowing before a fourth or fifth account gets made on impulse.

Phone verification is the first. Account creation frequently asks for a phone number, and the same number cannot be used to verify an unlimited number of accounts in a short window. Nothing announces the limit in advance. The signup simply stops working, usually at the least convenient moment.

Storage is the second. Each account gets its own free allowance, currently 15 GB shared across Gmail, Drive, and Photos. That sounds generous until it becomes clear that it is per account rather than pooled. Five accounts means five separate allowances that fill at five different rates, and five separate moments when mail stops being delivered because the quota ran out.

Inactivity is the third and the one most often missed. Google's policy allows accounts that have gone unused for two years to be deleted along with their contents. An account created for one signup and never opened again is exactly the profile that policy describes. If an address matters, it has to be used, or at least signed into, on a schedule.

The fourth limit is the sign-in list itself. Accounts signed into the same browser get numbered by position, which is where the /u/0, /u/1, /u/2 segments in Gmail and Drive addresses come from. That number is a position, not an identity, so it moves when an account is signed out. Signing out of one account in the switcher signs out of all of them at once.

Workspace answers the question differently

On Google Workspace, the picture changes, because there the address and the account are genuinely separate things.

An administrator can attach alias addresses to an existing user. Mail sent to an alias lands in that user's normal mailbox, the alias can be selected in the From field, and no additional license is charged. Google documents a cap of 30 aliases per user, which is far more than most people need. A role address such as billing or support does not require a second login, a second window, or a second password.

Google Groups covers the same ground from another direction. A group address can deliver to one person or several, membership changes without touching anyone's account, and handover to a different person later is a membership edit rather than a password transfer.

	Second Google Account	Workspace alias	Plus tagged address	Google Group	Send mail as
Separate mailbox	Yes	No	No	Optional	No
Separate password and storage	Yes	No	No	No	No
Can send from that address	Yes	Yes	Limited	Yes	Yes
Extra cost	Free tier or license	None	None	None	None
Handover to another person	Password transfer	Admin change	Not applicable	Membership edit	Not applicable
Setup time	Fifteen minutes	Two minutes	None	Five minutes	Ten minutes

The rule of thumb that falls out of the table is ownership. If the address will one day belong to someone else, or has to survive a change of staff, it needs to be a group or a Workspace object rather than a personal account. If the address just needs to receive and reply under a different name, an alias or a verified send as address does the job without adding anything to maintain.

Three cheaper moves before creating another account

Most requests for a second account are really requests for one of three behaviours, and all three are available without adding an account to maintain.

The first is sending under a different name. Gmail's send as setting adds a verified address to the From menu, so replies can leave under a project address, a domain address, or a role address while still being written in the main window. Verification is a confirmation mail sent to the other address, which means the address has to exist somewhere, but it does not have to be a Google Account. A domain address on a small hosting plan works.

The second is receiving mail addressed elsewhere. Two mechanisms cover this. Forwarding is set on the sending side and pushes mail through instantly, which suits addresses that need to be seen quickly. Mail fetching is set on the receiving side and pulls from up to five other addresses on a schedule, which suits low volume addresses that nobody is waiting on. Both drop mail into the same inbox, so a filter that labels by the address it was sent to is what keeps them usable.

The third is letting someone else handle a mailbox. Gmail delegation gives another person the ability to read and reply on behalf of an account without sharing its password, and messages sent that way carry a record that they were sent by the delegate. When the reason for a separate account is a separate role rather than a separate person, delegation and Google Groups both fit better than handing over credentials.

What none of these give is separate storage, a separate password, or a separate identity for signing into third party sites. When those are the actual requirement, a second account is correct and there is no shortcut. When they are not, adding an account creates maintenance that buys nothing.

The ceiling that actually binds is attention

Counting accounts is the wrong measurement. The number that hurts is how many identities have to be tracked at the same time.

Every additional signed in account adds a place where mail can arrive unnoticed, a chance of replying from the wrong address, and one more set of notifications that all look identical because they come from the same browser. Browser notifications carry the browser's identity, not the account's, so a new message alert says that something arrived without saying which of five inboxes received it. The only way to find out is to open and look, and the cost of that check is not the twenty seconds of reading. It is the interruption to whatever was in progress.

This is where the shape of the setup matters more than the count. A browser that keeps each web app in its own window gives every account a real identity at the operating system level, with its own name, its own icon, and its own notification rules in macOS System Settings. Work mail can stay audible during the day while a personal account stays silent, without any decision being made in the moment. The way sessions and windows get grouped by job rather than by tab is described under Workspaces, and which services are set up to run in that shape is listed under Supported apps.

Inside a single browser window none of this is available. Notification permission is granted to the browser as a whole, so the choice is all of them or none of them.

There is a second cost that only appears at four or five accounts. Every account carries its own security surface: a password, a second factor, a recovery address, a list of devices, and a set of third party apps that were granted access at some point. Reviewing one account takes a few minutes. Reviewing five takes an afternoon, which is why it does not happen, which is why the accounts that matter least are usually the ones with the weakest recovery path and the oldest granted permissions. The account created in a hurry for a single signup is the one that becomes a way in.

Deciding how many accounts to keep

Two questions settle almost every case. For each address currently in use, ask whether mail has to leave under that specific name, and whether mail arriving there has to be noticed within the hour.

Addresses that need neither belong in a shared inbox. Receipts, shipping notifications, and newsletters do not need a window, an icon, or a notification rule. They need a label and a filter, and they can be collected into a main account through the mail fetching settings, which pull from up to five other addresses.

Addresses that need both deserve their own container. A work address and a client address usually qualify. They have to send with the correct sender and they have to be seen quickly, which is exactly the combination that browser tabs handle badly.

Addresses that need only one of the two sit in the middle, and volume decides. An address that must send correctly but almost never receives can be registered as a send as identity on the main account. An address that receives constantly but never sends can be forwarded in and labelled.

Run that sort once and the list usually collapses. Most people who thought they were managing six accounts are actually managing two, plus four addresses that happen to be spelled differently.

What to change first

Write down every address currently in use and mark which ones actually need a separate mailbox rather than a separate string. Delete or consolidate the ones that fail the test, since each one removed is a password, a storage quota, and a security review that no longer needs attention. For the two or three that survive, give each a real window and its own notification rules rather than another tab, which is the arrangement SpaceDeck is built around.