Every backend engineer has hit this at least once.
You export a CSV from the database — users, orders, transactions —
and something is wrong. The import fails. Columns are misaligned.
Excel mangled the encoding. Half the dates are in the wrong format
because the file came from a European locale.
So you do what feels natural: paste it into ChatGPT, or upload it
to some random online converter, just to look at the structure.
And somewhere in the back of your head, something feels off about
that. Because it should.
I built a browser-based CSV Toolkit to fix this
CSV Toolkit on ToolsHubKit
— free, no signup, runs entirely in your browser. The file never
leaves your machine. You can disconnect from the internet and it
still works.
Why CSV is actually hard
CSV looks simple. Values separated by commas, rows by newlines.
Except there's no real standard. RFC 4180 is advisory, and most
exporters partially ignore it. Here's what actually breaks in
production:
Delimiter confusion
Not all CSVs use commas. European Excel uses semicolons (because
the comma is the decimal separator there). MySQL dumps use tabs.
Legacy systems use pipes. Assume the wrong delimiter and every
column is misaligned — and the error is often silent.
Encoding mismatches
Excel on Windows exports Windows-1252 or Latin-1 by default.
Google Sheets exports UTF-8. MySQL defaults to Latin-1. Open a
Latin-1 file in a UTF-8 parser and é becomes é. Fun to
debug at 2am.
The BOM problem
Excel prepends a UTF-8 Byte Order Mark (EF BB BF) to CSV
exports. When parsers don't handle it, your first column header
gets an invisible character prefix. The toolkit strips BOMs
automatically.
Inconsistent column counts
Row 47 has 8 fields. Every other row has 7. The import fails at
row 47 — or worse, silently shifts all data right for the rest
of the file.
Quoted field edge cases
Per RFC 4180, any field containing a comma must be quoted. Many
generators skip this. So Acme Corp, Inc becomes two separate
fields in your import target.
What the toolkit does
- Auto-detects delimiter — comma, semicolon, tab, pipe
- Handles encoding — UTF-8, Latin-1, Windows-1252, BOM stripping
- Instant table preview — see exactly what a parser sees
- Highlights malformed rows — inconsistent column counts, unbalanced quotes, escaped field issues
-
Filters in-browser — keep rows where
status = "active", drop PII columns, reorder to match import target schema - Multi-format export — clean CSV, JSON array, Markdown table
- Works on large files — 100k+ rows, all local
The import workflow that saves hours
Before any significant data import:
1. Preview first
Drop the file in and scan the first 50–100 rows. Catch structural
issues before they affect the full dataset.
2. Validate column counts
Malformed rows are highlighted immediately. Fix them before the
import, not after it fails at row 50,000.
3. Handle PII
Before sharing any CSV in a ticket or Slack thread — remove
sensitive columns in the toolkit, or run it through the
PII Redactor
for full redaction.
4. Export to JSON if needed
For API testing or JavaScript pipelines, export directly to JSON
array. Validate the structure with the
JSON Formatter
before submitting.
5. Import the cleaned version
Not the raw export. Always the cleaned version.
A 30-second preview step consistently catches the issues that
would otherwise fail halfway through importing 500,000 rows and
leave the database in a partial state.
The privacy argument
Most of us have a vague sense that uploading sensitive data to
random web tools is bad. Let's be specific:
Database exports contain PII almost by default — names, emails,
phone numbers, addresses, payment references. When you upload
that file to an online tool, you have no visibility into:
- Where the file goes
- How long it's stored
- Whether it's logged
- Whether it ends up in a training dataset
The CSV Toolkit's client-side architecture isn't a marketing claim
— it's a technical constraint. There's no server to upload to.
The parsing runs in your browser's JavaScript engine, on your
hardware, against your local memory.
Safe for: production database exports, customer data samples,
internal financial reports — anything you'd think twice about
emailing.
Try it
Free. No account. No upload. Works offline.
ToolsHubKit has 40+ developer utilities built the same way —
all browser-based, all privacy-first. If you find this useful,
the suite is worth bookmarking.
Built this as a side project. Feedback welcome in the comments
— especially edge cases the parser should handle that it
currently doesn't.
Top comments (0)