A custom email like [email protected] looks more credible than a personal Gmail address. Google Workspace and Microsoft 365 charge a monthly fee per mailbox for that credibility. If you are a sole trader, freelancer or running a side project, those fees add up before the business is making money.
There is a free custom domain email setup that uses Cloudflare Email Routing on the receiving side and Gmail's send-as feature on the sending side. It works, takes about fifteen minutes to configure and only costs the price of the domain itself. This guide walks through it and explains where the setup falls short, so you know when to upgrade.
What you will need
A domain you own (typically £8-£15 a year through a registrar like Namecheap, GoDaddy or 123-Reg)
A free standard Gmail account
A free Cloudflare account
Step 1. Route your domain through Cloudflare
Cloudflare acts as the receiving side. Mail sent to anything @yourdomain.co.uk arrives at Cloudflare first, then forwards to whichever Gmail address you nominate. The official Cloudflare Email Routing documentation is the canonical reference if anything in the dashboard differs from the steps below.
Create a free Cloudflare account and add your domain.
Cloudflare will give you two nameservers. Log into your domain registrar and replace the existing nameservers with the Cloudflare ones. Propagation usually takes under an hour.
Once the domain shows as active in Cloudflare, open it in the dashboard and click Email in the sidebar.
Click Get Started under Email Routing. Cloudflare will offer to add the required MX and TXT (SPF) records automatically. Accept.
Open the Routes tab and click Create address. Type the prefix you want (hello, info or your name) for the custom address, then put your personal Gmail address in Destination.
Cloudflare sends a verification link to your Gmail. Click it.
Quick check: send a test message from another inbox to [email protected]. It should arrive in your Gmail within seconds. Replies will still come from your personal Gmail address at this stage. The next two steps fix that.
Step 2. Generate a Google App Password
Gmail's send-as feature uses Gmail's SMTP server to deliver outgoing mail. For security reasons Google does not let your normal account password authenticate SMTP. You need a 16-character App Password instead, and App Passwords only appear in the Google Account menu when 2-Step Verification is on.
Open a private browsing window for this. It avoids confusion if you have work or school Google accounts signed in elsewhere.
Go to myaccount.google.com/security and turn 2-Step Verification on if it is not already.
Once 2-Step Verification is active, open myaccount.google.com/apppasswords directly. The menu is hidden from search if 2-Step Verification is off.
Type a memorable name (something like "Cloudflare email") and click Create.
Copy the 16-character code from the popup. The spaces are visual formatting only, so ignore them when you paste. Save the code somewhere safe; Google will not show it again.
Step 3. Add the address to Gmail
This is where Gmail learns to send mail as your custom domain.
Open Gmail, click the gear icon and choose See all settings.
Open the Accounts and Import tab.
In the Send mail as section, click Add another email address.
In the popup, enter your name as you want recipients to see it, then your custom address ([email protected]). Untick "Treat as an alias" and click Next Step.
Fill in the SMTP server details: SMTP Server is smtp.gmail.com, Port is 587, Username is your personal Gmail address, Password is the 16-character App Password from Step 2 (no spaces). Leave the connection set to TLS.
Click Add Account.
Gmail sends a confirmation code to your custom address. Cloudflare forwards it to your inbox. Click the link inside it to finish.
Step 4. The two settings that make it usable daily
Two small tweaks back in Accounts and Import make the daily workflow predictable.
Click "make default" next to your custom address. Compose now uses the business address by default.
Below the address list, select "Reply from the same address the message was sent to". Personal mail gets personal replies, business mail gets business replies. Without this setting every reply goes out from your default address regardless of which inbox the message landed in.
Where the free custom domain email setup falls short
This is honest: the Cloudflare and Gmail setup works well for low-volume one-to-one email. There are real limits beyond that.
The biggest is DKIM. DKIM is a cryptographic signature that proves an email was actually sent by your domain. Google Workspace, Microsoft 365 and dedicated sending services sign every outgoing message with DKIM as standard. Free Gmail cannot DKIM-sign mail for a domain you do not own through Workspace. SPF (which Cloudflare adds automatically) helps, but it is not equivalent protection.
In practice this means three things:
Your mail is more likely to land in spam, especially when emailing strangers or large providers like Outlook and Yahoo.
You cannot enforce a strict DMARC policy on your domain, which leaves room for spoofing.
Cold outreach and any kind of bulk or marketing sending is a bad fit for this setup.
The other limits are practical. One mailbox per Gmail account, so multiple staff need either multiple Gmails or a paid platform. No shared inboxes, no calendar at the domain level, no Drive at the domain level. If Google ever locks the underlying personal Gmail, you lose access to the business mail along with it.
When to upgrade to Google Workspace
Move to Google Workspace, Microsoft 365 or a dedicated mail host when any of the following becomes true:
You hire someone and need a second mailbox at the same domain.
You start sending newsletters, transactional email or any kind of bulk mail.
A noticeable share of your sent mail is going to spam.
You want shared calendars, files or a shared inbox under the domain.
Until then, the free setup is enough. Do not pay for what you do not yet need.
The website is usually the next bottleneck
A custom domain email implies a website to match. If yours is a placeholder, an old site that has gone stale, or nothing at all yet, that is usually the next problem to solve.
I build and maintain small business sites in WordPress, Craft CMS, Statamic and Laravel. The right choice depends on who updates the content and how often. There is a separate post on choosing between WordPress, Craft CMS and Statamic if you are weighing platforms.
Frequently asked questions
Is this setup really free?
The Cloudflare and Gmail components are free. You still pay for the domain itself, typically £8 to £15 a year depending on the registrar and the extension. There are no recurring per-mailbox fees on top of that.
Will my emails end up in spam?
Some of them might. Free Gmail cannot DKIM-sign mail from your custom domain, which is one of the main signals receiving servers use to decide whether mail is genuine. SPF (added by Cloudflare automatically) helps, but the setup is weaker than a paid host. For one-to-one replies it is usually fine. For cold outreach or bulk mail it is a bad fit.
Can I send marketing emails from this setup?
Not safely. Gmail's terms restrict bulk sending from personal accounts, and the deliverability problems get much worse at volume. Use a dedicated transactional email provider like Mailgun, Postmark or SMTP2GO for newsletters and transactional mail, kept separate from your day-to-day business inbox.
Can I add multiple custom addresses to the same Gmail?
Yes. In Cloudflare you can create as many routes as you want, all forwarding to the same Gmail inbox. Add each one as a separate Send mail as address in Gmail and you can reply from any of them.
Does this work with Outlook instead of Gmail?
Yes, the principle is the same. Outlook also supports adding an external SMTP send-as address, though the menu paths and security requirements differ. Cloudflare on the receiving side does not change.
Need a website to match the email?
I build small business sites in WordPress, Craft CMS, Statamic and Laravel. Tell me what you need.
Get in touch
