GuideLast updated

Gmail Custom Domain Without Workspace: What Works in 2027

Free Gmail can't host your domain, and the free forwarding plus Send as trick loses its sending half in January 2027. What still works without Workspace.

You can't get a Gmail custom domain without Workspace, because free Gmail doesn't host your domain and Google only does that with a paid subscription.

The free workaround, forwarding the domain into your personal Gmail and replying with Send as, keeps receiving after January 2027 but loses sending as the domain.

Can you use Gmail with a custom domain without Workspace?

Only with a paid subscription. Google says it in the FAQ on its business email page: "Standard Google Workspace plans require a subscription to access premium features such as ad-free Gmail at a custom company domain."

So a free @gmail.com account can't turn into you@yourbrand.com. What people did instead was put together 2 free pieces:

  • A forwarder sends all mail for the domain to your personal Gmail. Cloudflare Email Routing is one, and it's available on Free plans.
  • Gmail's Send as, set up with your domain address and an SMTP server, lets you pick you@yourbrand.com as the From address when you reply.

If you searched "custom domain Gmail free", this is probably the setup you found. I ran it myself for support@ on a few of my domains, and it worked fine until I changed something in DMARC on one of them and Send as stopped working.

So it was already a bit fragile. January 2027 ends the sending half anyway.

What January 2027 changes

Google's help page on the change is about Send as for third-party addresses, and an address on your own domain that you added to free Gmail is one of them. The parts that matter here:

  • Starting January 2027, Gmail drops third-party Send as on the web and in the mobile apps. During the Q3 to Q4 2026 transition it still works, but Gmail "may restrict new configurations".
  • Auto-forwarding into Gmail keeps working, since it's "independent of Gmail's Send as feature".
  • Gmail-to-Gmail aliases and Send as in Google Workspace aren't affected.

We're in that transition now, so an existing setup still sends as your domain for the moment, and a new one might get refused.

So half of the free setup survives. Mail to you@yourbrand.com still lands in Gmail, but from January your reply goes out from your @gmail.com address. The replacements for Send as, and what each one costs, are in what to use instead of Gmail Send As.

Your options without Workspace

I'd pick by 2 questions: do you need to reply as the domain, and how many domains do you have.

Receive only

If people write to you@yourbrand.com and you're fine answering from your Gmail address, keep forwarding. It's free, Google says it keeps working, and nothing changes for it in January.

That's fine for a personal site or a side project, where nobody minds which address the reply comes from. For anything with customers it looks off: they write to hello@yourbrand.com, get an answer from yourname@gmail.com, and next time they'll probably write to the Gmail address.

If you want to know why replying as the domain is so much harder than receiving, how to reply to email from a custom domain goes through it.

Send and receive on one domain, in Gmail

That's Workspace, and it's the only way to have Gmail itself on your domain. January doesn't touch it: Google lists Send as in Workspace as unaffected, so extra addresses on the domain keep working next to your own.

It's also exactly the subscription you were trying to avoid. If staying in Gmail is worth a monthly bill to you, I think it's the cleanest answer for one domain.

We did the cost math in Google Workspace multiple domains pricing, so I won't repeat the numbers here.

Send and receive on one domain, without Workspace

You need a real mailbox on the domain, at a host other than Google. Your registrar, your web host or an email host are the usual places to get one. Then you read and reply in one of the places Google itself suggests:

  • the provider's own website or app
  • a desktop mail client
  • the Gmail mobile app

The Gmail app is the closest you get to keeping everything in Gmail. Google's help page for it says the app reads and sends from another account over a standard IMAP connection, so you@yourbrand.com sits next to your Gmail account on your phone, and replies go out from the right address.

It only works with a real mailbox, though. A forward-only address has nothing for the app to connect to. And it's the phone and tablet app, so at a computer you're back to the provider's site or a desktop client.

If you were pulling a host mailbox into Gmail over POP, that ends in January 2027 too, along with Gmailify. That half is in Gmail check mail from other accounts.

For one domain, this is what I'd do if Workspace feels like too much. It's one more place to check at a desk, but replies come from the right address.

Several domains

With a few domains, every option above gets more annoying. With forwarding you still reply from Gmail. A mailbox per domain is a login per domain, or a desktop client with an account for each one. And Workspace is the subscription you wanted to skip.

This is the case we built Mailyond for. You connect each domain with one 5-minute DNS setup (3 records), every address on all of them lands in one inbox as threaded conversations, and you reply from the address people wrote to.

Mailyond is a separate inbox, not Gmail. Your personal mail stays in Gmail, and you open Mailyond for the domains.

You can connect yourbrand.com itself, which moves its mail over from the forwarder, or start with a subdomain like support.yourbrand.com while your forwarding keeps running.

It's from $10/month, with a 7-day free trial on Basic and Pro. If you have one domain and only read it, stay on forwarding, it's free and does the job.

Watch out for Send-as clones

With Send as going away, you'll probably see tools that promise to bring it back inside Gmail. Google's help page has a warning about them: third-party tools that "replicate Send as" often need your credentials or OAuth tokens.

That means giving a company your Gmail password, or a token that lets it into your account, so it can put a different address in the From field.

Check what a tool asks for and who runs it before you connect it. If it asks for your Gmail password, I'd skip it.

FAQ

Can I use Gmail with my own domain for free?

No, Gmail at a custom domain needs a paid Workspace subscription. The free way is forwarding the domain into your personal Gmail, which keeps working after January 2027, but your replies come from your Gmail address.

Does forwarding my domain to Gmail still work after January 2027?

Yes. Google says auto-forwarding into Gmail is "independent of Gmail's Send as feature", so mail to your domain keeps arriving in Gmail.

Can I still reply as my domain from Gmail?

Until January 2027, yes, through Send as, though Gmail "may restrict new configurations" during the Q3 to Q4 2026 transition. From January, Gmail drops third-party Send as on the web and in the mobile apps, so a reply from free Gmail goes out from your Gmail address. The exception is the Gmail mobile app, if you connect a real mailbox on the domain to it.

Do Workspace aliases still work?

Yes. Google lists Send as in Google Workspace and Gmail-to-Gmail aliases as unaffected by the January 2027 change.

Can I add my domain account to the Gmail app?

Yes, if the domain has a real mailbox. The Gmail app on Android, iPhone and iPad reads and sends from another account over a standard IMAP connection. A forward-only address has no mailbox for it to connect to.

Send and answer email across all your domains

Every address on every domain in one inbox, plus a Resend-compatible API for your app's email.

One DNS setup per domain
Verify in about five minutes
Price
Starting from $10 / month
Replies on the same domain
Answer from the address they wrote to