Recommended Free Tools
For a new WordPress installation, choose a host running MariaDB 10.11 or newer or MySQL 8.0 or newer. WordPress.org also recommends PHP 8.3 or newer, HTTPS, and a web server such as Apache with mod_rewrite or Nginx. WordPress identifies MySQL and MariaDB as its supported database servers; PostgreSQL, SQLite and other database engines are not supported at present.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
Older installations may still run with MySQL 5.5.5 or newer, but WordPress.org warns that legacy versions have reached official end of life and may expose a site to security vulnerabilities. Treat that as a migration situation, not as the target for a new site.
As an Amazon Associate I earn from qualifying purchases.
The current WordPress database requirement
The safest answer when evaluating a hosting plan in 2026 is to ask for the exact database product and version, not merely “a WordPress database.” The current WordPress.org Requirements page sets the recommended baseline at MariaDB 10.11 or greater or MySQL 8.0 or greater.
| Situation | Database guidance | How to interpret it |
|---|---|---|
| New installation | MariaDB 10.11+ or MySQL 8.0+ | Use this baseline when selecting or provisioning a server. |
| Existing legacy site | WordPress.org says WordPress will still run with MySQL 5.5.5+ | It may be possible to keep the site running temporarily, but the database is past official end of life and should be upgraded. |
| Older Developer Resources handbook page | MySQL 5.7+ or MariaDB 10.3+ | This is a separate, older set of stated thresholds, last updated December 17, 2025; do not substitute it for the current Requirements page when planning a new deployment. |
These figures are minimum or recommended thresholds, not a complete compatibility matrix. A release being newer than a threshold does not by itself prove that every WordPress version, plugin, theme or hosting configuration has been tested with it. For a precise release-to-release decision, check the documentation for the WordPress version you intend to run and the provider’s actual server specification.
Does WordPress support MySQL and MariaDB?
Yes. WordPress’s installation FAQ names MySQL and MariaDB as the supported database servers. They store the posts, pages, users, settings, comments and other structured data that WordPress reads and writes.
What WordPress does not support
The same FAQ says that other database engines, including PostgreSQL and SQLite, are not supported at present. A host cannot make an unsupported engine suitable simply by creating a database with a WordPress-looking name. WordPress core, its installation process and the normal plugin ecosystem expect MySQL-compatible behavior.
MySQL and MariaDB are not interchangeable labels
A provider may advertise “MySQL-compatible” hosting while running MariaDB. Ask which product is installed and which release is active. Record the complete answer, such as “MariaDB 10.11” or “MySQL 8.0,” rather than relying on a generic control-panel label.
Why the version matters
The database is a core runtime dependency, not an optional add-on. WordPress uses it on every request that retrieves content, checks a user session, saves an edit or updates configuration. A server that is below the recommended baseline can create an avoidable upgrade project and may leave the operating system, database server or extensions outside their vendors’ security-support windows.
Rank #2
WordPress.org specifically warns that the older legacy combination has reached official end of life and may expose sites to security vulnerabilities. The warning is important even if an old installation appears to work: “works” means the current code can connect and execute, not that the underlying server is receiving security fixes or that future WordPress releases and plugins will continue to behave the same way.
How the database requirement fits the rest of the stack
Database compatibility is only one part of the recommended environment. The current WordPress.org host checklist also asks for:
Free tools Windows power users keep installed
One-click scans. No signup required.
- PHP 8.3 or newer. PHP is the language runtime that executes WordPress and its extensions.
- HTTPS. Use a valid TLS certificate and configure the site to load securely.
- Apache with
mod_rewriteor Nginx. The web server must be able to route WordPress’s rewritten URLs correctly.
A plan can meet the database number and still be a poor WordPress choice if it supplies an obsolete PHP release, no HTTPS, or a web-server configuration that prevents pretty permalinks. Evaluate all four items together.
How to check the database version on an existing site
Check the live server rather than guessing from the year a hosting account was opened. Use an account with administrator access and avoid publishing the result, database hostname or credentials.
Rank #3
Check from the WordPress administration area
- Sign in to
/wp-admin. - Open Tools and then Site Health.
- Open the Info tab and expand the Database section. WordPress may show the server type and version, depending on the installation and host configuration.
- Note the exact product name and version. If the information is hidden or abbreviated, ask the host to confirm it in writing.
Check with SQL
If you have database access through a command-line client or an administration interface, run:
SELECT VERSION();For a server-variable view, run:
SHOW VARIABLES LIKE 'version';The returned value can identify both the engine and release. Do not run administrative changes while you are only trying to identify the version.
Check through a hosting panel or phpMyAdmin
phpMyAdmin is an optional web-based administration tool for MySQL and MariaDB. It is not a WordPress runtime requirement. If your host provides it, its home or database-server information screen may display the version. Treat that tool as a way to inspect or administer the server, not as something WordPress must have installed.
What to ask a hosting provider
Before buying or migrating, send a request that asks for the exact values rather than a marketing assurance. You can adapt this checklist:
- Which database engine is supplied: MySQL or MariaDB?
- What exact database-server version is running on the plan?
- Can the version be upgraded without moving to a different plan?
- Which PHP version is active, and can PHP 8.3 or newer be selected?
- Is HTTPS included and can a certificate be installed for every WordPress domain?
- Is the web server Apache with
mod_rewriteor Nginx configured for WordPress rewrites? - Are database backups available, and how are restores performed?
The WordPress.org Requirements page provides a copyable host question that asks about PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.0 or greater, Nginx or Apache with mod_rewrite, and HTTPS. Supplying those exact thresholds reduces the chance that “WordPress hosting” is interpreted as an outdated shared environment.
How to handle a legacy database safely
If your site reports an old MySQL release, do not start by replacing files or changing tables on the live site. Treat the work as an infrastructure upgrade.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall- Identify the complete stack. Record the WordPress version, PHP version, database product and version, active plugins and theme, and the hosting plan.
- Make verified backups. Keep a database export and a separate copy of the WordPress files. Confirm that the backup can be opened or restored before making changes.
- Create a staging copy. Test the site on a server using the current recommended database baseline and the PHP version you plan to use.
- Exercise real workflows. Test logins, publishing, media uploads, forms, scheduled tasks, search, checkout or membership features, and any external integrations your site depends on.
- Schedule the production change. Ask the host whether the database upgrade is in-place, requires a new server, or requires a migration. Obtain the rollback procedure and expected downtime.
- Recheck after the move. Confirm the reported database version, run the staging test list again, inspect error logs, and verify that backups continue to run.
Do not assume that a successful connection on the old server proves that every plugin is ready for a newer engine. Test the application as a whole, especially if it uses custom SQL or an abandoned extension.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common version and installation problems
“Your database server is too old” during installation
Confirm the actual server version with the SQL query above. If the host advertises a newer version but the installer sees an older one, the domain may be connected to a different server, an old database endpoint or a staging account. Give the host the exact version reported by WordPress and ask which server handles the request.
The host says “MySQL-compatible” but will not name the release
Ask for the engine and major/minor version in writing. Compatibility branding is not enough to evaluate a WordPress requirement or plan an upgrade.
A documentation page lists different numbers
You may be looking at the Developer Resources “Before You Install” page, which lists an older set of thresholds and records a December 17, 2025 update. The current Requirements page has the higher recommended baseline. They are two pages with different stated thresholds; do not present them as equivalent.
The server uses PostgreSQL or SQLite
That configuration is outside WordPress’s currently supported database engines. Move the site to a MySQL- or MariaDB-based environment instead of trying to force the standard installer to use an unsupported backend.
phpMyAdmin is missing
Missing phpMyAdmin does not mean WordPress is missing a requirement. It is an administration convenience. Ask the host for another safe way to view the version and create or restore backups, such as a provider console or command-line access.
Choosing between an adequate and a future-ready plan
When two plans meet the current database baseline, compare operational details rather than assuming the higher advertised number is automatically better. Check whether upgrades are performed promptly, whether you can select a supported PHP release, how backups and restores work, and whether the provider documents maintenance windows. A host that cannot disclose the exact engine version is harder to troubleshoot than one that publishes it clearly.
Also separate a minimum requirement from a performance claim. The official pages cited here publish requirements, not measured speed improvements, capacity figures or market-share statistics. Database version alone does not predict page-load time; query design, indexes, PHP workers, storage, caching, traffic and plugin behavior all matter.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Keeping the requirement current
WordPress requirements can change as PHP and database releases reach end of life. Recheck the current WordPress.org Requirements page when opening a new hosting account, planning a migration or upgrading a major WordPress release. Keep the provider’s specification, your version checks and your tested rollback plan together so that a future upgrade is a controlled maintenance task rather than an emergency.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
