Title: SQLite Database Integration Author: WordPress.org Published: Mutarama 17, 2023 Last modified: Kanama 13, 2026 --- Search plugins ![](https://s.w.org/plugins/geopattern-icon/sqlite-database-integration.svg) # SQLite Database Integration By [WordPress.org](https://profiles.wordpress.org/wordpressdotorg/) [Download](https://downloads.wordpress.org/plugin/sqlite-database-integration.3.0.0.zip) * [Details](https://kin.wordpress.org/plugins/sqlite-database-integration/#description) * [Reviews](https://kin.wordpress.org/plugins/sqlite-database-integration/#reviews) * [Development](https://kin.wordpress.org/plugins/sqlite-database-integration/#developers) [Support](https://wordpress.org/support/plugin/sqlite-database-integration/) ## Description **Run WordPress on SQLite.** The SQLite plugin is a community, feature plugin. The intent is to allow testing an SQLite integration with WordPress and gather feedback, with the goal of eventually landing it in WordPress core. The plugin replaces the default MySQL database layer with an SQLite-backed implementation. WordPress continues to use its standard `wpdb` API while the plugin translates and emulates MySQL queries for SQLite. #### What the plugin provides * **No database server.** Your site’s data is stored in a local SQLite database. * **Guided setup.** The installation screen checks for the required PHP extension, write access, and conflicting database drop-ins before enabling SQLite. * **Purpose-built compatibility.** A MySQL parser and emulation layer adapt MySQL syntax and behavior for SQLite. * **Useful diagnostics.** SQLite details appear in Site Health, and Query Monitor is supported. **Important:** Enabling SQLite creates a separate, empty database; it does not migrate an existing site. If you enable it on a site that uses MySQL or MariaDB, WordPress will ask you to set up the site again. Disabling the plugin reconnects WordPress to the previous database with its data unchanged. Changes made while using SQLite are not transferred. The plugin requires the PDO SQLite PHP extension and SQLite 3.37.0 or newer. ## FAQ ### What is the purpose of this plugin? The primary purpose of the plugin is to test WordPress with SQLite and gather feedback, with the goal of eventually including the integration in WordPress core. Read the original proposal on the [Make WordPress Core blog](https://make.wordpress.org/core/2022/09/12/lets-make-wordpress-officially-support-sqlite/) and the [call for testing](https://make.wordpress.org/core/2022/12/20/help-us-test-the-sqlite-implementation/) for more context. ### Can I use this plugin on my production site? Yes, but keep reliable backups and make sure SQLite is a good fit for your site’s traffic. SQLite supports concurrent reads but allows only one writer at a time, so MySQL or MariaDB may be a better fit for sites with heavy concurrent write traffic. Test your workload, themes, and plugins before switching. ### Will this plugin migrate my existing site to SQLite? No. Enabling SQLite starts a fresh WordPress installation in a separate database. Your existing MySQL or MariaDB database remains unchanged, but its content is not copied to SQLite. Disabling the plugin reconnects WordPress to the previous database. Content created while using SQLite is not transferred back. ### What does the plugin require? In addition to the WordPress and PHP versions listed above, the plugin requires the PDO SQLite PHP extension and SQLite 3.37.0 or newer. The setup screen also needs write access to the `wp-content` directory and will detect conflicting database drop-ins. ### Where can I submit my plugin feedback? Feedback helps improve the integration. For troubleshooting, questions, suggestions, or feature requests, [open an issue in the SQLite GitHub repository](https://github.com/wordpress/sqlite-database-integration/issues/new). ### How can I contribute to the plugin? Contributions are welcome through the [SQLite Database Integration repository on GitHub](https://github.com/WordPress/sqlite-database-integration). ### Does this plugin change how WordPress queries are executed? Yes. The plugin replaces the default MySQL-based database layer with an SQLite-backed implementation. WordPress continues to use the `wpdb` API, while queries are internally adapted to SQLite syntax and behavior. ## Reviews ![](https://secure.gravatar.com/avatar/e1ea4633379bbc6b5bc9e3fa3aeb4da60ccff6557ad69d37e851647ed4735a10? s=60&d=retro&r=g) ### 󠀁[Works great on my low-traffic site](https://wordpress.org/support/topic/works-great-on-my-low-traffic-site/)󠁿 [openletter](https://profiles.wordpress.org/openletter/) Kamena 29, 2025 I have no other services requiring MySQL/MariaDB, so this option saves me some memory and headache. Have been running for around one year and zero issues, but my site is very simple. ![](https://secure.gravatar.com/avatar/1b0c704cb4942dbae9b171341ee95b3e2cb7cd2d6dc0bcdaa4dcee89f3fc0a8d? s=60&d=retro&r=g) ### 󠀁[Util para crear sitios de desarrollo](https://wordpress.org/support/topic/util-para-crear-sitios-de-desarrollo/)󠁿 [ALPRADO WordPress Consultant](https://profiles.wordpress.org/alprado/) Kamena 29, 2025 SQlite debería de ser la opción por defecto para WordPress. Es mucho más simple de administrar que mySQL y puede funcionar igual de bien. Este plugin es indispensable para crear un WordPress de desarrollo que solamente necesita PHP para iniciar el servidor sin instalar XAMPP ni otro software. ![](https://secure.gravatar.com/avatar/ded41d1ff4a5d949ab95362f662e228df0c04f364ef3603dc304efc1c3372904? s=60&d=retro&r=g) ### 󠀁[Great, seems only one step away …](https://wordpress.org/support/topic/great-seems-only-one-step-away/)󠁿 [Gareth Bult](https://profiles.wordpress.org/madpenguin/) Ukuboza 3, 2024 Ok, so in terms of doing what it says in the tin, for me it looks great. I’ve set up 20 – 30 instances, it runs my core plugins and has a footprint of ~ 105M when running with a default setup. Seems to be at least as fast as the MySQL instances sat next to them. Here’s the problem tho’. It would seem I can’t actually convert any existing sites over to run on these instances without a lot of manual work. ( I say this after reading the experiences of some others who claim to have tried). Are there any relatively automatic tools and/or documentation that I might have missed when it comes to migrating a MySQL instance over to SqLite (and back, in the event of a problem), or at least a Roadmap of if / when such tools or plugins might become available? A roadmap or estimation might at least (if it’s a long way away) prompt someone to get on and do it? ![](https://secure.gravatar.com/avatar/9a38e5d4b02b4735c79831ec7d8e52ad04f20b2bc2bc3fc33593a60776bb1c11? s=60&d=retro&r=g) ### 󠀁[First start](https://wordpress.org/support/topic/first-start-2/)󠁿 [barbaroshh](https://profiles.wordpress.org/barbaroshh/) Ugushyingo 26, 2024 6 replies I added this plugin. Wordpress warned me that it would be reinstalled. But now everything is gone.) Will it come back, hopefully? ![](https://secure.gravatar.com/avatar/c6597faba22dfca2d73c37013974a0fa24b16556f91b1e1af6c0a9ed436d507e? s=60&d=retro&r=g) ### 󠀁[Great Plugin! Makes WP so fast!](https://wordpress.org/support/topic/great-plugin-make-wp-so-fast/)󠁿 [John Turner](https://profiles.wordpress.org/johnnytee/) Nzeri 28, 2024 1 reply Thank you dev team for providing this plugin ! ![](https://secure.gravatar.com/avatar/22dcf41213b58505959c76ae20650595fbd28c9653c683591c3c6f14d60f1aa5? s=60&d=retro&r=g) ### 󠀁[Excellent!](https://wordpress.org/support/topic/excellent-13553/)󠁿 [lucasbustamante](https://profiles.wordpress.org/lucasbustamante/) Kanama 26, 2024 1 reply I used it to spin up a test site in CI, it’s just elegant and brings WP closer to Static when we need it. There’s a place for SQLite simplicity in some WP workflows. Loved it! [ Read all 12 reviews ](https://wordpress.org/support/plugin/sqlite-database-integration/reviews/) ## Contributors & Developers “SQLite Database Integration” is open source software. The following people have contributed to this plugin. Contributors * [ WordPress.org ](https://profiles.wordpress.org/wordpressdotorg/) * [ Ari Stathopoulos ](https://profiles.wordpress.org/aristath/) * [ Jan Jakeš ](https://profiles.wordpress.org/janjakes/) * [ Adam Zieliński ](https://profiles.wordpress.org/zieladam/) * [ Bero ](https://profiles.wordpress.org/berislavgrgicak/) * [ Brandon Payton ](https://profiles.wordpress.org/bpayton/) * [ zaerl ](https://profiles.wordpress.org/zaerl/) “SQLite Database Integration” has been translated into 13 locales. Thank you to [the translators](https://translate.wordpress.org/projects/wp-plugins/sqlite-database-integration/contributors) for their contributions. [Translate “SQLite Database Integration” into your language.](https://translate.wordpress.org/projects/wp-plugins/sqlite-database-integration) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/sqlite-database-integration/), check out the [SVN repository](https://plugins.svn.wordpress.org/sqlite-database-integration/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/sqlite-database-integration/) by [RSS](https://plugins.trac.wordpress.org/log/sqlite-database-integration/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 3.0.0 **SQLite Database Integration 3 is here! 🎉** This release introduces an **all-new SQLite database driver for WordPress**, rebuilt from the ground up. Its purpose-built MySQL lexer, parser, and emulation layer deliver broader compatibility, more accurate behavior, and a stronger foundation for future improvements. The 3.0 release spans nearly two years of work, featuring [160 pull requests](https://github.com/WordPress/sqlite-database-integration/milestone/3?closed=1) and 1,075 commits from 15 contributors. **What’s new** The new driver advances SQLite support for WordPress, plugins, database tools, and other MySQL-based applications. These improvements include: * **New SQL engine:** The pure-PHP lexer and parser provide extensive coverage of the official MySQL grammar. * **Broad query support:** Complex joins, subqueries, CTEs, unions, and other advanced queries are now supported. * **Schema emulation:** WordPress and database tools can query emulated MySQL ` INFORMATION_SCHEMA` tables. * **Schema introspection:** `SHOW` and `DESCRIBE` statements provide accurate MySQL- like metadata. * **Improved data handling:** Types, casts, defaults, auto-increment, values, and escaping better match MySQL. * **Refined MySQL semantics:** Better emulation of SQL modes, variables, functions, transactions, and errors. * **Better concurrency:** Write-ahead logging and fewer locks reduce blocking between readers and writers. * **PDO API:** The new driver implements the PDO MySQL API, supporting many MySQL- based tools and applications. * **Extensive testing:** Test suites cover parsing, translation, metadata, concurrency, PDO, and end-to-end workflows. For more information about the new driver and its architecture, read the [driver announcement](https://make.wordpress.org/playground/2025/06/13/introducing-a-new-sqlite-driver-for-wordpress/). **Modular design** The project was redesigned as a set of focused packages, separating the core driver from its WordPress integration: * [SQLite Database Integration](https://github.com/WordPress/sqlite-database-integration/tree/v3.0.0/packages/plugin-sqlite-database-integration): The **WordPress plugin** powered by MySQL on SQLite. * [MySQL on SQLite](https://github.com/WordPress/sqlite-database-integration/tree/v3.0.0/packages/mysql-on-sqlite): A standalone **PDO MySQL drop-in** for running MySQL-based PHP applications on SQLite. * [MySQL proxy](https://github.com/WordPress/sqlite-database-integration/tree/v3.0.0/packages/mysql-proxy)( experimental): A **MySQL wire protocol bridge** to PDO-compatible drivers for clients outside PHP. This architecture opens the driver to new integrations, applications, and development tools beyond WordPress. **Upgrading to 3.0** Upgrading an existing SQLite site is straightforward: 1. **Back up** your SQLite database. 2. **Update the plugin** to version 3.0. On first connection, the new driver automatically initializes its metadata without changing your tables or content. If you used the new driver preview, you can now delete the `WP_SQLITE_AST_DRIVER` flag. **Breaking changes** Most WordPress sites need no changes. Review the following if you use a custom setup: * **New driver:** - The new driver is always used. The legacy driver was removed. - The `WP_SQLITE_AST_DRIVER` feature flag was removed. * **Updated SQLite version requirements:** - SQLite `3.37.0` or newer is required. - The `WP_SQLITE_UNSAFE_ENABLE_UNSUPPORTED_VERSIONS` opt-in enables limited SQLite `3.27.0`–`3.36.x` support. * **`DB_NAME` is required:** - It must be defined and non-empty. - It is used dynamically, independently of the SQLite file name and stored metadata. * **SQLite defaults have changed:** - Journal mode now defaults to [`WAL`](https://sqlite.org/wal.html). Account for `-wal` and `-shm` sidecar files. - Synchronous mode now defaults to [`NORMAL`](https://sqlite.org/pragma.html#pragma_synchronous) in `WAL` mode. * **Updated configuration constants:** - `DATABASE_ENGINE` was removed. Use `DB_ENGINE`. - `DATABASE_TYPE` is deprecated. Use `DB_ENGINE`. - `FQDBDIR` is deprecated. Use `DB_DIR`. - `FQDB` is deprecated. Use `DB_DIR` and `DB_FILE`. * **Updated driver classes:** - `WP_SQLite_Driver` is deprecated. Use `WP_MySQL_On_SQLite`. - `WP_PDO_MySQL_On_SQLite` was replaced by `WP_MySQL_On_SQLite`. - `WP_SQLite_Driver_Exception` was replaced by `WP_MySQL_On_SQLite_Exception`. - `WP_PDO_Proxy_Statement` was replaced by `WP_MySQL_On_SQLite_Statement`. * **Sunsetting `$GLOBALS['@pdo']`:** - Injecting a PDO connection through `$GLOBALS['@pdo']` is no longer supported. - Reading `$GLOBALS['@pdo']` is deprecated. Use `$wpdb->get_driver()->get_sqlite_pdo()`. * **Renamed driver constructor options:** - `pdo` `sqlite_pdo`. - `journal_mode` `sqlite_journal_mode`. - `synchronous` `sqlite_synchronous`. **Thank you** Thank you to everyone who helped build, test, review, and improve the new driver. Your work made this possible. **3.0 milestone:** [160 pull requests](https://github.com/WordPress/sqlite-database-integration/milestone/3?closed=1) **Changes since 2.2.23:** [`v2.2.23...v3.0.0`](https://github.com/WordPress/sqlite-database-integration/compare/v2.2.23...v3.0.0) #### 2.2.23 * Add Query Monitor 4.0 support ([#357](https://github.com/WordPress/sqlite-database-integration/pull/357)) * Translate MySQL CONVERT() expressions to SQLite ([#356](https://github.com/WordPress/sqlite-database-integration/pull/356)) #### 2.2.22 * Support INSERT without INTO keyword ([#354](https://github.com/WordPress/sqlite-database-integration/pull/354)) * Add tests for MySQL row-level locking clauses ([#342](https://github.com/WordPress/sqlite-database-integration/pull/342)) * Improve automated deploy setup. #### 2.2.21 * Monorepo setup + release automation ([#334](https://github.com/WordPress/sqlite-database-integration/pull/334)) * Rework release workflow ([#350](https://github.com/WordPress/sqlite-database-integration/pull/350)) * Fix incorrect PHP polyfill implementations ([#338](https://github.com/WordPress/sqlite-database-integration/pull/338)) ## Meta * Version **3.0.0** * Last updated **8 hours ago** * Active installations **4,000+** * WordPress version ** 6.4 or higher ** * Tested up to **7.0.4** * PHP version ** 7.2 or higher ** * Languages * [Catalan](https://ca.wordpress.org/plugins/sqlite-database-integration/), [Chinese (Taiwan)](https://tw.wordpress.org/plugins/sqlite-database-integration/), [Czech](https://cs.wordpress.org/plugins/sqlite-database-integration/), [English (UK)](https://en-gb.wordpress.org/plugins/sqlite-database-integration/), [English (US)](https://wordpress.org/plugins/sqlite-database-integration/), [German](https://de.wordpress.org/plugins/sqlite-database-integration/), [Japanese](https://ja.wordpress.org/plugins/sqlite-database-integration/), [Persian](https://fa.wordpress.org/plugins/sqlite-database-integration/), [Polish](https://pl.wordpress.org/plugins/sqlite-database-integration/), [Portuguese (Brazil)](https://br.wordpress.org/plugins/sqlite-database-integration/), [Russian](https://ru.wordpress.org/plugins/sqlite-database-integration/), [Spanish (Chile)](https://cl.wordpress.org/plugins/sqlite-database-integration/), [Spanish (Spain)](https://es.wordpress.org/plugins/sqlite-database-integration/), and [Swedish](https://sv.wordpress.org/plugins/sqlite-database-integration/). * [Translate into your language](https://translate.wordpress.org/projects/wp-plugins/sqlite-database-integration) * Tags * [database](https://kin.wordpress.org/plugins/tags/database/)[SQLite](https://kin.wordpress.org/plugins/tags/sqlite/) * [Advanced View](https://kin.wordpress.org/plugins/sqlite-database-integration/advanced/) ## Ratings 4.6 out of 5 stars. * [ 10 5-star reviews ](https://wordpress.org/support/plugin/sqlite-database-integration/reviews/?filter=5) * [ 1 4-star review ](https://wordpress.org/support/plugin/sqlite-database-integration/reviews/?filter=4) * [ 0 3-star reviews ](https://wordpress.org/support/plugin/sqlite-database-integration/reviews/?filter=3) * [ 0 2-star reviews ](https://wordpress.org/support/plugin/sqlite-database-integration/reviews/?filter=2) * [ 1 1-star review ](https://wordpress.org/support/plugin/sqlite-database-integration/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/sqlite-database-integration/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/sqlite-database-integration/reviews/) ## Contributors * [ WordPress.org ](https://profiles.wordpress.org/wordpressdotorg/) * [ Ari Stathopoulos ](https://profiles.wordpress.org/aristath/) * [ Jan Jakeš ](https://profiles.wordpress.org/janjakes/) * [ Adam Zieliński ](https://profiles.wordpress.org/zieladam/) * [ Bero ](https://profiles.wordpress.org/berislavgrgicak/) * [ Brandon Payton ](https://profiles.wordpress.org/bpayton/) * [ zaerl ](https://profiles.wordpress.org/zaerl/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/sqlite-database-integration/)