Most people who say they “set up a Gmail alias” actually configured forwarding. The two features solve different problems, live in different parts of the product, and fail in different ways. If you want mail sent to one address to land in another inbox, that is forwarding. If you want a new address that delivers into an inbox you already own, that is an alias. Getting the control plane right matters more than the click path, because Gmail forwarding is configured in Gmail settings under Forwarding and POP/IMAP, while true aliases are configured in the Google Workspace Admin console. Mix those up and you will spend an afternoon debugging a setting that was never going to work.

Forwarding and aliases solve different problems inside Gmail

A Gmail email alias is an additional address that delivers mail to the same inbox as your primary account. You do not get a second mailbox, a second password, or a second storage quota. Mail arrives, filters run, and labels apply exactly as they would for the main address. Google Workspace allows 30 aliases per user, which is generous for a person who needs role-based addresses such as support@ or billing@ without provisioning new seats. Consumer Gmail is different: Google documents alias limits on its help pages, and the rules are narrower than most people assume.

Gmail plus aliases are the consumer workaround. Append +anything to your username and the mail still routes to your inbox: janedoe+newsletters@gmail.com and janedoe+shopping@gmail.com both land at janedoe@gmail.com. These are not separate accounts, and you cannot send from a plus alias unless you add it as a Send mail as address. The plus sign is a labeling trick, not an identity. Gmail filters can be created on plus alias addresses, which is the whole point: sort vendor mail, receipts, or signup confirmations into their own labels without touching your primary flow.

There is also the dot trick, which is widely misunderstood. Gmail ignores periods in the local part of the username, so john.smith@gmail.com and johnsmith@gmail.com reach the same person. Dot aliases are not something you create. They exist automatically, and they do not give you extra addresses for signups in any meaningful way because you cannot send from the dotted variant by default. Treat dots as a curiosity, not a strategy.

Forwarding, by contrast, moves mail out of one inbox and into another. You might forward a legacy Yahoo or Outlook address into Gmail so you stop checking two places. You might forward a shared team address to whoever is on call this week. Either way, the destination receives copies, and the original mailbox keeps its own copy unless you configure deletion. That distinction matters for compliance and for anyone who assumes forwarding means migration.

Where each setting actually lives and how to configure it

Start with forwarding because the path is short and the failure mode is obvious. Open Gmail settings, go to the Forwarding and POP/IMAP tab, and click Add a forwarding address. Enter the destination, and Gmail sends a verification email to that address. The forward does not activate until someone clicks the confirmation link. This is deliberate: it stops anyone from silently siphoning your mail to an address you do not control. Once confirmed, choose whether to keep a copy in the original inbox, mark it read, or archive it, then save. If the verification email never arrives, check the spam folder at the destination before assuming Gmail broke.

Aliases work differently, and this is where admins get burned. In Google Workspace, you open the Admin console, go to Directory, then Users, select the user, and add the alias under the user’s profile. There is no verification email and no confirmation step, because the admin already controls the domain. The alias becomes live almost immediately, though propagation can take a few minutes. If you instead went to Gmail settings and poked around looking for an “add alias” button, hoping to create email alias Gmail would recognize on its own, you found nothing, concluded the feature was missing, and possibly configured forwarding to a nonexistent address as a substitute. That is the classic misconfiguration: an alias that “did not work” because forwarding was set up instead.

Sending is a third, separate concern. Send mail as lets you send from another address inside Gmail, and it supports up to 99 addresses per account. You add it under Accounts and Import, and Gmail verifies ownership either through a confirmation email or through SMTP credentials for the other provider. For a Workspace alias you already own, the alias usually appears as a send option automatically once it is provisioned. For a third-party address, you will need the SMTP server details from that provider. Note the deadline: Gmail will discontinue Send as for third-party addresses starting January 2027, so if you rely on sending through an external SMTP server from Gmail, plan a migration now rather than later. Sending from a Workspace alias on your own domain is unaffected.

A second Google account is the other option people reach for, and it is worth being blunt about the trade-off. A second Google account provides a separate inbox, separate storage, and separate sign-in, which is real isolation. It also means two calendars, two contact lists, and a login you will forget. If you genuinely need separation, such as a personal account and a work account on different domains, a second account is correct. If you just want a cleaner inbox, plus aliases and filters will do the job without the overhead. Changing your gmail.com address is allowed once every 12 months, which is an option if the username itself is the problem, but it breaks nothing and fixes little beyond cosmetics.

For anyone running a domain, a catch-all email is the fourth pattern and the one most often misapplied. A catch-all routes every address at your domain to one mailbox, which sounds convenient until spammers discover it and your inbox fills with mail addressed to random strings. Workspace does not offer catch-all natively in the standard interface, so most teams use routing rules or a third-party gateway. If you go that route, pair it with aggressive filtering and a real alias structure for the addresses you actually publish. AllMail publishes Gmail alias guides that walk through these patterns if you want a reference while configuring.

Pick the mechanism before you touch a settings page. Mail into an existing inbox: alias, configured in the Admin console for Workspace or via plus addressing for consumer Gmail. Mail out of one inbox into another: forwarding, configured under Forwarding and POP/IMAP with confirmation at the destination. Mail sent from a different address: Send mail as, configured under Accounts and Import, with the 2027 deadline in mind for third-party SMTP. Mail that must be fully isolated: a second Google account. Write down which one you chose and where you configured it, because six months from now the symptom will look identical regardless of which control plane you used, and the fix depends entirely on knowing which one you actually touched.