Skip to main content

​
libSQL / Turso Connections

TablePro supports libSQL in two modes: remote over the Hrana HTTP protocol (Turso cloud and self-hosted sqld) and local libSQL database files opened directly from disk. The driver is a downloadable plugin; TablePro offers to install it when you select libSQL / Turso in the connection form. See Plugins.

​
Connection Settings

Pick a mode with the Connection Mode dropdown:

​
Remote fields

​
Local File fields

In Local File mode the API Token field is hidden; local files need no authentication.
libSQL connection form showing Remote (Turso) and Local File modes

The libSQL connection form with the Connection Mode dropdown

Click Test Connection to verify, then Save & Connect.

​
Getting Your Credentials

​
Turso Cloud

Find the database URL on the Turso dashboard or with the CLI:

​
Self-hosted sqld

The default sqld HTTP endpoint is http://localhost:8080. If you started sqld without --auth-jwt-key-file, leave the token empty. With JWT authentication enabled, generate a token matching your configured key.
Do not open a file that is being synced as a Turso embedded replica while the owning app is running. Concurrent access to a syncing replica can corrupt it.

​
SQL Dialect

libSQL uses SQLite syntax; browsing, structure, EXPLAIN QUERY PLAN, data editing, and export work as they do for SQLite. See SQLite.

​
Troubleshooting

Authentication failed (HTTP 401): The token is wrong or expired. Generate a new one with turso db tokens create <name>; for sqld, check the JWT matches the configured key. Watch for stray whitespace in the pasted token. Invalid URL: Use https://your-db.turso.io for Turso or http://localhost:8080 for sqld, without a trailing slash or path. libsql:// URLs are accepted. Verify the database exists with turso db list. File not found (local mode): Re-pick the file with Browse… if it was moved or renamed. Encrypted libSQL files cannot be opened in local mode.

​
Known Limitations

Remote mode:
  • No persistent connections: each query is an independent HTTP request via the Hrana protocol
  • No multi-statement transactions: each SQL statement auto-commits independently
  • No custom SSL/SSH tunnels: connections use HTTPS (Turso Cloud) or HTTP (local sqld)
Local mode:
  • No embedded replica sync: local files open standalone, without syncing to a remote Turso database
  • No encrypted database files
  • libSQL-only SQL extensions (e.g. ALTER TABLE ALTER COLUMN) are unavailable; local mode uses the system SQLite engine
Both modes:
  • No database creation or switching from TablePro; a connection targets a single database
  • No bulk import through the plugin: use the Turso CLI or direct sqld import