JSON to CSV With Custom Delimiter
Not every CSV uses a comma.
Native JSON tool
JSON to CSV
Comma, semicolon, tab, pipe presets
Custom single-character delimiter
Proper RFC 4180 quoting
Switchable in one click
- Cost
- Free tier
- Sign-up
- Not required
- Processing
- Tool-specific
- Privacy
- Clearly disclosed
Add this JSON to CSV to your website
Drop the JSON to CSV into a blog post, product docs, intranet, or school portal with one iframe. Processing, privacy, and usage limits are the same as on the full tool page.
- One copy-ready line of HTML
- Responsive — adapts to any container width
- No API credentials are placed in the snippet
Embed code
<iframe
src="https://www.fixtools.io/json/json-to-csv?embed=1"
width="100%"
height="780"
frameborder="0"
style="border:0;border-radius:16px;max-width:900px;"
title="JSON to CSV by FixTools"
loading="lazy"
allow="clipboard-write"
></iframe>Attribution-friendly: a small "Powered by FixTools" link appears in the embed footer.
When non-comma delimiters are the right choice
Semicolons are the most common alternative to commas because they sidestep the European Excel locale problem. In German, French, Spanish, Italian, Dutch, and most other continental European locales, the comma is the decimal separator and conflicts with comma-delimited CSVs. A semicolon-delimited file opens cleanly into columns on those installs without invoking the Text Import Wizard. If you are sending data to recipients in continental Europe, semicolons are almost always the right default.
Tabs are common in scientific computing and Unix pipelines. The TSV (tab-separated values) format is essentially CSV with tabs, and tools like cut and awk handle tab-delimited files natively. Tabs also reduce the need for quoting because data values rarely contain literal tab characters, which makes TSV output cleaner and easier to read in a terminal than quoted CSV.
Pipes are common in log-style data and in some database export formats. The pipe character is unlikely to appear in data values, which again reduces quoting noise. Pipe-delimited files are easy to grep, easy to cut, and easy to scan visually. If your downstream tooling is a Unix pipeline, pipes are often a better choice than commas.
Custom characters serve niche use cases where the data contains all common delimiters. A file containing free text with commas, tabs, and pipes might use a rare character like the ASCII Unit Separator (US, decimal 31) as the delimiter to guarantee no collisions. FixTools accepts any single character as the delimiter, so even unusual choices are easy to configure.
How to use this tool
Pick comma, semicolon, tab, pipe, or any custom single-character delimiter for the converted CSV.
How It Works
Step-by-step guide to json to csv with custom delimiter:
- 1
Paste your JSON
Drop the JSON file or paste the text. The parser builds the schema preview.
- 2
Open the delimiter setting
In the options panel, find the Delimiter dropdown. Choose from comma, semicolon, tab, pipe, or pick Custom and type a single character.
- 3
Confirm in preview
The preview re-renders with the chosen delimiter visible between columns. Make sure no data value collides with the delimiter; if it does, quoting takes care of it but spot-check to be sure.
- 4
Download
Download the file. The output uses your chosen delimiter consistently across every row, with RFC 4180 quoting applied wherever a data value contains the delimiter, a newline, or a quote.
Real-world examples
Common situations where this approach makes a real difference:
German finance team Excel import
A finance team in Berlin uses German Excel, which expects semicolons. The converter outputs a semicolon-delimited CSV that opens with correct columns on first try, no Text Import Wizard required.
Unix pipeline with cut and awk
A data engineer pipes the converted CSV through cut and awk in a bash script. They pick tab as the delimiter because tab-delimited files are friendlier to those tools than quoted CSV.
Log ingestion with pipe-delimited expectation
A log analytics platform expects pipe-delimited input. The converter outputs pipe-delimited files that the ingestion endpoint accepts without configuration.
Free-text data with embedded commas
A researcher exports JSON with free-text fields containing many commas. A custom Unit Separator delimiter avoids excessive quoting and produces a cleaner file for downstream parsing.
Pro tips
Get better results with these expert suggestions:
Use semicolon for European Excel users
If you do not know the recipient's locale and they might be in Europe, defaulting to semicolon is safer than comma. Most Anglophone Excel installs also handle semicolons fine via the Text Import Wizard if needed.
Prefer tab for Unix pipelines
Tab is the friendliest delimiter for cut, awk, and other line-oriented Unix tools because data rarely contains literal tabs. The resulting TSV is also easier to read in a terminal than quoted CSV.
Avoid spaces as delimiter
Whitespace-separated files cause endless trouble because data often contains spaces. Stick with non-whitespace single characters unless your downstream tool genuinely requires space-delimited input.
Document your delimiter choice
When you ship a CSV with a non-standard delimiter, mention it in the email or filename. A README in the same folder or a note in the message saves the recipient a guessing step.
Frequently asked questions
Related guides
More use-case guides for the same tool:
Related tools
Other tools you might find useful:
Ready to get started?
Open JSON to CSV to review its free limits and processing method.
Open JSON to CSV →Free tier · No account needed · Transparent limits