WordPress PHP Version Update — Practical Guide for SA Businesses

A wordpress php version update is the process of switching the PHP runtime your hosting server uses to execute your site — one of the highest-value, lowest-cost maintenance steps a South African business owner can take. PHP runs directly on your hosting server, not inside WordPress itself, so it sits outside the WordPress dashboard entirely. Understanding what it actually costs to build and maintain a South African website starts with knowing that an unpatched PHP runtime can quietly compromise every rand invested in that site.

Most hosts let you change PHP in under five minutes. Most SA businesses have not done it in years.

This guide gives you the exact click path for the two most common hosting control panels used by South African WordPress sites — xneelo and Afrihost — alongside the version decision table and a pre-and-post checklist so you can do this yourself without handing it to a developer. It sits alongside ongoing website maintenance as one of the highest-return recurring tasks for any SA business running WordPress.

Why Your Site Is at Risk Right Now

PHP versions follow a strict end-of-life (EOL) schedule. Once a version reaches EOL, it receives zero security patches — not reduced support, not community backports, nothing. Any vulnerability discovered after that date stays unfixed on your server indefinitely.

As of September 2026, the EOL calendar looks like this:

EOL dates sourced from endoflife.date/php, which references the php.net supported-versions schedule directly.

If your site is on PHP 7.4, it has been running without a single security patch for 46 months. That is not a theoretical risk — known vulnerabilities in EOL versions are actively catalogued and exploited. A significant portion of live WordPress sites globally still run EOL PHP, which is precisely why attackers target PHP-version-specific exploits at scale.

Performance matters too. A Kinsta benchmark on a bare WordPress 6.8.0 install with no plugins (OPcache enabled) recorded 139 req/s on PHP 7.4 versus 148 req/s on PHP 8.4. A real site running 15+ plugins will see different absolute figures, but the benchmark illustrates the principle: a PHP version change delivers measurable throughput gains with zero changes to your WordPress installation. On a South African site where page speed directly affects conversions, that headroom is real — and it costs nothing beyond the five-minute panel change.

Choosing the Right Release for 2026

PHP 8.3 is the version to target for most South African WordPress sites in 2026: it is the version WordPress.org officially recommends, it is actively receiving security patches, and it has the widest plugin compatibility of any currently supported release. The make.wordpress.org core team confirmed in May 2026 that WordPress 6.8 and later fully support PHP 8.4, and WordPress 6.9/7.0 fully support PHP 8.5 — giving sites on modern WordPress a clear upgrade path.

For most South African businesses running WordPress 6.x on a standard shared host, PHP 8.3 is the safe, recommended target. It is the version WordPress.org explicitly recommends, it is the version xneelo migrated existing PHP 8.2 sites to automatically in August 2026, and it has the broadest plugin compatibility across the SA WordPress ecosystem.

Move to PHP 8.4 if you are on WordPress 6.8 or later and your theme and plugins have been verified compatible — the plugin author's changelog or their "tested up to" data in the WordPress plugin directory is your quickest reference. If one plugin has not been updated since 2023, test on staging before going live.

How to Check What Your Server Is Running

The fastest way to confirm your PHP version is the WordPress Site Health tool, which reads the actual runtime — not your hosting panel's default setting, which may differ from what a specific domain is actually using.

1. Log into your WordPress admin dashboard.
2. Navigate to Tools → Site Health.
3. Click the Info tab at the top.
4. Expand the Server section.
5. Your PHP version appears in the first row.

If the Site Health tool is unavailable (a rare case on locked-down managed hosts), log into your hosting control panel and check under the PHP or server settings for that domain directly. The hosting panel number and Site Health must agree — if they differ, the Site Health figure is what your WordPress installation actually uses.

How to Do a WordPress PHP Version Update Safely

A wordpress php version update follows the same sequence regardless of host: back up, check plugin compatibility, test on staging, then flip the switch in your hosting control panel. The steps that differ are the ones inside each host's panel. Knowing how to update PHP version in WordPress is a five-minute task once you know which panel to navigate — the longer time is always the pre-flight checks.

Before You Change Anything — The Pre-Update Checklist

Updating PHP on xneelo (South Africa)

xneelo uses its own control panel at create.xneelo.com, not the generic cPanel interface most global guides show. The path is:

1. Log in to create.xneelo.com.
2. Click Product in the left sidebar.
3. Click on your domain name.
4. Under Hosting Tools, select PHP Config.
5. Go to the Configuration tab and click Edit next to PHP Config.
6. Select your target PHP version from the dropdown.
7. Click Save — the change applies automatically within seconds.

Note: xneelo automatically upgraded sites still on PHP 8.2 to PHP 8.3 in August 2026. If your site is on xneelo and you have not touched the PHP settings, it is likely already on 8.3 — confirm in Site Health.

Updating PHP on Afrihost (South Africa)

Afrihost shared hosting uses CentOS Web Panel (CWP), accessed through ClientZone:

1. Log into ClientZone (my.afrihost.com).
2. Select the Hosting tab, then find your domain under Shared Hosting.
3. Click Website Manager → Log into Website Manager.
4. In the CWP dashboard, go to CWP Settings → PHP Selector.
5. Choose your domain from the dropdown.
6. Select the target PHP version and click Update Version.

