SQLite

{{Short description|Serverless relational database management system}} {{Infobox software | logo = SQLite370.svg | logo size = 220px | screenshot = SQLite3.png | caption = Screenshot of <code>sqlite3</code> command-line shell program | collapsible = | developer = D. Richard Hipp | released = {{Start date and age|2000|8|17|df=yes|br=yes}} | latest preview version = | latest preview date = | programming language = C | operating system = Cross-platform | platform = | size = 699&nbsp;KiB | genre = RDBMS (embedded) | license = Public domain<ref name="license">{{cite web | url = https://sqlite.org/copyright.html | title = SQLite Copyright | publisher = sqlite.org | access-date = May 17, 2010 }}</ref> | website = {{Official URL}} }} {{Infobox file format | name = SQLite Database File Format | icon = | extension = .sqlite, .sqlite3, .db, .db3, .s3db, .sl3 | _nomimecode = yes | mime = <code>application/vnd.sqlite3</code><ref>{{cite web |url = https://www.iana.org/assignments/media-types/application/vnd.sqlite3 |title = SQLite database file format media type at IANA |website = Internet Assigned Numbers Authority |publisher = IANA |access-date = 2019-03-08 }}</ref> | type code = | uniform type = | magic = <code>53 51 4c 69 74 65 20 66 6f 72 6d 61 74 20 33 00</code> (zero-terminated ASCII "SQLite format 3") | developer = | genre = | released = 2004-06-18 | extended from = | standard = | open = yes (Public Domain) | url = {{URL|https://sqlite.org/fileformat.html}} }} {{SQL sidebar}}

'''SQLite''' ({{IPAc-en|ˌ|ɛ|s|ˌ|k|juː|ˌ|ɛ|l|ˈ|aɪ|t}} "S-Q-L-ite",<ref>{{cite episode |series=The Changelog |number=201 |title=Why SQLite succeeded as a database — Richard Hipp, creator of SQLite |time=00:16:00 |url=https://changelog.com/podcast/201 |quote=How do I pronounce the name of the product? I say S-Q-L-ite, like a mineral. |access-date=2025-04-11 |archive-date=2022-07-07 |archive-url=https://web.archive.org/web/20220707033506/https://changelog.com/podcast/201 |url-status=live }}</ref><ref>{{cite video | people = D. Richard Hipp (presenter) | date = May 31, 2006 | title = An Introduction to SQLite | url = https://www.youtube.com/watch?v=f428dSRkTs4#t=1m14s | format = video<!-- HTML5 WebM video is available --> | publisher = Google Inc. | access-date =March 23, 2010 | time = 00:01:14 |quote={{IPA|[ˌɛsˌkjuˌwəlˈaɪt̚]}}}}</ref> {{IPAc-en|ˈ|s|iː|k|w|ə|,|l|aɪ|t}} "sequel-ite"<ref>{{cite video | people = D. Richard Hipp (presenter) | date = May 31, 2006 | title = An Introduction to SQLite | url = https://www.youtube.com/watch?v=f428dSRkTs4#t=48m15s | format = <!-- HTML5 WebM video is available --> | publisher = Google Inc. | access-date =March 23, 2010 | time = 00:48:15 |quote={{IPA|[ˈsikwəˌlaɪt̚]}} }}</ref>) is a free and open-source relational database engine written in the C programming language. It is not a standalone application; rather, it is a library that software developers embed in their applications. As such, it belongs to the family of embedded databases. According to its developers, SQLite is the most widely deployed database engine, as it is used by several of the top web browsers, operating systems, mobile phones, and other embedded systems.<ref>{{cite web |url = https://sqlite.org/mostdeployed.html |title = Most Widely Deployed SQL Database Estimates |publisher = SQLite.org |access-date = May 11, 2011}}</ref>

Many programming languages have bindings to the SQLite library. It generally follows PostgreSQL syntax, but does not enforce type checking by default.<ref name="Owens 2006">{{cite book |last=Owens |first=Michael |year=2006 |chapter=Chapter 4: SQL |editor1-last=Gilmore |editor1-first=Jason |editor2-last=Thomas |editor2-first=Keir |editor2-link=Keir Thomas |title=The Definitive Guide to SQLite |chapter-url=https://books.google.com/books?id=VsZ5bUh0XAkC&pg=PA133 |others=D. Richard Hipp (foreword), Preston Hagar (technical reviewer) |publisher=Apress |page=133 |isbn=978-1-59059-673-9 |access-date=30 December 2014 |archive-date=24 November 2020 |archive-url=https://web.archive.org/web/20201124002058/https://books.google.com/books?id=VsZ5bUh0XAkC&pg=PA133 |url-status=live }}</ref><ref>{{cite web | url=https://sqlite.org/stricttables.html | title=STRICT Tables | access-date=2022-08-11 | archive-date=2022-08-07 | archive-url=https://web.archive.org/web/20220807204905/https://sqlite.org/stricttables.html | url-status=live }}</ref> This means that one can, for example, insert a string into a column defined as an integer. Although it is a lightweight embedded database, SQLite implements most of the SQL standard and the relational model, including transactions and ACID guarantees.<ref>{{Cite web |title=Full-Featured SQL |url=https://www.sqlite.org/fullsql.html |access-date=January 24, 2025 |website=SQLite}}</ref> However, it omits many features implemented by other databases, such as materialized views and complete support for triggers and ALTER TABLE statements.<ref>{{Cite web |title=SQL Features That SQLite Does Not Implement |url=https://www.sqlite.org/omitted.html |access-date=January 24, 2025 |website=SQLite}}</ref>

==History== D. Richard Hipp designed SQLite in the spring of 2000 while working for General Dynamics on contract with the United States Navy.<ref name="Owens06">{{cite book |last=Owens |first=Michael |title=The Definitive Guide to SQLite |chapter=Introducing SQLite |year=2006 |pages=1–16 |publisher=Apress |isbn=978-1-59059-673-9 |doi=10.1007/978-1-4302-0172-4_1}}</ref> Hipp was designing software used for a damage-control system aboard guided-missile destroyers; the damage-control system originally used HP-UX with an Informix database back-end. SQLite began as a Tcl extension.<ref name=":0" />

In August 2000, version 1.0 of SQLite was released, with storage based on gdbm (GNU Database Manager). In September 2001, SQLite 2.0 replaced gdbm with a custom B-tree implementation,{{efn|SQLite's B-tree implementation was originally adapted from The Art of Computer Programming.<ref name="CoRecursive-interview">{{cite web |last1=Bell |first1=Adam |title=The Untold Story of SQLite |url=https://corecursive.com/066-sqlite-with-richard-hipp/ |website=Corecursive |access-date=16 November 2025}}</ref>}} adding transaction capability. In June 2004, SQLite 3.0 added internationalization, manifest typing, and other major improvements, partially funded by America Online. In 2011, Hipp announced his plans to add a NoSQL interface to SQLite, as well as announcing UnQL, a functional superset of SQL designed for document-oriented databases.<ref name="unql-interview">{{cite web |url=http://www.infoq.com/news/2011/08/UnQL |title=Interview: Richard Hipp on UnQL, a New Query Language for Document Databases |publisher=InfoQ |date=August 4, 2011 |access-date=October 5, 2011 |archive-date=April 8, 2014 |archive-url=https://web.archive.org/web/20140408215240/http://www.infoq.com/news/2011/08/UnQL |url-status=live }}</ref>

SQLite is one of four formats recommended for long-term storage of datasets approved for use by the Library of Congress.<ref>{{Cite web |url=https://sqlite.org/locrsf.html |title=LoC Recommended Storage Format |website=sqlite.org |access-date=2020-04-09 |archive-date=2020-04-23 |archive-url=https://web.archive.org/web/20200423212849/https://sqlite.org/locrsf.html |url-status=live }}</ref><ref>{{Cite web |url=https://www.loc.gov/preservation/digital/formats/fdd/fdd000461.shtml |title=SQLite, Version 3 |date=2017-03-28 |website=www.loc.gov |access-date=2020-04-09 |archive-date=2020-05-11 |archive-url=https://web.archive.org/web/20200511194518/https://www.loc.gov/preservation/digital/formats/fdd/fdd000461.shtml |url-status=live }}</ref><ref>{{Cite web |url=https://www.loc.gov/preservation/resources/rfs/data.html |title=Recommended Formats Statement – datasets/databases |publisher=Library of Congress |access-date=2020-04-09 |archive-date=2018-08-22 |archive-url=https://web.archive.org/web/20180822113435/https://www.loc.gov/preservation/resources/rfs/data.html |url-status=live }}</ref>

==Design== SQLite was designed to allow the program to be operated without installing a database management system or requiring a database administrator. Unlike client–server database management systems, the SQLite engine has no standalone processes with which the application program communicates. Instead, a linker integrates the SQLite library{{emdash}}statically or dynamically{{emdash}}into an application program which uses SQLite's functionality through simple function calls, reducing latency in database operations; for simple queries with little concurrency, SQLite performance profits from avoiding the overhead of inter-process communication.

Due to the serverless design, SQLite applications require less configuration than client–server databases. SQLite is called ''zero-configuration''<ref>{{cite web |title = SQLite Is A Zero-Configuration Database |url = https://sqlite.org/zeroconf.html |access-date = August 3, 2015 |publisher = SQLite.org |archive-date = May 2, 2024 |archive-url = https://web.archive.org/web/20240502210736/https://sqlite.org/zeroconf.html |url-status = live }}</ref> because configuration tasks such as service management, startup scripts, and password- or GRANT-based access control are unnecessary. Access control is handled through the file-system permissions of the database file.<ref name=":2">{{Cite web |title=SQLite |url=https://clickhouse.com/docs/en/engines/database-engines/sqlite |access-date=January 25, 2025 |website=ClickHouse Docs}}</ref> Databases in client–server systems use file-system permissions that give access to the database files only to the daemon process, which handles its locks internally, allowing concurrent writes from several processes.

SQLite stores the entire database, consisting of definitions, tables, indices, and data, as a single cross-platform file, allowing several processes or threads to access the same database concurrently. It implements this simple design by locking the database file during writing.<ref name=":2" /> Write access may fail with an error code, or it can be retried until a configurable timeout expires. SQLite read operations can be multitasked, though due to the serverless design, writes can only be performed sequentially. This concurrent access restriction does not apply to temporary tables, and it is relaxed in version 3.7 as write-ahead logging (WAL) enables concurrent reads and writes.<ref>{{cite web |url = https://sqlite.org/wal.html |title = Write Ahead Logging in SQLite 3.7 |publisher = SQLite.org |access-date = September 3, 2011 |quote = WAL provides more concurrency as readers do not block writers and a writer does not block readers. Reading and writing can proceed concurrently. |archive-date = May 2, 2024 |archive-url = https://web.archive.org/web/20240502210711/https://sqlite.org/wal.html |url-status = live }}</ref> Since SQLite has to rely on file-system locks, it is not the preferred choice for write-intensive deployments.<ref>{{cite web |title = Appropriate Uses For SQLite |url = https://sqlite.org/whentouse.html |access-date = 2015-09-03 |publisher = SQLite.org |archive-date = 2024-05-02 |archive-url = https://web.archive.org/web/20240502210713/https://sqlite.org/whentouse.html |url-status = live }}</ref>

SQLite uses PostgreSQL as a reference platform. "What would PostgreSQL do" is used to make sense of the SQL standard.<ref>{{cite web |last1=Berkus |first1=Josh |url=https://lwn.net/Articles/601144/ |title=PGCon 2014: Clustering and VODKA |website=Lwn.net |date=4 June 2014 |access-date=2017-01-06 |archive-date=2015-06-29 |archive-url=https://web.archive.org/web/20150629195442/https://lwn.net/Articles/601144/ |url-status=live }}</ref><ref>{{cite web |url=https://www.pgcon.org/2014/schedule/events/736.en.html |title=PGCon2014: SQLite: Protégé of PostgreSQL |website=Pgcon.org |date=20 September 2015 |access-date=2017-01-06 |archive-date=2014-12-30 |archive-url=https://web.archive.org/web/20141230193958/http://www.pgcon.org/2014/schedule/events/736.en.html |url-status=live }}</ref> One major deviation is that, with the exception of primary keys, SQLite does not enforce type checking; the type of a value is dynamic and not strictly constrained by the schema (although the schema will trigger a conversion when storing, if such a conversion is potentially reversible). SQLite strives to follow Postel's rule.<ref name=":1">{{cite web |title=SQLite: StrictMode |url=https://sqlite.org/src/wiki?name=StrictMode |url-status=live |archive-url=https://web.archive.org/web/20160304115940/https://sqlite.org/src/wiki?name=StrictMode |archive-date=March 4, 2016 |access-date=September 3, 2015 |website=Sqlite.org}}</ref>

==Features== SQLite implements most of the SQL-92 standard for SQL, but lacks some features. For example, it only partially provides triggers and cannot write to views (however, it provides INSTEAD OF triggers that provide this functionality). Its support of ALTER TABLE statements is limited.<ref>{{Cite web|url=https://sqlite.org/changes.html|title=Release History of SQLite|access-date=2021-03-22|archive-date=2021-03-16|archive-url=https://web.archive.org/web/20210316043517/https://sqlite.org/changes.html|url-status=live}}</ref>

SQLite uses an unusual type system for an SQL-compatible DBMS: instead of assigning a type to a column as in most SQL database systems, types are assigned to individual values; in language terms it is ''dynamically typed''. Moreover, it is ''weakly typed'' in some of the same ways that Perl is: one can insert a string into an integer column (although SQLite will try to convert the string to an integer first, if the column's preferred type is integer). This adds flexibility to columns, especially when bound to a dynamically typed scripting language. However, the technique is not portable to other SQL products. A common criticism is that SQLite's type system lacks the data integrity mechanism provided by statically typed columns, although it can be emulated with constraints like {{code|2=sql|1=CHECK(typeof(x)='integer')}}.<ref name="Owens06" /> In 2021, support for static typing was added through STRICT tables, which enforce datatype constraints for columns.<ref>{{Cite web |title=STRICT Tables |url=https://sqlite.org/stricttables.html |access-date=January 24, 2025 |website=SQLite}}</ref>

Tables normally include a hidden ''rowid'' index column, which provides faster access.<ref>{{cite web |title=SQL As Understood By SQLite |url=https://sqlite.org/lang_createtable.html#rowid |website=SQLite |access-date=21 May 2018 |quote=Searching for a record with a specific rowid, or for all records with rowids within a specified range is around twice as fast as a similar search made by specifying any other PRIMARY KEY or indexed value. |archive-date=21 May 2018 |archive-url=https://web.archive.org/web/20180521104530/https://sqlite.org/lang_createtable.html#rowid |url-status=live }}</ref> If a table includes an INTEGER PRIMARY KEY column, SQLite will typically optimize it by treating it as an alias for the ''rowid'', causing the contents to be stored as a strictly typed 64-bit signed integer and changing its behavior to be somewhat like an auto-incrementing column. SQLite includes an option to create a table without a rowid column, which can save disk space and improve lookup speed. WITHOUT ROWID tables are required to have a primary key.<ref>{{Cite web |title=Clustered Indexes and the WITHOUT ROWID Optimization |url=https://sqlite.org/withoutrowid.html |access-date=January 24, 2025 |website=SQLite}}</ref>

SQLite supports foreign key constraints,<ref>{{cite book |last=Karwin |first=Bill |editor-last=Carter |editor-first=Jacquelyn |date=May 2010 |title=SQL Antipatterns: Avoiding the Pitfalls of Database Programming |publisher=The Pragmatic Bookshelf |isbn=978-1-934356-55-5 |page=70 |quote=Sometimes you're forced to use a database brand that doesn't support foreign key constraints (for example MySQL's MyISAM storage engine or SQLite prior to version 3.6.19).}}</ref><ref>{{Cite web|url=https://sqlite.org/releaselog/3_6_19.html|title=SQLite Release 3.6.19 On 2009-10-14|website=sqlite.org|access-date=2020-10-15|archive-date=2020-10-29|archive-url=https://web.archive.org/web/20201029060401/http://sqlite.org/releaselog/3_6_19.html|url-status=live}}</ref> although they are disabled by default and must be manually enabled with a PRAGMA statement.<ref>{{Cite web |title=SQLite Foreign Key Support |url=https://sqlite.org/foreignkeys.html |access-date=January 24, 2025 |website=SQLite}}</ref>

Stored procedures are not supported; this is an explicit choice by the developers to favor simplicity, as the typical use case of SQLite is to be embedded inside a host application that can define its own procedures around the database.<ref>Source: developers' comments on [https://sqlite.org/forum/info/78a60bdeec7c1ee9 SQLite forum] {{Webarchive|url=https://web.archive.org/web/20230401220416/https://sqlite.org/forum/info/78a60bdeec7c1ee9 |date=2023-04-01 }}</ref>

SQLite does not have full Unicode support by default for backwards compatibility and due to the size of the Unicode tables, which are larger than the SQLite library.<ref>{{Cite web |title=Quirks, Caveats, and Gotchas In SQLite |url=https://sqlite.org/quirks.html |access-date=January 24, 2025 |website=SQLite}}</ref> Full support for Unicode case-conversions can be enabled through an optional extension.<ref>{{cite web |title = Case-insensitive matching of Unicode characters does not work |url = https://sqlite.org/faq.html#q18 |website = SQLite Frequently Asked Questions |access-date = 2015-09-03 |archive-date = 2015-09-05 |archive-url = https://web.archive.org/web/20150905054749/https://sqlite.org/faq.html#q18 |url-status = live }}</ref>

SQLite supports full-text search through its FTS5 loadable extension, which allows users to efficiently search for a keyword in a large number of documents similar to how search engines search webpages.<ref>{{Cite web |title=SQLite FTS5 Extension |url=https://sqlite.org/fts5.html |access-date=January 24, 2025 |website=SQLite}}</ref>

SQLite includes support for working with JSON through its ''json1'' extension, which is enabled by default since 2021. SQLite's JSON functions can handle JSON5 syntax since 2023. In 2024, SQLite added support for JSONB, a binary serialization of SQLite's internal representation of JSON. Using JSONB allows applications to avoid having to parse the JSON text each time it is processed and saves a small amount of disk space.<ref>{{Cite web |title=JSON Functions And Operators |url=https://sqlite.org/json1.html |access-date=January 24, 2025 |website=SQLite}}</ref>

In May 2025, the 25th‑anniversary release SQLite 3.50.0 introduced additional features, including new Unicode functions ({{Code|unistr()}} and {{Code|unistr_quote()}}), a new API ({{Code|sqlite3_setlk_timeout()}}) for setting lock timeouts, improved command‑line tools and rsync utility enhancements, and optimized JSONB.<ref>{{Cite web |title=SQLite Release 3.50.0 On 2025-05-29 |url=https://sqlite.org/releaselog/3_50_0.html |access-date=November 3, 2025 |website=SQLite}}</ref>

The maximum supported size for an SQLite database file is 281 terabytes.<ref>{{cite web|url=https://sqlite.org/limits.html|title=Limits In SQLite|website=SQLite.org|access-date=2022-09-19|archive-date=2021-11-07|archive-url=https://web.archive.org/web/20211107064937/https://sqlite.org/limits.html|url-status=live}}</ref>

==Development and distribution== SQLite's code is hosted with Fossil, a distributed version control system that uses SQLite as a local cache for its non-relational database format, and SQLite's SQL as an implementation language.<ref>{{cite web|url = https://www.fossil-scm.org/home/doc/trunk/www/theory1.wiki|title = Thoughts On The Design Of The Fossil DVCS|publisher = Fossil-scm.org|date = July 12, 2017|access-date = October 14, 2022|archive-date = October 13, 2022|archive-url = https://web.archive.org/web/20221013234319/https://www.fossil-scm.org/home/doc/trunk/www/theory1.wiki|url-status = live}}</ref><ref>{{cite web|url = https://www.fossil-scm.org/index.html/doc/tip/www/stats.wiki|title = Fossil: Fossil Performance|publisher = Fossil-scm.org|date = August 23, 2009|access-date = September 12, 2009|archive-date = October 9, 2009|archive-url = https://web.archive.org/web/20091009054952/http://www.fossil-scm.org/index.html/doc/tip/www/stats.wiki|url-status = live}}</ref>

SQLite is public domain, but not "open-contribution", with the website stating "the project does not accept patches from people who have not submitted an affidavit dedicating their contribution into the public domain."<ref>{{Cite web |title=SQLite Copyright |url=https://sqlite.org/copyright.html |access-date=2024-03-06 |website=sqlite.org |archive-date=2024-03-15 |archive-url=https://web.archive.org/web/20240315172355/https://sqlite.org/copyright.html |url-status=live }}</ref> Instead of a code of conduct, the founders have adopted a code of ethics based on the Rule of St. Benedict.<ref>{{Cite web |title=Code Of Ethics |url=https://sqlite.org/codeofethics.html |access-date=2024-03-06 |website=sqlite.org |archive-date=2024-02-19 |archive-url=https://web.archive.org/web/20240219225117/https://sqlite.org/codeofethics.html |url-status=live }}</ref>

A standalone command-line shell program called ''sqlite3''<ref>{{cite web|url = https://sqlite.org/cli.html|title = Command Line Shell For SQLite|publisher = Sqlite.org|access-date = October 14, 2022|archive-date = October 6, 2022|archive-url = https://web.archive.org/web/20221006104551/https://sqlite.org/cli.html|url-status = live}}</ref> is provided in SQLite's distribution. It can be used to create a database, define tables, insert and change rows, run queries and manage an SQLite database file. It also serves as an example for writing applications that use the SQLite library.

SQLite uses automated regression testing prior to each release. Over 2 million tests are run as part of a release's verification. The SQLite library has 156,000 lines of source code, while all the test suites combined add up to 92 million lines of test code. SQLite's tests simulate a number of exceptional scenarios, such as power loss and I/O errors, in addition to testing the library's functionality. Starting with the August 10, 2009 release of SQLite 3.6.17, SQLite releases have 100% branch test coverage, one of the components of code coverage. SQLite has four different test harnesses: the original public-domain TCL tests, the proprietary C-language TH3 test suite, the SQL Logic Tests, which check SQLite against other SQL databases, and the dbsqlfuzz proprietary fuzzing engine.<ref name="tests">{{cite web |title=How SQLite Is Tested |url=https://sqlite.org/testing.html |url-status=live |archive-url=https://web.archive.org/web/20091006224147/https://sqlite.org/testing.html |archive-date=October 6, 2009 |access-date=September 12, 2009 |publisher=SQLite.org}}</ref>

=={{anchor|Adoption}}Notable uses==

===Operating systems=== SQLite is included by default in: * Android<ref name="CoRecursive-interview"/><ref>{{cite web |title=android.database.sqlite |url=https://developer.android.com/reference/android/database/sqlite/package-summary |website=Android Developers |access-date=23 April 2026}}</ref> * BlackBerry Tablet OS<ref name = "Blackberry, GitHub" >{{Cite web |url=https://blackberry.github.com/ndk/components.html |title=Open Source Components for the Native SDK for BlackBerry Tablet OS |access-date=2017-09-19 |archive-url=https://web.archive.org/web/20130127102233/http://blackberry.github.com/ndk/components.html |archive-date=2013-01-27 |url-status=dead }}</ref> * iOS<ref name=":0" /> * Mac OS X 10.4 onwards (Apple adopted it as an option in macOS's Core Data API from the original implementation)<ref name=":0" /> * NetBSD<ref>{{cite web |title=sqlite3(1) - NetBSD Manual Pages |url=https://man.netbsd.org/sqlite3.1 |website=man.netbsd.org |publisher=NetBSD |access-date=23 April 2026}}</ref> * NixOS where it is used by the Nix core package management system<ref>{{cite web |title=Prerequisites |url=https://nix.dev/manual/nix/2.28/installation/prerequisites-source.html |website=nix.dev |publisher=NixOS |access-date=23 April 2026}}</ref> * OpenBSD, which supports exporting ports tree metadata as an SQLite database<ref>{{cite web |title=ports(7) - OpenBSD manual pages |url=https://man.openbsd.org/ports |website=man.openbsd.org |publisher=OpenBSD |access-date=23 April 2026}}</ref> * RPM based Linux distributions (including Red Hat Enterprise Linux and its derivative Fedora Linux), where it is used by the core package management system<ref>{{cite web |title=RPM Database Recovery |url=https://rpm.org/user_doc/db_recovery.html |website=rpm.org |access-date=23 April 2026}}</ref> * Windows 10 onwards<ref>{{cite web| url=https://docs.microsoft.com/en-us/windows/uwp/data-access/sqlite-databases#to-use-the-version-of-sqlite-that-is-installed-with-windows| title=To use the version of SQLite that is installed with Windows| date=20 October 2022| access-date=31 March 2022| archive-date=31 March 2022| archive-url=https://web.archive.org/web/20220331170828/https://docs.microsoft.com/en-us/windows/uwp/data-access/sqlite-databases#to-use-the-version-of-sqlite-that-is-installed-with-windows| url-status=live}}</ref>

===Middleware=== * ADO.NET adapter, initially developed by Robert Simpson, is maintained jointly with the SQLite developers since April 2010.<ref>{{cite web |url=http://system.data.sqlite.org/index.html/doc/trunk/www/index.wiki |title=Home |website=System.Data.SQLite |date=2016-12-30 |access-date=2017-01-06 |archive-date=2014-07-13 |archive-url=https://web.archive.org/web/20140713080835/http://system.data.sqlite.org/index.html/doc/trunk/www/index.wiki |url-status=live }}</ref> * ODBC driver has been developed and is maintained separately by Christian Werner.<ref>{{cite web |url=http://www.ch-werner.de/sqliteodbc/ |title=SQLite ODBC Driver |website=Ch-werner.de |date=2016-12-01 |access-date=2017-01-06 |archive-date=2014-06-26 |archive-url=https://web.archive.org/web/20140626165719/http://www.ch-werner.de/sqliteodbc/ |url-status=live }}</ref> Werner's ODBC driver is the recommended connection method for accessing SQLite from OpenOffice.org.<ref>{{cite web |url=http://documentation.openoffice.org/HOW_TO/data_source/SQLite.pdf |title=Using SQLite Database with OpenOffice.org : Version 2.0 |website=Documentation.openoffice.org |access-date=2017-01-06 |archive-date=2011-09-28 |archive-url=https://web.archive.org/web/20110928073029/http://documentation.openoffice.org/HOW_TO/data_source/SQLite.pdf |url-status=live }}</ref> * COM (ActiveX) wrapper making SQLite accessible on Windows to scripted languages such as JScript and VBScript. This adds SQLite database capabilities to HTML Applications (HTA).<ref>{{cite web|url = https://sqlite.org/cvstrac/wiki?p=SqliteWrappers|title = sqlite&nbsp;— Sqlite Wrappers|date = February 7, 2009|publisher = SQLite.org|access-date = February 7, 2009|archive-date = February 5, 2009|archive-url = https://web.archive.org/web/20090205225756/http://sqlite.org/cvstrac/wiki?p=SqliteWrappers|url-status = live}}</ref>

===Web browsers=== * The browsers Google Chrome, Opera, Safari and the Android Browser all allow for storing information in, and retrieving it from, an SQLite database within the browser, using the official SQLite Wasm (WebAssembly) build,<ref>{{Cite web | url = https://sqlite.org/wasm | title = sqlite3 WebAssembly & JavaScript Documentation Index | website = SQLite | access-date = 2023-05-08 | archive-date = 2024-05-02 | archive-url = https://web.archive.org/web/20240502210710/https://sqlite.org/wasm/doc/trunk/index.md | url-status = live }}</ref> or using the Web SQL Database technology, although the latter is becoming deprecated (namely superseded by SQLite Wasm or by IndexedDB). Internally, Chromium based browsers use SQLite databases for storing configuration data like site visit history, cookies, download history etc.<ref>{{cite web |url=https://www.foxtonforensics.com/browser-history-examiner/chrome-history-location |title=Location of Google Chrome history |website=www.foxtonforensics.com |date=2020-10-06 |access-date=2020-10-06 |archive-date=2023-02-28 |archive-url=https://web.archive.org/web/20230228184524/https://www.foxtonforensics.com/browser-history-examiner/chrome-history-location |url-status=live }}</ref> * Mozilla Firefox and Mozilla Thunderbird store a variety of configuration data (bookmarks, cookies, contacts etc.) in internally managed SQLite databases. Until Firefox version 57 ("Firefox Quantum"), there was a third-party add-on that used the API supporting this functionality to provide a user interface for managing arbitrary SQLite databases.<ref>{{cite web|url=https://addons.mozilla.org/en-US/firefox/addon/sqlite-manager/ |title=SQLite Manager :: Add-ons for Firefox |website=Addons.mozilla.org |date=2015-02-28 |access-date=2017-01-06 |url-status=dead |archive-url=https://web.archive.org/web/20170102010658/https://addons.mozilla.org/en-US/firefox/addon/sqlite-manager/ |archive-date=2017-01-02}}</ref> * Several third-party add-ons can make use of JavaScript APIs to manage SQLite databases.<ref>{{cite web |url=https://addons.mozilla.org/en-US/firefox/addon/sqlite-manager-webext/ |title=SQLite Manager – Get this Extension for 🦊 Firefox (en-US) |website=Addons.mozilla.org |date=2018-07-24 |access-date=2018-10-05 |archive-date=2018-10-05 |archive-url=https://web.archive.org/web/20181005112443/https://addons.mozilla.org/en-US/firefox/addon/sqlite-manager-webext/ |url-status=live }}</ref><ref>{{cite web |url=https://addons.mozilla.org/en-US/firefox/addon/sql-reader/ |title=SQLite Reader – Get this Extension for 🦊 Firefox (en-US) |website=Addons.mozilla.org |date=2018-09-01 |access-date=2018-10-05 |archive-date=2018-10-05 |archive-url=https://web.archive.org/web/20181005112536/https://addons.mozilla.org/en-US/firefox/addon/sql-reader/ |url-status=live }}</ref>

===Web application frameworks=== * Symfony * Laravel * Bugzilla * Django's default database management system * Drupal * Trac * Ruby on Rails's default database management system * web2py

===Others=== * Adobe Systems uses SQLite as its file format in Adobe Lightroom, a standard database in Adobe AIR, and internally within Adobe Acrobat Reader.<ref name=":0">{{cite web|title = Well-Known Users Of SQLite|url = https://sqlite.org/famous.html|access-date = August 5, 2015|publisher = SQLite|archive-date = July 11, 2015|archive-url = https://web.archive.org/web/20150711135311/https://sqlite.org/famous.html|url-status = live}}</ref> * Apple Photos uses SQLite internally.<ref name="apple-photos">{{cite web|url = https://simonwillison.net/2020/May/21/dogsheep-photos/|access-date = May 23, 2020|title = Using SQL to find my best photo of a pelican according to Apple Photo|work = Simon Willison’s Weblog|archive-date = May 22, 2020|archive-url = https://web.archive.org/web/20200522181550/https://simonwillison.net/2020/May/21/dogsheep-photos/|url-status = live}}</ref> * Audacity uses SQLite as its file format, as of version 3.0.0.<ref name="audacity">{{cite web|url = https://www.audacityteam.org/audacity-3-0-0-released/|access-date = March 17, 2021|title = Audacity 3.0.0 Released|date = 17 March 2021|archive-date = 14 August 2023|archive-url = https://web.archive.org/web/20230814021313/https://www.audacityteam.org/audacity-3-0-0-released/|url-status = dead}}</ref> * Evernote uses SQLite to store its local database repository in Windows. * Skype<ref name="skype">{{cite mailing list|url = https://www.mail-archive.com/sqlite-users%40sqlite.org/msg27326.html|archive-url=https://web.archive.org/web/20071117061133/https://www.mail-archive.com/sqlite-users%40sqlite.org/msg27326.html|archive-date=2007-11-17|first=Jeremy|last=Hinegardner|title = Skype client using SQLite?|mailing-list=sqlite-users|date = August 28, 2007|access-date = June 14, 2010}}</ref> * WhatsApp<ref name="WhatsApp">{{cite web |title=WhatsApp in Plain Sight: Where and How You Can Collect Forensic Artifacts |url=https://www.group-ib.com/blog/whatsapp-forensic-artifacts/ |website=www.group-ib.com |access-date=29 September 2025 |date=7 November 2019}}</ref> * The Service Management Facility, used for service management within the Solaris and OpenSolaris operating systems * Dropbox client software<ref name=":0"/> * Intuit uses SQLite in QuickBooks and TurboTax<ref name=":0"/> * McAfee Antivirus<ref name=":0"/> * Flame (malware) * BMW iDrive satellite navigation system * TomTom GPS systems, for the NDS map data * Proxmox VE - ''Proxmox Cluster File System'' ([https://pve.proxmox.com/wiki/Proxmox_Cluster_File_System_(pmxcfs) pmxcfs]) * Bentley Systems MicroStation<ref name=":0"/> * Bosch car multimedia systems<ref name=":0"/> * Airbus A350 flight system<ref name=":0"/> * Quicken Essentials and later versions of Quicken for Mac<ref>{{cite web|url=https://frugalvagabond.com/addendum-project-years-of-expenses-with-quicken-for-mac/|title=Addendum: Project Years of Expenses With Quicken for Mac|website=The Frugal Vagabond}}</ref> * Python standard library<ref>{{Cite web | url = https://docs.python.org/library/sqlite3 | title = sqlite3 — DB-API 2.0 interface for SQLite databases | website = The Python Standard Library Documentation }}</ref> * Xojo IDE<ref name=":0"/> * Wine<ref>{{cite web |title=Wine 11.9 Released |url=https://www.winehq.org/news/2026051501 |website=WineHQ |access-date=19 May 2026 |date=15 May 2026}}</ref>

==See also== {{Portal|Free and open-source software}} * Ordered key–value store * Comparison of relational database management systems * List of relational database management systems * MySQL * SpatiaLite

==Notes== {{Notelist}}

==References==

===Citations=== {{Reflist|30em}}

===Sources=== {{Refbegin}} * {{cite book |first1 = Grant |last1 = Allen |first2 = Mike |last2 = Owens |date = November 5, 2010 |title = The Definitive Guide to SQLite |edition = 2nd |publisher = Apress |page = 368 |isbn = 978-1-4302-3225-4 |url = http://apress.com/book/view/1430232250 |access-date = December 23, 2010 |archive-date = December 30, 2010 |archive-url = https://web.archive.org/web/20101230035043/http://apress.com/book/view/1430232250 |url-status = dead }} * {{cite book |first1 = Jay A. |last1 = Kreibich |date = August 17, 2010 |title = Using SQLite |edition = 1st |publisher = O'Reilly Media |page = 528 |isbn = 978-0-596-52118-9 |url = http://oreilly.com/catalog/9780596521196 |access-date = December 23, 2010 |archive-date = December 25, 2010 |archive-url = https://web.archive.org/web/20101225102001/http://oreilly.com/catalog/9780596521196 |url-status = live }} * {{cite book |first1 = Chris |last1 = Newman |date = November 9, 2004 |title = SQLite (Developer's Library) |edition = 1st |publisher = Sams |page = 336 |isbn = 0-672-32685-X |url = http://www.informit.com/store/product.aspx?isbn=067232685X |access-date = May 12, 2010 |archive-date = January 14, 2012 |archive-url = https://web.archive.org/web/20120114075902/http://www.informit.com/store/product.aspx?isbn=067232685X |url-status = live }} {{Refend}}

==Further reading== * {{cite journal |journal=Proceedings of the VLDB Endowment |url=https://dl.acm.org/doi/10.14778/3554821.3554842 |doi=10.14778/3554821.3554842 |title=SQLite: past, present, and future |date=2022-08-01 |volume=15 |number=12 |pages=3535–3547 |first1=Kevin P |last1=Gaffney |first2=Martin |last2=Prammer |first3=Larry |last3=Brasfield |first4=D Richard |last4=Hipp |first5=Dan |last5=Kennedy |first6=Jignesh M |last6=Patel|url-access=subscription }}

==External links== {{Commons category|}} * {{Official website}} * {{cite web |url=https://corecursive.com/066-sqlite-with-richard-hipp/|title=The Untold Story of SQLite |publisher=CoRecursive}}

{{Authority control}}

Category:SQLite Category:2000 software Category:C (programming language) libraries Category:Cross-platform free software Category:Database engines Category:Embedded databases Category:Free computer libraries Category:Free database management systems Category:Public-domain software with source code Category:Relational database management software for Linux Category:Relational database management systems Category:Serverless database management systems Category:Symbian software Category:Public-domain software