Filoven
Open navigation
All conversions

CSV to JSON

Every CSV value is text. Numbers, booleans and dates are inferred on the way in, which is convenient until a leading-zero ID like 0042 becomes the number 42.

Runs in your browser // nothing is uploaded

Loading converter

What survives the conversion

Derived from what each format is able to store, not from what the conversion promises.

Kept

  • CSV carries nothing that JSON can also hold.
  • Nested structure, which CSV could not store
  • Data types, which CSV could not store

Lost

  • Row and column values
Settings used

Parsed per RFC 4180 with the first row as keys, emitted as an array of objects.

When not to convert

Check ID and postcode columns before trusting the output in a downstream system.

About these formats

Data

What is a CSV file?

CSV is plain text where each line is a row and values are separated by commas. It is the most portable tabular format in existence and has no types, no formulas and no sheets. Its weakness is ambiguity: quoting, encodings and delimiters vary between tools.

Read the format guide
Data

What is a JSON file?

JSON is a lightweight text format for structured data, standardised as ECMA-404. It supports objects, arrays, strings, numbers, booleans and null, and nothing else. That deliberate minimalism is why it replaced XML as the default format for web APIs and configuration.

Read the format guide

Common questions

Does converting CSV to JSON lose anything?

Yes. Row and column values cannot be carried into JSON and is dropped. Every CSV value is text. Numbers, booleans and dates are inferred on the way in, which is convenient until a leading-zero ID like 0042 becomes the number 42.

Are my files uploaded when I convert CSV to JSON?

No. The conversion runs in your browser tab, so the file is never transmitted and the page works offline once loaded.

What settings does Filoven use for CSV to JSON?

Parsed per RFC 4180 with the first row as keys, emitted as an array of objects.

When should I not convert CSV to JSON?

Check ID and postcode columns before trusting the output in a downstream system.

Related conversions

JSON to CSV
Not for deeply nested data. The result will either be lossy or unreadable.
YAML to JSON
Not for a config file people edit by hand. Comments are usually why it is YAML.
JSON to YAML
Not for an API payload or anything a machine consumes. JSON parses faster everywhere.
XML to JSON
Not for a document where attribute versus element ordering carries meaning, such as SOAP or XSLT.
JSON to XML
Not unless the receiving system demands XML. It is the larger and slower format.
CSV to Excel
Not if the file feeds a script or a data pipeline. Those want CSV.

This page uses the JSON ⇄ CSV, which handles other formats too.

Last updated 2026-08-03