Paste a semicolon-separated list, common in European CSV exports, and get back a clean JSON array. Runs entirely in your browser.
Semicolon to JSON array
Paste a semicolon-separated list and this app splits it on every semicolon, trims each value, and returns a formatted JSON array. Same job as the comma converter, aimed at the delimiter a large share of the world actually exports spreadsheets with.
It's local. The split runs in your browser, not on a server, so nothing you paste is uploaded and there's no limit on how many lists you convert.
Where the format comes from
In much of Europe and plenty of other locales, the comma is the decimal separator, so three and a half is written '3,5' rather than '3.5'. A spreadsheet set to one of those locales can't use a plain comma as its field separator without it constantly colliding with decimal commas already in the numbers.
So Excel and similar tools switch the field separator itself to a semicolon whenever the regional settings put a comma at the decimal point. The file's still called a CSV and opens the same way, but the character actually separating columns is a semicolon.
Workflow
Nothing to configure, no locale setting to pick first.
Why it matters
Open a semicolon-delimited European export with a tool that assumes commas, and one of two things happens: the whole row reads as a single column because there's no comma to split on, or worse, a decimal comma inside a number gets mistaken for a boundary and a price gets silently split in two.
That's a quiet source of wrong data rather than an obvious error, which is exactly why matching the delimiter to the real export matters more here than for a plain comma list.
The underlying reason
Because the semicolon does the delimiting here, not the comma, a value like '3,5' for a decimal, or 'Doe, Jean' for a name, passes straight through unharmed. The comma inside the value is just text to this converter, only a literal semicolon counts as a boundary.
That's the whole point of the format: it lets locales that use a comma as a decimal point keep using commas normally in their data, while still having an unambiguous character to separate fields.
Straight answer
No, like the comma converter, this is a plain delimiter split, not an RFC 4180-style parser with quoting rules. A semicolon inside a quoted field, rare but possible, would still be treated as a boundary here.
For the vast majority of semicolon-separated lists, plain values with no semicolon of their own, this never matters. It only surfaces with genuinely quoted, semicolon-containing fields, which are uncommon.
Who it's for
Developers integrating with European accounting, ERP or government data exports use it to get a semicolon-delimited row into JSON without reconfiguring a full CSV parser for one file. Anyone who's opened a '.csv' from a French, German, Italian or Spanish source and found everything bunched into one column reaches for it once they realise the real separator is a semicolon.
Localisation and data teams use it to normalise exports from multiple regions into one consistent JSON shape before feeding them into an API.
What comes out
JSON.stringify never infers type here, so every value in the array comes back as a string, quotation marks included, even one that looks purely numeric. A European-style decimal like '3,5' converts to the string "3,5", exactly as written, comma and all.
That's actually the safer default for this format specifically. Guessing that '3,5' meant the number 3.5 would require assuming a locale, and getting it wrong would silently corrupt the value. Leaving it as a string and converting deliberately afterward, with the locale you actually know, avoids that mistake.
Paste the list above and press Convert. Each semicolon-separated value becomes one array item.
Yes, no signup, no paste limit, no run limit. It runs entirely in your browser.
No, the split runs on your own device. Nothing is transmitted or stored.
Because the software that made it uses a locale where the comma is the decimal separator, so it uses a semicolon as the field separator instead.
No, only semicolons count as boundaries here, so a comma used as a decimal point passes through untouched.
They're trimmed automatically, so 'red ; blue; green' comes back as three clean items.
No, this is a plain delimiter split, not a full CSV parser, so a semicolon inside quotes would still be treated as a boundary.
The empty item between them is dropped, and a trailing semicolon at the end doesn't produce a blank final item.
Yes, no length cap and no run limit.
Yes, the layout stacks on narrow screens.
This splits on semicolons, what many European CSV exports actually use. The comma tool splits on commas, used elsewhere and for plain lists.
The file is very likely semicolon-delimited, common for spreadsheets set to a European locale, so a comma-based reader finds nothing to split on.
Yes, semicolon delimiting is common across most locales where the comma is the decimal separator.
Not yet, paste, convert, copy for now.
Yes, it converts any semicolon-separated text the same way regardless of whether the values are numeric.
No, every semicolon-separated value becomes its own array item, repeats included.
The output is always syntactically valid JSON. It can't tell you whether the split points matched your intent.
Yes, if you paste prose instead of delimited data, a semicolon joining two clauses gets treated as a boundary and splits the sentence apart. This is for delimited data, not running text.
Yes, nothing is transmitted anywhere. Processing happens locally in your browser.
Open it in a plain text editor and look at the raw characters between values. If there's no semicolon in sight, use the comma tool instead.
No, it stays a string, comma included, exactly as pasted. Converting it to a number requires knowing the locale, which this tool doesn't assume for you.
The empty item at that end is dropped, the same as two semicolons appearing in a row.