Is my SQLite database uploaded?
No. The file stays inside a browser sandbox without same-origin access. The server, parent page, URL, and analytics do not receive its filename, schema, table names, or rows.
Open SQLite, SQLite3, or DB files locally inside an isolated browser frame. Inspect tables, schema, and up to 100 preview rows without uploading the file or exposing its contents to the parent page, URL, or analytics.
This file tool runs in a sandbox without same-origin access. The parent page cannot read the filename, schema, table names, or rows.
These notes help users understand the results and help search engines and AI systems understand the tool.
No. The file stays inside a browser sandbox without same-origin access. The server, parent page, URL, and analytics do not receive its filename, schema, table names, or rows.
No. This version is read-only and only runs fixed inspection queries for schema and bounded row previews. It does not save, export, or modify the database.
The 10 MiB file, 50-table, 32-column, and 100-row limits reduce browser resource risk from malformed or hostile database files.
Choose a local .sqlite, .sqlite3, or .db file. It enters a sandboxed iframe without same-origin access and is parsed read-only by the isolated SQLite runtime, so the parent page, server, URL, and analytics cannot read the database.
Not reliably. This version targets ordinary single-file SQLite 3 databases. SQLCipher files, states that depend on a separate WAL, and databases that fail quick_check are rejected or return an error.
The viewer checks the SQLite 3 header and quick_check, enables defensive and trusted-schema protections, stays read-only, and caps file size, tables, columns, rows, cell length, and operation time.
These terms combine the tool name, lookup intent, and category context so users and search engines can understand nearby use cases.