Convert Parquet to JSON
You have a .parquet file. The next tool wants JSON. You do not want to send the file to a converter you do not control.
Convert in the tab, not on a server
Parquet Fox opens the file locally. The query engine is DuckDB compiled to WebAssembly, running in this browser. The file is not uploaded to a Parquet Fox server for open, query, or export.
Caps we actually enforce: Parquet files up to 500 MB; CSV and JSON up to 2048 MB compressed on disk. Memory use still depends on the content, not only the compressed size.
SQL before export
Do not dump every row if you only need a slice. Run SQL in the tab first, then export JSON. Nested structs and lists become JSON objects and arrays in the result. That is usually what a JSON consumer wants.
- Open a file on the homepage and drop the
.parquet. - Optionally run SQL to pick columns or filter rows.
- Use Export and JSON.
When this is the wrong convert
Use a warehouse or a local DuckDB/Python job when you need a scheduled pipeline, many remote tables, or a file larger than the tab can hold. Need to inspect rows first? UseOnline Parquet Viewer. Need CSV for a spreadsheet instead? UseConvert Parquet to CSV.
FAQ
- Can I convert Parquet to JSON without uploading the file?
- Yes. Parquet Fox reads the file in your browser tab. The file is not uploaded to a Parquet Fox server for open, query, or export.
- Can I filter rows before I export JSON?
- Yes. Run SQL in the tab first, then export the result as JSON. That keeps the download smaller than dumping the whole file.