Updating PHP via Generic cPanel (Other SA Hosts)

If your SA host provides standard cPanel (common on Hostify, HostAfrica, and others):

1. Log into cPanel for your account.
2. Go to Software → MultiPHP Manager.
3. Tick the checkbox next to your domain.
4. Choose your PHP version from the PHP Version dropdown.
5. Click Apply.

Managed WordPress hosts (cloud-based services rather than traditional SA shared hosting) typically handle PHP via a dedicated dashboard section or support request — check your host's knowledge base for the exact path.

What to Test When the Change Goes Live

A successful PHP change leaves your site behaving identically to before — WordPress PHP compatibility failures surface immediately as fatal errors or white screens, not as slow regressions over days. That means a two-minute check of your key pages immediately after the change tells you everything you need to know. Here is the post-update walk-through:

• Homepage and navigation — load the homepage, click through your main menu items. Any PHP fatal error produces a white screen or an error message immediately.
• Contact and enquiry forms — submit a test entry and confirm it arrives. Forms using older PHP mail functions are among the most common breakage points after a major PHP version change.
• E-commerce checkout (if applicable) — add an item to cart and step through to payment. Payment gateway integrations like PayFast and Peach Payments have their own PHP dependencies.
• Admin dashboard — log in to wp-admin and check that all plugins show as active with no error notices at the top of the screen.
• Site Health again — return to Tools → Site Health and check the status tab. A green "Good" result confirms the server environment is healthy.

If something breaks, roll back immediately by returning to your hosting panel and selecting your previous PHP version. The rollback takes the same number of clicks as the original change. Once you are on the previous version, re-run your PHP compatibility scanner to identify the specific plugin or theme causing the issue, then update it or contact the developer.

Why South African Businesses Choose Growth Pulse Media

Growth Pulse Media was built by someone who has operated large-scale South African e-commerce infrastructure — not just advised on it. Our web design and maintenance work runs on the same stack SA businesses actually use: WordPress on local and regional hosting, PayFast and Peach Payments integrations, POPIA-compliant contact and lead-capture forms. When we recommend a PHP target, it is based on what we have seen break and what holds stable across the SA hosting ecosystem.

We keep a limited client load so every engagement gets senior-level attention. If your WordPress site is due for an environment review — PHP version, plugin audit, performance check — our web design and maintenance service covers the full technical stack, not just the visible layer. All work is executed in-house; nothing is outsourced offshore.

Related reading: if you are evaluating what your site should cost to run beyond the PHP question, what a website costs to run per year in South Africa breaks down hosting, maintenance, and ongoing costs with Rand figures.

Who This Guide Is Not Right For

Frequently Asked Questions

How do I know which PHP version my WordPress site is using?

Go to Tools → Site Health → Info → Server in your WordPress dashboard. The PHP version row shows the version your site is actually running. This is the most reliable method because it reads the actual runtime for your specific domain — a per-domain PHP setting overrides the account default, so the hosting panel's account-level display can differ from what WordPress actually uses.

Can a PHP version update break my WordPress site?

It can, if a plugin or theme uses PHP functions that were deprecated or removed in the target version. PHP 7.4-era code sometimes uses functions removed in PHP 8.x. The fix is to run a PHP compatibility scan before updating, test on a staging copy first, and update any flagged plugins. If something does break on the live site, rolling back takes under two minutes through your hosting control panel.

Is PHP 8.3 or PHP 8.4 better for WordPress in 2026?

PHP 8.3 is the official WordPress.org recommendation and the safer default for most sites because it has the widest plugin compatibility. PHP 8.4 is fully supported from WordPress 6.8 onwards and delivers marginally better throughput in benchmarks — move to it once you have confirmed your plugins are compatible on staging. The performance difference between the two is small; the security gap between either and PHP 7.4 or 8.1 is significant.

What is the minimum PHP version WordPress supports?

The technical minimum is PHP 7.4, but WordPress.org explicitly warns that versions below 8.3 have reached their end of life and "may expose your site to security vulnerabilities." Treat 7.4 as a hard floor you should not stay on, not a safe operating point. PHP 7.4 has been without security patches since November 2022 — over 46 months of unpatched exposure as of September 2026.

How long does updating PHP take on a WordPress site in South Africa?

The actual switch in your hosting panel takes under two minutes on xneelo, Afrihost, or cPanel. The total time including pre-update backup, compatibility scan, and post-update testing is typically 30–60 minutes for a careful first run. Subsequent updates (for example, moving from 8.3 to 8.4 once you have already cleaned up your plugin list) take less time because the compatibility groundwork is already done.

Dirk van Greuning Founder, Growth Pulse Media

Founder of Growth Pulse Media and a specialist in South African search dominance. Dirk translates his experience in scaling South African businesses into high-velocity digital strategies for B2B and retail leaders. He writes about SEO, lead generation, and paid media from an operator's perspective — prioritising pipeline value over impressions.

Connect on LinkedIn