Why are numbers in quotes in the output?

Every CSV value becomes a JSON string on purpose. Automatic type guessing silently corrupts data — a phone number 0044… would lose its leading zeros and a product code 1e5 would become 100000. Strings are the only lossless choice.

Can it handle commas and line breaks inside values?

Yes, as long as those values are wrapped in double quotes — the standard CSV convention. Doubled quotes inside quoted values are also understood.

What if my file uses semicolons or tabs instead of commas?

Auto-detect picks the most frequent of comma, semicolon, tab and pipe in the first line, or you can choose the delimiter yourself from the dropdown.

Is my data uploaded to a server?

No. Parsing and conversion happen entirely in your browser — your data never leaves your device.

Convert CSV to JSON

Paste CSV data or upload a .csv file and get JSON back — an array of objects when the first row is a header, or an array of arrays when it isn't. Quoted fields, embedded commas, line breaks inside quotes and escaped quotes are all handled. Nothing is uploaded to Filesvo.

Paste your CSV

…or paste directly into the box above

DelimiterFirst row is a header

Processed on your device — files are never uploaded to Filesvo.

How to use Filesvo

Paste your CSV into the box, or upload a .csv file.
Pick the delimiter (auto-detect works for comma, semicolon, tab and pipe) and say whether the first row is a header.
Click Convert to JSON, then copy the result or download it as a .json file.

How the conversion works

The parser follows the CSV rules from RFC 4180: fields wrapped in double quotes may contain the delimiter, line breaks and doubled quotes; rows may end in Windows or Unix line endings; a UTF-8 byte-order mark is stripped. With a header row, each data row becomes a JSON object keyed by the header names — duplicate or empty header cells get positional names so no data is lost.

All values stay strings. The tool does not guess whether "007" is a number or "true" is a boolean, because guessing corrupts real data — leading zeros in phone numbers and IDs would vanish. If you need typed values, convert the specific fields in your own code where you know what they mean.

Transparency handling

Values are kept as strings deliberately — no type coercion — so IDs like 007 and text like TRUE survive untouched.

Private by design

Your files are processed directly in your browser using open-source engines that run in your browser and are not uploaded to Filesvo. Nothing is stored on our servers, because nothing ever reaches them.

Frequently asked questions

Why are numbers in quotes in the output?: Every CSV value becomes a JSON string on purpose. Automatic type guessing silently corrupts data — a phone number 0044… would lose its leading zeros and a product code 1e5 would become 100000. Strings are the only lossless choice.
Can it handle commas and line breaks inside values?: Yes, as long as those values are wrapped in double quotes — the standard CSV convention. Doubled quotes inside quoted values are also understood.
What if my file uses semicolons or tabs instead of commas?: Auto-detect picks the most frequent of comma, semicolon, tab and pipe in the first line, or you can choose the delimiter yourself from the dropdown.
Is my data uploaded to a server?: No. Parsing and conversion happen entirely in your browser — your data never leaves your device.

JSON to CSV Converter

Turn a JSON array of objects into CSV with proper quoting — entirely in your browser.

JSON Formatter & Validator

Pretty-print, validate or minify JSON with clear error messages — entirely in your browser.

XML to JSON Converter

Turn XML into readable JSON — attributes, nested elements and repeated tags handled — entirely in your browser.