Skip to content
Database

SQLite Releases

Track every SQLite release. Version timelines, feature evolution, WASM support, and usage guidance for the world's most deployed database.

Official Site Documentation

—

Total Versions

—

Supported

—

Latest

Version Timeline

All tracked releases with lifecycle status and EOL dates.

Loading version data…

Lifecycle Timeline

Visual overview of active support and maintenance windows.

3.38
3.39
3.40
3.42
3.44
3.46
3.48
2022 2023 2024 2025 2026 2027 2028
Active
Maint
Active
Maint
Active
Maint
Active
Maint
Active
Maint
Active
Maint
Active
Maint
Active / LTS
Maintenance
Today

Upgrade Paths

Migration guidance between major versions — breaking changes, effort estimates, and tips.

Any 3.x Latest 3.x Low Difficulty
Est. < 15 minutes

Breaking Changes

  • No breaking changes — all 3.x versions are backward compatible
  • Database file format unchanged since 3.0.0 (2004)
  • New features are additive and opt-in

Migration Notes

SQLite upgrades are trivially easy. Replace the binary/library. No schema migration needed. No data conversion. Old databases just work. This is one of SQLite's greatest strengths.

Version Risk Assessment

Evaluate risk factors before choosing a version for production.

Version EOL Risk CVE Risk Ecosystem Cloud Support Overall Recommended Action
SQLite 3.35 and below None Low Supported Full Low Works forever — but update for math functions, STRICT tables, JSONB
SQLite 3.40+ None Low Active Full Low Current — recommended

SQLite has no EOL risk. Scores reflect feature currency only. Assessed as of March 2026.

Feature Evolution

Side-by-side feature differences across major versions.

Feature 3.37 3.39 3.42 3.45
STRICT tables Stable Stable Stable Stable
Math functions Stable Stable Stable Stable
JSON functions Stable Stable Stable Stable
JSONB (binary JSON) No No No Stable
FTS5 (full-text search) Stable Stable Stable Stable
RIGHT/FULL OUTER JOIN No Stable Stable Stable
WASM support Preview Stable Stable Stable
Column-level COLLATE Stable Stable Enhanced Enhanced
File format 3.x 3.x 3.x 3.x
Support pledge 2050 2050 2050 2050

Embed Badges

Add live SQLite status badges to your README, docs, or dashboard.

Health Status

Overall support health

SQLite Health Status
![SQLite Health Status](https://img.releaserun.com/badge/health/sqlite.svg)

EOL Countdown

Next end-of-life date

SQLite EOL Countdown
![SQLite EOL Countdown](https://img.releaserun.com/badge/eol/sqlite.svg)

Latest Version

Current stable release

SQLite Latest Version
![SQLite Latest Version](https://img.releaserun.com/badge/v/sqlite.svg)

CVE Status

Known vulnerabilities

SQLite CVE Status
![SQLite CVE Status](https://img.releaserun.com/badge/cve/sqlite.svg)

Frequently Asked Questions

Common questions about SQLite releases and lifecycle.

Does SQLite have end-of-life dates?
No. SQLite has pledged support until 2050. There are no EOL versions. All SQLite releases are backward compatible. The file format has been stable since 2004 (version 3.0) and is guaranteed stable through 2050.
When should I use SQLite vs PostgreSQL?
SQLite is ideal for: embedded/mobile apps, local-first applications, development/testing, configuration storage, and single-server web apps handling <100K requests/day. PostgreSQL is better for: multi-server deployments, high-concurrency writes, complex queries on large datasets, and when you need advanced features (extensions, replication, LISTEN/NOTIFY).
Can SQLite handle web application traffic?
Yes, for many workloads. SQLite handles read-heavy traffic well. With WAL mode and proper configuration, it handles moderate write loads on a single server. Rails, Laravel, and Django all support SQLite in production. Rails 8 uses SQLite by default for new apps (Solid Queue, Solid Cache, Solid Cable).
What is SQLite WASM?
SQLite compiles to WebAssembly and runs in web browsers. This enables client-side databases in web applications. Combined with the Origin Private File System (OPFS), SQLite WASM provides persistent local storage with full SQL capabilities. Libraries like sql.js and wa-sqlite make this practical.
What are STRICT tables?
STRICT tables (added in 3.37, 2021) enforce type checking on columns. Traditional SQLite uses type affinity (any value can go in any column). STRICT tables reject type mismatches, making SQLite behave more like PostgreSQL/MySQL. Recommended for new projects that want data integrity.

Related Tools

Dep EOL Scanner

Check your dependencies for end-of-life packages.

Stack Health Scorecard

Get an overall health grade for your tech stack.

Release Index

Browse all tracked platforms and their release timelines.