WordPress 7.1 Hosting Requirements: What Your Host Needs to Support

The versions WordPress 7.1 will run on, the versions it actually recommends, and a checklist to confirm your hosting plan before you update.

Illustration of a server rack with status lights connected to the cloud, representing the server a WordPress site runs on
On this page
  1. The short answer
  2. Stable releases vs the WordPress 7.2 beta
  3. PHP: what to run, and what's reaching end of life
  4. Database: MySQL and MariaDB
  5. PHP extensions WordPress needs
  6. Memory and other PHP settings
  7. What's new in WordPress 7.1 that touches hosting
  8. How to check your current setup
  9. How to upgrade PHP safely
  10. What DreamHost and Hosting.com publish
  11. WordPress 7.1 hosting checklist
  12. What to ask a host before you buy
  13. Frequently asked questions
  14. Sources

WordPress 7.1 is the current stable version of WordPress, and the latest build is 7.1.4, released on October 28, 2026. It will run on PHP 7.4 or later with MySQL 5.5.5 or MariaDB 5.5.5 or later, but those are backward-compatibility floors, not targets. For a site you depend on, WordPress.org recommends PHP 8.3 or newer, MySQL 8.0 or newer (or MariaDB 10.11 or newer), and HTTPS support. The WordPress Hosting Team goes further for new installations: PHP 8.4 or 8.5, MySQL 8.4, or MariaDB 10.11, 11.4 or 11.8.

The short answer

WordPress 7.1 server requirements: what it runs on and what to ask your host for
ComponentWordPress 7.1 still runs onWordPress.org recommendsHosting Team recommends for new installs
PHP7.4 or later8.3 or later8.4 or 8.5
MySQL5.5.5 or later8.0 or later8.4 LTS
MariaDB5.5.5 or later10.11 or later10.11, 11.4 or 11.8 LTS
HTTPSNot required to runHTTPS supportNot covered separately
PHP memory limit128 MB for a basic installNot stated on the requirements page256 MB default; 512 MB or more for WooCommerce or page builders
Web serverAny server that runs PHP and MySQLApache or NginxApache 2.4, nginx 1.30 or 1.31; LiteSpeed and OpenLiteSpeed also listed

Sources: WordPress.org requirements, the WordPress 7.1 Server Compatibility page and the Hosting Handbook's server environment page. The memory figures are the Handbook's suggested tiers for hosts, not hard limits in WordPress itself.

Stable releases vs the WordPress 7.2 beta

WordPress 7.1 was released on August 19, 2026, and has had four maintenance and security releases since. WordPress.org's release archive says only the most recent version in the 7.1 series is safe to use and actively maintained.

WordPress versions as of November 14, 2026
VersionStatusDateUse it on a live site?
7.1.4Current stable security releaseOctober 28, 2026Yes. WordPress recommends updating immediately
7.1.1 to 7.1.3SupersededSeptember 17 to October 6, 2026No. Update to 7.1.4
7.2 betaTesting releaseBeta 1 on October 20, 2026; final release scheduled for December 8, 2026No. Test it on a staging copy only

The 7.2 Beta 1 announcement is explicit: don't install, run or test it on production or mission-critical websites. If you want to try 7.2 early, use a staging site or WordPress Playground.

Our recommendation: run 7.1.4 on live sites now, and test 7.2 on staging before it ships. If you run a store, plan the 7.2 update for after your busiest trading weeks rather than on release day.

PHP: what to run, and what's reaching end of life

WordPress 7.0 raised the minimum PHP version from 7.2.24 to 7.4, and 7.1 keeps that minimum. According to the Hosting Team's 7.1 page, WordPress 7.1 is fully compatible with PHP 7.4 through 8.5. PHP 7.4, 8.0 and 8.1 are already end of life and supported only for backward compatibility.

PHP versions WordPress 7.1 supports, with upstream support dates
PHP versionUpstream statusEnd of lifeWhat it means for you
8.5Active supportDecember 31, 2029Fine for WordPress 7.1 if your plugins and theme support it
8.4Active supportDecember 31, 2028The Hosting Handbook's recommended production version
8.3Security fixes onlyDecember 31, 2027Meets WordPress.org's recommendation; plan a move to 8.4
8.2Security fixes onlyDecember 31, 2026Upgrade soon: security support ends in weeks
7.4, 8.0 and 8.1End of lifeAlready passedRuns WordPress 7.1, but gets no PHP security fixes

If your host still runs PHP 7.2 or 7.3, WordPress won't update your site to the 7.x series. The Make WordPress Core announcement says those sites stay on the 6.9 branch.

Plugins set their own minimums too. WooCommerce, for example, has announced that WooCommerce 11.6, planned for February 2027, will require PHP 8.1 or newer, and it recommends PHP 8.3 or newer. If you sell online, see our guide to WooCommerce hosting for small businesses.

