Loading WASM module... If this takes "a long time" it may have failed and the browser's dev console may contain hints as to why.

This page lists the SQLite3 APIs exported by `sqlite3.wasm` and exposed to clients by `sqlite3.js`. These lists are generated dynamically by loading the JS/WASM module and introspecting it, with the following caveats:

- Some APIs are explicitly filtered out of these lists because they are strictly for internal use within the JS/WASM APIs and its own test code.
- This page runs in the main UI thread so cannot see features which are only available in a Worker thread. If this page were to function via a Worker, it would not be able to see functionality only available in the main thread. Either way, it would be missing certain APIs.

This page exposes a global symbol named `sqlite3` which can be inspected using the browser's dev tools.

Jump to...

- `sqlite3` namespace
- `sqlite3.version` object
- `sqlite3_...()` functions
- `SQLITE_...` constants
- `sqlite3.oo1` namespace
- `sqlite3.wasm` namespace
- `sqlite3.wasm.pstack` namespace
- Compilation options used in this module build

# `sqlite3` Namespace

The `sqlite3` namespace object exposes the following...

# `sqlite3.version` Object

The `sqlite3.version` object exposes the following...

# `sqlite3_...()` Function List

The `sqlite3.capi` namespace exposes the following `sqlite3_...()` functions...

`` = function is specific to the JS/WASM bindings, not part of the C API.

# `SQLITE_...` Constants

The `sqlite3.capi` namespace exposes the following `SQLITE_...` constants...

# `sqlite3.oo1` Namespace

The `sqlite3.oo1` namespace exposes the following...

# `sqlite3.wasm` Namespace

The `sqlite3.wasm` namespace exposes the following...

# `sqlite3.wasm.pstack` Namespace

The `sqlite3.wasm.pstack` namespace exposes the following...

# Compilation Options

`SQLITE_...` compilation options used in this build of `sqlite3.wasm`...