Article

How to Upload a CSV to an Email Verifier: Step-by-Step Guide

By Unlimited Verifier Team ·

Diagram of a CSV email list flowing through email verification checks into Valid, Risky and Invalid result groups when uploaded to an email verifier.

Summary

To upload a CSV to an email verifier, save your list as UTF-8 CSV or Excel under 10MB with one address per row in an email column, then upload it. Unlimited Verifier detects the column automatically and sorts every address into Valid, Risky or Invalid.

To upload a CSV to an email verifier, export your list with each address in its own column, save the file as UTF-8 CSV (or Excel) under 10MB, and drop it on the verifier's upload page. In Unlimited Verifier, the email column is detected automatically and every address is sorted into Valid, Risky or Invalid. Upload problems usually trace back to the file's structure rather than the tool, so preparation matters as much as the upload. For the wider process, see our bulk email list verification workflow.

Quick answer

What actually happens when you upload a CSV?

The verifier reads each row, takes the address from the email column, and runs it through a fixed sequence of checks. Each row comes back labelled Valid, Risky or Invalid, and the output keeps the original row order so you can join results back to your source data.

The checks run in this order:

  1. Syntax. Is the address shaped correctly? A common reference for address format is RFC 5322: a local part, an @ sign and a domain.
  2. Domain. Does the domain exist and accept mail?
  3. MX records. Does the domain publish mail servers to receive messages?
  4. SMTP mailbox. The verifier asks the receiving server whether the mailbox exists. The dialogue follows RFC 5321, and a well-behaved check stops before any message body is transmitted.

