Focused purpose
What this tool does
Validate CSV or TSV locally with required, type, range, length, regex, allowed-list and cross-column rules. Export valid and invalid rows without an account.
- ✓ Required and type rules
- ✓ Range, length and regex checks
- ✓ Allowed values
- ✓ Cross-column relations
Workflow
How to use it
- 01
Open the file and review inferred column types.
- 02
Add explicit rules and run validation.
- 03
Inspect failures, then export separate result files.
Available controls
Available options
- Build rules visually.
- Save non-sensitive recipes locally.
- Validate one or all columns.
- Export valid and invalid rows separately.
Required email and age range
Example before and after
Email is required and age must be between 18 and 120.
Before
id,email,age 1,ada@example.com,36 2,,17 3,bad,200
After
valid.csv: row 1 invalid.csv: rows 2–3 with rule codes
Expected result: One row passes and two rows receive explicit rule failures.
Practical scenarios
Common use cases
Check a CRM import template.
Validate IDs and email formats.
Enforce amount and date ranges.
HONEST LIMITS
Important limitations
- iValidation confirms configured rules, not overall business correctness.
- iComplex database lookups are unavailable in a front-only app.
FAQ
Questions about this tool
Can rules be saved?
Yes. Non-sensitive rule definitions can be stored locally as a recipe.
Can I export only invalid rows?
Yes. Valid and invalid subsets are generated separately with a report.
Does a valid export guarantee correct business data?
No. It guarantees only the rules you configured and the structural export checks.