Persistent Databases in the Browser with DuckDB-Wasm and OPFS
A DuckDB blog post titled "Persistent Databases in the Browser with DuckDB-Wasm and OPFS" appeared on the DuckDB site, dated September 18, 2026, and was subsequently surfaced on Lobsters with a publication timestamp of September 19, 2026. The title pairs DuckDB-Wasm, the WebAssembly build of DuckDB, with OPFS, the Origin Private File System, indicating the post addresses keeping a database persistent in the browser rather than only in memory. The supplied source text consists of the page title and SVG path markup from the page, and does not include the article body. As a result, no version numbers, benchmark figures, storage limits, API names, browser support details, or performance claims can be reported from this source. What can be stated is limited to the framing in the title: the topic is persistent databases in the browser, and the two named components are DuckDB-Wasm and OPFS. Any further specifics about how persistence is implemented, what constraints apply, or how the approach performs are not present in the provided text and are therefore omitted.
The post points developers to a documented approach for keeping DuckDB-Wasm data persistent in the browser via OPFS instead of losing it on reload.