No server. Your list never leaves the browser.

Personalized outreach
from your own Gmail,
one real email at a time

Fanout sends N individual emails, one gmail.send per person, with per recipient tokens, randomized throttling, and a daily cap that protects your account.

Free while in beta · Works with consumer Gmail and Workspace

mail.google.com Bulk Personalize

Subject

Quick question, {{FirstName|there}}

Body

Hi {{FirstName}},

Saw that {{Company}} just opened its Denver office. Congrats on the move.

Best,
Nita

Sending campaign

live
184 of 297 sentnext in 14s
  • priya.nair@northwind.co sent
  • deshawn.owens@harbor.io sent
  • mara.koenig@lattice.dev sending
  • tomas.rivera@brightpath.app queued

Randomized 8 to 30s gap · daily cap 500 of 500 tracked

A look inside

Five calm steps, one window that never leaves Gmail

Watch the whole flow, from a raw list to a finished send.

mail.google.com Fanout

Import recipients

Upload a CSV or paste rows from a spreadsheet. Everything stays in this browser.

Upload CSV Paste

Drop a CSV or click to browse

northwind-list.csv

297 rows · 4 columns detected

ready

Map your columns

Headers were matched to tokens automatically. Adjust any that look off.

First name{{FirstName}} auto
Company{{Company}} auto
City{{City}} auto
Email address Recipientrequired

Preview a real row

No missing values
3 of 297priya.nair@northwind.co

Subject

Quick question, Priya

Hi Priya,

Saw that Northwind just opened its Denver office. Congrats on the move.

Best,
Nita

Sending campaign

live
184 of 297 sentnext in 14s
  • priya.nair@northwind.cosent
  • deshawn.owens@harbor.iosent
  • mara.koenig@lattice.devsending
  • tomas.rivera@brightpath.appqueued

Randomized 8 to 30s gap · daily cap 500 of 500 tracked

Campaign complete

Every message left from your own Gmail, one at a time.

100%

delivered

Sent297
Failed0
Elapsed2h 41m
Export report
Step 1 of 5Import

Use the steps above, arrow keys, or the buttons to move.

0

gmail.send per recipient, never a shared BCC

0

daily cap on Workspace, 500 on consumer Gmail

0

recipients per campaign, sent one by one

0

servers, your data stays in the browser

The problem

Mail merge tools route through a stranger's servers

Most bulk senders upload your contact list to their backend, blast from a shared IP, and put your Gmail reputation in someone else's hands. Fanout does the opposite. It drives your own Gmail from inside the browser, sends each message as a distinct email, and keeps every name, address, and note on your machine.

Fanout vs the blast tools

A personalization tool, not a mail blaster

The usual mass senders route your list and your reputation through their own servers to hit volume. Fanout gives that up on purpose, so the trade is real. Here is where the two part ways.

Fanout
Typical mass mailers
How each email is sent
One gmail.send per person, straight from your own Gmail
Blasted from shared sending servers you rent
Where your contact list lives
In your browser, never uploaded anywhere
Uploaded to and stored on their backend
Open and click tracking
None. No pixel and no rewritten links
A tracking pixel and rewritten links in every message
Sending reputation
Yours, guarded by daily caps and randomized throttling
A shared IP pool you do not control
What the recipient gets
A normal email that threads back into your inbox
A tracked broadcast from a bulk system
What it costs
Free while in beta, no card and no account with us
A monthly subscription per seat

If you need open tracking, inbox rotation, and thousands of sends a day, a server based blaster is the right tool. If you want each email to genuinely come from you, this is.

Built to protect the account you send from

Every design choice bends toward keeping your Gmail healthy.

Real personalization with fallbacks

Drop {{FirstName|there}} anywhere in subject or body. Every value is HTML escaped, and an empty token with no fallback blocks the send instead of leaking a literal brace.

Account safety comes first

A 403 from Gmail stops the whole campaign, not just one send. Daily caps are checked before every network call, and the throttle floor can never drop to zero.

Resumes exactly where it stopped

The send queue lives in IndexedDB, so if the browser sleeps the worker mid run, Fanout wakes and picks up the next pending recipient. No double sends, ever.

PII never touches a log

Names, addresses, and message content stay local and get scrubbed out of every log line. There is no backend to breach because there is no backend.

Deliverability aware throttling

Sends land on a randomized 8 to 30 second cadence rather than a robotic tick, so your pattern reads like a human, not a firehose.

Lives inside Gmail

A Bulk Personalize button appears right in compose. Replies come back to your inbox, threading and all, because the mail genuinely came from you.

Not a mass mailer. A personalization tool that treats every recipient as a single, deliberate email from you.

How it works

Three steps from a list to a warm inbox

01

Open compose, click Bulk Personalize

Write your draft with tokens in plain Gmail. Fanout reads the draft straight from the compose window.

02

Paste your list, map the columns

Headers like first name and company map to tokens automatically. Fix any mapping, preview a real row, and Fanout flags missing values before you send.

03

Send and watch it go

One email leaves at a time on a randomized gap. Live progress shows sent, sending, and queued, and you can pause whenever you want.

People who send from their own name, not a blast IP

Reply rate on my seed round outreach went from a trickle to real conversations. It sends from my actual Gmail, so it threads and it does not look like a broadcast.
PRPriya RamanFounder, Northwind Labs
I recruit for three roles at once and personalize every note. The daily cap warnings stopped me from tripping a Workspace limit the week before a big push.
DODeshawn OwensTalent lead, Harbor
My laptop slept halfway through a 900 person send and I panicked. Fanout just resumed the next morning at recipient 412 with zero duplicates.
MKMara KoenigGrowth, Lattice.dev

Questions worth asking

Is this a mass mailer or spam tool?

No. Fanout sends one distinct email per recipient with real personalization. There is no shared BCC and no blast. It is meant for warm, individual outreach you would be comfortable sending by hand.

Will Gmail flag or suspend my account?

Fanout stays under Gmail's own daily limits, 500 on consumer and 2,000 on Workspace, spaces sends on a randomized 8 to 30 second gap, and halts the entire run the moment Gmail returns a 403. Protecting your account is the whole point.

Where does my contact list go?

Nowhere. There is no server. Your list, your draft, and your progress live in the browser's own storage, and personal data is scrubbed from every log.

What happens if my browser closes mid send?

The queue is stored on disk, so the next time the extension wakes it resumes at the next pending recipient. A recipient is claimed inside a transaction, so a resume can never send the same person twice.

Does it work with both consumer Gmail and Workspace?

Yes. It detects the account type and applies the matching daily cap, and when the type is unknown it defaults to the safer 500 limit.

What permissions does it ask for?

Only the scopes needed to send as you: gmail.send plus basic sign in. It cannot read your inbox, and you connect through Google's own OAuth screen.

How many recipients can one campaign hold?

Up to 5,000 per campaign. They still go out one at a time under your daily cap, so a large list simply spreads across more days.

What does it cost?

Free while in beta. There is no account to create with us and no card required, because everything runs locally against your own Gmail.

Send outreach that reads like it was written for one person

Because with Fanout, it was. Add the extension, connect your Gmail, and send a test to yourself in under two minutes.

No credit card · No server · Cancel by uninstalling