Confirm the schema and row count
Use the metadata panel for the loaded schema, then run a count. A renamed column, unexpected type, or surprising row total is often the fastest signal that you received the wrong file or pipeline version.
Open Parquet
Apache Parquet is a compressed, columnar file format — which is exactly why double-clicking a .parquet file gets you nothing. It is binary, so Notepad, Excel, and text editors show gibberish, and most advice online starts with "install Python and pandas".
You do not need any of that for a quick look. viewparquet opens local Parquet files directly in your browser: drag the file in and DuckDB-WASM reads it on your device. The file is not uploaded to viewparquet, there is no account, and no desktop software is required.
Updated August 21, 2026 · Reproducible checks, limitations, and primary references are included below.
Open your Parquet fileNo sign-up or install. Core file viewing and SQL processing run in your browser tab.
Or click "Open a file" and pick it. DuckDB-WASM parses the file on-device for viewing and SQL; its contents are not uploaded to viewparquet. You can also open a file straight from S3 or a URL.
Browse the virtualized grid, check column names and DuckDB types, and use the table metadata panel for a schema snapshot. Run SQL or export to Parquet, CSV, or JSON Lines when you need more.
Opening a file proves that it is readable; it does not prove that the rows are complete, unique, or safe to use. Check the structure and a few invariants before exporting or sharing a result.
Use the metadata panel for the loaded schema, then run a count. A renamed column, unexpected type, or surprising row total is often the fastest signal that you received the wrong file or pipeline version.
Check nulls, duplicate identifiers, timestamp ranges, and category values for the columns that drive the next decision. A grid preview can look plausible while a key field is incomplete farther down the file.
Select only the columns and rows needed for the task. This makes mistakes easier to spot and reduces browser work, but it is not a guarantee about memory use or remote bytes transferred.
Open the flights sample from the homepage and run this query. The checked-in file has 231,083 rows and three columns: delay, distance, and time.
SELECT
count(*) AS rows,
min(delay) AS min_delay,
max(delay) AS max_delay
FROM data;What to expect: Expected for the repository sample verified on August 19, 2026: 231,083 rows, a minimum delay of -58, and a maximum delay of 180. A different result means the input or sample version changed; it is not a universal Parquet expectation.
These sources support the format and tool behavior described on this page. Product-specific boundaries are checked against the shipped viewer using the claim-verification method.
No default desktop app opens .parquet files — the format is a binary, columnar data file, not a document. Use a Parquet viewer: viewparquet opens the file in your browser with no install, and command-line options include the DuckDB CLI and parquet-tools.
Open it in a browser-based viewer. Drag the .parquet file into viewparquet and DuckDB-WASM reads it locally — no Python, pandas, Spark, or install required. You can browse rows, inspect column types, and run SQL.
Open your browser (Edge or Chrome both work), go to viewparquet.com, and drag the .parquet file into the page. Nothing is installed and the file is processed locally. On a managed corporate machine, the site and WebAssembly runtime must still be permitted by your organization policy.
No. Microsoft's current Power Query connector matrix marks Parquet as unsupported in Excel. Open the file in viewparquet, export the rows you need to CSV, and import that CSV with Excel's text/CSV workflow instead.
For viewing, SQL, and export, DuckDB-WASM processes the local file in your browser and does not upload the dataset to viewparquet servers. Optional AI is a separate path: when you invoke it, your browser sends your message and configured context directly to the chosen provider, and settings can allow samples or bounded query-result values. Review Settings → AI and the provider policy before using AI with confidential data.
There is no universal file-size guarantee. Browser memory, Parquet layout, column types, and the query or export all affect the practical limit; the grid reads pages of results, so selecting only the columns and rows you need is the safest approach for a large file.
Drop a Parquet, GeoParquet, CSV, or JSON file into viewparquet: browse rows, run DuckDB SQL, and export results in-browser without uploading the dataset to viewparquet. Optional AI sends messages and applicable context directly to the provider you choose; review Settings → AI before use.