DuckDB-Wasm’s (dynamic) extension loading is modeled after the regular DuckDB’s extension loading, with a few relevant differences due to the difference in platform.
Extensions in DuckDB are binaries to be dynamically loaded via
dlopen. A cryptographical signature is appended to the binary.
An extension in DuckDB-Wasm is a regular Wasm file to be dynamically loaded via Emscripten’s dlopen. A cryptographical signature is appended to the Wasm file as a WebAssembly custom section called
This ensures the file remains a valid WebAssembly file.
Currently we require this custom section to be the last one, but this can be potentially relaxed in the future.
INSTALL semantic in native embeddings of DuckDB is to fetch, decompress from
gzip and store data in local disk.
LOAD semantic in native embeddings of DuckDB is to (optionally) perform signature checks and dynamic load the binary with the main DuckDB binary.
INSTALL is a no-op given there is no durable cross-session storage. The
LOAD operation will fetch (and decompress on the fly), perform signature checks and dynamically load via the Emscripten implementation of dlopen.
Autoloading, i.e., the possibility for DuckDB to add extension functionality on-the-fly, is enabled by default in DuckDB-Wasm.
|autocomplete||Adds support for autocomplete in the shell|
|excel||Adds support for Excel-like format strings|
|fts||Adds support for Full-Text Search Indexes|
|icu||Adds support for time zones and collations using the ICU library|
|inet||Adds support for IP-related data types and functions|
|json||Adds support for JSON operations|
|parquet||Adds support for reading and writing parquet files|
|sqlite_scanner GitHub||Adds support for reading SQLite database files||sqlite, sqlite3|
|substrait GitHub||Adds support for the Substrait integration|
|tpcds||Adds TPC-DS data generation and query support|
|tpch||Adds TPC-H data generation and query support|
WebAssembly is basically an additional platform, and there might be platform-specific limitations that make some extensions not able to match their native capabilities or to perform them in a different way. We will document here relevant differences for DuckDB-hosted extensions.
The HTTPFS extension is, at the moment, not available in DuckDB-Wasm. Https protocol capabilities needs to go through an additional layer, the browser, which adds both differences and some restrictions to what is doable from native.
As with regular DuckDB extensions, DuckDB-Wasm extension are by default checked on
LOAD to verify the signature confirm the extension has not been tampered with.
Extension signature verification can be disabled via a configuration option.
Signing is a property of the binary itself, so copying a DuckDB extension (say to serve it from a different location) will still keep a valid signature (e.g., for local development).
Official DuckDB extensions are served at
extensions.duckdb.org, and this is also the default value for the
When installing extensions, a relevant URL will be built that will look like
DuckDB-Wasm extension are fetched only on load, and the URL will look like:
Note that an additional
duckdb-wasm is added to the folder structure, and the file is served as a
DuckDB-Wasm extensions are served pre-compressed using Brotli compression. While fetched from a browser, extensions will be transparently uncompressed. If you want to fetch the
duckdb-wasm extension manually, you can use
curl --compress extensions.duckdb.org/<...>/icu.duckdb_extension.wasm.
As with regular DuckDB, if you use
SET custom_extension_repository = some.url.com, subsequent loads will be attempted at
Note that GET requests on the extensions needs to be CORS enabled for a browser to allow the connection.
Both DuckDB-Wasm and its extensions have been compiled using latest packaged Emscripten toolchain.