How it works
Paste your email template with {{variable}} placeholders in Step 1, then paste your contact list CSV in Step 2. Click Preview emails and the tool renders the first 20 merged emails exactly as recipients would see them, with any issues flagged inline.
Paste your template
Use {{variable_name}} placeholders anywhere in the subject or body.
No variables detected yet. Add placeholders like {{first_name}} to your template.
Paste your contact list
Paste CSV or spreadsheet rows. Include a header row so the tool can match columns to variables.
Column headers should match your template variables. For example, a column named first_name fills in {{first_name}}. Headers are matched case-insensitively.
0 detected rows
Preview merged emails
See the first 20 emails exactly as they will be sent, with issues flagged inline.
Paste a template and contact list to get started.
Fill in Steps 1 and 2, then click Preview emails.
What it flags
The tool catches the mistakes that turn a polished cold email sequence into an embarrassing send. If the CSV itself needs cleanup before you preview the merge, run it through the cold email CSV checker.
- Empty values — a contact row where a cell is blank, producing "Hi ," or "Quick idea for ,"
- Placeholder values — cells containing N/A, undefined, null, or similar stand-ins
- Broken variables — template placeholders that look like typos close to a real column header, such as {{frist_name}} when first_name exists
- Variables missing from CSV — placeholders in the template with no matching column anywhere in the contact list
- Unused CSV columns — columns in the contact list that are never referenced in the template
- Duplicate suffixes — company names that repeat a suffix after a mail merge, like "Acme Inc. Inc."
A practical review flow
Preview the merge after the CSV is cleaned and before the sequence goes into a sending tool. The goal is to catch the mistakes a normal spreadsheet scan misses: empty greetings, repeated company suffixes, awkward sentence fragments, and template variables that look right until they render.
- Scan the issue summary first and fix broken variables before reading individual previews.
- Read the first few rendered emails out loud, especially the greeting and first sentence.
- Check rows with empty, placeholder, or unusually long fields before exporting.
- Open the CSV next to the preview so each issue becomes a row edit, not a vague warning.
- Run one final preview after edits so fixed columns did not create a new mismatch.
What it does not do
It checks the rows in the CSV you paste and previews the exact merge output: missing values, obvious placeholder values, broken variables, unused columns, and duplicate suffixes. It does not send emails, verify mailboxes, check deliverability, enrich missing fields, score senders, or sync to your CRM.
Privacy
The preview runs locally in your browser. Your template and contact list are never uploaded to any server.