Database: MySQL and MariaDB

WordPress works with either MySQL or MariaDB. Here the official pages don't quite line up:

  • WordPress.org's requirements page recommends MySQL 8.0 or greater, or MariaDB 10.11 or greater.
  • The Hosting Team's 7.1 page notes that MySQL 8.0 reached end of life on April 30, 2026, and recommends MySQL 8.4 LTS. It also says MariaDB 10.6 reached end of life on July 6, 2026.

So MySQL 8.0 still meets WordPress.org's published recommendation, but it no longer receives upstream fixes. If you choose a new host or plan, ask for MySQL 8.4 or a supported MariaDB LTS version. You can see what your site uses in Tools > Site Health > Info > Database.

On shared hosting, the host decides the database version. DreamHost's help center says its shared MySQL servers run MySQL 8, and that shared servers are moved to MySQL 8.4 on a proactive schedule. Customers who need 8.4 sooner can add a MySQL VPS.

PHP extensions WordPress needs

The Hosting Handbook's server environment page splits PHP extensions into required and highly recommended. Most hosts enable these by default, but it's worth checking, especially on a VPS you manage yourself. The Status tab in Tools > Site Health warns you if required or recommended modules are missing.

PHP extensions listed in the WordPress Hosting Handbook
StatusExtensionsWhat they do
Requiredjson, hash, mysqliData handling, hashing and the database connection
Highly recommendedcurl, dom, exif, fileinfo, igbinary, imagick, intl, mbstring, openssl, xml, zipRemote requests, image handling, file type checks, text handling, secure connections and update packages
Cachingopcache, plus one of apcu, memcached or redisKeeps compiled PHP and frequent data in memory

Two are easy to miss. Imagick gives better image quality than the GD fallback, and zip is needed to install plugin, theme and WordPress update packages.

Memory and other PHP settings

WordPress doesn't set PHP's memory_limit itself. According to the Hosting Handbook, its own defaults are 40 MB for front-end requests (64 MB on Multisite) and 256 MB for admin, cron and image processing. WordPress tries to raise PHP's limit to these values when needed, and if the server doesn't allow that, the server's setting applies. The Handbook suggests these tiers for hosts:

  • 128 MB: enough for a basic install.
  • 256 MB: the recommended default.
  • 512 MB or more: for resource-heavy sites, such as WooCommerce stores or sites built with page builders.

Shared plans often cap memory, CPU and processes per account. If you see "Allowed memory size exhausted" errors, ask your host what your plan allows before raising WP_MEMORY_LIMIT in wp-config.php.

What's new in WordPress 7.1 that touches hosting

WordPress 7.1 doesn't add a new server requirement, but one feature changes how your server is used.

Image processing can move into the browser

According to the client-side media processing dev note, WordPress 7.1 can resize, compress, rotate and convert images in the editor using WebAssembly, before uploading them. It's on by default in supported browsers:

  • Chrome and Edge 137 or later on desktop, and Chrome on Android from version 146.
  • Devices with more than 2 GB of memory and at least two CPU cores, on a connection faster than 2G.

Everyone else, including Firefox and Safari users, falls back to the usual server-side processing. Your host still needs Imagick or GD.

Two details matter for hosting and security setups:

  • Content Security Policy: if a security plugin or your server sets a worker-src policy, it must allow blob:. Otherwise processing quietly falls back to the server.
  • Image plugins: the server-side hooks wp_image_editors, image_memory_limit and image_make_intermediate_size don't run for images processed in the browser. If you use an image optimization or watermark plugin, test uploads after updating.

The feature can help on small plans, because large phone photos no longer have to be resized by PHP. Developers can switch it off with the wp_client_side_media_processing_enabled filter.

AI connections from WordPress 7.0

WordPress 7.0 added an AI Client and a Connectors screen for linking external AI services. Our view: these connections are requests from your server to the AI provider, so if your host restricts outgoing connections, which is uncommon on standard plans, ask before relying on them. The curl and openssl extensions listed above cover the usual case.

How to check your current setup

  1. Open Site Health. In WordPress, go to Tools > Site Health > Info. The Server section shows your PHP version, memory limit and other PHP settings. The Database section shows MySQL or MariaDB and its version.
  2. Check the Status tab. Site Health flags an outdated PHP version, missing PHP modules and other critical issues.
  3. Find your host's PHP setting. At DreamHost, you can change a site's PHP version in the panel. At Hosting.com, newer accounts change it per website in the Hosting Panel, while its managed VPS and managed dedicated customers open a support ticket.
  4. Write down what you find. Compare it with the table at the top of this page before you update WordPress or change plans.

How to upgrade PHP safely

