SQLite database file visualizations
The SQLite database file format can be parsed without too much difficulty, unlike big traditional database management systems. Here are some web-page-based client-side tools to extract some kinds of low-level information that cannot be done through SQL or SQLite’s C API.
File header
This only examines the database file header, which is the foremost 100 bytes of the file.
Read local file:
| Field | Interpreted value | Error message |
|---|---|---|
| Format string: | ||
| Page size: | ||
| Write version: | ||
| Read version: | ||
| Page end reserved space: | ||
| Maximum embedded payload fraction: | ||
| Minimum embedded payload fraction: | ||
| Leaf payload fraction: | ||
| File change counter: | ||
| Database size: | ||
| First freelist trunk page: | ||
| Number of freelist pages: | ||
| Schema cookie: | ||
| Schema format number: | ||
| Default page cache size: | ||
| Largest root B-tree page: | ||
| Text encoding: | ||
| User version: | ||
| Incremental vacuum: | ||
| Application ID: | ||
| Reserved: | ||
| Version-valid-for number: | ||
| SQLite version number |
Page owners
This traverses all the B-trees to determine which table owns each page of the file. The memory and processing time scale linearly with file size, so visualizing files larger than ~100 MB is not recommended.
Read local file:
Legend:
| Color | Name |
|---|
The source TypeScript code and compiled JavaScript code are available for viewing.