Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Troubleshooting

How to Fix Elementor Not Loading in WordPress

Short answer

Elementor not loading is usually caused by low PHP memory, a plugin or theme conflict, or broken permalinks. Raise the WordPress memory limit to at least 256 MB, turn on Safe Mode to test for conflicts, and re-save your permalink settings. If the page still will not load, turn off Cloudflare Rocket Loader and ask your host to check the server error log.

Key takeaways

  • Elementor needs WordPress 6.8 or greater, PHP 7.4 or greater, and at least 256 MB of memory as of November 2026.
  • Safe Mode loads the editor without theme styles or third-party plugin scripts, so if the page loads there, a plugin or theme is the cause.
  • Re-saving permalinks and rebuilding .htaccess fixes broken rewrite rules that stop Elementor from reaching the page.
  • Cloudflare Rocket Loader defers JavaScript and can leave the Elementor editor stuck on a grey loading page.
  • If the page fails in Safe Mode with a clean theme, the cause is on the server, so contact your host.

What does “Elementor not loading” mean?

“Elementor not loading” means a page built with Elementor shows a blank page, a grey screen, or a spinner that never ends instead of the page content.

Elementor's own help page lists the same signs: a blank page called the white screen of death, a grey page with endless loading, and a click on “Edit with Elementor” that sends you back to the live page instead of opening the builder. See the Can't Edit with Elementor guide from Elementor.

The front of the site can fail too. A visitor may see nothing where your Elementor page should be, while the rest of WordPress still works.

Why is Elementor not loading on my site?

The most likely causes are low PHP memory, a plugin or theme conflict, broken permalinks, outdated Elementor or WordPress versions, and Cloudflare Rocket Loader.

Work through the causes in this order, because the first two fix most cases. Check the simplest cause first, and change one thing at a time so you know which fix worked.

CauseWhat you seeFirst check
PHP memory too lowBlank page or endless spinnerElementor > System Info
Plugin or theme conflictGrey loading screenSafe Mode
Broken permalinksEditor cannot reach the pageSettings > Permalinks
Outdated versionsEditor opens, then stopsDashboard > Updates
Cloudflare Rocket LoaderGrey page that never loadsCloudflare Speed settings
Server blocksBlank page, console errorsBrowser console

Elementor's preview guide lists the same causes: low PHP memory, plugin or theme conflicts, corrupted permalinks, server firewalls, and Cloudflare Rocket Loader. See How to Fix the “Preview Could Not Be Loaded” Error from Elementor.

How do I check if my server meets Elementor's requirements?

Check Elementor > System Info and compare each value with Elementor's published requirements before you change anything else.

Elementor needs WordPress 6.8 or greater, PHP 7.4 or greater, and MySQL 5.6 or greater or MariaDB 10.5 or greater, as of November 2026. See the System Requirements to Use Elementor page from Elementor.

WordPress.org sets a higher bar: it recommends PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.4 or greater, and HTTPS support. See the WordPress Requirements page from WordPress.org.

Elementor also sets a memory bar: a WP Memory limit of 256 MB, 512 MB recommended, and 768 MB for best performance, as of November 2026. Elementor notes that sites with other plugins that have their own minimums, such as WooCommerce, may need 512 MB to avoid loading issues.

PHP itself caps script memory with the memory_limit setting, which defaults to 128M, and setting it to -1 removes the limit, according to the PHP manual.

If your PHP version is below 7.4, ask your host to upgrade it. Our guide on how to update the PHP version in WordPress walks through the check.

How do I raise the PHP memory limit for Elementor?

Raise the WordPress memory limit to at least 256 MB, and to 512 MB on a site with many plugins, by adding one line to wp-config.php.

  1. Back up your site first, so you can undo the change.
  2. Open wp-config.php in the site root folder, usually public_html, with your host file manager or FTP.
  3. Add define( 'WP_MEMORY_LIMIT', '512M' ); directly above the line that reads /* That's all, stop editing! Happy publishing. */.
  4. Save the file, then open Elementor > System Info to confirm the new value.

WordPress tries to raise PHP memory to 40 MB on a single site and 64 MB on a multisite by default, according to the Editing wp-config.php page in the WordPress developer docs.

Elementor's own preview guide says Elementor needs a minimum of 256 MB of PHP memory, and 512 MB is recommended for complex sites. See How to Fix the “Preview Could Not Be Loaded” Error from Elementor.

