Convert

Local · Zero upload

CSV / Excel ⇄ JSON

Spreadsheet import · JSON export · Header detection

CSV / Excel

Ready

Raw input

Parsed output

Fixed height; long code scrolls inside the panel

ABOUT

About CSV / Excel ⇄ JSON

Turn CSV or Excel spreadsheets into JSON arrays, or export JSON to CSV for easy data import and export.

Excel from ops, sales, and finance is often the first "real data" for API integration. Local parsing avoids uploading customer lists and order details to third-party converters—compliance teams appreciate that.

DEEP DIVE

Learn more about CSV / Excel ⇄ JSON

CSV and Excel are what business users know best; APIs and databases usually consume JSON. JSONSort converts both ways—headers map to JSON keys—so ops spreadsheets become program-ready structures fast.

Excel .xlsx files parse locally in the browser—no cloud spreadsheet upload—keeping business data private.

CSV has no single standard: delimiters may be comma, semicolon, or tab; quoting rules differ between Excel export and Unix cut. Always preview the first few JSON rows and confirm column names and types before scripts or DB writes.

FEATURES

Core capabilities

CSV → JSON

First row as headers; each row becomes a JSON object in an array output.

JSON → CSV

Flatten JSON arrays to tables for export to non-technical users.

Excel import

Drag-and-drop .xlsx / .xls files for parsing.

Delimiter detection

Auto-handle comma, tab, and other common CSV delimiters.

Instant preview

Paste CSV and immediately see the JSON array structure.

Local parsing

Spreadsheet data never uploads—suited for business tables with customer info.

Type inference

Numbers and boolean strings auto-detected—less parseInt downstream.

JSON flat export

Nested JSON arrays export to flat CSV for Excel.

HOW TO USE

How to use

1
Paste CSV or upload an .xlsx file
2
Confirm headers and delimiter
3
Copy JSON or export CSV
4
On failure, check the error, fix source syntax, and retry
5
Pretty-print with the formatter or export for downstream scripts

WORKFLOW

Typical workflow

End-to-end flow from import to export so teams use CSV / Excel ⇄ JSON consistently.

Prepare spreadsheet

Save Excel as CSV UTF-8, or drag-and-drop .xlsx directly.

Preview JSON

Check the first record's keys and value types.

Clean (optional)

Use merge & clean to drop empty columns, or format for readability.

Import downstream

Copy JSON to Postman, scripts, or Mock tools.

USE CASES

Use cases

Data

Data engineering

Convert ops Excel exports to JSON for ETL pipelines.

Backend

Backend developers

Bulk-import CSV user data, preview JSON structure, then write DB scripts.

Frontend

Frontend developers

Convert product CSV samples to JSON for Mock data sources.

Testing

QA engineers

Convert test-case CSV to JSON to drive automation frameworks.

Growth

Growth ops

Convert event signup Excel to JSON for marketing automation.

Finance

Finance reconciliation

Convert bank CSV statements to JSON for internal reconciliation APIs.

TIPS

Tips

CSV first row must be headers—otherwise keys become col1, col2, etc.
Fields with commas must be double-quoted or columns split incorrectly.
Multi-sheet Excel parses the first sheet only—export the target sheet first.
JSON → CSV is great for exporting API array responses to product/ops.
After conversion, use the formatter to confirm numbers weren't parsed as strings.
For large tables, validate column mapping on a few rows before the full file.
Windows Excel CSV may be GBK—save as UTF-8 before import.
Date columns often stay strings—parse by locale downstream.
Empty rows are skipped; blocks separated by blank rows may need manual cleanup.
Huge JSON arrays → CSV: watch Excel's ~1.04M row limit.

LOCAL VS ONLINE

Local vs online tools

JSONSort stays purely frontend—this comparison shows why local tools fit dev data better.

Comparison

JSONSort (local)

Typical online tools

Data privacy

Fully local, zero upload

Most require server upload

Response speed

Milliseconds, no network latency

Affected by network and server load

Offline use

PWA offline supported

Usually requires internet

Sensitive data

JWT/config/logs handled with confidence

Leak risk

Ads & tracking

No ads, no data tracking

Most include ads or Analytics

File drag-and-drop

Import local files directly

Some tools limit upload size

Tool integration

19 tools on one page

Usually one site per tool

Open & transparent

Pure static pages—audit the source

Closed-source server, not auditable

TROUBLESHOOTING

Common pitfalls & fixes

Issues you may hit in practice and how to handle them—save time on trial and error.

Misaligned columns

Tip:Commas inside fields without quotes—fix in Excel or add quotes manually.

Garbled Chinese text

Tip:Confirm UTF-8 encoding; choose UTF-8 CSV when importing in Excel.

Numbers become strings

Tip:Leading zeros or very long numbers stay strings—cast types explicitly downstream.

Wrong sheet

Tip:Only the first sheet is parsed—export the target sheet first.

FAQ

How are Excel formula cells handled?

Reads the displayed value (computed result), not the formula.

What do empty cells become?

Usually "" or null, depending on column type inference.

Does it support UTF-8 BOM CSV?

Yes. BOM is auto-detected and Chinese content is handled correctly.

Can I specify a custom delimiter?

Common delimiters are auto-detected. If that fails, convert tabs to commas before paste.

Can I skip headers?

Without headers you get col1, col2, etc.—always provide a header row.

Is data uploaded to a server?

No. All JSONSort tools run locally in your browser—your input is never sent to any backend.

Do I need to sign up or install anything?

No. Open the page and go—no account, no client download, PWA offline cache supported.

How large can files be?

Depends on browser memory; multi-MB data usually runs smoothly. Split very large files or use merge & clean first.