{"id":530,"date":"2026-05-20T15:34:58","date_gmt":"2026-05-20T15:34:58","guid":{"rendered":"https:\/\/www.ahosting.net\/blog\/?p=530"},"modified":"2026-05-23T11:46:40","modified_gmt":"2026-05-23T11:46:40","slug":"wordpress-7-0-hosting-requirements-is-your-host-ready","status":"publish","type":"post","link":"https:\/\/www.ahosting.net\/blog\/wordpress-7-0-hosting-requirements-is-your-host-ready\/","title":{"rendered":"WordPress 7.0 Hosting Requirements: Is Your Host Ready?"},"content":{"rendered":"\n<script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What are the WordPress 7.0 hosting requirements?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"In short, the WordPress 7.0 hosting requirements are: PHP 7.4 minimum (PHP 8.3 recommended, PHP 8.4 optimal), MySQL 8.0 or MariaDB 10.6 as the minimum database, at least 256MB of PHP memory (512MB for AI features), and HTTPS for AI Connectors. Sites on PHP 8.1 or MySQL 5.7 risk broken functionality after upgrading.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Do the WordPress 7.0 hosting requirements include a PHP upgrade?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"For most sites, a PHP upgrade is required. The WordPress 7.0 hosting requirements set PHP 7.4 as the hard minimum. However, PHP 8.3 is the recommended version and PHP 8.4 is optimal. PHP 8.1 reached end-of-life on December 31, 2025, and no longer receives security patches. Consequently, sites on PHP 8.1 should upgrade to 8.3 or 8.4 before updating WordPress.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Do the WordPress 7.0 hosting requirements include MySQL 8.0?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Indeed, MySQL 8.0 or MariaDB 10.6 is a hard minimum in the WordPress 7.0 hosting requirements. The new DataViews admin interface uses query patterns that MySQL 5.7 does not support. As a result, sites on MySQL 5.7 may see a broken admin panel or query errors after updating to WordPress 7.0.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How much PHP memory do the WordPress 7.0 hosting requirements specify for AI features?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Specifically, for AI features, the WordPress 7.0 hosting requirements recommend 512MB of PHP memory. The general minimum is 256MB. The new Abilities API and WP AI Client need this headroom to run well. Plans capped at 256MB or less may consequently see AI features fail silently or throw fatal errors.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What is the WP AI Client introduced in WordPress 7.0?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Notably, the WP AI Client is a standardized connection layer built into WordPress 7.0 core. It lets you configure an AI provider once in Settings, and all compatible plugins share those credentials automatically. This replaces the old approach where each AI plugin managed its own separate API connection to providers like OpenAI, Google Gemini, or Anthropic Claude.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Does my hosting IP address affect WordPress 7.0 AI features?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"In practice, a stable outbound IP is an underappreciated WordPress 7.0 hosting requirement. The WP AI Client makes API calls from your server to AI providers. On a shared IP, those calls can be rate-limited or flagged due to activity from other sites sharing the same IP. Therefore, a dedicated IP gives your AI calls an isolated, trusted identity \u2014 which is why AHosting includes a free dedicated IP with every WordPress hosting plan.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Can shared hosting meet the WordPress 7.0 hosting requirements?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Yes, shared hosting can meet the WordPress 7.0 hosting requirements if the host supports PHP 8.3 or higher, MySQL 8.0 or MariaDB 10.6, and at least 256MB of PHP memory. However, the most common blockers are hosts still defaulting to PHP 8.1 and running MySQL 5.7. Check your versions in WordPress Tools, Site Health, Info, and Server before updating.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What PHP version best satisfies the WordPress 7.0 hosting requirements in 2026?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Overall, PHP 8.4 is the optimal choice for the WordPress 7.0 hosting requirements in 2026. It has security support through December 2028, the best performance benchmarks (roughly 21% faster for WooCommerce vs PHP 7.4), and broad plugin compatibility. PHP 8.3 is a solid alternative with support through December 2027. Avoid PHP 8.2 \u2014 it loses all support in December 2026.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What is the Abilities API in WordPress 7.0?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Specifically, the Abilities API is a secure framework built into WordPress 7.0 core. It standardizes how plugins request and run AI-powered actions. Instead of building their own AI integrations, plugins request capabilities \u2014 content writing, image alt text, tone adjustment, and translation \u2014 through a consistent, gated interface. This is one of the main reasons the WordPress 7.0 hosting requirements now include memory and IP guidance for AI use.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Should I test WordPress 7.0 hosting requirements on staging before updating production?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Above all, testing on staging before going live is strongly recommended. The safest path to verify the WordPress 7.0 hosting requirements is: (1) full backup, (2) clone to staging, (3) upgrade PHP to 8.3 or 8.4 and test, (4) confirm MySQL 8.0 and test again, (5) update WordPress 7.0 on staging and verify, (6) repeat on production only after staging passes. Never test PHP upgrades or WordPress core updates directly on a live site.\"\n      }\n    }\n  ]\n}\n<\/script>\n\n\n\n<!-- TL;DR Custom HTML Block -->\n<div class=\"ah-tldr\">\n  <span class=\"ah-tldr-badge\">TL;DR<\/span><br>\n  WordPress 7.0 hosting requirements include PHP 7.4 minimum (PHP 8.3 recommended), MySQL 8.0 or MariaDB 10.6, and at least 512MB of memory for the new AI features. If your host has not upgraded, you risk a broken dashboard the moment you hit &#8220;update.&#8221;\n<\/div>\n\n\n<div class=\"wp-block-aioseo-table-of-contents\"><ul><li><a class=\"aioseo-toc-item\" href=\"#aioseo-listen-to-this-post-as-a-podcast-6\">&#x1f3a7; Listen to This Post as a Podcast<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-wordpress-7-0-hosting-requirements-what-actually-changed-9\">WordPress 7.0 Hosting Requirements: What Actually Changed<\/a><ul><li><a class=\"aioseo-toc-item\" href=\"#aioseo-the-three-requirements-that-changed-everything-13\">The Three Requirements That Changed Everything<\/a><\/li><\/ul><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-the-full-wordpress-7-0-hosting-requirements-minimum-specs-20\">The Full WordPress 7.0 Hosting Requirements: Minimum Specs<\/a><ul><li><a class=\"aioseo-toc-item\" href=\"#aioseo-how-to-check-your-current-php-and-mysql-versions-25\">How to Check Your Current PHP and MySQL Versions<\/a><\/li><\/ul><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-php-8-1-is-end-of-life-the-most-urgent-wordpress-7-0-hosting-requirement-32\">PHP 8.1 Is End-of-Life: The Most Urgent WordPress 7.0 Hosting Requirement<\/a><ul><li><a class=\"aioseo-toc-item\" href=\"#aioseo-which-php-version-should-you-run-on-wordpress-7-0-37\">Which PHP Version Should You Run on WordPress 7.0?<\/a><\/li><\/ul><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-wordpress-7-0-hosting-requirements-for-ai-features-42\">WordPress 7.0 Hosting Requirements for AI Features<\/a><ul><li><a class=\"aioseo-toc-item\" href=\"#aioseo-why-hosting-quality-affects-wordpress-7-0-ai-performance-48\">Why Hosting Quality Affects WordPress 7.0 AI Performance<\/a><\/li><\/ul><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-mysql-8-0-the-wordpress-7-0-database-hosting-requirement-most-hosts-ignore-56\">MySQL 8.0: The WordPress 7.0 Database Hosting Requirement Most Hosts Ignore<\/a><ul><li><a class=\"aioseo-toc-item\" href=\"#aioseo-why-mysql-5-7-breaks-the-new-admin-interface-58\">Why MySQL 5.7 Breaks the New Admin Interface<\/a><\/li><\/ul><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-does-your-setup-meet-the-wordpress-7-0-hosting-requirements-65\">Does Your Setup Meet the WordPress 7.0 Hosting Requirements?<\/a><ul><li><a class=\"aioseo-toc-item\" href=\"#aioseo-php-version-69\">&#x2705; PHP Version<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-database-version-74\">&#x2705; Database Version<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-memory-and-resources-79\">&#x2705; Memory and Resources<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-server-and-ip-setup-84\">&#x2705; Server and IP Setup<\/a><\/li><\/ul><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-ahosting-meeting-wordpress-7-0-hosting-requirements-since-2002-91\">AHosting: Meeting WordPress 7.0 Hosting Requirements Since 2002<\/a><ul><li><a class=\"aioseo-toc-item\" href=\"#aioseo-whats-included-with-every-ahosting-wordpress-plan-95\">What&#039;s Included With Every AHosting WordPress Plan<\/a><\/li><\/ul><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-how-to-upgrade-your-hosting-to-meet-wordpress-7-0-requirements-105\">How to Upgrade Your Hosting to Meet WordPress 7.0 Requirements<\/a><ul><li><a class=\"aioseo-toc-item\" href=\"#aioseo-step-1-back-up-everything-107\">First Step: Back Up Everything<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-step-2-set-up-a-staging-site-109\">Second Step: Set Up a Staging Site<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-step-3-upgrade-php-on-staging-111\">Third Step: Upgrade PHP on Staging<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-step-4-upgrade-your-database-117\">Fourth Step: Upgrade Your Database<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-step-5-update-wordpress-7-0-on-staging-then-live-119\">Fifth Step: Update WordPress 7.0 on Staging, Then Live<\/a><\/li><\/ul><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-wordpress-7-0-hosting-requirements-quick-reference-table-123\">WordPress 7.0 Hosting Requirements: Quick Reference Table<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-conclusion-get-your-hosting-right-before-you-update-128\">Conclusion: Get Your Hosting Right Before You Update<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-frequently-asked-questions-about-wordpress-7-0-hosting-requirements-130\">Frequently Asked Questions About WordPress 7.0 Hosting Requirements<\/a><\/li><\/ul><\/div>\n\n\n<p class=\"wp-block-paragraph\">WordPress 7.0 is officially here. After months of work, two delays, and four release candidates, the biggest WordPress update in years landed on May 20, 2026. It is not just a feature drop. Indeed, it is a platform shift. The new Abilities API, WP AI Client, and DataViews admin redesign all point one way: the bar for hosting just went up. Do you know the WordPress 7.0 hosting requirements and is your host ready?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, most upgrade guides cover <em>what<\/em> WordPress 7.0 does. This one covers whether your hosting can actually <em>run<\/em> it \u2014 and what to do right now if it can&#8217;t.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Whether you are a site owner who clicks &#8220;update&#8221; and hopes for the best, or a developer with a dozen client sites to manage, this post tells you exactly what to check before you hit that button.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"aioseo-listen-to-this-post-as-a-podcast-6\" class=\"wp-block-heading\">&#x1f3a7; Listen to This Post as a Podcast<\/h2>\n\n\n\n<figure class=\"wp-block-audio\"><audio controls src=\"https:\/\/www.ahosting.net\/blog\/wp-content\/uploads\/2026\/05\/Mandatory_server_requirements_for_WordPress_7.m4a\"><\/audio><figcaption class=\"wp-element-caption\">Listen to this post. Part of the AHosting WordPress Hosting series.<\/figcaption><\/figure>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"aioseo-wordpress-7-0-hosting-requirements-what-actually-changed-9\" class=\"wp-block-heading\">WordPress 7.0 Hosting Requirements: What Actually Changed<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In fact, the WordPress 7.0 hosting requirements changed because the platform itself changed. For most of the past decade, hosting specs barely moved. New blocks, better tooling, small tweaks. For example, PHP 8.0 worked fine. MySQL 5.7 kept running. Budget <a href=\"https:\/\/www.ahosting.net\/web-hosting.html\">shared hosting<\/a> plans kept pace without friction.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, WordPress 7.0 breaks that pattern. Three things changed at once. Together, they raise the bar for what any host must provide.<\/p>\n\n\n\n<h3 id=\"aioseo-the-three-requirements-that-changed-everything-13\" class=\"wp-block-heading\">The Three Requirements That Changed Everything<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>1. The PHP floor moved up.<\/strong> Specifically, the WordPress 7.0 hosting requirements for PHP set 7.4 as the hard minimum. PHP versions below that will not load the platform at all. In particular, PHP 8.3 is the recommended version, with PHP 8.4 offering the best speed of any supported release. If your host still defaults to PHP 8.1, that version went end-of-life on December 31, 2025. Your site is running without security patches.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>2. The database bar rose.<\/strong> Additionally, WordPress 7.0 requires MySQL 8.0 or MariaDB 10.6 as a minimum. Specifically, the DataViews interface \u2014 the new React-based admin replacing the old WP List Tables \u2014 needs database features that MySQL 5.7 does not have. Indeed, many budget hosts still run MySQL 5.7. That problem shows up after you update \u2014 not before.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>3. AI features need real memory.<\/strong> Furthermore, the new Abilities API and WP AI Client need at least 512MB of PHP memory to run well. The WordPress default has always been 64MB or 128MB. Plans capped at 256MB will, consequently, see AI features fail silently.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In practice, none of this is theory. If you upgrade on a host that has not kept up, you will see a broken admin panel, failed plugins, or a white screen from a database conflict. Typically, you will only find out when something breaks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Let&#8217;s go through each WordPress 7.0 hosting requirement in detail.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<figure class=\"wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe loading=\"lazy\" title=\"Is Your Hosting Ready for WordPress 7.0? PHP, MySQL &amp; AI Requirements Explained\" width=\"500\" height=\"281\" src=\"https:\/\/www.youtube-nocookie.com\/embed\/mkLa2wtoVVo?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe>\n<\/div><\/figure>\n\n\n\n<h2 id=\"aioseo-the-full-wordpress-7-0-hosting-requirements-minimum-specs-20\" class=\"wp-block-heading\">The Full WordPress 7.0 Hosting Requirements: Minimum Specs<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before diving into the <em>why<\/em>, here is the complete list of WordPress 7.0 hosting requirements. These align with the <a href=\"https:\/\/wordpress.org\/about\/requirements\/\" target=\"_blank\" rel=\"noopener\">official WordPress system requirements<\/a> published on WordPress.org. Also, print it. Share it with your host. Check it before you update.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Component<\/th><th>Minimum<\/th><th>Recommended<\/th><th>Optimal<\/th><\/tr><\/thead><tbody><tr><td><strong>PHP<\/strong><\/td><td>7.4<\/td><td>8.3<\/td><td>8.4<\/td><\/tr><tr><td><strong>MySQL<\/strong><\/td><td>8.0<\/td><td>8.0<\/td><td>8.4<\/td><\/tr><tr><td><strong>MariaDB<\/strong><\/td><td>10.6<\/td><td>10.11<\/td><td>11.4 LTS<\/td><\/tr><tr><td><strong>PHP Memory<\/strong><\/td><td>64MB<\/td><td>256MB<\/td><td>512MB+<\/td><\/tr><tr><td><strong>Disk Space<\/strong><\/td><td>1GB<\/td><td>5GB+<\/td><td>Varies<\/td><\/tr><tr><td><strong>HTTPS<\/strong><\/td><td>Required<\/td><td>Required<\/td><td>With HTTP\/2<\/td><\/tr><tr><td><strong>PHP Extensions<\/strong><\/td><td>mod_rewrite, cURL, DOM, Exif, Fileinfo, Hash, Imagick or GD, JSON, Mbstring, OpenSSL, pcre, XMLReader, Zip<\/td><td>Same<\/td><td>Same<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Notably, the most important row for existing site owners is PHP. Meeting the WordPress 7.0 hosting requirements for PHP means running at least version 7.4. In practice, you want 8.3 or 8.4. Specifically, anything below 8.2 is either end-of-life or close to it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, the database row is the one most people miss. That jump from MySQL 5.7 to MySQL 8.0 is not a small update. It changes how the database handles queries. Moreover, the new DataViews admin is built for MySQL 8.0 behavior. If you are on a <a href=\"https:\/\/www.ahosting.net\/wordpress-hosting.html\">WordPress hosting<\/a> plan set up years ago on a cheap shared tier, there is a real chance your host has not upgraded the database. Most do not announce it. Typically, you only find out when something breaks.<\/p>\n\n\n\n<h3 id=\"aioseo-how-to-check-your-current-php-and-mysql-versions-25\" class=\"wp-block-heading\">How to Check Your Current PHP and MySQL Versions<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The fastest way to check your WordPress 7.0 hosting requirements is to open <strong>Tools \u2192 Site Health \u2192 Info \u2192 Server<\/strong> in your WordPress admin. Your PHP version, database type, and database version are all listed there.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">From the command line, for <a href=\"https:\/\/www.ahosting.net\/vps-hosting.html\">VPS hosting<\/a> users:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>php -v          # Shows your PHP version\nmysql -V        # Shows your MySQL\/MariaDB version<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">By contrast, shared hosting users depend on their host to make upgrades. If your host has not moved to MySQL 8.0, it is time to push them \u2014 or find a host that already meets the WordPress 7.0 hosting requirements as standard.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"aioseo-php-8-1-is-end-of-life-the-most-urgent-wordpress-7-0-hosting-requirement-32\" class=\"wp-block-heading\">PHP 8.1 Is End-of-Life: The Most Urgent WordPress 7.0 Hosting Requirement<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Here is the WordPress 7.0 hosting requirement that gets the least attention. PHP 8.1 went end-of-life on December 31, 2025. That means no patches at all \u2014 not limited, and not critical-only. PHP 8.1 is therefore fully unsupported now.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Consequently, many shared hosting plans still default new installs to PHP 8.1. Budget hosts avoid upgrade costs. As a result, you \u2014 the site owner \u2014 carry the security risk.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Here is the full PHP lifecycle for 2026, based on the <a href=\"https:\/\/www.php.net\/supported-versions.php\" target=\"_blank\" rel=\"noopener\">PHP supported versions page<\/a>:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>PHP Version<\/th><th>Active Support<\/th><th>Security Support<\/th><th>Status in 2026<\/th><\/tr><\/thead><tbody><tr><td>PHP 7.4<\/td><td>Ended Nov 2021<\/td><td>Ended Nov 2022<\/td><td>&#x26d4; Critical: unsupported 4+ years<\/td><\/tr><tr><td>PHP 8.0<\/td><td>Ended Nov 2022<\/td><td>Ended Nov 2023<\/td><td>&#x26d4; Critical: unsupported 3+ years<\/td><\/tr><tr><td>PHP 8.1<\/td><td>Ended Nov 2023<\/td><td><strong>Ended Dec 31, 2025<\/strong><\/td><td>&#x26a0;&#xfe0f; EOL \u2014 no patches, active risk<\/td><\/tr><tr><td>PHP 8.2<\/td><td>Ended Dec 2024<\/td><td><strong>Ends Dec 2026<\/strong><\/td><td>&#x26a0;&#xfe0f; Security-only until year end<\/td><\/tr><tr><td>PHP 8.3<\/td><td>Ends Dec 2025<\/td><td><strong>Ends Dec 2027<\/strong><\/td><td>&#x2705; Safe through 2027<\/td><\/tr><tr><td>PHP 8.4<\/td><td>Ends Dec 2026<\/td><td><strong>Ends Dec 2028<\/strong><\/td><td>&#x2705; Best \u2014 safe through 2028<\/td><\/tr><tr><td>PHP 8.5<\/td><td>Ends Dec 2027<\/td><td>Ends Dec 2029<\/td><td>&#x2705; Newest \u2014 broadest coverage<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 id=\"aioseo-which-php-version-should-you-run-on-wordpress-7-0-37\" class=\"wp-block-heading\">Which PHP Version Should You Run on WordPress 7.0?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, the answer for the WordPress 7.0 hosting requirements is clear: <strong>skip PHP 8.2 and go straight to 8.3 or 8.4.<\/strong> PHP 8.2 loses all support in December 2026. That is less than seven months away. You would upgrade only to face another upgrade before the year ends.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">As a result, PHP 8.4 is the smarter long-term pick. Security patches run through December 2028. <a href=\"https:\/\/fatlabwebsupport.com\/blog\/website-maintenance\/wordpress-php-version-upgrade\/\" target=\"_blank\" rel=\"noopener\">Independent 2026 benchmarks<\/a> show it delivers a 6.6% speed gain for standard WordPress sites versus PHP 7.4 \u2014 and a 21% gain for WooCommerce stores.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Fortunately, AHosting&#8217;s <a href=\"https:\/\/www.ahosting.net\/wordpress-hosting.html\">WordPress hosting plans<\/a> support PHP 8.3 and 8.4 on every tier. You switch versions in seconds via cPanel&#8217;s MultiPHP Manager. No support ticket, no wait, and no new plan needed.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"aioseo-wordpress-7-0-hosting-requirements-for-ai-features-42\" class=\"wp-block-heading\">WordPress 7.0 Hosting Requirements for AI Features<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The biggest addition in WordPress 7.0 is not a new block. Specifically, it is the Abilities API and the WP AI Client. Together, they give WordPress a standard way to connect to AI services \u2014 OpenAI, Google Gemini, Anthropic Claude, and others \u2014 through one shared setup. This changes the WordPress 7.0 hosting requirements in ways most shared plans are not ready for. For more detail on what these tools do, see the <a href=\"https:\/\/make.wordpress.org\/core\/\" target=\"_blank\" rel=\"noopener\">WordPress core development blog<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Specifically, here is what the new AI system includes:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The Abilities API<\/strong> \u2014 A secure framework for AI-powered actions. Plugins use it to run tasks like content writing, image alt text, and translation. They request these through a gated system, so no plugin can grab your credentials directly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>WP AI Client<\/strong> \u2014 The connection layer. Set up your AI service once in <strong>Settings \u2192 Connectors<\/strong>. After that, every compatible plugin shares those settings. No more entering API keys in five different places.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>AI Experiments Plugin<\/strong> \u2014 Ships with WordPress 7.0 core. It requires admin approval before plugins can access your AI setup. This stops a rogue plugin from quietly using your API credits.<\/p>\n\n\n\n<h3 id=\"aioseo-why-hosting-quality-affects-wordpress-7-0-ai-performance-48\" class=\"wp-block-heading\">Why Hosting Quality Affects WordPress 7.0 AI Performance<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In practice, the WordPress 7.0 hosting requirements for AI features are not on a spec sheet. They show up in whether the features actually work. The AI tools make outbound calls from your server to an AI provider. As such, your hosting affects every one of those calls:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Memory limits:<\/strong> The WP AI Client needs headroom. A 256MB PHP limit may not be enough when several AI tasks run at once. For <a href=\"https:\/\/www.ahosting.net\/woocommerce-hosting.html\">WooCommerce hosting<\/a> stores using AI at scale, 512MB is the floor.<\/li>\n\n\n\n<li><strong>Response time:<\/strong> Server speed sets how fast your AI calls start and finish. Overloaded shared servers add delay to every AI task. In other words, a slow server means slow AI \u2014 every time.<\/li>\n\n\n\n<li><strong>Dedicated IP stability:<\/strong> AI providers track request origins. On a shared IP, your calls can be flagged or slowed due to a neighbour site&#8217;s activity \u2014 not yours. A dedicated IP gives your AI calls a clean identity. Notably, this is why email experts have always backed dedicated IPs: you control your own reputation. AHosting includes a free dedicated IP on every WordPress plan.<\/li>\n\n\n\n<li><strong>Uptime:<\/strong> AI workflows depend on your server being up. For example, a host with 99.9% uptime is still down eight hours per year. That gap shows up in the reliability of every AI-powered task.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"aioseo-mysql-8-0-the-wordpress-7-0-database-hosting-requirement-most-hosts-ignore-56\" class=\"wp-block-heading\">MySQL 8.0: The WordPress 7.0 Database Hosting Requirement Most Hosts Ignore<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Of all the WordPress 7.0 hosting requirements, the MySQL 8.0 minimum gets the least coverage. That is a mistake \u2014 and indeed, it will break admin panels on many sites today.<\/p>\n\n\n\n<h3 id=\"aioseo-why-mysql-5-7-breaks-the-new-admin-interface-58\" class=\"wp-block-heading\">Why MySQL 5.7 Breaks the New Admin Interface<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In fact, WordPress has been moving toward MySQL 8.0 behavior across several releases. Version 7.0 makes that shift final. The new DataViews interface uses query patterns that need MySQL 8.0&#8217;s CTE (Common Table Expressions) support and window functions \u2014 all <a href=\"https:\/\/dev.mysql.com\/doc\/relnotes\/mysql\/8.0\/en\/\" target=\"_blank\" rel=\"noopener\">documented in the MySQL 8.0 release notes<\/a>. On MySQL 5.7, those queries fail or return wrong results.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Here is what the gap looks like:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Feature<\/th><th>MySQL 5.7<\/th><th>MySQL 8.0<\/th><th>MariaDB 10.6<\/th><\/tr><\/thead><tbody><tr><td><strong>DataViews admin tables<\/strong><\/td><td>&#x26a0;&#xfe0f; Errors possible<\/td><td>&#x2705; Full support<\/td><td>&#x2705; Full support<\/td><\/tr><tr><td><strong>Common Table Expressions<\/strong><\/td><td>Limited<\/td><td>&#x2705; Full support<\/td><td>&#x2705; Full support<\/td><\/tr><tr><td><strong>Window functions<\/strong><\/td><td>&#x274c; Not supported<\/td><td>&#x2705; Full support<\/td><td>&#x2705; Full support<\/td><\/tr><tr><td><strong>JSON functions<\/strong><\/td><td>Basic<\/td><td>&#x2705; Enhanced<\/td><td>&#x2705; Enhanced<\/td><\/tr><tr><td><strong>UTF-8 full support<\/strong><\/td><td>Partial<\/td><td>&#x2705; Full<\/td><td>&#x2705; Full<\/td><\/tr><tr><td><strong>Security patches<\/strong><\/td><td>EOL Jan 2024<\/td><td>&#x2705; Active<\/td><td>&#x2705; Active<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">As a result, MySQL 5.7 has been end-of-life since January 2024. Running WordPress on MySQL 5.7 today means an unsupported PHP version <em>and<\/em> an unsupported database. The combined risk is, consequently, serious.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Fortunately, if you are on a modern plan, your host handles the MySQL upgrade during a maintenance window. With AHosting, WordPress hosting plans use MySQL 8.0 as standard. The WordPress 7.0 database requirement is met before you even log in.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"aioseo-does-your-setup-meet-the-wordpress-7-0-hosting-requirements-65\" class=\"wp-block-heading\">Does Your Setup Meet the WordPress 7.0 Hosting Requirements?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, before you update to WordPress 7.0, run through this checklist. Every unchecked box is something to resolve before you proceed. Think of it as the minimum standard for a safe update.<\/p>\n\n\n\n<!-- WP 7.0 READINESS CHECKER \u2014 SELF-CONTAINED -->\n<style>\n.wp70chk{max-width:700px;margin:0 auto;font-family:inherit;padding:8px 0}\n.wp70chk *{box-sizing:border-box}\n.wp70chk-head{margin-bottom:20px}\n.wp70chk-title{font-size:clamp(18px,2.5vw,22px);font-weight:800;color:#1e3a5f;margin:0 0 4px}\n.wp70chk-sub{font-size:14px;color:#64748b;margin:0}\n.wp70chk-score{background:#f1f5f9;border-radius:12px;padding:20px 24px;margin-bottom:20px;display:flex;align-items:center;gap:24px;flex-wrap:wrap}\n.wp70chk-dial{flex-shrink:0}\n.wp70chk-snum{font-size:26px;font-weight:800;color:#1e293b;line-height:1;margin-bottom:4px}\n.wp70chk-slabel{font-size:13px;color:#475569}\n.wp70chk-verdict{font-size:16px;font-weight:700;margin:0 0 3px}\n.wp70chk-vsub{font-size:13px;color:#475569;margin:0}\n.wp70chk-grid{display:grid;grid-template-columns:repeat(auto-fit,minmax(200px,1fr));gap:12px;margin-bottom:20px}\n.wp70chk-card{background:#fff;border:1.5px solid #e2e8f0;border-radius:10px;padding:14px 16px;transition:border-color .2s}\n.wp70chk-card.pass{border-color:#86efac}\n.wp70chk-card.fail{border-color:#fca5a5}\n.wp70chk-card.warn{border-color:#fcd34d}\n.wp70chk-clabel{font-size:11px;font-weight:700;color:#64748b;text-transform:uppercase;letter-spacing:.06em;margin-bottom:8px}\n.wp70chk-card select{width:100%;font-size:13px;background:#f8fafc;border:1px solid #e2e8f0;border-radius:6px;padding:7px 10px;color:#1e293b;cursor:pointer}\n.wp70chk-badge{display:inline-flex;align-items:center;gap:4px;font-size:11px;font-weight:700;padding:3px 8px;border-radius:20px;margin-top:8px;letter-spacing:.03em}\n.wp70chk-badge.pass{background:#dcfce7;color:#166534}\n.wp70chk-badge.fail{background:#fee2e2;color:#991b1b}\n.wp70chk-badge.warn{background:#fef9c3;color:#854d0e}\n.wp70chk-fix{font-size:12px;color:#64748b;margin-top:6px;line-height:1.5}\n.wp70chk-cta{background:#eff6ff;border:1.5px solid #bfdbfe;border-radius:10px;padding:16px 20px;display:flex;align-items:flex-start;gap:14px;flex-wrap:wrap}\n.wp70chk-cta-icon{font-size:22px;flex-shrink:0;margin-top:1px}\n.wp70chk-cta-text{font-size:13px;color:#374151;line-height:1.6;flex:1}\n.wp70chk-cta-text strong{color:#1e293b}\n.wp70chk-cta-link{display:inline-block;margin-top:8px;background:#2563eb;color:#fff;font-size:12px;font-weight:700;padding:7px 16px;border-radius:20px;text-decoration:none}\n.wp70chk-cta-link:hover{background:#1d4ed8;color:#fff}\n<\/style>\n\n<div class=\"wp70chk\">\n  <div class=\"wp70chk-head\">\n    <div class=\"wp70chk-title\">Is your hosting ready for WordPress 7.0?<\/div>\n    <div class=\"wp70chk-sub\">Choose your current server specs below to get an instant readiness score.<\/div>\n  <\/div>\n\n  <div class=\"wp70chk-score\">\n    <svg class=\"wp70chk-dial\" width=\"72\" height=\"72\" viewBox=\"0 0 72 72\">\n      <circle cx=\"36\" cy=\"36\" r=\"28\" fill=\"none\" stroke=\"#e2e8f0\" stroke-width=\"7\"><\/circle>\n      <circle cx=\"36\" cy=\"36\" r=\"28\" fill=\"none\" stroke=\"#86efac\" stroke-width=\"7\" stroke-dasharray=\"175.9\" stroke-dashoffset=\"175.9\" stroke-linecap=\"round\" transform=\"rotate(-90 36 36)\" id=\"wpc70arc\"><\/circle>\n      <text x=\"36\" y=\"41\" text-anchor=\"middle\" font-family=\"inherit\" font-size=\"16\" font-weight=\"800\" fill=\"#1e293b\" id=\"wpc70num\">0\/5<\/text>\n    <\/svg>\n    <div>\n      <div class=\"wp70chk-snum\" id=\"wpc70pct\">0%<\/div>\n      <div class=\"wp70chk-slabel\">readiness score<\/div>\n    <\/div>\n    <div style=\"flex:1;min-width:160px\">\n      <div class=\"wp70chk-verdict\" id=\"wpc70verdict\" style=\"color:#1e293b\">Pick your specs to begin<\/div>\n      <div class=\"wp70chk-vsub\" id=\"wpc70vsub\">Your result will appear here.<\/div>\n    <\/div>\n  <\/div>\n\n  <div class=\"wp70chk-grid\" id=\"wpc70grid\"><\/div>\n\n  <div class=\"wp70chk-cta\" id=\"wpc70cta\" style=\"display:none\">\n    <div class=\"wp70chk-cta-icon\" id=\"wpc70ctaicon\">\u24d8<\/div>\n    <div>\n      <div class=\"wp70chk-cta-text\" id=\"wpc70ctatext\"><\/div>\n      <a href=\"https:\/\/www.ahosting.net\/wordpress-hosting.html\" class=\"wp70chk-cta-link\" target=\"_blank\" rel=\"noopener\">\n        View AHosting WordPress Plans \u2192\n      <\/a>\n    <\/div>\n  <\/div>\n<\/div>\n\n<script>\n(function(){\nvar C=[\n  {id:'php',label:'PHP version',\n   opts:[\n     {v:'?',t:'Not sure \u2014 I need to check'},\n     {v:'f0',t:'PHP 7.4 or below'},\n     {v:'f1',t:'PHP 8.1 (EOL Dec 2025)'},\n     {v:'w',t:'PHP 8.2 (EOL Dec 2026)'},\n     {v:'p83',t:'PHP 8.3'},\n     {v:'p84',t:'PHP 8.4 \\u2014 optimal'},\n     {v:'p85',t:'PHP 8.5'}\n   ],\n   status:function(v){return v==='?'?null:v[0]==='f'?'fail':v==='w'?'warn':'pass'},\n   msg:function(v){\n     if(v==='?')return'Check: Tools \\u2192 Site Health \\u2192 Info \\u2192 Server.';\n     if(v==='f0')return'Critical: PHP 7.4 and below are unsupported for 4+ years. Upgrade to PHP 8.4 immediately.';\n     if(v==='f1')return'PHP 8.1 is end-of-life \\u2014 no security patches since Dec 31, 2025. Upgrade to 8.3 or 8.4.';\n     if(v==='w')return'PHP 8.2 loses all support Dec 2026. Upgrade to 8.4 now to skip another forced migration.';\n     if(v==='p83')return'Good choice. Security support through Dec 2027.';\n     if(v==='p84')return'Optimal. Security support through Dec 2028.';\n     return'Newest. Maximum future-proofing.';\n   }\n  },\n  {id:'mysql',label:'Database version',\n   opts:[\n     {v:'?',t:'Not sure \\u2014 I need to check'},\n     {v:'f',t:'MySQL 5.7 (EOL Jan 2024)'},\n     {v:'p80',t:'MySQL 8.0'},\n     {v:'p84',t:'MySQL 8.4'},\n     {v:'pm10',t:'MariaDB 10.6'},\n     {v:'pm11',t:'MariaDB 10.11 or 11.x'}\n   ],\n   status:function(v){return v==='?'?null:v==='f'?'fail':'pass'},\n   msg:function(v){\n     if(v==='?')return'Check: Tools \\u2192 Site Health \\u2192 Info \\u2192 Server.';\n     if(v==='f')return'The new DataViews admin interface breaks on MySQL 5.7. Contact your host about upgrading.';\n     return'Meets the WordPress 7.0 database requirement.';\n   }\n  },\n  {id:'mem',label:'PHP memory limit',\n   opts:[\n     {v:'?',t:'Not sure'},\n     {v:'f',t:'64MB or 128MB (WordPress default)'},\n     {v:'w',t:'256MB'},\n     {v:'p',t:'512MB'},\n     {v:'pp',t:'1GB or more'}\n   ],\n   status:function(v){return v==='?'?null:v==='f'?'fail':v==='w'?'warn':'pass'},\n   msg:function(v){\n     if(v==='?')return'Check phpinfo() or ask your host.';\n     if(v==='f')return'Too low for AI features. The Abilities API and WP AI Client need at least 256MB minimum.';\n     if(v==='w')return'Meets the minimum but AI features may fail under load. 512MB is the recommended floor.';\n     return'Sufficient for all WordPress 7.0 AI features.';\n   }\n  },\n  {id:'ip',label:'IP address type',\n   opts:[\n     {v:'?',t:'Not sure'},\n     {v:'w',t:'Shared IP'},\n     {v:'p',t:'Dedicated IP'}\n   ],\n   status:function(v){return v==='?'?null:v==='w'?'warn':'pass'},\n   msg:function(v){\n     if(v==='?')return'Check your hosting dashboard or ask your host.';\n     if(v==='w')return'AI API calls may be rate-limited due to neighbour activity on the shared IP. A dedicated IP isolates your calls.';\n     return'Your AI API calls have an isolated, stable identity. AHosting includes this free on every plan.';\n   }\n  },\n  {id:'ssl',label:'HTTPS \/ SSL',\n   opts:[\n     {v:'?',t:'Not sure'},\n     {v:'f',t:'HTTP only \\u2014 no SSL certificate'},\n     {v:'p',t:'HTTPS active'}\n   ],\n   status:function(v){return v==='?'?null:v==='f'?'fail':'pass'},\n   msg:function(v){\n     if(v==='?')return'Look for the padlock icon in your browser address bar.';\n     if(v==='f')return'Required for WordPress 7.0 AI Connectors. The WP AI Client will not connect to providers over plain HTTP.';\n     return'Required for AI Connectors.';\n   }\n  }\n];\nvar state={php:'?',mysql:'?',mem:'?',ip:'?',ssl:'?'};\nfunction icon(s){return s==='pass'?'\\u2713':s==='fail'?'\\u2717':s==='warn'?'\\u26a0':'\\u2013';}\nfunction sLabel(s){return s==='pass'?'Pass':s==='fail'?'Fail \\u2014 action needed':s==='warn'?'Warning \\u2014 review':'';}\nfunction render(){\n  var g=document.getElementById('wpc70grid');\n  g.innerHTML=C.map(function(c){\n    var v=state[c.id],s=c.status(v);\n    var cls='wp70chk-card'+(s?' '+s:'');\n    var sid='wpc70s_'+c.id;\n    var lid='wpc70l_'+c.id;\n    var opts=c.opts.map(function(o){return'<option value=\"'+o.v+'\"'+(v===o.v?' selected':'')+'>'+o.t+'<\/option>';}).join('');\n    var badge=s?'<div class=\"wp70chk-badge '+s+'\">'+icon(s)+' '+sLabel(s)+'<\/div>':'';\n    var fix=v!=='?'?'<div class=\"wp70chk-fix\">'+c.msg(v)+'<\/div>':'';\n    return'<div class=\"'+cls+'\"><div class=\"wp70chk-clabel\" id=\"'+lid+'\">'+c.label+'<\/div><select id=\"'+sid+'\" aria-labelledby=\"'+lid+'\" onchange=\"wpc70ch(\\''+c.id+'\\',this.value)\">'+opts+'<\/select>'+badge+fix+'<\/div>';\n  }).join('');\n  score();\n}\nwindow.wpc70ch=function(id,v){state[id]=v;render();};\nfunction score(){\n  var scored=C.filter(function(c){return state[c.id]!=='?';});\n  var passed=scored.filter(function(c){return c.status(state[c.id])==='pass';});\n  var failed=scored.filter(function(c){return c.status(state[c.id])==='fail';});\n  var warned=scored.filter(function(c){return c.status(state[c.id])==='warn';});\n  var n=passed.length,tot=C.length,pct=Math.round((n\/tot)*100);\n  var circ=175.9,offset=(circ-(circ*(n\/tot))).toFixed(1);\n  var arcColor=failed.length>0?'#fca5a5':warned.length>0?'#fcd34d':'#4ade80';\n  document.getElementById('wpc70arc').setAttribute('stroke-dashoffset',offset);\n  document.getElementById('wpc70arc').setAttribute('stroke',arcColor);\n  document.getElementById('wpc70num').textContent=n+'\/'+tot;\n  document.getElementById('wpc70pct').textContent=pct+'%';\n  var vEl=document.getElementById('wpc70verdict'),vSub=document.getElementById('wpc70vsub');\n  var cta=document.getElementById('wpc70cta'),ctaText=document.getElementById('wpc70ctatext'),ctaIcon=document.getElementById('wpc70ctaicon');\n  if(scored.length===0){vEl.textContent='Pick your specs to begin';vEl.style.color='#1e293b';vSub.textContent='Your result will appear here.';cta.style.display='none';return;}\n  if(failed.length>0){\n    vEl.textContent='Not ready \\u2014 '+failed.length+' critical issue'+(failed.length>1?'s':'');vEl.style.color='#991b1b';\n    vSub.textContent='Resolve these before updating to WordPress 7.0.';cta.style.display='flex';ctaIcon.textContent='\\u26d4';\n    ctaText.innerHTML='<strong>Action required:<\/strong> Your host does not meet the WordPress 7.0 hosting requirements. AHosting includes PHP 8.3\/8.4, MySQL 8.0, 512MB memory, and a free dedicated IP on every WordPress plan \\u2014 all out of the box.';\n  }else if(warned.length>0){\n    vEl.textContent='Almost ready \\u2014 '+warned.length+' warning'+(warned.length>1?'s':'');vEl.style.color='#854d0e';\n    vSub.textContent='WordPress 7.0 core will work, but AI features may be limited.';cta.style.display='flex';ctaIcon.textContent='\\u26a0\\ufe0f';\n    ctaText.innerHTML='<strong>Recommended:<\/strong> Upgrade to 512MB PHP memory and add a dedicated IP before enabling the WP AI Client and Abilities API.';\n  }else if(n===tot){\n    vEl.textContent='Fully ready for WordPress 7.0';vEl.style.color='#166534';\n    vSub.textContent='All '+tot+' requirements pass. Safe to update.';cta.style.display='flex';ctaIcon.textContent='\\u2705';\n    ctaText.innerHTML='<strong>You\\'re good to go.<\/strong> Follow the staged path: full backup \\u2192 clone to staging \\u2192 update WordPress 7.0 on staging \\u2192 verify \\u2192 deploy to production.';\n  }else{\n    vEl.textContent=n+' of '+tot+' checks complete';vEl.style.color='#1e293b';\n    vSub.textContent='Choose the remaining specs to complete your score.';cta.style.display='none';\n  }\n}\nrender();\n})();\n<\/script>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Manual checklist:<\/strong><\/p>\n\n\n\n<h3 id=\"aioseo-php-version-69\" class=\"wp-block-heading\">&#x2705; PHP Version<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>PHP 8.3 or 8.4 is available on your account<\/li>\n\n\n\n<li>You know how to switch PHP versions in cPanel<\/li>\n\n\n\n<li>Your key plugins work on PHP 8.3+ (check changelogs)<\/li>\n<\/ul>\n\n\n\n<h3 id=\"aioseo-database-version-74\" class=\"wp-block-heading\">&#x2705; Database Version<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Your account uses MySQL 8.0+ or MariaDB 10.6+<\/li>\n\n\n\n<li>You have checked this via Tools \u2192 Site Health \u2192 Info \u2192 Server<\/li>\n\n\n\n<li>You have contacted your host if you are still on MySQL 5.7<\/li>\n<\/ul>\n\n\n\n<h3 id=\"aioseo-memory-and-resources-79\" class=\"wp-block-heading\">&#x2705; Memory and Resources<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>PHP memory limit is at least 256MB (512MB for AI features)<\/li>\n\n\n\n<li>You have a staging site to test the update before going live<\/li>\n\n\n\n<li>You have a full backup from the last 24 hours<\/li>\n<\/ul>\n\n\n\n<h3 id=\"aioseo-server-and-ip-setup-84\" class=\"wp-block-heading\">&#x2705; Server and IP Setup<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Your site has a dedicated IP address<\/li>\n\n\n\n<li>Your server has a valid SSL certificate<\/li>\n\n\n\n<li>mod_rewrite is enabled<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Once all four sections are checked, you are ready to update. If PHP or MySQL is the blocker, the fastest fix is a hosting upgrade. Any host that makes PHP switching a support ticket is not meeting the WordPress 7.0 hosting requirements \u2014 let alone the spirit of them.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"aioseo-ahosting-meeting-wordpress-7-0-hosting-requirements-since-2002-91\" class=\"wp-block-heading\">AHosting: Meeting WordPress 7.0 Hosting Requirements Since 2002<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">AHosting has built WordPress-optimized hosting since 2002. That is more than two decades before &#8220;managed WordPress hosting&#8221; became a product category. Interestingly, the choices we made long before WordPress 7.0 was announced line up exactly with the WordPress 7.0 hosting requirements.<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">&#8220;Every WordPress plan at AHosting meets the WordPress 7.0 hosting requirements from day one \u2014 PHP 8.3 and 8.4 support, MySQL 8.0, 512MB memory, and a free dedicated IP on every plan. When WordPress 7.0 launched today, our clients were already ready.&#8221; \u2014 Matt Chrust, Director of Business Development<\/p>\n<\/blockquote>\n\n\n\n<h3 id=\"aioseo-whats-included-with-every-ahosting-wordpress-plan-95\" class=\"wp-block-heading\">What&#8217;s Included With Every AHosting WordPress Plan<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Specifically, here is what every <a href=\"https:\/\/www.ahosting.net\/wordpress-hosting.html\">AHosting WordPress plan<\/a> includes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Free dedicated IP<\/strong> \u2014 Vital for AI API reliability and email delivery. Included on every plan, not sold as an add-on.<\/li>\n\n\n\n<li><strong>PHP 8.3 and 8.4 support<\/strong> \u2014 Switch in seconds via cPanel. No downtime, no ticket.<\/li>\n\n\n\n<li><strong>MySQL 8.0 as standard<\/strong> \u2014 Every new account uses MySQL 8.0. The database requirement is met from the start.<\/li>\n\n\n\n<li><strong>512MB PHP memory<\/strong> \u2014 Set at the account level. Enough for the Abilities API and WP AI Client to run well.<\/li>\n\n\n\n<li><strong>CloudLinux with CageFS<\/strong> \u2014 Each account is isolated. A neighbour site&#8217;s spike or breach does not touch your resources.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Additionally, for sites that need more than shared hosting \u2014 heavy AI work, WooCommerce at scale, or custom API setups \u2014 our <a href=\"https:\/\/www.ahosting.net\/vps-hosting.html\">VPS servers<\/a> and <a href=\"https:\/\/www.ahosting.net\/dedicated-server.html\">dedicated server<\/a> plans give you full control. Set your own PHP, database, and memory limits. No shared resources, no constraints.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"aioseo-how-to-upgrade-your-hosting-to-meet-wordpress-7-0-requirements-105\" class=\"wp-block-heading\">How to Upgrade Your Hosting to Meet WordPress 7.0 Requirements<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you have found a gap \u2014 PHP too old, MySQL too old, memory too low \u2014 here is the safest path to meet the WordPress 7.0 hosting requirements before you run the update:<\/p>\n\n\n\n<h3 id=\"aioseo-step-1-back-up-everything-107\" class=\"wp-block-heading\">First Step: Back Up Everything<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">First and foremost, this step is non-negotiable. Before touching PHP, MySQL, or WordPress core, take a full backup. Use UpdraftPlus, Solid Backup, or your host&#8217;s own tool. Store the backup offsite \u2014 not just on the same server.<\/p>\n\n\n\n<h3 id=\"aioseo-step-2-set-up-a-staging-site-109\" class=\"wp-block-heading\">Second Step: Set Up a Staging Site<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Next, create a staging copy of your site. Test every hosting change there before it touches live. Most good hosts offer one-click staging. If yours does not, that is worth noting.<\/p>\n\n\n\n<h3 id=\"aioseo-step-3-upgrade-php-on-staging-111\" class=\"wp-block-heading\">Third Step: Upgrade PHP on Staging<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In cPanel \u2192 MultiPHP Manager, switch to PHP 8.3 or 8.4. Then, test right away. The most common issues are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Curly brace syntax in old PHP strings (e.g., <code>$var{0}<\/code> \u2192 use <code>$var[0]<\/code>)<\/li>\n\n\n\n<li>Old plugin code using deprecated properties<\/li>\n\n\n\n<li>Composer autoloaders that need to be rebuilt for PHP 8.x<\/li>\n<\/ul>\n\n\n\n<h3 id=\"aioseo-step-4-upgrade-your-database-117\" class=\"wp-block-heading\">Fourth Step: Upgrade Your Database<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Similarly, if you are on MySQL 5.7, talk to your host. That migration from 5.7 to 8.0 needs a database dump and restore. It also involves checking for old SQL syntax. For <a href=\"https:\/\/www.ahosting.net\/reseller-hosting.html\">reseller hosting<\/a> users with many client accounts, ask your host directly: &#8220;When are you upgrading to MySQL 8.0?&#8221;<\/p>\n\n\n\n<h3 id=\"aioseo-step-5-update-wordpress-7-0-on-staging-then-live-119\" class=\"wp-block-heading\">Fifth Step: Update WordPress 7.0 on Staging, Then Live<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Finally, once PHP 8.3+ and MySQL 8.0 are confirmed on staging, update WordPress 7.0 there. Check the admin, test DataViews in Posts and Pages, and confirm your theme and plugins are intact. Only then move to live.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In most cases, the whole process takes two to four hours. Updating directly on a live site, however, risks downtime that takes far longer to fix.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"aioseo-wordpress-7-0-hosting-requirements-quick-reference-table-123\" class=\"wp-block-heading\">WordPress 7.0 Hosting Requirements: Quick Reference Table<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For reference, here is a one-page summary of every WordPress 7.0 hosting requirement, why it matters, and what happens if you skip it. Share this with your developer or host.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Requirement<\/th><th>WP 7.0 Minimum<\/th><th>Why It Matters<\/th><th>Risk if Ignored<\/th><\/tr><\/thead><tbody><tr><td>PHP 7.4<\/td><td>Hard minimum<\/td><td>Core will not load below this<\/td><td>White screen \/ fatal error<\/td><\/tr><tr><td>PHP 8.3+<\/td><td>Recommended<\/td><td>Best plugin support + security patches<\/td><td>Security gaps, warnings<\/td><\/tr><tr><td>MySQL 8.0<\/td><td>Hard minimum<\/td><td>DataViews admin needs it<\/td><td>Broken admin, query errors<\/td><\/tr><tr><td>MariaDB 10.6<\/td><td>MySQL alternative<\/td><td>Full support for all WP 7.0 features<\/td><td>Same as MySQL 5.7<\/td><\/tr><tr><td>512MB Memory<\/td><td>AI recommendation<\/td><td>Abilities API \/ WP AI Client need room<\/td><td>AI features fail silently<\/td><\/tr><tr><td>Dedicated IP<\/td><td>Best practice<\/td><td>Stable AI API identity<\/td><td>Rate limiting from neighbours<\/td><\/tr><tr><td>HTTPS\/SSL<\/td><td>Required<\/td><td>AI Connectors need it<\/td><td>AI connections refused<\/td><\/tr><tr><td>Staging site<\/td><td>Best practice<\/td><td>Test before going live<\/td><td>Avoidable production downtime<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">In other words, every row in this table is a specific WordPress 7.0 hosting requirement that affects whether the platform runs, stays secure, and uses AI features fully.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"aioseo-conclusion-get-your-hosting-right-before-you-update-128\" class=\"wp-block-heading\">Conclusion: Get Your Hosting Right Before You Update<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress 7.0 is the biggest infrastructure shift the platform has made in years. The PHP jump, the MySQL 8.0 minimum, and the 512MB memory recommendation are not soft suggestions. They mark the direction the platform is heading. Moreover, every release from here will build on this base.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">As a result, sites that check their WordPress 7.0 hosting requirements <em>before<\/em> updating will have a smooth upgrade. Those that update first and fix hosting second will face downtime, bugs, and unhappy users.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ultimately, twenty-four years of WordPress hosting has taught us one thing at AHosting: hosting quality is the multiplier on everything else. Indeed, a well-tuned site on solid hosting will always beat a perfectly optimized site on weak hosting.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Consequently, if your host does not include PHP 8.3, MySQL 8.0, and a dedicated IP as standard, WordPress 7.0 is the right moment to switch. Every AHosting WordPress plan meets the WordPress 7.0 hosting requirements from day one \u2014 free dedicated IP included, for the AI API reliability and email delivery that other hosts charge extra for.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.ahosting.net\/wordpress-hosting.html\">Explore AHosting WordPress Hosting Plans \u2192<\/a><\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 id=\"aioseo-frequently-asked-questions-about-wordpress-7-0-hosting-requirements-130\" class=\"wp-block-heading\">Frequently Asked Questions About WordPress 7.0 Hosting Requirements<\/h2>\n\n\n\n<!-- FAQ ACCORDION v4 \u2014 SELF-CONTAINED -->\n<style>\n.ahfaq{max-width:700px;margin:0 auto;font-family:inherit}\n.ahfaq *{box-sizing:border-box;margin:0;padding:0}\n.ahfaq-head{text-align:center;margin-bottom:28px}\n.ahfaq-title{font-size:clamp(20px,3vw,26px);font-weight:800;color:#1e3a5f;margin-bottom:6px}\n.ahfaq-sub{font-size:14px;color:#64748b}\n.ahfaq-list{display:flex;flex-direction:column;gap:10px}\n.ahfaq-item{background:#eef6ff;border:1.5px solid #bfdbfe;border-radius:10px;overflow:hidden;transition:border-color .25s,box-shadow .25s}\n.ahfaq-item:hover{border-color:#93c5fd;box-shadow:0 2px 12px rgba(37,99,235,0.1)}\n.ahfaq-item.open{background:#fff;border-color:#3b82f6;box-shadow:0 4px 16px rgba(37,99,235,0.12)}\n.ahfaq-q{display:flex;align-items:center;justify-content:space-between;gap:12px;padding:15px 18px;cursor:pointer;user-select:none}\n.ahfaq-q-text{font-size:14px;font-weight:700;color:#1e40af;line-height:1.35;flex:1}\n.ahfaq-item.open .ahfaq-q-text{color:#1d4ed8}\n.ahfaq-arr{width:24px;height:24px;border-radius:50%;background:#dbeafe;border:1px solid #93c5fd;display:flex;align-items:center;justify-content:center;flex-shrink:0;transition:all .25s;color:#2563eb;font-size:11px;font-weight:700}\n.ahfaq-item.open .ahfaq-arr{background:#3b82f6;border-color:#3b82f6;color:#fff;transform:rotate(180deg)}\n.ahfaq-a{display:none;padding:0 18px 16px;font-size:13.5px;color:#374151;line-height:1.7}\n.ahfaq-item.open .ahfaq-a{display:block}\n.ahfaq-a a{color:#2563eb;text-decoration:underline}\n.ahfaq-count{font-size:11px;color:#94a3b8;text-align:center;margin-top:16px;letter-spacing:.03em}\n<\/style>\n\n<div class=\"ahfaq\">\n  <div class=\"ahfaq-head\">\n    <div class=\"ahfaq-title\">Frequently Asked Questions<\/div>\n    <div class=\"ahfaq-sub\">Everything you need to know about WordPress 7.0 hosting requirements<\/div>\n  <\/div>\n  <div class=\"ahfaq-list\" id=\"ahfaqList\"><\/div>\n  <div class=\"ahfaq-count\" id=\"ahfaqCount\">0 of 10 answered<\/div>\n<\/div>\n\n<script>\n(function(){\nvar QA=[\n  {q:\"What are the WordPress 7.0 hosting requirements?\",a:\"In short, the WordPress 7.0 hosting requirements are: PHP 7.4 minimum (PHP 8.3 recommended, PHP 8.4 optimal), MySQL 8.0 or MariaDB 10.6 as the minimum database, at least 256MB of PHP memory (512MB for AI features), and HTTPS for AI Connectors. Sites on PHP 8.1 or MySQL 5.7 risk broken functionality after upgrading.\"},\n  {q:\"Do the WordPress 7.0 hosting requirements include a PHP upgrade?\",a:\"For most sites, a PHP upgrade is required. The WordPress 7.0 hosting requirements set PHP 7.4 as the hard minimum. However, PHP 8.3 is the recommended version and PHP 8.4 is optimal. PHP 8.1 reached end-of-life on December 31, 2025, and no longer receives security patches. Consequently, sites on PHP 8.1 should upgrade to 8.3 or 8.4 before updating WordPress.\"},\n  {q:\"Do the WordPress 7.0 hosting requirements include MySQL 8.0?\",a:\"Indeed, MySQL 8.0 or MariaDB 10.6 is a hard minimum in the WordPress 7.0 hosting requirements. The new DataViews admin interface uses query patterns that MySQL 5.7 does not support. As a result, sites on MySQL 5.7 may see a broken admin panel or query errors after updating to WordPress 7.0.\"},\n  {q:\"How much PHP memory do the WordPress 7.0 hosting requirements specify for AI features?\",a:\"Specifically, for AI features, the WordPress 7.0 hosting requirements recommend 512MB of PHP memory. The general minimum is 256MB. The new Abilities API and WP AI Client need this headroom to run well. Plans capped at 256MB or less may consequently see AI features fail silently or throw fatal errors.\"},\n  {q:\"What is the WP AI Client introduced in WordPress 7.0?\",a:\"Notably, the WP AI Client is a standardized connection layer built into WordPress 7.0 core. It lets you configure an AI provider once in Settings &rarr; Connectors. After that, all compatible plugins share those credentials automatically &mdash; replacing the old approach where each AI plugin managed its own separate API connection to providers like OpenAI, Google Gemini, or Anthropic Claude.\"},\n  {q:\"Does my hosting IP address affect WordPress 7.0 AI features?\",a:\"In practice, a stable outbound IP is an underappreciated WordPress 7.0 hosting requirement. The WP AI Client makes API calls from your server to AI providers. On a shared IP, those calls can be rate-limited or flagged due to activity from other sites sharing the same IP. Therefore, a dedicated IP gives your AI calls an isolated, trusted identity &mdash; which is why AHosting includes a free dedicated IP with every WordPress hosting plan.\"},\n  {q:\"Can shared hosting meet the WordPress 7.0 hosting requirements?\",a:\"Yes, shared hosting can meet the WordPress 7.0 hosting requirements if the host supports PHP 8.3 or higher, MySQL 8.0 or MariaDB 10.6, and at least 256MB of PHP memory. However, the most common blockers are hosts still defaulting to PHP 8.1 and running MySQL 5.7. Check your versions in WordPress Tools &rarr; Site Health &rarr; Info &rarr; Server before updating.\"},\n  {q:\"What PHP version best satisfies the WordPress 7.0 hosting requirements in 2026?\",a:\"Overall, PHP 8.4 is the optimal choice for the WordPress 7.0 hosting requirements in 2026. It has security support through December 2028, the best performance benchmarks (roughly 21% faster for WooCommerce vs PHP 7.4), and broad plugin compatibility. PHP 8.3 is a solid alternative with support through December 2027. Avoid PHP 8.2 &mdash; it loses all support in December 2026.\"},\n  {q:\"What is the Abilities API in WordPress 7.0?\",a:\"Specifically, the Abilities API is a secure framework built into WordPress 7.0 core. It standardizes how plugins request and run AI-powered actions. Instead of building their own AI integrations, plugins request capabilities &mdash; content writing, image alt text, tone adjustment, and translation &mdash; through a consistent, gated interface. This is one of the main reasons the WordPress 7.0 hosting requirements now include memory and IP guidance for AI use.\"},\n  {q:\"Should I test WordPress 7.0 hosting requirements on staging before updating production?\",a:\"Above all, testing on staging before going live is strongly recommended. The safest path to verify the WordPress 7.0 hosting requirements is: (1) full backup, (2) clone to staging, (3) upgrade PHP to 8.3 or 8.4 and test, (4) confirm MySQL 8.0 and test again, (5) update WordPress 7.0 on staging and verify, (6) repeat on production only after staging passes. Never test PHP upgrades or WordPress core updates directly on a live site.\"}\n];\nfunction countAnswered(){var c=document.querySelectorAll('.ahfaq-item.open').length;document.getElementById('ahfaqCount').textContent=c+' of '+QA.length+' answered';}\ndocument.getElementById('ahfaqList').innerHTML=QA.map(function(item,i){return'<div class=\"ahfaq-item\" id=\"ahfaq-'+i+'\"><div class=\"ahfaq-q\" onclick=\"ahfaqToggle('+i+')\"><span class=\"ahfaq-q-text\">'+item.q+'<\/span><span class=\"ahfaq-arr\">&#9660;<\/span><\/div><div class=\"ahfaq-a\">'+item.a+'<\/div><\/div>';}).join('');\nwindow.ahfaqToggle=function(i){document.getElementById('ahfaq-'+i).classList.toggle('open');countAnswered();};\ncountAnswered();\n})();\n<\/script>\n","protected":false},"excerpt":{"rendered":"<p>TL;DR WordPress 7.0 hosting requirements include PHP 7.4 minimum (PHP 8.3 recommended), MySQL 8.0 or MariaDB 10.6, and at least 512MB of memory for the new AI features. If your host has not upgraded, you risk a broken dashboard the moment you hit &#8220;update.&#8221; WordPress 7.0 is officially here. After months of work, two delays, [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":533,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[8],"tags":[27],"class_list":["post-530","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress","tag-wordpress"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/posts\/530","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/comments?post=530"}],"version-history":[{"count":21,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/posts\/530\/revisions"}],"predecessor-version":[{"id":588,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/posts\/530\/revisions\/588"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/media\/533"}],"wp:attachment":[{"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/media?parent=530"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/categories?post=530"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/tags?post=530"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}