A PHP upgrade is usually painless, but an old plugin or theme can break. This is the order we recommend:

  1. Back up the files and the database, and keep a copy off the server.
  2. Update WordPress, plugins and your theme first. Current versions are far more likely to support newer PHP.
  3. Check each plugin's "Requires PHP" and "Tested up to" details on WordPress.org, or with the developer for premium plugins.
  4. Test on staging if your plan includes it, then switch the live site.
  5. Browse key pages and test forms and checkout, and check your error log for warnings.
  6. Keep the old version noted so you can switch back quickly if something breaks.

DreamHost offers paid PHP Extended Support for sites that can't yet move off an end-of-life version. Treat that as a short bridge, not a plan.

What DreamHost and Hosting.com publish

Both providers can run WordPress 7.1. This is what their official pages say about the parts covered above.

DreamHost and Hosting.com: published details relevant to WordPress 7.1, checked November 14, 2026
ItemDreamHostHosting.com
PHP versions8.2 to 8.5 listed as available; 8.1 and older are unsupported and may add PHP Extended Support chargesSelectable per website in the Hosting Panel; the help article we read doesn't list versions, so confirm 8.3 to 8.5 before buying
DatabaseMySQL 8 on shared servers, moving to 8.4 on DreamHost's scheduleNot stated on the pages we read; ask
BackupsDaily automated backups on Web Hosting plansDaily backups kept for 30 days on shared plans
Staging for testing updatesDreamPress onlyPro and Max shared plans, and all Managed WordPress plans
More detailDreamHost review and DreamPress reviewHosting.com review and Managed WordPress review

If you'd rather not manage PHP versions, staging and caching yourself, managed WordPress hosting takes on more of that work. Our guide to shared vs managed WordPress hosting explains the trade-offs, and WP Engine is another managed platform we've reviewed.

View DreamHost WordPress Plans (opens DreamHost: WordPress Hosting in a new tab)

View Hosting.com Shared Plans (opens Hosting.com Shared Hosting in a new tab)

WordPress 7.1 hosting checklist

  • PHP 8.3 or newer is available, ideally 8.4, and you can choose the version yourself
  • MySQL 8.4 or MariaDB 10.11, 11.4 or 11.8, or a clear date for moving off MySQL 8.0
  • HTTPS with free, automatically renewing certificates
  • A PHP memory limit of at least 256 MB, or 512 MB for a store or page builder site
  • The required and recommended PHP extensions, including Imagick, zip and OPcache
  • Daily backups stored away from the server, with restores you can run yourself
  • Staging, if you update plugins or themes often
  • SFTP or SSH access, and PHP running under your own account user

The last point comes from WordPress.org's requirements page, which says hosting is more secure when PHP runs under your account's username rather than a shared server user. Our WordPress security guide covers the rest of what a host should handle.

What to ask a host before you buy

If a plan page doesn't answer these, send a pre-sales question by ticket or email so you have the reply in writing:

I'm planning to run WordPress 7.1. Which PHP versions can I choose on [plan name], and can I switch between them myself? Which MySQL or MariaDB version will my database use, and when will it next be upgraded? What is the PHP memory limit, and are Imagick and OPcache enabled?

For a wider buying checklist, see how to choose reliable hosting.

Frequently asked questions

What PHP version does WordPress 7.1 need?

WordPress 7.1 requires PHP 7.4 or later. WordPress.org recommends PHP 8.3 or newer, and the WordPress Hosting Team recommends PHP 8.4 or 8.5 for new installations.

Does WordPress 7.1 work with PHP 8.5?

Yes. The Hosting Team's 7.1 compatibility page lists WordPress 7.1 as fully compatible with PHP 8.5. Your plugins and theme also need to support it, so test before switching.

Is MySQL 8.0 still OK for WordPress?

It meets WordPress.org's published recommendation of MySQL 8.0 or greater, but MySQL 8.0 reached end of life on April 30, 2026. The Hosting Team recommends MySQL 8.4 LTS, so ask your host when it will move.

Should I install WordPress 7.2 now?

Not on a live site. As of November 14, 2026, 7.2 is in beta and scheduled for release on December 8, 2026. WordPress.org says not to run betas on production or mission-critical sites.

Do I need a VPS to run WordPress 7.1?

No. Shared hosting that offers the recommended PHP and database versions can run WordPress 7.1. A VPS or managed WordPress plan helps when you need more resources or control.

What happens if my host only offers PHP 7.2 or 7.3?

WordPress won't update your site to the 7.x series. It stays on the 6.9 branch until you move to PHP 7.4 or newer, and ideally to PHP 8.3 or later.

Sources

Requirements last checked: November 14, 2026. WordPress, PHP and hosting providers update these pages regularly, so check the linked sources before making changes.