How to Use Gmail With Your Own Domain: 3 Ways Compared (Workspace vs Free Forwarding vs Send-As)
Gmail is the inbox you already know, but you@gmail.com on an invoice or a family invitation looks like a hobby. You can run Gmail with a custom domain in three real ways: one costs $8.28 a month and just works, one is free but comes with strings attached (and a January 2027 deadline), and one isn’t Gmail at all. Here is an honest comparison, then the exact steps for both Gmail routes.
Before you start
Three things decide which route fits you, so settle them before you touch any settings:
- Do you only need to receive, or also send? Receiving mail on your domain is free and easy: a forwarding rule copies
hello@yourdomain.cominto Gmail. Sending as your domain is where cost, spam filters and Google’s rules come in. - Is it just you? A partner, spouse, kids or a first employee each need their own address and inbox. The free route gives you one inbox, full stop.
- Where is your DNS? Have the login for your registrar (Namecheap, GoDaddy, Squarespace, Porkbun) or Cloudflare ready. Every route below needs at least one DNS change.
For the Workspace route you’ll work at admin.google.com. For the free route you’ll bounce between Gmail’s settings and your DNS panel. Either way, start with a domain you already own; if you still need one, you can buy it during Workspace signup through Google’s partner registrar.
Heads-up: Google’s help page for “Send emails from a different address or alias” now carries a notice that, starting January 2027, Gmail will no longer support “Send as” for third-party addresses (it names @yahoo.com and @outlook.com as examples). Google Workspace aliases and other Gmail addresses are not affected. A custom-domain address forwarded into free Gmail is not Google-hosted, so treat the free route as having a shelf life and read the current notice before you build on it.
14-day free trial · 10% off your first year with our referral link
The three ways at a glance
| What you get | 1. Google Workspace | 2. Free Gmail + forwarding + Send mail as | 3. Another host (iCloud+, Fastmail, Zoho) |
|---|---|---|---|
| Cost | $8.28/user/month (Business Starter, with our link), 14-day trial | $0 for forwarding; about $4–$9/month if you add a paid SMTP server | From free (Zoho) to a few dollars a month |
| A real mailbox on your domain | Yes, inside Gmail | No, mail is copied into your @gmail.com inbox | Yes, but not Gmail |
| Sending signed as your domain (DKIM) | Yes, built in | Only with a paid SMTP server; via smtp.gmail.com recipients see “via gmail.com” | Yes |
| Storage | 30 GB pooled per user on Starter (2 TB on Standard) | Your Google Account’s 15 GB | Varies (Zoho’s free plan: 5 GB per user) |
| Calendar, Drive, Meet on the domain | Yes | No, they stay on @gmail.com | Their own apps, not Google’s |
| More people or addresses | A user per person, up to 30 free aliases each, free Groups | One inbox; every extra address needs its own SMTP login | Yes (iCloud+: 5 domains, 10 addresses per person) |
| Admin controls and account recovery | Admin console, enforced 2-Step, offboarding | None beyond your personal account | Basic to good, depending on host |
| Outlook after January 2027 | Unaffected | “Send as” for third-party addresses is being removed | Unaffected |
The short version: if you send mail that matters (quotes, invoices, client replies, school forms), pick Workspace. If the domain only needs to receive, or it is a side project, the free route is fine for now. If you are deep in Apple’s ecosystem or want to leave Google, look at way 3.
Way 1: Google Workspace, the real Gmail on your domain
This is what “Gmail with your own domain name” means when Google says it. You get a proper mailbox at you@yourdomain.com with the Gmail interface, apps and search; outgoing mail is DKIM-signed for your domain so it passes DMARC; Calendar, Drive, Meet and Gemini run on the domain too; and the Admin console lets you add a second person in a minute. Business plans cap at 300 users, which no family or small business will hit, and each user can send up to 2,000 messages a day. Plans start at $8.28 per user per month with our link; see current pricing. Six short steps, each with its own detailed guide:
Step 1: Sign up and pick a plan
Start the trial through our link, enter your domain when asked, and choose Business Starter unless you need 2 TB of storage or recorded Meet calls. Full walkthrough: How to Set Up Google Workspace. Check: you land in the Admin console setup wizard with your domain shown at the top.
Step 2: Verify you own the domain
The wizard gives you a TXT record (google-site-verification=…) to add at your registrar; many registrars can add it automatically from the wizard. Guide: Verify Your Domain for Google Workspace. Check: the wizard shows the domain as verified.
Step 3: Create your users and aliases
Add one user per person. Each user can carry up to 30 free aliases (hello@, sales@, a short first-name address) that all land in the same inbox, and Gmail can send from any of them. Guide: Google Workspace Email Aliases. Check: sign in at mail.google.com with the new address.
Step 4: Point your MX record at Google
Google’s current recommendation is a single MX record: smtp.google.com, priority 1. Remove any other MX records, including a forwarder’s. Registrar-by-registrar steps: Google Workspace MX Records. Check: send a message from an outside account to your new address; it should arrive within minutes, although Google says activation can take up to 72 hours.
Step 5: Authenticate your mail (SPF, DKIM, DMARC)
Add SPF (v=spf1 include:_spf.google.com ~all), generate a 2048-bit DKIM key at Admin console → Apps → Google Workspace → Gmail → Authenticate email and publish it at google._domainkey, then, 48 hours later, a DMARC record at _dmarc starting with v=DMARC1; p=none; rua=mailto:…. Values and screenshots: SPF, DKIM & DMARC for Google Workspace. Check: send yourself a message, open it, choose “Show original” and look for PASS next to SPF, DKIM and DMARC.
Step 6: Bring your old mail and devices across
Import your @gmail.com history, set forwarding from the old account, and add the new account to your phone. Guide: Migrate Gmail to Google Workspace. Check: old threads are searchable in the new inbox and a message sent to the old address shows up there too.
Way 2: Free Gmail + forwarding + Send mail as (the free route)
This is the classic “gmail custom domain free” trick, and it still works in October 2026 with two caveats that are bigger than they used to be. The idea: a forwarding service accepts mail for your domain and delivers it into your personal Gmail; then Gmail’s “Send mail as” feature lets you reply from you@yourdomain.com. The catch on the sending side is that for an address Google doesn’t host, Gmail asks for an SMTP server, username and password when you add it. Confirming the address with a code is no longer enough on its own, so you need to decide who sends your outbound mail before you start. Read Google’s current rules on Send emails from a different address or alias.
Step 1: Set up forwarding for your domain
Pick one forwarder. They all do the same job; choose by where your DNS already lives.
- Your registrar. Namecheap includes free forwarding (Domain List → Manage → Advanced DNS → Mail Settings → Email Forwarding, then Domain → Redirect Email → Add Forwarder; up to 100 forwarders; your domain must use Namecheap’s DNS). Squarespace Domains (where Google Domains ended up) is also free: open the domain → Email → Email Forwarding → Add rule, fill in “Forward from” and “Forward to”, up to 100 aliases, live within 24–48 hours. Porkbun and most other registrars have something similar; search their help centre for “email forwarding”.
- Cloudflare Email Routing (free, but your domain must use Cloudflare DNS). Dashboard → Compute → Email Service → Email Routing → Onboard Domain. Cloudflare adds MX records for
route1.mx.cloudflare.net,route2…androute3…, an SPF recordv=spf1 include:_spf.mx.cloudflare.net ~alland a DKIM record atcf2024-1._domainkey. Add and verify your Gmail address under Destination Addresses, then Routing Rules → Create routing rule. Receiving only: Cloudflare’s own docs say Email Routing “does not support sending or replying from your Cloudflare domain”. Full steps in Cloudflare’s Email Routing guide. - ImprovMX works with any DNS host. The free plan covers 1 domain, 25 aliases and 500 forwarded emails a day, with no SMTP sending. Copy the MX and SPF values from Domain Settings → DNS Settings into your registrar.
Check: from a different account, send a test to hello@yourdomain.com. It should appear in Gmail within a few minutes (allow longer right after a DNS change).
Step 2: Choose an SMTP server for sending
Option A, free: use Google’s own server, smtp.gmail.com, port 587 with TLS, your full @gmail.com address as the username and an app password (step 4). Mail goes out through Google and is authenticated as gmail.com, not your domain, so Gmail-using recipients see “you@yourdomain.com via gmail.com” and your domain’s SPF and DKIM never come into play. Fine for a hobby domain, not for a business.
Option B, paid but proper: an SMTP service that signs mail with your own domain. ImprovMX adds SMTP on its paid plans (Light at $50/year with 750 sends a month, Premium at $9/month with 12,000); you create an SMTP credential, add its two DKIM CNAME records (dkimprovmx1._domainkey and dkimprovmx2._domainkey) and point Gmail at smtp.improvmx.com on port 587, following ImprovMX’s Gmail SMTP guide. Transactional email providers and some web hosts offer the same thing. Cloudflare’s separate Email Sending product also offers authenticated SMTP, but it is in beta and needs a Workers Paid plan, so it is aimed at developers.
Step 3: Fix your SPF record
A domain gets one SPF record. If you chose option B, merge the provider’s include: into the forwarder’s record rather than adding a second one, for example v=spf1 include:_spf.mx.cloudflare.net include:(your SMTP provider) ~all, and stay under SPF’s limit of 10 lookups. With option A there is nothing useful to add: Google authenticates the message as gmail.com regardless of what your domain’s record says.
Step 4: Create an app password (option A only)
Gmail will not accept your normal password here. In your Google Account go to Security → 2-Step Verification (it must be switched on) → App passwords, name it something like “Gmail send-as” and copy the 16-character password it shows you once.
Step 5: Add the address in Gmail
In Gmail: Settings (gear) → See all settings → Accounts and Import → “Send mail as” → Add another email address. Enter your name and you@yourdomain.com, click Next, then fill in the SMTP server, port 587, username and password from step 2 or 4, keep “Secured connection using TLS”, and click Add Account. Google emails a confirmation code to the new address, which your forwarder delivers into this same inbox; paste it in.
Step 6: Decide on “Treat as an alias” and your default
Ticked, Gmail treats the new address as you: mail you send to it behaves like mail to yourself and replies come straight back to this inbox. Unticked, Gmail treats it as a separate person’s address; ImprovMX recommends unticked for its SMTP setup. For a one-person domain either works, so follow your provider’s advice and toggle it if replies behave oddly. Then, still under “Send mail as”, tick “Reply from the same address the message was sent to” and, if you want every new message to come from the domain, click “make default”.
Check: send a message to an outside address (not the one your domain forwards to), then open it on the receiving side and choose “Show original”. Look at the SPF, DKIM and DMARC lines and at whether the sender shows “via”. That is exactly what your recipients’ spam filters see.
The caveats, stated plainly
- Deliverability is second-class. With option A your domain is never authenticated; with option B it is, but your mail reputation rides on a shared SMTP service. Expect the occasional spam placement you would not get from Workspace.
- DMARC bites. Publish
p=quarantineorp=rejectfor your domain while sending through smtp.gmail.com and your own mail fails DMARC. Keepp=noneon this route, or don’t publish DMARC at all until your sending is aligned. - One inbox, nothing else. No second user, no Calendar invites or Drive sharing from the domain, no admin console or recovery options if the personal account is lost.
- It is fragile. Changing your Google password invalidates app passwords, a registrar’s forwarder can stop silently after a DNS edit, and forwarders sometimes get rate-limited on busy days.
- January 2027. Google is retiring “Send as” for third-party addresses; forwarding itself is not affected, so you will still receive, but the reply-as-your-domain half is the part that goes away.
14-day free trial · 10% off your first year with our referral link
Way 3: Other paid hosts (a real mailbox, just not Gmail)
If you don’t care about the Gmail interface, several hosts give you a proper mailbox on your domain, each with its own apps and calendar:
- iCloud+ custom email domain. Included with any iCloud+ subscription: up to 5 domains, up to 10 addresses per domain per person, shareable with your Family Sharing group. Lives in Apple Mail, not Gmail.
- Fastmail. Custom domains on its personal plans and on the Standard and Professional business plans (not Basic). Good calendar and contacts, imports from Gmail, no Google apps.
- Zoho Mail. A “Forever Free” plan for up to 5 users with 5 GB each on one domain, web and mobile apps only (no IMAP or POP), plus inexpensive paid tiers. Nearest thing to a free Workspace for a tiny team.
We compare these for households in Best Email Hosting for Families.
Which way should you pick?
- Freelancer or consultant: Workspace. Your quotes and invoices must land in the inbox, you’ll want booking links on the domain, and the price is one coffee a month. See Google Workspace for solopreneurs.
- Family: Workspace if you want each person their own address with a parent as admin (how families use it); iCloud+ if everyone is already on Apple devices.
- Hobby project or a domain that mostly receives: free forwarding, plus option A if you occasionally need to reply. Keep DMARC at
p=noneand plan for 2027. - Anything with a second person: never the free route. Two people on one forwarded inbox ends in deleted mail and awkward replies.
Moving from the free route to Workspace later (without losing mail)
The upgrade is painless if you do it in this order, because nothing about your address changes:
- Leave forwarding switched on and sign up for Workspace with the same domain. Verifying ownership adds a TXT record, which doesn’t interfere with your forwarder’s MX.
- Create your user with the exact address you have been using as a send-as alias.
- Replace the forwarder’s MX records with
smtp.google.com(priority 1). From that moment new mail goes to the Workspace inbox; in old Gmail, set Settings → Forwarding and POP/IMAP → Forwarding to the new address so anything still sent to @gmail.com follows you. - Import your history with the steps in Migrate Gmail to Google Workspace.
- Clean up: delete the “Send mail as” entry and the app password in the old account, remove the forwarder’s SPF
include:and DKIM records, publish Google’s SPF, generate DKIM, and only then add DMARC. - Tell nobody anything. Your contacts keep writing to the same address and never notice.
14-day free trial · 10% off your first year with our referral link
Troubleshooting
- Gmail rejects the SMTP settings (“Authentication failed” or “Couldn’t reach server”): you used your normal password instead of an app password, 2-Step Verification is off, the port doesn’t match the encryption (587 with TLS, 465 with SSL), or your SMTP provider expects the alias rather than your Gmail address as the username.
- You can’t add a new third-party address at all. Google has said it is limiting new third-party “Send as” setups ahead of the January 2027 removal. There is no workaround on free Gmail; the durable fix is way 1.
- Recipients see “via gmail.com” (or via your provider). Gmail shows “via” when the domain that authenticated the message isn’t the one in the From address. Only sending through a server that DKIM-signs for your domain removes it: Workspace, or a paid SMTP service with DKIM configured.
- DMARC fails or mail bounces with a DMARC error. Your domain publishes an enforcing policy while your mail is authenticated as another domain. Drop to
p=noneuntil SPF or DKIM is aligned, then tighten. - Forwarded mail lands in spam. Forwarders rewrite the envelope sender so SPF passes, but a sender’s strict DMARC policy or a signature broken by an added footer can still fail; Cloudflare’s own docs warn that “restrictive DMARC policies might make forwarded emails fail to be delivered”. Make sure the forwarder’s SPF record is in place and mark the first few messages “Not spam”.
- Forwarding loop or “too many hops”. Your domain forwards to Gmail and Gmail auto-forwards back to the domain, or a catch-all points at an address that is itself forwarded. A forwarding chain must end at a real mailbox; remove the rule that sends mail back.
- The confirmation code never arrives. Forwarding isn’t live yet (allow up to 24–48 hours at some registrars), the rule covers a different alias, or the code is in Spam.
Related setup guides
- All Google Workspace setup guides
- How to Set Up Google Workspace: Complete Guide
- How to Verify Your Domain for Google Workspace
- Google Workspace MX Records: Setup by Registrar
- SPF, DKIM & DMARC for Google Workspace
- Google Workspace Email Aliases: Full Guide
- Migrate Gmail to Google Workspace
- Google Workspace Email Forwarding & Routing
- Custom domain email with Google Workspace
- Gmail vs Google Workspace: privacy differences
Frequently asked questions
Can I use Gmail with my own domain for free?
Partly. Receiving is free: a forwarding rule at your registrar, Cloudflare Email Routing or ImprovMX’s free plan delivers mail for your domain into your Gmail inbox. Sending as the domain needs an SMTP server in Gmail’s “Send mail as” settings; Google’s own smtp.gmail.com with an app password is free but shows “via gmail.com” to recipients, and Google is retiring Send as for third-party addresses in January 2027.
Is Google really ending “Send as” for non-Gmail addresses?
Google’s help page for sending from a different address now states that, starting January 2027, Gmail will no longer support Send as for third-party email addresses such as @yahoo.com or @outlook.com. Google Workspace aliases and other Gmail addresses are not affected. Forwarding into Gmail keeps working; it is the ability to reply from an outside address inside free Gmail that goes away. Check Google’s page for the latest wording.
What does “via gmail.com” next to my name mean, and how do I get rid of it?
Gmail shows “via” when the domain that authenticated a message is different from the domain in the From address. Sending your custom-domain address through smtp.gmail.com authenticates it as gmail.com, hence the label. To remove it, send through a server that signs with your own domain’s DKIM key: Google Workspace does this automatically, and paid SMTP services such as ImprovMX let you add DKIM records.
Does Cloudflare Email Routing let me send email from my domain?
No. Cloudflare’s documentation says Email Routing does not support sending or replying from your Cloudflare domain; it only receives and forwards, and your replies go out from the destination address. Cloudflare has a separate Email Sending product with authenticated SMTP, but as of October 2026 it is in beta, requires a Workers Paid plan and is designed for developers rather than inbox use.
How much does Gmail with a custom domain cost through Google Workspace?
Business Starter is $8.28 per user per month through our referral link (10% off the first year), with a 14-day free trial, 30 GB of pooled storage per user, Gemini included and up to 30 free aliases per user. Business Standard is $16.56 and Business Plus $25.83. A one-person domain therefore costs about $100 a year, and a family of four about $400.
Can I keep my @gmail.com address after moving to Workspace?
Yes. Your personal Google Account stays exactly as it is. Most people set the old account to forward to the new Workspace address, import the old mail once, and add both accounts to the Gmail app on their phone. Over time the @gmail.com address becomes a fallback for personal sign-ups while the domain address handles everything that matters.
Which option is best for a family domain?
Google Workspace if you want each family member their own inbox, a parent as administrator, and shared calendars and Drive on the domain; it costs $8.28 per person per month. If everyone already uses iPhones and Macs, iCloud+ includes custom domains with up to 10 addresses per person and can be shared through Family Sharing. The free forwarding route only works for a single shared inbox.
Do I need SPF, DKIM and DMARC if I only send a few emails a day?
Google’s stricter bulk-sender rules apply at 5,000 messages a day, but its baseline guidelines expect every sender’s domain to pass SPF or DKIM, and mailbox providers score unauthenticated mail harder every year. On Workspace all three take fifteen minutes. On the free route you can only authenticate properly with a paid SMTP server, which is the main reason businesses should skip that route.
MyOwnGoogle is reader-supported. If you start a Google Workspace trial through our links we may earn a commission, at no extra cost to you. This never affects what we recommend.