Generate spintax
Runs on Cloudflare Workers AI. Free: 10 generations an hour, 25 a day per visitor, and a shared daily allowance for everyone. Nothing you enter is stored.
How it works
Paste the email
Subject optional. Keep your merge tags in whichever syntax your tool uses — {{firstName}}, {firstName}, {{company}} — they are protected.
Pick the spin level
Light spins greetings, sign-offs and a few phrases. Medium gives most sentences two or three phrasings. Heavy rewrites nearly everything, including the subject, with three or four options.
Natural alternatives
Each option must read as a full, natural sentence in the same tone and length, not a synonym swap. Nesting is limited to two levels so every sending tool can render it.
Count and preview
The page counts the distinct variants and hands the result to the spintax previewer so you can check renders before it goes live.
What spintax is for
Gmail and Microsoft cluster near-identical messages arriving from many senders at once, and a fleet of secondary domains sending one template is exactly that cluster. Spintax — {option a|option b|option c} blocks the sending tool resolves at send time — gives each message its own wording so the cluster never forms. It only works if each alternative is a sentence a person would write. Thesaurus spinning (“leverage / utilise / harness”) produces text that reads as machine-written to a filter and to a reader, and the newer filters are content classifiers that recognise it immediately. The generator is instructed to rewrite, not substitute, and to keep length and tone constant across options.
How much spin is enough
Multiply the option counts and you have the number of distinct emails. Thirty to a few hundred variants is plenty for a fleet; going into the thousands adds nothing and makes the template unreadable to whoever maintains it. Light spin is right for a follow-up in a thread, medium for a first email across a fleet, heavy only when the same template will run for months on many domains. Spin the subject line too — it is the first thing clustered.
How the generator is tuned
The model behind this page is an open-weight model running on Cloudflare's network, and the instructions it follows are mine — the same rules I apply when I edit a client's sequence: short sentences, no marketing words, open with the reader, one question at the end, keep merge tags intact. Those instructions are edited over time as I see what it gets wrong, so the output improves without the page changing. It is a starting draft, not a finished campaign: read it as you would a junior writer's work, cut what does not fit, and run the result through the readability checker and spam word checker before it goes into a sequence.
Limits and privacy
Each visitor gets ten generations an hour and twenty-five a day, and there is a shared daily allowance across the whole site that resets at 00:00 UTC — when it runs out the tool says so rather than failing silently. Inputs are sent to the model and discarded; nothing is stored, logged with your text, or used to train anything. The generated text is yours.
Frequently asked questions
Which syntax does it output?
Standard {a|b|c} with single braces, which Instantly, Smartlead, lemlist, Woodpecker and most others accept. Merge tags keep whatever syntax you pasted.
Why limit nesting to two levels?
Several tools render deeper nesting wrongly or not at all, and it makes the count of variants explode without adding real variety. Two levels give more than enough.
Does spintax hurt deliverability?
Bad spintax does — synonym swaps read as spam. Natural spintax helps, because it stops the fingerprint. The previewer shows you which kind you have.
Is my email stored?
No. It goes to the model once and is not kept.
Limits?
Ten generations an hour, twenty-five a day per visitor, plus a site-wide daily allowance resetting at 00:00 UTC.
Last reviewed
What to run next
The checks that most often follow this one.
More in this category
Guides that go deeper
When the tools tell you something is wrong
The diagnostics here are free and always will be. When the fix is bigger than a DNS record, this is the work I do.
Deliverability rescue
Mail landing in spam, replies gone quiet, or a domain suddenly blocked. I find the actual cause rather than guessing, and fix it.
- Authentication and alignment failures
- Blocklist delistings and reputation repair
- Gateway and filter-level blocks
- A written report on what broke and why
Email & sending infrastructure
Sending domains, inboxes, authentication and warmup, built to survive volume instead of burning down in a month.
- Domain and inbox fleets at any scale
- SPF, DKIM, DMARC and tracking domains
- Google Workspace and Microsoft 365 inboxes
- Handover documentation you actually own
Domain, DNS & migration
Changing registrar, mail provider or host without a day of downtime or a week of mail silently failing.
- Registrar and nameserver moves
- Workspace and Microsoft 365 migrations
- MX, SSL and subdomain cutover
- Staged rollout with rollback at every step
Monitoring & retainer
Infrastructure drifts. Records get edited, certificates expire, domains get listed. Ongoing eyes on the fleet.
- Scheduled checks across every domain
- Alerts before your clients notice
- Monthly reporting
- Priority response when something breaks
Start with a call
Bring a domain and the symptom. I will tell you what is actually wrong and whether you need me at all — plenty of people leave that call able to fix it themselves.
Thirty minutes, no pitch
We will run the checks together on your actual domains, and you will leave knowing what is broken, what it takes to fix, and what it should cost. If that is a job you can do in-house, I will say so.