SQLite Editor
CREATE A LOCAL SQLITE FILE

Create a SQLite database

Choose a filename and a starting point. Create a real SQLite file, then add tables, run SQL and save a copy on your device.

No account or uploadA real SQLite file

Start a new database

Creates a new file on this device. In the editor, turn off Read only before adding or changing data. Use Save as to keep a copy.

  1. Inspect your database in the editor
  2. Add tables or records, then save a copy

Start blank

Get a valid initialized SQLite 3 file with no user tables. Use Database Structure to design your first table, or Execute SQL to create it. A filename without an extension receives .sqlite.

Or try a tasks table

The starting table has an integer primary key, required title and a done value that defaults to zero. It contains no records. Review its SQL before adding your own data.

Save the whole database

Save as creates a database copy containing its tables and data. CSV and JSON exports contain selected values instead. Keep the editor open until you have checked the saved file.

Build on a small, clear starting point

The Tasks table option uses the same schema builder as the editor. You can inspect the definition, add columns and review later changes in the existing tools.

Open an existing database instead
CREATE TABLE "tasks" (
  "id" INTEGER PRIMARY KEY,
  "title" TEXT NOT NULL,
  "done" INTEGER NOT NULL DEFAULT 0
);

Creating a SQLite file

Do I need to upload a file?

No. This page creates a new database locally. It does not modify an existing file. If another database has unsaved work, the editor asks you to review replacement before opening the new file.

Why does the new file start read-only?

The editor opens files in inspection mode. Turn off Read only in Database settings when you want to add a table or records. This makes the editing choice explicit.

Can I create a .db file?

Yes. Choose a filename ending in .db, .sqlite or .sqlite3. The contents are SQLite 3 regardless of which supported filename extension you choose.

Will it survive closing the browser?

Save a database copy before closing or refreshing. Browser-managed storage is not permanent storage, and this tool does not recover later edits after a crash.