Elementor PHP Version: What to Check Before You Update

Key takeaways

• Elementor's minimum is PHP 7.4, but it recommends 8.3 or newer. Elementor's requirements page says it will work with 7.4 and that it highly recommends PHP 8.3+. Checked 22 October 2026.
• The minimum is not the safe choice. Because PHP 8.1 and older no longer get fixes from the PHP project, a site running Elementor's bare minimum has no official patch for the two flaws announced on 21 October 2026.
• Update in a set order. Back up, update WordPress, Elementor, Elementor Pro and every add-on, then test on a copy, then change PHP at your host.
• Add-ons and custom code are the usual trouble. The page builder itself is rarely the weak point. Third-party add-ons, old widgets and custom snippets are.
• A broken editor is easy to spot. A white screen, a stuck loading panel or a server error after the change means something on the site does not like the new PHP.
• You can go back. If you hold a backup and your host can restore the earlier PHP, a failed attempt is a matter of minutes rather than days.

For the bigger picture before you start, read our main guide to the PHP vulnerability of October 2026. It explains the flaws and who is exposed.

What Elementor says about PHP

Two official pages were read for this post on 22 October 2026. The first is Elementor's system requirements page. The second is the Elementor listing on WordPress.org.

The WordPress.org listing showed Elementor version 4.3.5, last changed on 13 October 2026. That number will move, so check the listing for the current one. Two things follow from this. First, you can run Elementor on PHP 7.4 and it will load. That says nothing about whether it is safe. Second, Elementor's own advice and WordPress.org's advice point the same way. WordPress.org also suggests PHP 8.3 or newer, which we went through in our guide to the WordPress minimum PHP version.

On security, php.net's advisory dated 21 October 2026 names the patched versions: 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Anything on 8.1 or older has no official fix. What that means for each branch is in our post on PHP end of life dates.

What Elementor does not tell you

The requirements page covers Elementor and Elementor Pro. It cannot cover the other code on your site. A normal Elementor site also holds a theme, third-party add-on packs, often WooCommerce, custom CSS and code snippets. Each has its own PHP needs. A check of Elementor alone can say yes while an old add-on says no, so the checks below start with the full list of what is installed.

Before you change PHP: the checks, in order

1. Write down your current numbers. From the dashboard go to Tools, then Site Health, then the Info tab. Note the PHP version in the Server block, the WordPress version, and the version of Elementor and Elementor Pro. The click path is laid out in our guide to checking and updating your PHP version on WordPress.
2. Take a full backup. Files and database, stored somewhere off the server. Do not rely on a backup that lives only on the same host.
3. List every plugin and add-on. Note which ones add widgets to Elementor. Look at when each was last updated in the Plugins screen. Any plugin left without updates for ages is the prime suspect.
4. Update in this order. WordPress first, then Elementor, then Elementor Pro, then add-ons, then the theme. If Elementor Pro asks for a licence check, do it before you start, not halfway through.
5. Look at the page list. Pick the pages that matter most: home, main service or product pages, contact page, checkout. You will test these later.
6. Open your custom CSS and snippets. CSS rarely breaks on a PHP change. PHP snippets can. Anything in a snippets plugin, in the theme's functions file, or in a child theme needs a look.
7. Test on a staging copy. Many hosts give you a one click staging site. Switch the copy to the new PHP, not the live site.
8. Change PHP on the live site only after the copy passes. Pick a quiet hour, tell your team, and keep the backup close.

If your site is a shop, read our notes for WooCommerce shop owners as well.

What a broken editor looks like

A PHP change can fail in a few ways. These are the ones to watch for in an Elementor site:

• A white screen on the front of the site or in the admin.
• A server error message such as a 500 error, or a notice that the site has had a critical error.
• The Elementor editor stuck on its loading screen, or opening with a blank panel.
• Widgets that vanish from a page, or an add-on's widgets that show as missing in the panel.
• Forms that no longer send, or a popup that no longer opens.
• A long list of warnings at the top of pages. Warnings are a sign of a plugin that will need an update soon, even if the page still works.

Elementor's help centre has articles on these themes, including one on a fatal error after updating, one on Safe Mode, and two on rolling back to an earlier version. We did not read their steps for this post, so open them yourself before you rely on a method.

The general approach for a white screen or a server error is the same on any WordPress site. Deactivate the plugins, reactivate them singly, and check the error log to spot the one that breaks. The test step of our guide to checking and updating your PHP version walks through it. In the Elementor case, add-on plugins are usually the first to switch off.

How to go back if it fails

Rolling back is two steps, and you need both.

1. Put the old PHP version back at your host. Ask them or use their panel. WordPress.org says the host has to do this, not WordPress.
2. Restore the backup if the site data changed. If the failure came from a plugin update and not from PHP alone, the backup puts the files and database back as they were.

If only one add-on fails, you may not need to roll back at all. You can switch it off, or replace it with a maintained plugin, and keep the new PHP. Staying on an old PHP is a short fix only. Given the 21 October 2026 flaws, aim to be back on a fixed release soon. Our questions to ask your web host will get you a date and the confirmation in writing.

When this advice does not apply, and what is unclear

• You do not run PHP yourself. A site on a hosted builder gives you no PHP setting to change at all. Our post on Webflow security explains that case.
• You manage your own server. The steps for changing PHP differ. Our guide to managed hosting versus shared hosting shows who normally does the patching.
• Elementor's wording may change. We checked its requirements and the WordPress.org listing on 22 October 2026. Both can change with a new release, so check them again when you update.
• We have not read every add-on's page. There are too many. Check each one's own listing or ask its author which PHP versions it supports.
• The page builder may not be the issue. WordPress.org says the PHP flaws are not specific to WordPress, so changing builders is not a fix. If you are weighing options, our comparison of Elementor, Divi and a custom theme looks at the trade offs.

How we help at Amariq

An Elementor site has more moving parts than a plain theme, because the builder, its add-ons and your custom CSS all have to agree with the new PHP. Since the advisory came out we have taken WordPress sites to a newer PHP, normally beginning with a full backup and a review of the add-ons. Prefer to hand it off? The WordPress PHP update gig on Fiverr is priced by the size of your site. Our WordPress development page shows how we build and maintain these sites. Our Fiverr and Upwork client reviews are open for anyone to read, and the walkthroughs on our YouTube channel show how we work, so you can size us up before handing anything over.

Frequently asked questions

Which PHP version is required by Elementor?

On its requirements page Elementor gives 7.4 as the minimum and strongly urges PHP 8.3 or newer. WordPress.org's listing for the plugin also shows 7.4 as the minimum. Checked 22 October 2026.

What PHP version is best for Elementor?

Elementor recommends 8.3 or newer. Because of the October 2026 security flaws, your release should also be the patched one for its branch or newer, for example 8.3.36 or 8.4.27. Our PHP update guide lists all four.

Will updating PHP break Elementor?

Elementor itself is not the usual cause. Older add-ons, custom snippets and themes are more likely to fail on a newer PHP. Update everything first, test on a staging copy, and keep a backup.

My Elementor editor will not load after a PHP change. What now?

Deactivate your add-ons, then activate each again in turn and open the editor after every one. Still no culprit? Ask your host to switch back to the previous PHP version and restore your backup. Then get help before trying again.

Can I stay on PHP 7.4 because Elementor still works on it?

It will run, but it is no longer fixed by the PHP project, and Elementor does not recommend it. Given the flaws of 21 October 2026, move to a supported, fixed version as soon as you can test it safely.

Is it possible to hire this out?

Yes. A short fixed scope job is a common way to handle it. Look for a clear backup step, a test list, a written report and an administrator invite instead of a shared password.