Ask how many email addresses a Gmail account can hold and you get three different answers depending on who is counting and what they mean by “address.” Google’s consumer service allows 10 outbound identities, Google Workspace allows 30 aliases per user, and Microsoft 365 documents a proxy address limit of roughly 300 to 400 per mailbox. The ceiling is not a single number because each provider counts a different mechanism. For anyone planning role addresses, registration identities, or a catch-all domain, that distinction decides which platform to buy.
The consumer Gmail limit that matters most in daily use is the send-as cap. Gmail allows sending as up to 99 other addresses, but the practical and commonly cited figure for alternate identities is tighter: a Gmail account can hold 10 outbound identities in the standard configuration most users encounter. That number governs how many different From addresses you can compose from inside one inbox. It does not govern how much mail the mailbox can receive, which is a separate mechanism entirely.
Google Workspace changes the arithmetic. A business mailbox on a custom domain allows up to 30 aliases per user, and those aliases are real routable addresses that land in the same inbox. Thirty is a generous allowance for a person who needs a few role addresses (sales@, support@, billing@) alongside a personal address, but it is a hard ceiling. Add a catch-all domain on top and you get broader coverage, though Google treats catch-all as a routing rule rather than a set of named aliases, and mail to unmatched addresses can be filtered or rejected depending on how the domain is configured.
Plus addressing delivers mail to the base Gmail address, which means user+newsletter@gmail.com and user+shopping@gmail.com both land in the same inbox. This is the closest thing to an unlimited supply of email addresses on Gmail, because the tag after the plus sign is arbitrary. The catch is that plus tags are trivially stripped by any form that validates against a strict pattern, and many signup systems now reject them outright. It helps to understand plus addressing vs catch-all domain when deciding how to filter and track which vendor sold your address, but plus tags are not separate identities and you cannot send from them.
Google also caps how often you can change a gmail.com address at three times, which matters if you treat the address itself as a disposable registration tool. The combination of a 10-identity send limit, a 30-alias Workspace limit, and plus tags that most forms see through means Gmail is a poor fit for anyone who needs hundreds of distinct addresses. It is excellent at what it does; it is simply not built to be an address factory.
Microsoft 365 documents a proxy address limit of roughly 300 addresses per mailbox, and Exchange Online is enabled by default to accept them. Each proxy address is a full alternate email address that routes to the same mailbox, and the platform treats them as first-class objects you can manage in bulk through PowerShell. That is an order of magnitude beyond the Workspace alias limit, and it changes the calculus for organizations that need many role addresses per person or per shared mailbox.
The practical comparison is stark. A user needing hundreds of role addresses should choose Exchange Online, not Gmail. A single Microsoft 365 mailbox can absorb 300 proxy addresses, where a Google Workspace user is capped at 30 aliases and a consumer Gmail account has 10 outbound identities. If your plan involves assigning a distinct email address per website, per department, or per regional brand, the Microsoft ceiling is the only one of the three that does not force you into shared mailboxes or a catch-all workaround within the first month.
There is a trade-off in management overhead. Hundreds of proxy addresses on one mailbox are only useful if someone maintains them, and a misconfigured proxy address silently routes mail to the wrong place. Exchange Online gives you the headroom; it does not give you the discipline. Teams that go this route usually pair it with naming conventions and a periodic audit, because 300 addresses is enough rope to hang a mail flow if nobody is watching.
The genuinely unlimited option is a catch-all domain, which accepts mail for every address on the domain. A catch-all mailbox does not care whether you created the address in advance; anything sent to anything@yourdomain arrives. That is the only mechanism across these providers that scales without a documented number attached, and for registration-heavy workflows it is often the right answer regardless of platform. The catch-all domain is described by AllMail as the only genuinely unlimited option, which is accurate: aliases and proxy addresses are enumerable and capped, while a catch-all is bounded only by your willingness to receive.
The numbers tell you what to buy. If you need 10 identities to send from, Gmail works. If you need 30 aliases per user on a business domain, Google Workspace works. If you need hundreds of routable addresses on one mailbox, Microsoft 365 with its proxy address limit is the platform to choose, and Exchange Online is where that capacity actually lives. If you need an address per website with no ceiling at all, a catch-all domain on email forwarding is the mechanism that gets you there, and you should budget for the filtering discipline it requires. Pick the ceiling that matches your workflow before you migrate, because moving a domain between providers later is a weekend you will not get back.