Article
What File Formats Do Email Verifiers Accept? CSV, Excel and More
By Unlimited Verifier Team ·

Summary
Unlimited Verifier accepts CSV and Excel files up to 10MB and detects the email column automatically. Plain text, TSV, Google Sheets and Apple Numbers files need one export step to CSV or Excel before upload.CSV is the common denominator for bulk email verification, and Unlimited Verifier accepts CSV and Excel files up to 10MB, detects the email column automatically, and exports results as CSV, Excel or JSON. Plain text, tab-separated (TSV) and Google Sheets files need one export step to CSV or Excel before you upload them.
Quick answer
- Upload CSV or Excel, up to 10MB per file. CSV is the safest default.
- The email column is detected automatically, so you don't need to rename headers to a fixed name. Confirm the detected column before the run starts.
- Plan limits decide how you split a file. Free lists hold up to 150 emails, with 25 lists a month. Pro lists hold up to 25,000 emails each.
- Export results as CSV, Excel or JSON. Free keeps results for 24 hours; Pro keeps them for 30 days.
- Other formats need converting first, including plain text, TSV, Google Sheets and Apple Numbers.
This page covers the format question in depth. For the full export, verify and re-import process, see our bulk email list verification workflow.
Which file formats does Unlimited Verifier accept on upload?
Unlimited Verifier accepts CSV and Excel files, each up to 10MB. Anything else should be converted before upload. The table below shows what to do with each common source format.
| Format | Upload directly? | What to do first |
|---|---|---|
| CSV (.csv) | Yes | Save as UTF-8 and confirm the delimiter is a comma |
| Excel workbook | Yes | Keep the list on one sheet, with headers in row 1 |
| Google Sheets | No, export first | File > Download > Comma-separated values (.csv); see Google Docs Editors Help |
| Tab-separated (TSV) | No, convert first | Import into a spreadsheet, then save as CSV so fields with commas are quoted correctly |
| Plain text list | No, convert first | Put one address per row in a spreadsheet, add a header, save as CSV |
| Apple Numbers | No, export first | Export to CSV or Excel |
| Database or JSON export | No, convert first | Select the email and key fields only, then export to CSV |
| Compressed archive (.zip) | No | Unzip, then upload the CSV or Excel file inside |
CSV is plain text, with one record per line and fields separated by commas. RFC 4180 describes the format. A CSV has no styling, hidden sheets or formulas, which makes it predictable to move between systems. Many ESPs and CRMs offer a CSV export, so it's usually the shortest path from your source to the verifier.
Excel suits teams that keep lists in a workbook. The usual reasons a workbook reads unexpectedly are extra sheets, title rows above the headers and merged cells. If an Excel upload behaves oddly, re-save the list as CSV and upload that instead.
Bottom line: Upload CSV or Excel. Keep Excel to one clean sheet, and convert everything else first.
Why does the file's internal structure matter more than its extension?
A file can have the right extension and still fail, because most upload problems sit inside the file. Three structural traps cause most of them.
- Unquoted commas. RFC 4180 says fields containing commas, double quotes or line breaks should be wrapped in double quotes.
Jane,"Acme, Inc.",jane@acme.comis three fields. Without the quotes,Jane,Acme, Inc.,jane@acme.comreads as four, and the email moves from the third column to the fourth. - Semicolon delimiters. In many European locales, Excel saves "CSV" with semicolons, because the comma is the decimal separator there. The file looks normal in Excel but collapses into a single column in tools that expect commas. Open it in a plain text editor and check the first line.
- Encoding. Accented or non-Latin names (é, ñ, ü) turn into garbled characters if the file isn't saved as UTF-8, the encoding defined by the Unicode Standard. In Excel, choose "CSV UTF-8" under Save As.
There is also an invisible problem. Addresses copied from web pages or email signatures often carry trailing spaces or non-breaking spaces. RFC 5321 defines the mailbox syntax that SMTP uses, and a stray leading or trailing space can make an address fail a strict syntax check, even though it looks fine on screen.
Bottom line: Check the delimiter, quoting, encoding and whitespace. The extension alone tells you very little.
How big can a file be before it's rejected?
There are two ceilings: the 10MB file size and the per-list row limit, which is 150 emails on Free and 25,000 on Pro. Which one you hit first depends on how wide the file is.
At Pro's 25,000-row cap, a 10MB file averages about 400 bytes per row (10,000,000 ÷ 25,000 = 400). An email-only row is roughly 25 to 35 bytes, so a narrow file reaches the row cap first. A wide CRM export with 15 to 20 columns can reach the size cap first. Aim for 9MB or less so you have headroom, whichever unit a system uses to count megabytes.
Worked example: a 48,000-row CRM export
The file has 18 columns, and each field averages 28 bytes including its comma, so each row is 18 × 28 = 504 bytes.
- Total size: 48,000 × 504 = 24,192,000 bytes, or about 24.2MB.
- Size rule: 24.2MB ÷ 10MB = 2.42, so at least 3 files.
- Row rule: 48,000 ÷ 25,000 = 1.92, so 2 files would be enough by row count alone.
Option A keeps all 18 columns. Split into three files of 16,000 rows, each is 16,000 × 504 = 8,064,000 bytes, or about 8.1MB. All three fit.
Option B keeps four columns (email, first name, last name, signup date): 4 × 28 = 112 bytes per row, or about 5.4MB in total. Split by the row rule into 25,000 and 23,000 rows, the files are about 2.8MB and 2.6MB. Two files are enough.
Option B is leaner, but only the columns you upload can be joined back to your records. Keep the full export in your own system and match results on the email address. If you need extra fields returned in the output, see how to keep custom fields when verifying an email list.
Bottom line: Divide the file size by the row count to estimate bytes per row, then split by whichever limit binds first.
How many emails can each plan cover in a month?
Standard verification is unlimited on every plan, with no per-email fees. The limits that matter are list count, list size and deep verifications.
| Plan | Price | Lists per month | Emails per list | Deep verifications per month | API access | Results kept |
|---|---|---|---|---|---|---|
| Free | $0 | 25 | Up to 150 | 750 | No | 24 hours |
| Pro | $29/month, or $25/month billed annually | Unlimited | Up to 25,000 | 25,000 | Yes, 100,000 emails a month | 30 days |
Free check. A 3,000-contact list is 3,000 ÷ 150 = 20 lists, which fits within the 25 a month. A 4,000-contact list needs 4,000 ÷ 150 = 26.67, rounded up to 27 lists, which exceeds the cap. Free therefore covers at most 25 × 150 = 3,750 emails a month through list uploads.
Pro check. A 4,000-contact list fits in one Pro list, since the limit is 25,000 per list. The monthly price is $29, or $25 billed annually. Over a year, that's $348 monthly versus $300 annually, a saving of $48.
Cost per 1,000. If one full 25,000-row list runs in a month, monthly billing works out to $29 ÷ 25 = $1.16 per 1,000 addresses, and annual billing to $25 ÷ 25 = $1.00 per 1,000. This assumes one full list, so a lighter month costs more per address. The stated email verification pricing structure makes this easy to model before you commit.
Bottom line: Free suits small one-off checks. Pro is the plan for anything above 3,750 emails a month or any list over 150 rows.
How do you prepare and upload a file so it works the first time?
Work through these steps in order. Each one removes a failure that would otherwise show up later as a bad result or a rejected file.
- Export from your source as CSV. Select the email column and any fields you need to match results back later, such as a customer ID. Why: a clean export avoids reformatting a spreadsheet by hand.
- Open the file in a plain text editor and read the first line. Confirm the fields are separated by commas and the headers appear once. Why: a semicolon file looks fine in Excel but arrives as one column.
- Remove blank rows, title rows and extra sheets. Only the header row and data rows should remain. Why: a title row can be read as a contact.
- Trim whitespace and non-breaking spaces from the email column. Our guide on cleaning a messy CSV of emails before upload shows the fixes. Why: spaces cause syntax failures that look like dead addresses.
- Remove duplicate addresses. See how to remove duplicate emails before verifying. Why: duplicates use up your list allowance and make counts harder to reconcile.
- Check size and row count against the limits above, and split the file if needed. Use the Option A or Option B logic from the worked example. Why: the binding limit decides how many files you need.
- Save as UTF-8 CSV. In Excel, choose File > Save As > CSV UTF-8. Why: UTF-8 keeps accented names intact.
- Sign up if you don't have an account, then upload and verify a list. Confirm the detected email column before starting. For a walkthrough of the upload screen itself, see how to upload a CSV to an email verifier.
- Review the Valid, Risky and Invalid counts once processing finishes. If your file has two email columns, such as work and personal addresses, read how to verify a list with multiple email columns before uploading.
- Export the results before the retention window closes: 24 hours on Free, 30 days on Pro. Why: results disappear after that window, and you can't rebuild the export later.
Bottom line: Export, check structure, trim, deduplicate, check the limits, save as UTF-8, then upload and export within the retention window.
What format should you export results in?
Unlimited Verifier exports results as CSV, Excel or JSON. Each one fits a different next step.
| Export format | Best for | Watch out for |
|---|---|---|
| CSV | Re-importing Valid contacts into an ESP or CRM. The most portable option. | Opening it in Excel can strip leading zeros (postcodes, for example) and change long numbers. Keep the CSV as your import copy. |
| Excel | Reviewing Risky results by hand and deciding what to do with each group. | Excel auto-formats columns. Don't re-save a review copy as your import file. |
| JSON | Developers feeding results into scripts, databases or dashboards. | It needs parsing and isn't a spreadsheet format. |
The product has no native integrations with ESPs, CRMs or Zapier, so the workflow is to export a CSV, verify it, and re-import the Valid contacts, or to call the API from your own code. Results are sorted into Valid, Risky and Invalid. Our guide to valid vs risky vs invalid results explains what each bucket means. Risky results often come from catch-all email verification domains, which accept every address, so the mailbox can't be confirmed. Once you've re-imported Valid contacts, segmenting a list by verification status keeps the Valid, Risky and Invalid groups separate for later campaigns.
Keep a suppression list of Invalid addresses. That's part of email verification compliance and hygiene, and it stops dead addresses from returning in your next import.
Bottom line: Use CSV to re-import, Excel to review, and JSON to automate. Export within the retention window for your plan.
Should you upload a file or call the API?
A file upload suits a list you already have. The email verification API suits data that arrives continuously. Under the published plan facts, API access is on Pro only, and bulk requests accept up to 10,000 emails each.
| Scenario | Best input | Why |
|---|---|---|
| One-off import of 5,000 contacts from a CRM | CSV upload | One file, one result set, one re-import |
| Sign-up form that should check addresses as they're typed | Single-email API check | Results return per address; see real-time email validation |
| Nightly job adding new contacts from a database | Bulk API requests of up to 10,000 emails | No manual exports; counts against the Pro API allowance |
| One address before a sale or a send | Free email checker | No file needed |
Teams running email verification for ecommerce and SaaS flows often use both. A full CSV pass cleans the existing database, then the API checks new addresses as they arrive. For the automation patterns, see email verification API and automation.
As a worked example, a 48,000-address backfill takes five bulk requests (48,000 ÷ 10,000 = 4.8, rounded up) and uses 48,000 of Pro's 100,000 monthly API emails, leaving 52,000 for live checks. Re-verify the database on a schedule as described in email list maintenance best practices.
Bottom line: Upload a file for the backlog and use the API for everything that arrives after it.
What should you check on any verifier's file-format page?
Other best email verification tools differ on format support, and this article doesn't compare them. Instead, use the table below as a checklist. Fill in each vendor's column from its own help pages and pricing, and then compare like with like.
| What to check | Why it matters | Unlimited Verifier (published) |
|---|---|---|
| Accepted file types | Decides whether you convert first | CSV and Excel |
| Maximum file size | Wide CRM exports hit this limit first | 10MB |
| Maximum emails per list | Decides how many files you split into | 150 (Free), 25,000 (Pro) |
| Column detection | Avoids manual header mapping | Automatic email-column detection |
| Export formats | Decides the re-import path | CSV, Excel, JSON |
| Result retention | Sets how long you have to export | 24 hours (Free), 30 days (Pro) |
For a wider checklist covering accuracy claims and workflow fit, read how to choose an email verifier.
Bottom line: Compare vendors on the same six rows, and verify each one on its own published page.
What are the most common format mistakes?
- Uploading the wrong sheet from a multi-tab workbook. Keep only the sheet that holds the list, so an old tab can't be confused with live data.
- Leaving commas unquoted in company names or addresses. The row splits and the email lands in the wrong column.
- Using semicolons on a comma-based file. It looks fine in Excel and arrives as one column.
- Carrying trailing or non-breaking spaces into the email column. Addresses look valid to a person but fail syntax checks.
- Splitting by row count alone. A 48,000-row, 18-column file clears the row cap and still exceeds 10MB.
- Uploading the same addresses twice. You spend list allowance twice and can't reconcile the counts.
- Missing the retention window. Free results last 24 hours. Pro results last 30 days. Export before they expire.
- Re-importing Risky addresses automatically. Risky results need a decision first. See what to do with unknown emails after verification.
- Deleting Invalid addresses without a suppression list. Re-importing the same dead addresses brings the problem back. Read should you delete or suppress invalid emails.
- Compressing the file before upload. Unzip it first, since the accepted upload formats are CSV and Excel.
If a large share of results come back Invalid, the cause is usually the source of the addresses, not the file format. See what to do if 30 percent of your list is invalid.
Bottom line: Most failed uploads come from structure, limits or retention, and you can check all three before you start.
How we compared (and limitations)
This article is based on Unlimited Verifier's published product facts: CSV and Excel uploads up to 10MB, automatic email-column detection, CSV, Excel and JSON exports, Free at 25 lists of up to 150 emails a month, Pro at up to 25,000 emails per list, 24-hour and 30-day result retention, and API access on Pro. The company states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark.
The format rules come from public standards: RFC 4180 for CSV and RFC 5321 for mailbox syntax. Menu paths for Google Sheets and Excel reflect general behaviour, so check Google Docs Editors Help and Microsoft Support for current steps. We did not test other verifiers' format support, and vendor policies change without notice. The byte sizes, file splits and cost-per-1,000 figures are illustrative arithmetic on the stated limits. Measure your own file's size and row count before you split it.
Bottom line: Plan around the published limits, and use your own file's size and row count to decide how to split it.
Format conversion guide
| Format | Upload directly? | Convert to |
|---|---|---|
| CSV | Yes | n/a |
| Excel | Yes | n/a |
| Google Sheets | No | CSV (File > Download) |
| TSV | No | CSV |
| Plain text | No | CSV with header |
| Apple Numbers | No | CSV or Excel |
| ZIP | No | Unzip, then CSV/Excel |
Frequently asked questions
What file formats can I upload to an email verifier?
Most bulk email verifiers accept CSV and Excel files. Unlimited Verifier accepts both, with a 10MB limit per file. Other formats such as TSV, plain text, Google Sheets and Apple Numbers should be exported or converted to CSV or Excel first.
Is CSV or Excel better for email verification uploads?
CSV is the safer default. It is plain text with no hidden sheets, styling or formulas, so it parses predictably. Use Excel only if the workbook has one clean sheet with headers in row 1.
What is the maximum file size for email verification?
Unlimited Verifier accepts files up to 10MB each. Plan limits also cap how many emails a single list can contain, so large lists may need to be split into several files before upload.
Can I upload a Google Sheets file directly?
Not directly. In Google Sheets, choose File, then Download, then Comma-separated values (.csv), and upload the resulting CSV file instead.
Does the email verifier need a specific column name?
No. Unlimited Verifier detects the email column automatically. Confirm the detected column before the run starts so the right values are checked.
Why does my CSV fail to upload?
Common causes are unquoted commas inside fields, a semicolon or tab delimiter instead of a comma, non-UTF-8 encoding, and merged or extra header rows. Re-save the file as UTF-8 CSV with a comma delimiter and one header row.
Can I upload a ZIP file to an email verifier?
No. Unzip the archive first and upload the CSV or Excel file inside it.
What format should I export verification results in?
Results can be exported as CSV, Excel or JSON. CSV works best for importing back into an ESP or CRM, while JSON suits developers integrating results into other systems.
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.