Convert JSON to PARQUET
Turn JSON files into PARQUET. A Parquet table with one row per object and its columns and types inferred by DuckDB; nested objects and lists become structs and lists.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop JSON files on the dialor turn it to pick what to do
JSON rows in a Parquet table.Each object becomes one row, with columns and types inferred by DuckDB.
What you get
One Parquet file with a row for each object in the JSON. The columns and their types are inferred by DuckDB from the data.
Nested objects become structs, and lists become lists. The conversion gives you one file.
Types and columns
You do not set the columns or types yourself. DuckDB infers them, so the table follows what the JSON holds.
The conversion has no options.
When it stops
If the JSON cannot be parsed, the conversion stops with
input_corrupted. The file needs to be valid JSON before it can become a table.To go the other way, use PARQUET to JSON.
JSON and PARQUET.What each format is.
The formats
JSON
JSON, the data format of every API.
- Extensions
- .json
- MIME type
- application
/json - Kind
- Text and data
Parquet
The columnar data format of analytics. Compressed, typed and fast to scan.
- Extensions
- .parquet .pq
- MIME type
- application
/vnd .apache .parquet - Kind
- Text and data
In your code.The same JSON to PARQUET conversion through the API, for your app or your agent.
$ cv convert report.json report.parquet$ cv convert report.json report.parquetQuestions.What people ask about JSON to PARQUET.
Yes. The table has one row per object.
DuckDB infers the columns and their types from the JSON.
Nested objects become structs, and lists become lists.
The file could not be parsed. The conversion stops with input_corrupted when that happens.