Email verification
CSV Email Verification: A Practical Workflow for Clean Lists
CSV email verification, step by step: prepare a UTF-8 file, pick the email column, review repeated rows, read results and see which outcomes cost credits.

CSV Email Verification: A Practical Workflow for Clean Lists
You have a spreadsheet of contacts and want to know which addresses are worth keeping. How do you check them without breaking the file or paying for results you can't use?
Short answer: Save the list as a UTF-8 CSV, pick the one column that holds the addresses, and look over unreadable and repeated rows before you start. Then read each result by its category. Only completed valid or invalid results cost a credit. This guide walks through each step using FairValid's current help and pricing pages, checked on November 14, 2026.
Step 1: Prepare the file
FairValid's CSV and text list guide gives these file limits:
- Uploads: UTF-8 CSV or TXT, up to 100 MB (100,000,000 bytes) and 1,000,000 data rows.
- Pasted text: up to 8 MiB and 100,000 rows.
- Spreadsheet files: save them as CSV before you upload.
Before you export from your spreadsheet, check two things. First, all the addresses should be in one column. Second, if the first row holds column names, select "The first row names the columns" when you import.
You don't need to delete your other columns. The CSV guide says other columns stay attached to their original source row, so names, company fields or internal IDs stay linked to the address they came with.
Step 2: Choose the email column from the full-file preview
After you upload, look over the full-file preview and pick the column that holds the addresses. Take your time here. If a file has both a "work email" and a "personal email" column, picking the wrong one means you verify the wrong list.

Step 3: Review unreadable and repeated rows before the run
The CSV guide asks you to review unreadable and repeated rows before you start a run.
- Unreadable rows: Look at these before you go on. It's often cleaner to fix them in the source file and import again than to leave them in.
- Repeated rows: These are handled for you within the import. If the same address appears more than once in one imported list, it is checked once and the result is shared with every source row where it appears. Repeated rows don't create extra sample or run charges.
This rule only covers repeats within a single import. It doesn't mean that sending the same address again in a separate submission, or rechecking it later, is always free. If you have overlapping lists, think about merging them into one file first.
Step 4: Read results by category
The results guide describes results as evidence, not a delivery guarantee. Here is what each outcome means:
- Valid: a usable positive check. It doesn't guarantee inbox delivery.
- Invalid: the address did not pass.
- Catch-all: the domain may accept many addresses, so a conclusion about the specific mailbox may be less certain. Read the result detail before you decide.
- Unknown: the check could not return a dependable answer.
- Still checking: there is no final answer yet. This is not the same as Unknown.
The results guide lists technical failures and unprocessed items separately from Unknown, and says they don't create a net verification charge.
One practical way to sort the list: keep valid addresses for your next step, remove invalid ones, and set catch-all and Unknown rows aside for your own review policy. Don't put still-checking rows into any final category until they resolve.
Step 5: Understand what the run costs
The pricing page sets out the credit rules:
- A valid or invalid result costs 1 credit per completed result.
- Unknown and catch-all results have 0 net charge. Any credits held for them are released or returned.
- While a row is still checking, there is no final charge yet. A hold is not a completed charge.
Your account includes 300 free credits each month, and free credits are used first. The monthly allowance does not roll over. Paid credits don't expire while the account stays open. You can add credits with a monthly plan or a one-time purchase, and you don't need a subscription to buy credits once. As of November 14, 2026, the pricing page lists a one-time purchase of 10,000 credits at USD 19.50, excluding tax. Check the current quote and tax before you pay.
Illustrative example
This is a made-up example to show the arithmetic. It is not a measured result.
Say a CSV has 1,200 data rows, and 200 of them repeat addresses found elsewhere in the same file. That leaves 1,000 unique addresses to check. Suppose 900 come back valid or invalid and 100 come back Unknown or catch-all, with none still checking and no technical failures. The net charge is 900 credits. The repeated rows add nothing, and the 100 uncertain results have no net charge. If the full 300-credit monthly allowance is available, the first 300 credits come from it and the other 600 come from paid credits.
Step 6: Match results back to your original rows
Other columns stay attached to their original source row, and a repeated address shares one result across all its source rows. Together, that lets you match each result to the row it came from, so you can update your own list without guessing which row is which.

A quick checklist
- Save as a UTF-8 CSV within the size and row limits.
- Put the addresses in one column, and mark the header row if there is one.
- Confirm the email column in the full-file preview.
- Review unreadable and repeated rows, and think about merging overlapping lists into one import.
- Read each result category on its own terms, and keep still checking separate from Unknown.
- Use your attached source columns to match results back to your file.
Try it on your next list
If you have a list waiting, a small first import is a low-risk way to try this workflow with your monthly free credits. Keep the CSV guide and the results guide open during your first run.