If System Info still shows the old value after your edit, your host caps the limit. Ask the host to raise it, because no setting in wp-config.php can pass a server cap. Our guide to fixing the allowed memory size exhausted error covers the same limit in more depth.

How do I find a plugin or theme conflict with Safe Mode?

Turn on Safe Mode, and if Elementor loads, a plugin or theme is the cause.

Safe Mode loads the editor without active theme styles or third-party plugin scripts during your editing session, and live visitors see no change.

To turn it on, go to Elementor > Tools > General, set Safe Mode to Enable, and click Save Changes. See the How to Fix the “Preview Could Not Be Loaded” Error guide from Elementor.

If the page loads in Safe Mode, find the conflicting plugin with these steps:

  1. Go to Plugins > Installed Plugins and deactivate every plugin except Elementor and Elementor Pro.
  2. Open the page in Elementor to confirm it loads.
  3. Reactivate one plugin at a time, and reload the editor after each one.
  4. The last plugin you reactivated before the problem returns is the cause.

Elementor's help page gives the same method: deactivate all plugins except Elementor and Elementor Pro, then reactivate each one until the problem reappears. See the Can't Edit with Elementor guide from Elementor.

If no plugin is the cause, switch to a default theme such as Hello Elementor and test again. If the page loads with the default theme, your theme is the cause, so contact the theme developer.

Re-save your permalink settings and clear every cache layer, because stale rewrite rules and old cached files can stop Elementor from reaching the page.

Corrupted permalink structures break communication between the Elementor editor and the web server, according to Elementor's preview guide. To flush them, go to Settings > Permalinks, select Plain, click Save Changes, then select Post name again and click Save Changes.

If the .htaccess file is damaged, rebuild it: delete .htaccess from the public_html folder, then go to Settings > Permalinks and click Save Changes so WordPress makes a clean one. Elementor's preview guide gives the same two steps. See How to Fix the “Preview Could Not Be Loaded” Error from Elementor.

A bad permalink setup can also show up as a missing page, so if the page itself returns a 404, read our guide on fixing a 404 error on posts.

Clear the cache at every layer, not just in the browser:

  • Clear your browser cache and hard-refresh the page.
  • Clear your caching plugin cache, if you use one.
  • Clear your host cache from the hosting panel.
  • Purge the Cloudflare cache, if you use Cloudflare.

If edits still do not appear after the page loads, the cause is usually a cache layer you missed. Our guide on fixing changes not showing on your site covers each layer in order.

How do I fix Cloudflare Rocket Loader blocking Elementor?

Turn off Cloudflare Rocket Loader, because it defers JavaScript and can leave the Elementor editor stuck on a grey loading page.

Cloudflare's own docs say Rocket Loader defers the loading of all JavaScript until after rendering, and advise that if you see JavaScript or jQuery issues, you should disable Rocket Loader and retest. See the Rocket Loader docs from Cloudflare.

To turn it off:

  1. Log in to the Cloudflare dashboard and open Speed.
  2. Find the Rocket Loader setting and switch it to Off.
  3. Go to Caching > Configuration and click Purge Everything.

Elementor gives the same advice: Cloudflare users may need to switch off Rocket Loader, because it can take time to load the editor and sometimes leaves you stuck on the grey loading page. See the Can't Edit with Elementor guide from Elementor.

If you need Cloudflare on the site, keep it on for visitors but test the editor with Rocket Loader off first. That test tells you whether Rocket Loader was the cause. Our guide on how to set up Cloudflare for WordPress covers the settings that work with WordPress.

What should I do if Elementor still will not load after these fixes?

If the fixes above fail, check the browser console, the editor loading method, and your site URLs, then look at the server error log.

Try the editor loading method first. Go to Elementor > Settings > Advanced and switch the editor loading method to Enabled, as Elementor's help page advises for preview URL problems. See the Can't Edit with Elementor guide from Elementor.

Next, check your site URLs. Go to Settings > General and make the Site Address (URL) the same as the WordPress Address (URL), then click Save Changes. A mismatch between the back-end and front-end URLs can cause the blank page error.

Then check the browser console. Right-click the page, select Inspect > Console, and look for red error messages.

Elementor's preview guide maps the common codes: 401 means password protection is blocking admin folders, 403 means a firewall such as mod_security or bad file permissions is blocking access, and 500 means the server ran out of PHP memory or hit a script error.

Two server settings are worth checking with your host. X-Frame-Options must be set to “same origin”, and the Content-Security-Policy frame-ancestors value must be 'self', because a none value blocks the Elementor preview iframe. Elementor lists both in its System Requirements page.

