pickfit

BrowseWeb apps

DuckDB Web Shell

A DuckDB SQL shell that runs in the browser via WebAssembly and queries Parquet, CSV and JSON files.

No install, just open itTested in a browserKnown vulnerabilities

Open it

Before you use it: known vulnerabilities

pickfit found 1 known high or critical vulnerability in the packages this site is built with (OSV.dev, 16 Nov 2026). Weigh this before you use it.

  • crates:flatbuffers 2.1.2 Generated code can read and write out of bounds in safe code (GHSA-3jch-9qgp-4844, critical, fixed in 22.9.29)

No install, just open it

shell.duckdb.orgOpen the site
  • No account needed
  • No ads seen
  • Contacted 2 other sites
  • Not checked whether what you type leaves your device

What it does

  • Run SQL queries in the browser
    How to use it
    1. Type LOAD httpfs; in the shell and press Enter.
    2. Type a query such as FROM '<parquet file URL>'; and press Enter.
    3. Read the result table below the query, which shows the row count and the first rows.
    Tested
  • Read Parquet, CSV and JSON files
    Not tested
  • Load core and community extensions
    Not tested
  • Share queries with a URL
    Not tested

How far pickfit got

  1. Opens in a browser
  2. 1 of 4 features work

Good for

  • query remote Parquet files with SQL in the browser
  • attach and read a remote DuckDB database file
  • run geospatial queries with the spatial extension

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

It worked when used in a browser

When pickfit opened it in a browser on 15 Nov 2026, the page loaded to its main screen. pickfit then used it, and this worked: Run SQL queries in the browser.

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.