Article
How to Prepare an Email List for Verification: Practical Steps Before You Upload
By Unlimited Verifier Team ·

Summary
To prepare an email list for verification, export it as UTF-8 CSV, freeze the original file, remove duplicates and placeholder rows, strip hidden characters, and split files that exceed your tool's per-list limit. Preparation ensures the verifier reads one clean address per row, so results are accurate and countable.To prepare an email list for verification, export it as a UTF-8 CSV, remove duplicates and placeholder rows, strip hidden characters, split any file above your tool's per-list limit (25,000 rows on Unlimited Verifier's Pro plan), and keep an untouched copy of the original. Preparation is the stage of bulk email list verification that teams most often rush, and a dirty export produces wrong counts, wastes allowance on rows you never needed, and can make good addresses look invalid.
Quick answer
- Freeze the original file first. Never clean the only copy, because you will need it for audits, reconciliation and appeals.
- Fix the characters, then the rows. Trim spaces, replace curly quotes, split multi-address cells, and deduplicate on a normalised key.
- Quarantine, don't delete. Move placeholders and non-addresses to a separate file, and tag every row with its source.
- Respect the per-list limit. Free lists hold 150 emails and Pro lists hold up to 25,000. Keep each upload under 10MB.
What does it mean to prepare an email list for verification?
Preparing a list means making the file complete, consistent and countable before a verifier reads it. You fix the structure and the stray characters, but you never alter the addresses themselves. The finished file has one address per row, one clearly labelled email column, UTF-8 encoding, and a log of every count you took along the way.
Preparation is different from verification. Verification estimates whether each address can receive mail. Preparation makes sure the verifier reads the right text in the right column. Confusing the two causes most avoidable errors, because teams blame the verifier for problems that started in the export.
Bottom line: Prepare the file so the verifier sees one clean address per row, then let verification judge each address.
Why does preparation change your verification results?
Unprepared lists fail in four ways, and each one has a different cost.
- Counts inflate. Duplicates and placeholders make totals hard to reconcile with your CRM, and they consume allowance you could have spent on higher-risk segments.
- Good addresses get marked Invalid. A stray non-breaking space or a curly quote can make a real address fail the syntax check. If you then suppress it, you have removed a real contact because of a formatting fault. A false removal loses a customer permanently, while a missed bad address only costs you one bounce, so false removals are the more damaging error.
- Attribution is lost. Without a source column, a high Invalid rate can't be traced to the trade-show import or the legacy CRM export that caused it, so the same problem repeats.
- Compliance gets harder. The data minimisation principle in Article 5(1)(c) of the UK GDPR asks you to process only the personal data a task needs. Exporting every legacy field into a third-party tool runs against that principle, and it is a core part of email verification compliance and hygiene.
Ecommerce and SaaS teams often feel these problems most, because their lists turn over quickly. Our overview of email verification for ecommerce and SaaS covers the typical sources of that churn.
Bottom line: Preparation protects your counts, your customers and your ability to explain results later.
Which file format should you export for verification?
Export as UTF-8 CSV with a header row and one address per row. It is the format verifiers read most predictably, and it preserves accented names. Use Excel for hand editing only, and save back to CSV before you upload.
| Format | Works well for | Watch out for |
|---|---|---|
| UTF-8 CSV | Almost every export; the default choice | Some European locales of Excel expect semicolon separators; a legacy encoding garbles accented names |
| Excel (XLSX) | Hand cleaning with filters, find-and-replace and formulas | Excel converts long numeric IDs to scientific notation and can turn text into hyperlinks; very large sheets slow down |
| Google Sheets | Shared cleaning with a team | Remove duplicates lets you choose which columns to compare, so an unselected timestamp column can stop true duplicates from matching |
| Plain text, one address per line | Email-only lists with no custom fields | You lose source tags, consent dates and any segmentation data |
Unlimited Verifier accepts CSV and Excel files up to 10MB and detects the email column automatically. Results can be exported as CSV, Excel or JSON.
Bottom line: Export UTF-8 CSV with a header row, and treat Excel as an editing tool rather than a delivery format.
How do you prepare an email list step by step?
Follow these nine steps in order. Each one produces a count you can check against the next, so any discrepancy can be traced to a specific fix.
- Freeze the original. Save a copy named with the source and date, such as
trade-show-2024-export-RAW.csv, and never edit it. This file is your audit trail. - Export every row in one pass. Include a column called
import_sourceand fill it with the origin of each row. Tagging at export costs almost nothing. Tagging after verification means guessing. - Confirm and rename the email column. Rename the header to
emailand remove any duplicate or translated headers. Auto-detection works best when there is one obvious candidate. - Clean the characters. Trim leading and trailing spaces, replace non-breaking spaces and curly quotes, and re-save as UTF-8. In Excel,
SUBSTITUTE(A2,CHAR(160)," ")replaces non-breaking spaces on Windows. CHAR codes follow different character sets on a Mac, so there, paste a copied non-breaking space into Find and Replace. - Split multi-address cells. A cell reading
a@x.com; b@y.comshould become two rows. Otherwise only one address is verified, or the whole cell fails. - Deduplicate on a normalised key. Compare trimmed, lowercased addresses, but keep the original text in the output. RFC 5321 treats domain names as case-insensitive and notes that local parts can be case-sensitive. Most large consumer providers in practice treat addresses case-insensitively, so lowercase is a sensible comparison key, not a rewrite of the data. When duplicates exist, keep the most recent record, but check consent fields before you discard the older row. If the older row holds a consent timestamp the newer one lacks, carry that field across rather than deleting it.
- Check the top domains for typos. Sort or pivot your domains by count. Misspellings such as
gmial.comorhotmial.comshow up as high-volume domains that match no major provider. Flag them for review. Don't auto-correct them, because a misspelt-looking domain can belong to a real company. - Quarantine the non-addresses. Move rows with no
@, placeholder values such asn/aortest@test.com, and example domains into a separate file. Don't delete them, because you will want that record when someone asks why the count dropped. - Log the counts and split. Record the raw count, the count after each step and the final total. Split the file if needed, using the limits in the section below.
For more on duplicates, see how to remove duplicate emails before verifying.
Bottom line: Each step should produce a number you can check, so any shortfall can be traced to the fix that caused it.
What data problems break verification, and how do you fix them?
Most verification anomalies come from a short list of formatting faults. The table covers the ones that appear most often in exports from spreadsheets, web forms and PDFs.
| Problem | Typical symptom | Fix |
|---|---|---|
| Non-breaking or stray spaces, often from Word, PDFs or web forms | Real addresses flagged Invalid; duplicates missed | Trim, and replace CHAR(160) (see step 4) |
| Curly quotes around addresses, such as “name@x.com” | Syntax failures | Replace with straight quotes, or delete them |
| Several addresses in one cell | Only one address verified, the rest ignored | Split into separate rows (step 5) |
| Legacy encoding, not UTF-8 | Garbled names in custom fields | Re-save as CSV UTF-8 |
Commas inside unquoted fields, such as Acme, Inc |
Columns shift and addresses land in the wrong column | Wrap the field in double quotes, or fix the export setting |
| Duplicate or translated headers, such as “E-Mail” and “Email” | Auto-detection picks the wrong column | Keep one header named email |
Placeholder values, such as none or test |
Inflated Invalid counts | Quarantine (step 8) |
| Mixed-case copies of the same address | Duplicates survive a case-sensitive dedupe | Use a lowercased comparison key (step 6) |
For messy files that fail at import, see how to clean a messy CSV of emails before upload.
Bottom line: Most failures are formatting faults, so fix the text before you blame the verifier.
How big can each file be before you need to split it?
Your plan's limits decide how you split the file. The figures below are from Unlimited Verifier's published plan details.
| Limit | Free ($0) | Pro ($29/month, or $25/month billed annually) |
|---|---|---|
| Emails per list | 150 | Up to 25,000 |
| Lists per month | 25 | Unlimited |
| Maximum emails per month via lists | 3,750 (25 × 150) | No list-count cap |
| Deep verifications per month | 750 | 25,000 |
| Upload size | 10MB | 10MB |
| Results kept | 24 hours | 30 days |
| API access | No | Yes, 100,000 emails per month |
Standard verification is unlimited on every plan, including Free, with no per-email fees. Deep verifications are the capped resource, so reserve them for the segments that need the closest look. For the wider cost picture, see email verification pricing.
Upload size is rarely the binding limit. A row with an address and three short fields is typically around 200 bytes, so 25,000 rows come to roughly 5MB. Files with dozens of custom columns hit 10MB first, and you can check the size in your operating system before uploading.
Worked example: a 71,300-row sign-up export
A B2B software company exports 71,300 rows from trade-show and webinar sign-ups. The counts below are illustrative.
- Raw rows: 71,300
- Duplicates after trimming and lowercasing removed: −6,820, leaving 64,480
- Non-addresses and placeholders quarantined: −1,140, leaving 63,340
- Multi-address cells split (380 cells holding two addresses each add one row): +380, leaving 63,720
On Pro, the file splits into three uploads: 25,000 + 25,000 + 13,720 = 63,720. The company uses its 25,000 monthly deep verifications on the highest-risk segment, the oldest trade-show imports, and runs standard verification on everything. At $29 for the month, the Pro fee works out to about $0.46 per 1,000 addresses (29 ÷ 63.72), or about $0.39 on the annual price. That is the fee spread over the list, not a per-email charge.
On Free, the same list needs 63,720 ÷ 150 ≈ 425 lists. The monthly cap is 25 lists, so at 3,750 emails a month the job would take 63,720 ÷ 3,750 ≈ 17 months. Free is useful for testing your process, not for cleaning a list of this size.
Bottom line: Split on the per-list limit, then check the monthly list cap before you start.
Should you verify the whole list or a sample first?
Verify the whole list for the final clean. Use a sample earlier, to estimate the size of the problem and decide where to focus.
| Approach | Use when | Trade-off |
|---|---|---|
| Full list | The final clean, when every address needs a label | Uses the most deep-verification allowance |
| Random sample | Estimating the Invalid rate before you commit | An estimate for the list as a whole, not a verdict on any address |
| Source-by-source | One import looks suspect | Depends on the import_source tag from step 2 |
| Real-time checks at signup | Stopping new bad data at the point of entry | Doesn't clean an existing list; see real-time email validation |
For a sample, the standard sample-size formula at 95% confidence and ±3% margin is n = 1.96² × 0.25 ÷ 0.03² ≈ 1,067 rows, using the worst-case assumption that half the list is invalid. A random sample of 1,000 rows gives a margin of about ±3.1%. That is enough to tell whether a list is roughly 5% invalid or roughly 30%. It is not enough to judge a 500-row segment. If the sample shows a high rate, see what to do if 30 percent of your list is invalid.
Bottom line: A 1,000-row random sample tells you how big the problem is, and the full verification tells you which addresses to act on.
How do you prepare and verify a list in Unlimited Verifier?
This tutorial assumes you have a CSV export and no integration with your ESP or CRM. Unlimited Verifier has no native ESP, CRM or Zapier connectors, so the workflow is manual unless you call the API.
- Export your contacts as CSV from your ESP or CRM, with all fields and an
import_sourcecolumn. - Save the original as a read-only copy, as in step 1 above.
- Clean the file using the nine preparation steps, and save it as CSV UTF-8. Keep custom fields in the file so they come back with your results. For the mechanics, see how to keep custom fields when verifying an email list.
- Split the file if it exceeds 150 rows on Free or 25,000 rows on Pro.
- Sign up for an account. The Free plan is enough to test the process on a 150-row sample.
- Upload and verify a list. Confirm the email column was detected correctly before you start. If the file has more than one address column, see how to verify a list with multiple email columns. For the upload mechanics, see how to upload a CSV to an email verifier.
- Read the three buckets. Valid addresses are ready to use. Invalid addresses go to suppression. Risky addresses include catch-all domains, disposable addresses and role accounts. For interpretation, see valid vs risky vs invalid email results explained. For catch-all domains specifically, see catch-all email verification.
- Download the results immediately as CSV, Excel or JSON. Free results are kept for 24 hours and Pro results for 30 days, so don't rely on the platform as your archive.
- Re-import manually. Load Valid contacts into your ESP as a new segment, and suppress Invalid addresses. To decide which to suppress and which to delete, see should I delete or suppress invalid emails. Then use how to segment a list by verification status to keep the buckets separate.
For a single doubtful address, such as a high-value customer who came back Risky, the free email checker gives a quick second look.
Automating it: Teams that verify continuously can use the email verification API. It supports single-address checks and bulk batches of up to 10,000 emails per request, and Pro includes 100,000 API emails a month. API access is not included on Free. This is the core of email verification API and automation, and it replaces the manual export and re-import loop with a script. The verification engine is also open source on GitHub, so technical teams can read the logic for themselves.
Bottom line: Preparation takes you from export to a file the verifier can read, and the tutorial takes you from that file to a labelled, re-importable list.
What are the most common preparation mistakes?
- Cleaning the only copy. Without the raw file, you can't reproduce counts or answer an ESP's questions.
- Running Remove Duplicates on whole rows. In Excel, the default dialog compares every column. If a timestamp differs, true duplicates survive. Select only the email column, or dedupe on a normalised key.
- Keeping the first duplicate. The first row is often the stalest. Keep the most recent record, but carry forward any consent field the newer row lacks.
- Deleting rows without a trace. Quarantine them, so every change to the count can be explained.
- Saving CSV in the wrong encoding. Accented names turn into unreadable characters, and the problem only shows up after upload.
- Forgetting the 24-hour window on Free. Results disappear if you don't download them the same day.
- Expecting a 40,000-row file to run on Free in one go. At 150 emails per list, that is 267 lists, far beyond the 25-list monthly cap.
- Verifying before tagging sources. You then can't tell which import caused the problem.
- Treating a valid address as a consented one. Verification indicates that an address can receive mail. It doesn't show that the person agreed to receive your messages.
Bottom line: Most preparation errors are avoidable, and each one leaves a count that would have caught it.
How we compared (and limitations)
This guide draws on public documentation and general data-handling practice. We have not benchmarked any verification tool against a controlled dataset, and spreadsheet behaviour can change between software versions. The plan limits and retention periods come from Unlimited Verifier's published plan details and may change. The 99.5% accuracy figure is Unlimited Verifier's own stated figure for deep verification, not an independent benchmark. For a broader view of the best email verification tools, read independent reviews, and for choosing between vendors, see how to choose an email verifier.
Preparation also cannot solve everything. It can't establish consent, and it can't guarantee inbox placement. Your sender reputation depends on what you do after verification. Google's email sender guidelines and Yahoo's sender requirements set expectations for bulk senders, and the FTC's CAN-SPAM compliance guide covers the US baseline. For ongoing upkeep once the list is clean, see email list maintenance best practices.
Bottom line: A prepared list is a far better starting point, but the real work lies in what you do with the results.
Preparation checklist in order
- Freeze the original file (copy it, never edit it).
- Export as UTF-8 CSV with one email column.
- Trim spaces and replace curly quotes.
- Split cells containing multiple addresses.
- Deduplicate on lowercased, trimmed address.
- Move placeholders and non-addresses to a quarantine file.
- Tag each row with its source.
- Split files above your tool's per-list limit.
- Log row counts at each stage so totals reconcile.
Frequently asked questions
What format should an email list be in before verification?
Export the list as a UTF-8 CSV with one email address per row and a clearly labelled email column. UTF-8 avoids garbled characters, and a single column keeps the verifier from reading the wrong field. Keep a source column if you can, so invalid results can be traced back to where the address came from.
Should I remove duplicate emails before verifying?
Yes. Deduplicate on a normalised key, meaning the address lowercased and trimmed of spaces. Removing duplicates first stops you paying allowance to check the same address twice and keeps your totals consistent with your CRM.
Can I delete invalid-looking rows before uploading?
Avoid deleting them. Move placeholders and non-addresses, such as 'none' or 'test@test', to a separate quarantine file instead. Some rows that look wrong may be formatting faults, and keeping them lets you recover real contacts.
Why do good email addresses come back as invalid?
Hidden characters are the usual cause. A non-breaking space, a curly quote or a stray character can make a real address fail the syntax check. Trimming whitespace and replacing curly quotes before upload usually fixes this.
How big can an email list be for verification?
Limits depend on the tool and plan. For Unlimited Verifier's Pro plan, lists can hold up to 25,000 rows, and free lists hold 150 emails. Check your provider's current documentation for file size caps, then split larger files into batches.
Should I keep a copy of the original list?
Yes, always. Keep an untouched copy of the original export so you can run audits, reconcile counts with your CRM and answer appeals about why an address was removed.
Does preparing a list change the email addresses themselves?
It should not. Preparation fixes structure and stray characters but never edits the addresses. Changing an address, even to correct an apparent typo, means you are verifying something that was never the customer's real address.
Is it allowed to send my full customer list to a verification tool?
It depends on your legal basis and your data processing agreement. Under the UK GDPR data minimisation principle, you should only share the personal data a task needs, so export just the email column where possible. Check the ICO guidance on data minimisation for details.
How often should I prepare and verify my list?
Most teams verify before a major campaign, after large imports and on a regular schedule for inactive segments. Frequency depends on how fast your list changes, so ecommerce and SaaS lists often need more frequent checks.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.