What it is
A free checker that compares a CSV file with the contract you agreed on. It reads quotes, commas inside values, semicolons, tabs and Excel exports, and runs fully in your browser.
CSV contract checker
Write down the columns you expect, drop in the CSV your partner sent, and CSV Guard checks every header and every row. You get renamed and missing columns, bad dates, duplicates, broken numbers and risky cells with row numbers, plus an evidence note you can send back.
A free checker that compares a CSV file with the contract you agreed on. It reads quotes, commas inside values, semicolons, tabs and Excel exports, and runs fully in your browser.
Operations teams importing partner data, data engineers, founders babysitting a fragile import and support people caught between two vendors.
Imports fail with vague errors, or worse, load wrong data quietly. Here every problem has a column, rows and an example, so the fix starts with facts instead of a long email thread.
Files are read in this tab. Nothing is uploaded or stored.
Paste a schema and a CSV, or load the demo to see a full report.
The evidence note includes example values from the file. Check it before you send it outside your team.
Write the contract once and reuse it for every delivery.
order_id int required unique
email email required
amount decimal required
currency enum:EUR|USD|TRY
created_at date required
sku textWrite the column name exactly as agreed. Matching also catches different case, spacing and small typos, and tells you which one it was.
text, int, decimal, date, email, url, bool, or enum: with the allowed values joined by a vertical bar.
required means no empty cells, unique means no repeated values. Leave them out when they do not apply.
Paste the expected header line and every column is checked for presence and order only.
List the columns you expect with types and flags. Keep it next to your import code.
Paste the CSV or open the file. The separator, quotes and line endings are detected for you.
Errors break imports or load wrong data. Warnings are worth cleaning but will not stop you.
Copy the evidence note into the partner thread, or download the problems as a CSV for your team.
No. Parsing and checks run in this page, and the file never leaves your device.
A cell starting with = or @ can run as a formula when someone opens the file in a spreadsheet. That is a known attack called CSV injection.
An invisible character some tools put at the start of UTF 8 files. It can glue itself to the first header name and break matching.
It tells you exactly what to fix and where. Changing partner data automatically would hide the problem instead of solving it.