When is this useful?
A 100-column CSV is hard to review by eye. Profiling gives you a shortlist: date-looking fields, numeric-looking fields, and columns with lots of blanks. That lets you spend attention where conversion risk is highest.
FREE WEB TOOL
Infer integer, number, boolean, date, or string types for each CSV column and show blank rates.
Use this before sending a CSV to another system when you want to quickly find columns that look numeric, date-like, boolean, text-heavy, or unusually sparse. It is a triage tool, not a schema generator.
A 100-column CSV is hard to review by eye. Profiling gives you a shortlist: date-looking fields, numeric-looking fields, and columns with lots of blanks. That lets you spend attention where conversion risk is highest.
The inferred type is based on the values, not on a schema stored in the CSV. A column full of 00123-style values may look like integers while actually being product identifiers. Treat the result as a review signal, not permission to convert the column.
0 and 1 is inferred as integer.If order_id is inferred as integer and created_at as date, pause before converting anything. A long or zero-padded order ID should probably stay text even though it looks numeric.
If an inferred type surprises you, inspect a few raw values from that column. The label matters less than why the values matched it. Blank rate is reported separately, so you can use type + sparsity together to prioritize review before import.