Convert a SQLite database to JSON locally - ideal for APIs, scripts and web apps, no upload.
Running locally on your device ...
Running locally on your device ...
0%
Your files never left your device
Continue with this file
No re-upload neededThese tools accept .JSON - your file is handed over directly.
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
If you want to bring a SQLite database’s content into a JavaScript program, an API mock file or a test fixture, JSON is usually the more direct target than CSV - it supports real numbers, nests cleanly and is the language modern web apps think in anyway.
This tool opens the file entirely locally in the browser (sql.js, WebAssembly SQLite) and reads every user table via SQL. If the database holds exactly one table, a plain JSON array of row objects is produced. With several tables you get ONE JSON object mapping each table name to its own row array - so the whole database stays in one file, no ZIP needed.
The file never leaves your device - unlike online converters that upload an entire database to a server. The conversion even works offline after the first load.
| Input formats | SQLITE, DB, DB3, SQLITE3 |
|---|---|
| Output format | JSON |
| Batch processing | No |
| Processing | Locally in your browser (WebAssembly) |
| File upload | None |
Limitations: A single table yields a flat JSON array; several tables yield a {tableName: [...]} object. BLOB columns are emitted as base64 text. Views, indexes and triggers are not read. Very large databases need memory. Encrypted SQLite files (e.g. SQLCipher) are not supported.
No. It is opened and read entirely locally in the browser.
An object mapping each table name to its row array, e.g. {"customers":[...], "orders":[...]}.
Yes, INTEGER and REAL columns are written as real JSON numbers, not as text.
As base64 text, since JSON itself has no binary type.
Yes, with the "SQLite to XLSX" tool.
SQLite to CSV · SQLite to Excel · DBF to CSV · XLSX to JSON · JSON to CSV