S
by WordPress.org 4.6 (12 reviews)

SQLite Database Integration

Run WordPress on SQLite.

SQLite Database Integration ranks #2,980 among WordPress.org plugins with 5,000+ active installations, is #279 of 5,058 in the Security category, a 4.6/5 rating from 12 reviews, and was last updated Oct 28, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4
v3.1.2 Current Version v3.1.2
Updated 4 days ago Last Update on 28 Oct, 2026
Refreshed 18 hours ago Last Refreshed on
#279 of 5,058 in Security Top 5% by installs Downloads +5.5% this week Actively maintained
View on WordPress.org
Rank
#2,980
— No change
Active Installs
5K+
-8.2%
KW Avg Position
17
0.5 worse
Downloads
983.6K
+2,015 today
Support Resolved
0%
— No change
Rating
92%
Review 4.6 out of 5
4.6 (12 reviews)

Next Milestone 6K

Total Progress 85.5%
5K+ 6K+
57
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 145 more installs to reach 6K+

Rank Changes

2,935 2,948 2,961 2,973 2,986 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
2,934 2,949 2,964 2,979 2,994 17-10-2026 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
Current #2,980
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

2K 4K 6K 8K 10K 12K 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
2K 4K 6K 8K 10K 12K 17-10-2026 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

4.6
12 reviews
Overall 92%
5
10 (83%)
4
1 (8%)
3
0 (0%)
2
0 (0%)
1
1 (8%)

Security History

Source: WPVulnerability

No known vulnerabilities on record for SQLite Database Integration. Checked 1 month ago.

TL;DR

AI summary of the plugin's readme

This plugin is for WordPress users and developers who want to test running WordPress with SQLite instead of MySQL. It provides an experimental database integration layer, developed as a feature plugin with the goal of eventual inclusion in WordPress core.

  • SQLite database integration
  • Community feature plugin

Frequently Asked Questions

Common questions about SQLite Database Integration

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 and the call for testing for more context.
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.
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.
By default, the SQLite database is stored in a randomized path under WP_CONTENT_DIR . '/database'. The full path is recorded in db-path.php and exposed by the DB_PATH constant at runtime. For example: Database path: WP_CONTENT_DIR . '/database/.ht.020a33c5d9e5407e8e93b43e55abf62e/.ht.sqlite' Recorded in: WP_CONTENT_DIR . '/database/db-path.php' as return __DIR__ . '/...'; Exposed by: DB_PATH The random path makes the database location difficult to guess when it is not otherwise protected. We recommend setting DB_PATH to an explicit, protected path outside the web root that your web server does not expose. Integrations should always read DB_PATH after WordPress loads instead of assuming a fixed database path.
To properly secure the SQLite database, define the DB_PATH constant to an explicit path that is protected from public web access. An explicit DB_PATH value is used as-is without randomization. Define it in wp-config.php: // Use protected DB path that is not exposed by the web server. define( 'DB_PATH', '/private/wordpress/database.sqlite' ); Caution: An explicit DB_PATH must point to a protected location that your web server does not expose. Store the database outside the web root and make sure it's protected. The value of DB_PATH must be an absolute path to the SQLite database file, or :memory: for an in-memory SQLite database. The database directory must be writable by PHP. Changing DB_PATH selects a different database without moving an existing one.
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.
Feedback helps improve the integration. For troubleshooting, questions, suggestions, or feature requests, open an issue in the SQLite GitHub repository.
Contributions are welcome through the SQLite Database Integration repository on GitHub.
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.

More plugins by WordPress.org

Sign In / Register

You need to sign in or register to use this feature.