Also check for a stray index.html file in the public_html root. A static index.html file overrides the main WordPress index.php file, so delete it. If the page shows a server error instead of a blank screen, our guide on fixing a 500 internal server error is the next step.

How do I know the fix worked?

The fix worked when the Elementor page loads fully in the editor and on the live site, and the same page loads after you clear the cache.

Check each of these before you call the job done:

  • The page opens in the Elementor editor with all widgets visible.
  • The live page shows the full content in a private browser window.
  • Elementor > System Info shows a memory limit of 256 MB or more.
  • The browser console shows no red errors when the page loads.
  • The page still loads after you reactivate every plugin you need.

If the page loads but feels slow, the loading problem is fixed and speed is a separate job. A guide on speeding up Elementor covers that next step.

When should I contact my host?

Contact your host when the memory limit will not rise, the server log shows a fatal error, or the page fails in Safe Mode with a clean theme.

Those three signs point at the server, not at your content. Your host can raise the PHP memory limit, fix X-Frame-Options, whitelist Elementor requests in mod_security, and read the PHP error log. Elementor's help page also advises asking your host to confirm the error from the server PHP error logs.

Send the host a short note with these facts:

  • Your PHP version and memory limit from Elementor > System Info.
  • Whether the page loads in Safe Mode.
  • The exact error from the browser console, if any.
  • The steps you already tried, in order.

Give the host the page URL that fails and the time it failed. That lets them match your report to the right lines in the server log.

What mistakes should you avoid?

The most common mistake is changing several settings at once, because then you cannot tell which change fixed the page.

Avoid these traps:

  • Editing wp-config.php without a backup first.
  • Raising only WP_MEMORY_LIMIT when the host caps the PHP memory_limit at the server level.
  • Reactivating all plugins at once after Safe Mode, which hides the conflicting one.
  • Updating Elementor but not Elementor Pro, since mismatched versions can conflict. Elementor's help page warns that a newer version with an outdated version can cause conflicts.
  • Clearing only the browser cache and forgetting the host cache and the CDN cache.
  • Trying to edit the blog archive page with Elementor. Archive pages cannot be edited like a normal page, so edit the template in Elementor > Theme Builder instead.

Frequently asked questions

Why does Elementor show a blank page when I try to edit?

A blank page usually means the server ran out of PHP memory or a plugin conflict stopped the editor scripts. Check Elementor > System Info for the memory limit, raise it to at least 256 MB, and then test the page in Safe Mode. If it loads in Safe Mode, reactivate your plugins one at a time to find the one causing the conflict.

How much memory does Elementor need?

Elementor needs a WP Memory limit of 256 MB, recommends 512 MB, and lists 768 MB for best performance as of November 2026. Sites with many plugins or WooCommerce may need 512 MB to avoid loading issues. You can set it in wp-config.php, but if your host caps the limit at the server level, ask the host to raise it.

Will Safe Mode change what visitors see on my site?

No. Safe Mode only changes your own editing session by loading the editor without active theme styles or third-party plugin scripts. Live visitors see the site exactly as before while you test. Turn Safe Mode off again once you have found the cause, and leave the conflicting plugin or theme deactivated.

Can my theme stop Elementor from loading?

Yes. A theme can load scripts or a preloader that clash with the editor. Switch to a default theme such as Hello Elementor and open the page again. If it loads, your theme is the cause, so check the theme settings for a preloader option or contact the theme developer for a fix.

Why does Elementor load on some pages but not others?

Heavier pages need more memory, so a page with many widgets can fail while a simple page loads. A single page can also have broken content, such as code pasted from another page, or a permalink that no longer matches. Test the failing page in Safe Mode and re-save your permalinks to narrow it down.

Should I edit the blog page with Elementor?

No. The blog archive page is a dynamic page managed by WordPress, so it cannot be edited like a normal static page. Trying to open it in Elementor can trigger a loading error. Edit the layout in Elementor > Theme Builder instead, by choosing the template type for the archive.

Sources

  1. System Requirements to Use Elementor Elementor
  2. Can't Edit with Elementor - What Should I Do? Elementor
  3. How to Fix the 'Preview Could Not Be Loaded' Error Elementor
  4. WordPress Requirements WordPress.org
  5. Editing wp-config.php WordPress Developer Resources
  6. Rocket Loader Cloudflare
  7. Description of core php.ini directives PHP.net

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test