https://parquetkit.com/docs Practical guides on working with Parquet files — no Spark, no installs, everything in the browser. en https://parquetkit.com/docs/check-if-parquet-file-is-corrupted https://parquetkit.com/docs/check-if-parquet-file-is-corrupted Validate a Parquet file in your browser: check the footer and schema instantly, then scan every row group with one SQL query. No pyarrow, no Spark. https://parquetkit.com/docs/compare-two-parquet-files https://parquetkit.com/docs/compare-two-parquet-files Diff two Parquet files by key to find added, removed and changed rows — in your browser, with DuckDB SQL, or with a short pandas script. https://parquetkit.com/docs/merge-multiple-parquet-files https://parquetkit.com/docs/merge-multiple-parquet-files Combine several Parquet files into a single dataset with DuckDB SQL in your browser — including files whose schemas don't quite match — or with pyarrow. https://parquetkit.com/docs/open-parquet-file-without-spark https://parquetkit.com/docs/open-parquet-file-without-spark Five ways to open and inspect a Parquet file — from zero-install browser tools to DuckDB one-liners — and when each one makes sense. https://parquetkit.com/docs/open-parquet-in-excel https://parquetkit.com/docs/open-parquet-in-excel Excel cannot read Parquet natively. Convert the file to CSV in your browser — and trim oversized files with SQL first — to get it into a spreadsheet. https://parquetkit.com/docs/parquet-column-data-type-mismatch https://parquetkit.com/docs/parquet-column-data-type-mismatch Spark or Databricks fails reading a Parquet dataset when one file's column type changed. Here is how to find the drifted file and column, and fix it. https://parquetkit.com/docs/parquet-int96-timestamps https://parquetkit.com/docs/parquet-int96-timestamps Timestamps shifted by hours, wrong by centuries, or rejected outright? Your Parquet file probably uses legacy INT96. What it is and how to deal with it. https://parquetkit.com/docs/parquet-magic-bytes-not-found https://parquetkit.com/docs/parquet-magic-bytes-not-found The PAR1 magic bytes error means your Parquet file is truncated or not Parquet at all. Here is how to diagnose it in seconds and where the file broke. https://parquetkit.com/docs/parquet-vs-csv https://parquetkit.com/docs/parquet-vs-csv A practical comparison of Parquet and CSV — file size, query speed, type safety and tool support — with concrete guidance on choosing. https://parquetkit.com/docs/print-parquet-schema-without-installing https://parquetkit.com/docs/print-parquet-schema-without-installing See a Parquet file's columns, types and row count in seconds — in your browser, with no pyarrow, Spark or parquet-tools. Works for multi-GB files. https://parquetkit.com/docs/query-parquet-with-sql-in-browser https://parquetkit.com/docs/query-parquet-with-sql-in-browser Run real SQL against local Parquet and CSV files using DuckDB in the browser: joins, aggregates and window functions with zero setup.