GeoDataViewer
Menu
Launch Studio
Theme
.sqlite

SQLite Viewer

Learn what SpatiaLite is, how it extends SQLite for GIS, and when teams convert it into simpler exchange or delivery formats.

Upload your .sqlite or .db files containing spatial tables.
All processing runs locally in your browser.

SQLite

Upload your .sqlite or .db files containing spatial tables.

How to open SQLite online

View SQLite and Spatialite geospatial databases. Upload your .sqlite or .db files containing spatial tables.

Privacy

Files are processed on your device in the browser. GeoDataViewer does not upload your datasets to a server for viewing.

Common issues

If a dataset uses multiple required sidecar files, make sure you provide the complete set together. For best results, keep all sidecars in one zip archive when applicable.

Related tools

Measure distances, areas, elevation, and radius circles using the tools menu, then come back to inspect your SQLite layer on the map.

What is SQLite?

SpatiaLite extends SQLite with spatial types, indexes, and functions so a single portable database file can support GIS-style querying and editing workflows.

SpatiaLite is attractive because it combines the portability of SQLite with many of the practical benefits people expect from a spatial database.
It is especially useful when a project wants SQL-based filtering, joins, and structured storage without depending on a heavier server database or a loose collection of flat files.

What is SQLite used for?

  • Portable spatial database workflows that need SQL querying in one file.
  • Offline analysis, joins, and structured data management without a separate database server.
  • Moving database-style GIS projects between machines while staying in a file-based workflow.

Common use cases

  • Analyst handoff packages that need more structure than GeoJSON or CSV.
  • Field or laptop workflows that want database capabilities without running PostGIS.
  • Intermediate processing stores for ETL pipelines and local data science work.

Strengths

  • Single-file SQLite packaging is easy to move and archive.
  • Spatial SQL and indexing support make it more powerful than simple flat files.
  • Good compromise between database behavior and file-based portability.

Limitations

  • Less familiar to non-GIS or spreadsheet-only users than CSV and Excel.
  • Some consumer tools and lightweight viewers do not understand spatial SQL containers directly.
  • Tile delivery and simple presentation workflows may still prefer other targets.

File extensions and sidecar files

.sqlite
Common SQLite container extension used for SpatiaLite-enabled datasets.
.sqlite3 / .db
Alternate SQLite file extensions often seen in the broader ecosystem.
spatial metadata tables
Internal SQLite tables that register geometry columns, spatial reference metadata, and indexes.

Convert SpatiaLite / SQLite online

SQLite Viewer FAQ

When is SpatiaLite a good choice?

It is a strong choice when you want file portability plus spatial SQL, indexing, and structured storage in one SQLite database.

Why convert SpatiaLite to GeoJSON or CSV?

Those exports are easier for web apps, spreadsheets, and non-database consumers that do not need SQL-based storage.

Is SpatiaLite the same as GeoPackage?

Both build on SQLite, but they serve different ecosystems and conventions, so conversion often depends on which downstream tools need to read the data.