Tool Launcher

Search for a tool...

1tt.dev1tt.dev
All guides

SQLite in the Browser with Turso & libSQL

Open SQLite databases entirely client-side with WebAssembly — plus how Turso and libSQL are extending SQLite for edge and multi-tenant workloads.

SQLite everywhere

SQLite is the most deployed database engine in the world. It powers every iPhone, every Android device, every browser, and countless desktop and embedded applications. A single file holds an entire relational database — no server process, no configuration, no network round-trips.

The 1tt.dev SQLite Browser lets you open and query these files directly in the browser. Drag and drop a .sqlite, .db, or .sqlite3 file and start exploring — nothing is uploaded to a server.

The SQLite Browser is available on Pro and Max plans.

How it works

Under the hood, the browser uses sql.js — a WebAssembly compilation of the full SQLite C library. When you drop a file, it is read into memory and passed to the WASM engine. Every query runs locally in your browser tab with the same behavior as native SQLite.

  • Browse tables and views with column types, primary keys, and indexes
  • Run arbitrary SQL with syntax highlighting
  • Sort, filter, and paginate results in a data grid
  • Export query results as CSV

AI-assisted SQL

The SQLite Browser includes an AI assistant that generates SQL from natural language. Describe what you need — "find duplicate entries by email" — and the assistant writes a query using the actual tables and columns in your database.

  • Schema-aware — the AI reads your database schema and generates queries that reference real table and column names
  • Suggestion chips — one-click query suggestions based on the tables in your file, so you can start exploring immediately
  • Edit and refine — generated SQL lands in the editor where you can tweak it before running

Turso and libSQL: SQLite for the edge

SQLite was designed as an embedded, single-writer database. That model works brilliantly for local apps, but it has limitations for modern server workloads: no built-in replication, no network access protocol, and no multi-tenant isolation.

libSQL is an open-source fork of SQLite created to address these gaps while staying fully compatible with the SQLite file format and SQL dialect. It adds:

  • Server mode — libSQL can run as a standalone server that accepts connections over HTTP or WebSockets, turning SQLite into a networked database
  • Replication — built-in support for streaming replication from a primary to read replicas, enabling edge-distributed SQLite
  • Embedded replicas — an application can embed a local SQLite replica that syncs from a remote primary, giving you local-read performance with cloud durability
  • Multi-tenancy — namespaced databases on a single server, each isolated with its own schema and data
  • Extensions — native support for user-defined functions, virtual tables, and other extensions that upstream SQLite restricts in certain environments

What is Turso?

Turso is a managed platform built on libSQL. It provides hosted SQLite databases that replicate to edge locations around the world. You get the simplicity of SQLite — a single-file mental model, standard SQL, zero operational overhead — with the reach and durability of a distributed database.

  • Global replication — databases replicate to data centers close to your users for sub-millisecond reads
  • Embedded replicas — Turso's SDK lets your app embed a local SQLite file that syncs from the cloud, so reads never hit the network
  • Per-tenant databases — create thousands of isolated databases on a single Turso group, ideal for SaaS applications where each customer gets their own database
  • SQLite compatibility — Turso databases are real SQLite files. You can export them and open them in any SQLite tool — including the 1tt.dev SQLite Browser

Using Turso databases with 1tt.dev

If you use Turso or libSQL, you can export your database as a .sqlite file and open it in the 1tt.dev SQLite Browser for inspection. This is useful for:

  • Debugging production data without connecting directly to the live database
  • Inspecting schema changes before and after migrations
  • Sharing a snapshot of a database with a teammate
  • Running ad-hoc queries on an exported backup

Common use cases

  • Mobile app databases — pull the SQLite file from an iOS or Android device and browse it instantly
  • Browser storage — inspect cookies.sqlite, places.sqlite, and other browser databases
  • Dataset exploration — many open datasets ship as SQLite files. Drop one in and start querying
  • Quick SQL prototyping — test schema designs and queries without installing any database software