Two results need special handling. A catch-all domain accepts mail for any address, so the server cannot confirm a specific mailbox; those addresses land in Risky (see Catch-all email verification for how they're handled). Disposable and role-based addresses such as info@ are flagged so you can decide whether to mail them.

Why this matters: a list with a few hundred dead addresses is a nuisance. A list with thousands can trigger bounce-driven throttling or suspension at your sending provider. Google's email sender guidelines say bulk senders should keep spam rates below 0.1% and never let them reach 0.3%. Dead or recycled addresses are a common source of complaints, so cleaning the list protects that number too.

Bottom line: An upload is a batch version of the same checks, so the quality of your output depends on how cleanly the file is structured.

What file format and size limits apply?

Unlimited Verifier accepts CSV and Excel files up to 10MB, with automatic email-column detection. The plan limits decide how much you can verify in one go, and for most users the per-list row cap matters more than file size.

Limit Free ($0) Pro ($29/month, or $25/month billed annually)
File types CSV or Excel, up to 10MB CSV or Excel, up to 10MB
Emails per list Up to 150 Up to 25,000
Lists per month 25 Unlimited
Standard verification Unlimited Unlimited
Deep verifications per month 750 25,000
API access No Yes, 100,000 emails a month
Results kept 24 hours 30 days

Before you commit, compare email verification pricing against the list sizes you actually handle, not the headline price. On Pro, the monthly plan works out to about $1.16 per 1,000 deep verifications at full allowance (29 ÷ 25), and the annual plan to $1.00 per 1,000 (25 ÷ 25). Standard checks add no per-email cost.

Why the row cap binds first: A narrow file with an address, a first name and a signup date is typically somewhere around 60 to 100 bytes per row (a rough estimate that depends on your data). At that size, 10MB holds well over 100,000 rows, so the 25,000-row list cap is what you hit. Wide exports are different. At roughly 400 bytes per row (long notes, URLs, several dates), 10MB (10,000,000 bytes) holds about 25,000 rows, which lines up with the Pro cap. Excel .xlsx files are compressed, so they can hold more data per megabyte than the same CSV, but they still count against the row cap.

Bottom line: Plan around the per-list row cap first and check file size second. For Pro, 25,000 rows per list is your planning number.

How do you prepare the CSV so it uploads cleanly?

Preparation usually takes as long as the upload, and it prevents most of the errors people blame on the tool. If you want a deeper walkthrough, see how to prepare an email list for verification. The table below covers the problems that cause real trouble.

Problem in the file What you'll notice Fix
Several addresses in one cell, separated by commas or semicolons The row fails the syntax check Split them into separate rows
Semicolon-delimited export (common where Excel uses comma decimals) Every row lands in one column in the preview Save with a comma delimiter, or split with Data > Text to Columns
Accented names saved in the wrong encoding Garbled characters in custom fields after re-import Save as CSV UTF-8
Long numeric IDs Excel shows values like 1.23457E+16 after reopening Format the ID column as text before export
Unquoted names containing commas Columns shift and the email lands in the wrong column Quote each field, as RFC 4180 specifies
Case-only duplicates (Jane@Acme.com and jane@acme.com) The same person counts twice against your row cap and allowance Trim spaces, lowercase, then de-duplicate
Blank rows and footer totals Counted as failures and skew your percentages Delete them

Two more habits make the rest of the workflow easier. Export only the columns you need, plus any ID or custom field you'll want to join back later. And label the address column email, so auto-detection has an obvious match. If a contact has more than one address, see how to verify a list with multiple email columns. For a fuller cleanup routine, follow how to clean a messy CSV of emails before upload.

Bottom line: Ten minutes of preparation prevents most upload failures and keeps your row counts reconcilable at the end.

How do you upload a CSV to Unlimited Verifier, step by step?

  1. Create an account. Create a free account and test with a small file. Move to Pro only when a list exceeds 150 emails or you need API access.
  2. Prepare the file. Confirm it has a header row and a dedicated email column, is saved as CSV UTF-8 or Excel, and is under 10MB.
  3. Open the upload page. Go to Upload and verify a list and choose the file from your computer.
  4. Check the preview. Confirm the email column the tool detected. If it picked a different column, fix the header or the file before running the check.
  5. Check the row count. Data rows should equal the file's total lines minus the header. On Free, the list must hold 150 rows or fewer; on Pro, 25,000 or fewer.
  6. Run the verification. Wait for the job to finish before closing the tab.
  7. Read the three buckets. Valid addresses are safe to mail. Invalid addresses should be removed and suppressed. Risky addresses include catch-all, disposable and role-based addresses that need a decision.
  8. Download the results. Export as CSV, Excel or JSON the same day, since Free keeps results for 24 hours and Pro for 30 days.
  9. Reconcile the counts. Valid + Risky + Invalid should equal the rows you uploaded. Any gap means rows were skipped, so check the source file before going further.
  10. Re-import the Valid contacts into your sending tool as a new segment, as covered below.

For spot checks before a large run, the free email checker tests individual addresses, which helps when a single source looks suspicious.

Bottom line: The upload takes minutes. The reconciliation in step 9 is what proves the list was checked in full.

What if your list is bigger than the per-list limit?

Split the file into chunks no larger than the cap, then track the total across the month. The arithmetic decides what fits in a plan cycle.

Free plan example: A 10,000-row list needs 67 lists of 150 addresses (10,000 ÷ 150 = 66.7, rounded up). Free allows 25 lists a month, which is 25 × 150 = 3,750 emails per month at most. The job therefore spans three months: 3,750 + 3,750 + 2,500 = 10,000.

Pro plan example: The same 10,000 rows fit in one list, because Pro allows up to 25,000 per list. Splitting is only needed when a file goes beyond 25,000 rows.

To split in Excel, sort by a stable column such as signup date, then copy the header plus the first 25,000 data rows into one workbook, the next block into another, and so on. In Google Sheets, put each block on its own sheet and download each as CSV. Keep the original file untouched so you can reconcile the totals against it.

Bottom line: On Free, the monthly list count is the real ceiling (3,750 emails). On Pro, the 25,000-row cap per list is the only ceiling most users hit.

What does a 38,400-row checkout export look like in practice?

The example below is illustrative. The arithmetic and plan limits are real; the result percentages are hypothetical. It reflects a common pattern for email verification for ecommerce and SaaS teams that export customers from a store or billing system.

Starting point: An export of 38,400 data rows with columns for email, first name, customer ID and last order date.

Step 1: Remove duplicates. After lowercasing and trimming, 1,600 rows repeat an address already in the file, leaving 36,800 unique addresses. (Deduplication is covered in how to remove duplicate emails before verifying.)

Step 2: Split for the per-list cap. 36,800 exceeds 25,000, so split into two lists: 25,000 + 11,800 = 36,800.

Step 3: Plan the deep budget. Standard checks cover all 36,800 addresses at no extra cost. Deep verifications are capped at 25,000 a month. Assume this run uses 9,000 of them, which leaves 16,000 for later runs in the same month.

Step 4: Read the output (hypothetical results).

Bucket Count Share
Valid 33,100 89.9% (33,100 ÷ 36,800)
Risky 1,840 5.0%
Invalid 1,860 5.1%
Total 36,800

The totals reconcile: 33,100 + 1,840 + 1,860 = 36,800.

Step 5: Cost. One month of Pro at $29 covers the run. That's about $0.79 per 1,000 addresses ($29 ÷ 36,800 × 1,000). On the annual plan at $25 a month, the same run costs about $0.68 per 1,000.

Step 6: Re-import. Import the 33,100 Valid contacts as a new segment, suppress the 1,860 Invalid addresses, and keep the 1,840 Risky addresses out of main sends until they've been reviewed.

Alternative route: Using the Email verification API, a script could send the 36,800 addresses in batches of up to 10,000 per request. That's four requests (10,000 + 10,000 + 10,000 + 6,800), drawing 36,800 of the 100,000 monthly API emails included on Pro.

Bottom line: Once you know the three limits (rows per list, deep checks per month and the reconciliation total), the arithmetic is simple.

Web upload or API: which method should you use?

Use the web upload for one-off cleans and periodic list reviews. Use the API when verification needs to run automatically, such as when new contacts enter a pipeline. The email verification API and automation approach requires a developer, but it removes the export-and-upload loop.

Method Best for Input Limit Plan needed Output
Web upload Periodic cleans, one-off imports CSV or Excel up to 10MB 150 per list (Free) or 25,000 per list (Pro) Free or Pro CSV, Excel or JSON download
API batch Recurring or automated checks Addresses sent from your code Up to 10,000 per request; 100,000 emails a month on Pro Pro Results returned to your script
Free single checker Spot checks on individual addresses One address at a time Not designed for lists None Result on screen
Spreadsheet formulas Format checks only Cells in your sheet No platform limit None Syntax-style checks; they cannot confirm a mailbox exists

The last row is the one people underestimate. Formulas can flag a missing @ sign or a stray space, but they cannot ask a mail server whether a mailbox exists. A list can look perfectly formatted and still be full of dead addresses.

Bottom line: Use the web upload for lists, and the API when verification has to happen inside a workflow.

How do you get the results back into your sending tool?

Unlimited Verifier has no native ESP, CRM or Zapier integrations, so the loop is manual or scripted: export the results, re-import the Valid contacts, and suppress the rest. Plan that round trip before you start.

  1. Download the results file the same day, because Free keeps results for 24 hours and Pro for 30 days. Store it somewhere you control.
  2. Import the Valid rows as a new segment rather than overwriting your main audience. This keeps a clear record of what passed. See how to segment a list by verification status.
  3. Suppress the Invalid rows in your sending tool. Deleting and suppressing have different effects, so read should I delete or suppress invalid emails before you choose.
  4. Keep Risky rows out of main sends. Review them separately using what to do with unknown emails after verification and valid vs risky vs invalid email results explained.
  5. Keep your custom fields. To join results back to names, plans or customer IDs, follow how to keep custom fields when verifying an email list. Format ID columns as text before export so Excel doesn't round them.

Bottom line: Your spreadsheet is the integration, so treat the export-and-import step with the same care as the verification itself.

How should you handle privacy when uploading contact data?

Uploading a contact list to a third-party verifier means sharing personal data, so treat it as a vendor relationship. Good email verification compliance and hygiene covers both the verification and the handling of the data around it.

Bottom line: Verification reduces bounces but doesn't create consent, and the upload is a data-sharing decision you should document.

What are the most common mistakes when uploading a CSV?

If your results show a large share of Invalid addresses, read what to do if 30 percent of your list is invalid before you send anything.

Bottom line: Most mistakes are about file structure and bookkeeping, not the verification itself.

How we compared (and limitations)

This guide draws on public documentation: the RFCs that define address syntax, CSV format and SMTP behaviour, Google's sender guidelines, the GDPR text, the FTC's CAN-SPAM guide, and Unlimited Verifier's published plan facts. We have not run controlled tests against other verifiers, so this article doesn't rank tools against each other. For that comparison, see our guides to the best email verification tools and how to choose an email verifier.

Limitations to keep in mind:

Bottom line: Use the limits, file rules and reconciliation steps here as your working checklist, and confirm the figures that matter to your budget on the live plan page before you upload.

Upload checklist and reconciliation steps

  1. Export or save as UTF-8 CSV (or Excel), under 10MB.
  2. Put one address per row in a column named email.
  3. Remove blank rows, duplicates and merged header cells.
  4. Split files that exceed your plan's per-list cap.
  5. Upload and confirm the detected email column in the preview.
  6. Run the check and download results the same day.
  7. Reconcile: uploaded rows = Valid + Risky + Invalid.
  8. If totals differ, find and fix malformed rows, then re-upload.

Frequently asked questions

What format should my CSV be in before uploading?

Save the file as UTF-8 CSV, or use an Excel file, with one email address per row in its own column. Naming the column email makes detection easier. Keep the file under 10MB so the upload is accepted without trouble.

Why does my upload show fewer rows than my file contains?

Rows are usually skipped when they are malformed, such as stray line breaks, unescaped commas inside fields, or blank lines. Open the file in a plain text editor to check for these issues, fix them, and upload again. Then confirm that the total of Valid, Risky and Invalid matches the row count.

Can I upload a Google Sheets or Numbers file directly?

Export it first. Download the sheet as CSV or Excel from its file menu, then upload the exported file. This keeps the structure predictable and avoids formatting that can confuse the column detection.

What if my email column is not detected?

Check the preview step before running the check. If the wrong column is selected, rename the header to email in your source file and re-upload. Also remove any merged cells or extra header rows above the column names.

What does a Risky result mean after upload?

Risky means the address could not be confirmed as either deliverable or undeliverable. Common causes are catch-all domains, which accept mail for any address, and some role-based or disposable addresses. Decide case by case whether to send, based on how important the contact is and your tolerance for bounces.

How do I handle a list larger than the per-list limit?

Split the file into several smaller CSVs, each under the per-list row cap for your plan. Keep the header row in every part and run each part as its own upload. Afterwards, merge the exported results and remove any duplicate addresses.

Should I remove duplicates before uploading?

Yes, removing duplicates first saves time and keeps your counts accurate. Sort the email column and delete repeated addresses, ignoring letter case. The cleaned file will also make it easier to reconcile results against your source list.

How long are verification results kept?

Retention depends on your plan. Based on the article, results are kept for 24 hours on Free and 30 days on Pro. Export your results as CSV, Excel or JSON on the same day so you always have a local copy.

Does verifying a CSV send emails to the addresses?

Verification checks whether a mailbox exists without sending a message to the recipient. The process stops before any message body is transmitted. Verification does not replace permission-based sending, so keep your own consent records for every contact.

Why is my verification result different from a bounce I got before?

Verification gives a prediction based on checks at the time you run them, while a bounce is what the receiving server actually returned during a send. Mailboxes can be created, closed or made full at any time, so results can change. Re-verify older lists before a major campaign.

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 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.