EOL.WikiEOL.Wiki
← ← Back to all products

SQLite

Active
DatabasesLatest Version: 3.53.4Latest Release: Jul 24, 2026

SQLite is a lightweight, self-contained, serverless SQL database engine used by millions of applications.

Support summary

SQLite currently has supported cycles. Track the next EOL date and validate upgrades before your change window.

What do EOL and support statuses mean?

Next EOL

No announced EOL date is currently listed.

Supported cycles

1

0 lts

Versions

3

Latest Version

3.53.4

Active Support

1

EOL

2

Lifecycle Timeline

Aug 17, 2000As of Sep 19, 2026
3Active · Date not announced
2EOL · Sep 18, 2004
1EOL · Sep 28, 2001
ActiveSecurityEOLHistorical phase unknown

Bars show history up to the snapshot date. Gray intervals lack dated support boundaries; arrows indicate an unannounced EOL date, not a support guarantee.

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
3Sep 18, 2004MaintainedDate not announced3.53.4No
Active
2Sep 28, 2001EndedSep 18, 20042.8.17No
EOL
1Aug 17, 2000EndedSep 28, 20011.0.32No
EOL

Data sources

Frequently Asked Questions

Which versions of SQLite have reached end of life?
The following SQLite versions have reached end of life and no longer receive security updates: 2, 1. It is recommended to upgrade to a supported version.
Is it safe to continue using SQLite 2?
SQLite 2 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of SQLite?
The latest version of SQLite is 3.53.4, released in the 3 release cycle.
How many versions of SQLite are currently supported?
SQLite currently has 1 actively supported version(s): 3.
When does SQLite 3 reach end of life?
SQLite 3 does not have a specific end-of-life date announced yet.
What should I do when SQLite reaches end of life?
When a SQLite version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.