LOCAL SQLITE TOOLS

Export SQLite data to JSON

Choose a table or read-only query, then export complete results as JSON. Preserve exact SQLite values with a clearly defined output format.

No file uploadNo account needed

Choose your database

Small files open in memory. Larger files need supported browser disk storage and enough free space. Encrypted and WAL-mode browser files are not supported.

Select a table or read-only query
Export all rows as JSON

Keep the database together

Browse tables, views, indexes and triggers. Saving a database keeps its structure and data together; exporting CSV creates a separate table of values.

Export beyond the preview

Browsing shows 100 rows at a time. Query previews show up to 1,000 rows per statement. Use All rows JSON or Run + export full query JSON for the complete result. The Preview JSON action exports only the bounded preview.

Your working copy stays local

Files are processed in this browser. Save changes before closing or refreshing. Browser storage can be cleared and does not provide crash recovery.

Know the JSON you will get

The output has a columns array and positional rows. Duplicate column labels remain separate. SQLite NULL becomes JSON null; large integers use decimal text tags and BLOBs use hex tags.

This is a table or query export, not GeoJSON, a row-object API response or a complete database backup. Choose All rows JSON in Export after selecting your table.

{
  "columns": ["id", "payload", "note"],
  "rows": [[
    {"type":"integer","decimal":"9223372036854775807"},
    {"type":"blob","hex":"00ff"},
    null
  ]]
}

TRY A REAL DATABASE

A small library, ready to explore

The fictional sample has books, authors and 3,001 loans, with relationships and a useful view. Browse tables, try a join, or export all loans to check a complete result.

Download sample SQLite database

SELECT books.title, COUNT(*) AS loans
FROM loans JOIN books ON books.id = loans.book_id
GROUP BY books.id ORDER BY loans DESC;

Questions about this task

Does opening a database upload it?

No. File contents and SQL stay on this device. Ordinary page and asset requests reach the website host. This site does not provide remote AI access.

Can I edit a .db file?

Yes, when it contains a supported SQLite 3 database. The .db extension is also used by other formats. Open the database, switch off Read only and review changes before saving a complete copy.

What happens with large files?

Files up to 100 MiB use an in-memory copy. Larger files need browser disk storage, isolation support and available quota. Exports can need extra free space. An unsupported browser shows a capability error.

Does JSON preserve the whole database?

No. JSON exports values from one selected table or read-only query. It does not include table definitions, indexes, triggers or relationships. Save a complete SQLite copy for a database backup.

Can I open a live WAL database?

The browser accepts one database file and cannot safely reconstruct its WAL companions. Use the source application to checkpoint and export a standalone database first. Do not delete sidecar files manually.