A practical preflight before your next CSV import
Check structure, meaning, and destination rules before committing a table to another system.
A thoughtful toolkit for your tablesMessy data.
Messy data.
Clear next steps.
A clearer path from messy data to ready-to-use tables. Inspect a CSV, choose a rule, preview every change, and export a result you can check.
Start with a data check →Start with a common task
Nine useful starting points from our 25-tool collection.
Inspect
Data quality check
Find what needs attention.
Clean
Data cleaner
Tidy text. Keep control.
Clean
Duplicate remover
Keep the right record.
Compare
Two-table comparison
See exactly what changed.
Prepare
Date formatter
Make dates unambiguous.
Prepare
Import validator
Catch mistakes before import.
Inspect
Row filter
Keep records that meet a rule.
Combine
Join tables by key
Bring fields together using a unique key.
Export
Table format converter
Export CSV, TSV, JSON, or Markdown.
A simple, visible workflow
1
Read a file or paste a table
CSV and TSV, up to 5 MiB. Values are kept as text.
2
Choose what to check
Set a key, a date format, or a field rule you understand.
3
Review and export
See records and reasons before downloading a separate result.
Examples are fictional. They demonstrate rules using invented values. Check results against the requirements of your own import system.
From the Rowlane blog
Longer reads on the decisions around everyday table work.
Keep identifiers intact from export to import
A workflow for protecting leading zeros, long codes, and exact identifiers across applications.
Decide what counts as a duplicate before deleting rows
Separate repeated records from repeated entities and make a defensible decision about matching keys.
Tool-by-tool guides
Short instructions for a specific operation and its limits.
Start here
A five-minute check before your next CSV import
Read the structure first. A clean-looking spreadsheet can still carry an extra separator, an empty header, or a blank required value.
ComparisonCompare two snapshots without false matches
A dependable comparison needs a stable key, a clear before/after order, and an explicit meaning for a change.
ValidationBuild an import checklist from actual rules
A structurally valid CSV can still violate the receiving system’s rules. Turn those requirements into explicit checks.
DuplicatesChoose a duplicate key you can defend
Two records with the same name are not automatically the same customer. A useful duplicate rule starts with the identity of the record.
For spreadsheets, export the worksheet you need as UTF-8 CSV or TSV. XLSX workbook formulas, styles, and multiple worksheets are outside this browser workflow.