Use Gmail With a Custom Domain: 3 Ways (2026 Guide)

By Umair Ali Sadaqat · Updated November 6, 2026 · Editorial policy

Use Gmail with your own domain via Google Workspace, or the free send-as and forwarding route Google is ending in January 2027. Steps and a tradeoff table.

Short answer: The dependable way to use Gmail with a custom domain is Google Workspace, which gives you [email protected] inside the normal Gmail interface for a per-user monthly fee. The free alternative, forwarding your domain's mail to a regular Gmail account and replying with "Send mail as," is being retired: Google says Send as for third-party addresses, Gmailify and POP fetching end in January 2027. If you are setting this up today, pick Workspace unless you only need a short-term workaround.

The three ways, compared

	Google Workspace	Forwarding + Send mail as	Forwarding only
Inbox	Real Gmail inbox on your domain	Free Gmail inbox	Free Gmail inbox
Reply from domain address	Yes, natively	Yes, until Google ends it in January 2027	No, replies come from your @gmail.com address
Cost	Paid per user (see below)	Free, plus your email host if it charges	Free, plus your email host if it charges
Future-proof	Yes	No, being removed for third-party addresses	Forwarding itself is unaffected
Best for	Any business or client-facing mail	A short bridge while you migrate	Receive-only addresses like info@

Option 1: Google Workspace (recommended)

Workspace is the only option here that Google itself recommends for a custom domain. Business Starter is listed at $7 per user per month on the Annual/Fixed-Term plan and $8.40 on the Flexible plan (checked November 2026). Promotions, taxes and regional pricing can change what you pay, so check the total before you confirm.

Setup steps

Own a domain first. If you do not have one, compare domain registrars and see what a domain costs.
Sign up for Google Workspace and enter your domain when asked.
Verify the domain. Google asks you to prove ownership, typically by adding a record at your DNS host. If you need a refresher on editing DNS, see how to add a custom domain.
Add the MX record. Google's current guidance for new setups is one record: name @ (or your subdomain label), value smtp.google.com, priority 1 (checked November 2026). Delete any old MX records from your previous email host so mail is not split between two places.
Create your users (for example [email protected]) and sign in at gmail.com with that address.
Add authentication records for your domain (SPF, DKIM, DMARC) from the admin console so your mail passes spam checks.

Two practical notes. If your domain predates 2023 on Workspace, you may see older aspmx.l.google.com records; they still work, so leave them if mail flows. And MX changes can take time to spread, so keep the old mailbox open until test messages arrive in the new one.

Option 2: Forwarding plus "Send mail as" (ending January 2027)

This is the classic free trick: your domain host forwards mail to a Gmail address, and you add the domain address as a sending identity. It still works today, but read the deadline before you build a business on it.

What Google has said. Per Google's own help page, starting January 2027 Gmail will no longer support Send as for third-party addresses. Google's timeline says that in Q3 and Q4 2026 these features keep working but Gmail may restrict new configurations, and in January 2027 it fully removes Send as for third-party accounts, Gmailify and POP fetching. Gmail-to-Gmail aliases and Google Workspace Send as are not affected. Google's pages do not name custom domains specifically, but the exemptions cover only Gmail and Workspace identities, so a custom domain on a free personal account is most likely affected. Expect new setups to be restricted already.

Steps (while it is still available)

At your registrar or email host, create a forward from [email protected] to your Gmail address. Test it by sending a message.
In Gmail on a computer, click Settings, then See all settings, then the Accounts and import tab.
Under Send mail as, click Add another email address.
Enter your name and your domain address, then click Next Step.
Enter the outgoing SMTP server details from your email host, with the username and password for that mailbox. Google's help page lists SSL on port 465 and TLS on port 25 or 587 as options.
Click Send verification, then open the message from [email protected] (check spam) and click the link.
Compose a message, click the From line, and pick your domain address. Use Make default if you want replies to go out from it automatically.

Before you rely on it

Replies sent through a different SMTP server than the one your domain's records expect can fail authentication checks and land in spam.
When the feature is removed, you lose the ability to send from the domain address in Gmail on the web. The mailbox at your email host still works in its own app or webmail.

Option 3: Forwarding only

If you just need to receive mail at [email protected], forward it to Gmail and be done. Google states that auto-forwarding set up at your third-party provider is independent of Send as and is not affected by the January change. The catch: replies come from your @gmail.com address unless you add Send as, so it suits notification addresses and low-stakes inboxes, not customer conversations.

If you want a domain to send visitors to a website rather than a mailbox, that is a different job; see domain forwarding.

Which should you choose?

Use this checklist:

[ ] Do customers reply to this address? Use Workspace.
[ ] Will you still depend on it after January 2027? Use Workspace.
[ ] Is it a receive-only inbox (info@, hello@)? Forwarding only is fine.
[ ] Do you already have a mailbox at your host and want a few more weeks to migrate? Send mail as can bridge the gap, but plan the move.
[ ] Do you prefer a desktop client? Google notes that Outlook, Thunderbird and Apple Mail can keep accessing Gmail over IMAP or POP, and your email host's own IMAP and SMTP also work in a mail client.

Common mistakes

Leaving old MX records in place. Two providers' MX records mean mail goes to either one unpredictably.
Testing only inbound mail. Send a message from your domain address to an outside account and check it does not land in spam.
Buying the domain and email from different places without a plan. That is fine, but note which dashboard holds your DNS before you edit anything.
Skipping SPF, DKIM and DMARC. They are what make your domain look legitimate to receiving servers.

Pair the email address with a site

A domain email looks more credible when the same domain also serves a website. We.Inc's free plan lets you publish up to three sites from ready-made templates; the AI builder that drafts a site from a prompt starts on the Starter plan at $20 a month. You can connect the domain once DNS is in order; the steps are in our custom domain help article, and you can sign up here.

Frequently asked questions

Can I use Gmail with a custom domain for free?

Until January 2027, yes, in a limited way: you forward your domain's email to a free Gmail address and add the domain address under Settings, Accounts, Send mail as. Google has announced that it will remove Send as for third-party addresses, along with Gmailify and POP fetching, in January 2027, and it points people who want a custom domain to Google Workspace. Treat the free route as temporary.

How much does Google Workspace cost for a custom domain email?

Google's help pages list Business Starter at $7 per user per month on the Annual/Fixed-Term plan and $8.40 per user per month on the Flexible plan (checked November 2026). Google's pricing page may show promotions, taxes are extra, and prices vary by region, so confirm the figure at checkout. The domain itself is a separate cost if you do not already own one.

What MX record does Google Workspace use?

For new setups, Google's current guidance is a single MX record pointing to smtp.google.com with priority 1 (checked November 2026). Domains that started on Workspace before 2023 may use older aspmx.l.google.com style records, which still work. Some registrars want a trailing period after the hostname.

Will my emails go to spam if I send from my domain through Gmail?

Deliverability depends mostly on your domain's authentication records (SPF, DKIM and DMARC) and on how you send. With Google Workspace you set these up for your domain in the admin console. Sending a domain address through a mismatched SMTP server is more likely to fail authentication checks, which is another reason to use Workspace for business mail.

Can I keep using my existing domain email and just read it in Gmail?

You can ask your email host to auto-forward messages to your Gmail address. Google states that auto-forwarding configured at the third-party provider is independent of Send as and is not affected by the January 2027 change. Replying from the domain address inside Gmail is the part that stops working for non-Workspace accounts.

Related guides and tools

DNS lookup

Start building

How we research, test and update this page: our editorial policy. We.Inc is our own product.