How to Change the PHP Version in DirectAdmin (and Why It Matters)

PHP is the language WordPress, Laravel and most other web applications run on, and the version your site uses affects speed, security and whether your plugins work at all. Every ProWebHosting plan includes a PHP version selector, so you are never stuck on whatever the server default happens to be. This guide shows where the setting lives in DirectAdmin, how to switch safely and what to do when a plugin breaks.

Why the PHP version matters

Each PHP release gets about two years of active support, during which bugs are fixed, followed by a further period of security fixes only. After that the branch is unsupported: a newly discovered vulnerability is never patched. Running a site on an unsupported PHP version is the software equivalent of leaving a window open.

Newer versions are also faster. PHP 8 introduced a just-in-time compiler and a long list of internal optimisations, and each 8.x release has continued to trim execution time. On shared hosting, where your account has a fixed CPU share, a faster PHP means the same visitors use less of that share and pages return sooner. For the current dates, check the official PHP supported versions page. As of September 2026 the position is:

Where the PHP version is set in DirectAdmin

DirectAdmin sets the PHP version per domain, not per account. That is useful: an old client site that needs PHP 8.1 for one more month can sit next to a new site on 8.4 in the same hosting account. The setting lives on the Domain Setup page.

Subdomains can run a different version from their parent domain. Under Account Manager, open Subdomain Management, find the subdomain, and use the Document Root Override settings, which include their own PHP Version Selector. This is handy for a staging copy at staging.yourdomain.com that you want to test on a newer PHP before moving the live site.

Depending on how the server is configured, you may also see a PHP Settings page in your account. It lists the version and lets you adjust common values such as memory_limit, upload_max_filesize, post_max_size, max_execution_time and max_file_uploads without editing php.ini by hand. On servers that use the CloudLinux selector, the equivalent tool appears under Advanced Features as Select PHP Version and additionally lets you toggle individual PHP extensions. If you do not see one of these pages, the Domain Setup selector is the one to use, and support can adjust limits for you.

Test before you switch the live site

Switching PHP takes ten seconds, and switching back takes the same ten seconds, so the risk is short-lived. Still, a store or a busy site deserves a few checks beforehand so the switch happens on your terms rather than at 2 AM after a customer complains.

1. Take a backup. Use Create/Restore Backups under System Info & Files, or at least export the database, so you can roll back if a plugin corrupts something during an update.
2. Read Site Health. WordPress flags an outdated PHP version and, after the switch, reports any fatal errors it caught.
3. Check each plugin and theme. On its wordpress.org page, look at Requires PHP and Tested up to, and the date of the last update. A plugin untouched for three years is the likely one to break.
4. Update everything first. Plugin and theme authors usually ship PHP compatibility fixes in ordinary updates, so being current removes most problems before they start.
5. If you can, test on a staging subdomain running the new version before touching the live domain.
6. Switch during a quiet hour, then click through the home page, a post, the contact form, the checkout if you have one, and the WordPress admin.

Common WordPress plugin problems after a PHP upgrade

Most sites move from PHP 8.2 or 8.3 to 8.4 without any visible change. When something does go wrong, it is nearly always an old plugin or theme using a function that PHP removed or tightened. The symptoms are recognisable once you have seen them.

If the admin area itself is unreachable, you can disable the offending plugin without logging in. Open File Manager, go to public_html/wp-content/plugins, and rename the plugin folder. WordPress deactivates it on the next load. Alternatively switch the PHP version back in Domain Setup, fix the plugin, and switch forward again.

Really old code, such as a custom theme from 2015 that still uses the mysql_ functions removed in PHP 7, will not run on any supported version. The honest options are a rewrite of that piece or a new theme. Keeping the whole site on an unsupported PHP version to preserve one old function is not a good trade.

Which version should you choose?

For a WordPress site with current plugins, choose 8.4. It is in active support, it is fast, and the WordPress core and the major plugins have supported it for some time. Move to 8.5 once the plugins you depend on state support for it. Only stay on 8.2 or 8.3 if a specific plugin forces you to, and note the end-of-support date in your calendar.

For a custom PHP application, follow your framework. Laravel, for example, publishes a minimum PHP version for each release. Match it, and use the per-domain selector so different projects on the same account can sit on different versions. Our DirectAdmin hosting page lists what is included on every plan, and if you need a specific extension enabled, ask support rather than working around it.

Frequently asked questions