Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
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
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

Elementor Not Working Properly: Causes and How to Fix It

Elementor Not Working Properly: Causes and How to Fix It

Short answer

Elementor usually breaks because of a plugin or theme conflict, a low PHP memory limit, outdated versions, stale cache, or a firewall blocking its requests. Turn on Elementor Safe Mode first to test for conflicts, then raise memory, update everything and regenerate CSS.

Key takeaways

  • Safe Mode is the quickest way to spot a plugin or theme conflict.
  • Aim for a PHP memory limit of 256M or more.
  • Keep Elementor and Elementor Pro on matching current versions.
  • Regenerate Elementor CSS and clear every cache layer when edits don't show.
  • Firewalls and security plugins can block saving.

Why is Elementor not working properly?

Elementor usually stops working properly because of a plugin or theme conflict, low PHP memory, an outdated version, stale cache, or a server setting that blocks its editor requests.

The symptoms vary a lot. Some people see a grey loading screen. Others find that widgets won't drag, styles don't show on the live page, or changes refuse to save.

The good news is that the causes repeat. Work through the checks below in order and most sites are back to normal within an hour.

If your problem is specifically the editor spinning forever, our guide to fixing the Elementor editor not loading goes deeper on that one symptom.

What are the common signs Elementor is broken?

The common signs are an editor stuck on loading, widgets panel not appearing, changes not saving, styles missing on the front end, or a critical error after an update.

Match your symptom to the likely cause before you start changing things:

SymptomMost likely causeFirst thing to try
Editor stuck on loading screenPlugin conflict or low memoryTurn on Elementor Safe Mode
Widgets panel empty or greyPHP memory limit or JavaScript errorRaise memory limit, check browser console
Changes look fine in editor, not on live pageCache or CSS print methodRegenerate CSS and clear cache
Can't save, update button failsFirewall, mod_security or REST API blockCheck security plugin and host firewall
White screen or critical errorFatal PHP error after updateCheck debug log, roll back version
Pro widgets missingElementor Pro inactive or version mismatchUpdate both plugins together

Writing down the exact symptom also helps if you later contact Elementor or your host.

How do you use Elementor Safe Mode to find a conflict?

Turn on Safe Mode from Elementor, then Tools, then the General tab, and Elementor loads its editor with other plugins and your theme switched off for that session only.

Safe Mode is the fastest conflict test because it doesn't affect visitors. Elementor explains it in its debugging with Safe Mode guide.

Here is how to read the result:

  1. Enable Safe Mode and open a page in Elementor.
  2. If the editor now works, a plugin or your theme is the cause.
  3. Turn Safe Mode off again.
  4. Deactivate plugins one by one on a staging copy until the problem returns.
  5. If Safe Mode doesn't help, look at the server, memory or Elementor itself.

Elementor has a separate page for when Safe Mode doesn't solve the problem. Those cases usually point to hosting limits.

Our general guide on how to fix a plugin conflict shows a clean way to test plugins without breaking the live site.

Is your PHP memory limit too low for Elementor?

Low memory is a very common cause, and Elementor's System Info screen shows your current limit, which should ideally be 256M or more for a builder-heavy site.

Open Elementor, then System Info, and look at the WordPress memory limit line. If it shows a low figure, raise it.

You can usually set it in wp-config.php with this line, placed above the line that says to stop editing:

define( 'WP_MEMORY_LIMIT', '256M' );

Some hosts cap memory at the server level. If the number doesn't change after you edit wp-config.php, ask your host to raise it. Our guide on how to increase the PHP memory limit covers every method.

If you see an Allowed memory size exhausted message, that confirms the problem. See our memory exhausted fix for the detailed steps.

Are your Elementor, WordPress and PHP versions compatible?

Elementor works best when Elementor, Elementor Pro, WordPress and PHP are all on current supported versions, and a mismatch between free and Pro versions often breaks widgets.

Check these four things:

  • Elementor and Elementor Pro. Update them together. An old Pro with a new free version, or the other way round, is a frequent cause of missing widgets.
  • WordPress core. Run the latest release if your other plugins support it.
  • PHP version. Check it under Tools, then Site Health, then Info. Compare it with the requirements Elementor lists in its help centre.
  • Your theme. An old theme can load scripts that clash with the editor.

If the trouble started right after an update, Elementor lets you roll back to an earlier version from Elementor, then Tools, then Version Control. Use it as a short-term fix while you find the real cause.

When Pro specifically breaks after updating, read our guide to Elementor Pro not working after an update.

Could caching be showing an old version of your page?

Yes, if edits appear in the editor but not on the live page, a cache layer is usually serving the old version, so regenerate Elementor's CSS and then clear every cache.

There can be several caches between you and your visitors:

  1. Elementor's own generated CSS files
  2. A cache plugin such as WP Rocket or LiteSpeed Cache
  3. Server cache from your host
  4. A CDN such as Cloudflare
  5. Your browser

Start with Elementor. Go to Elementor, then Tools, and click Regenerate Files and Data, or the similarly named button in your version. Then clear the other layers.

Our step-by-step guide on clearing cache in WordPress with Elementor covers each layer in order.

Also check any minify or combine settings in your cache plugin. Combining JavaScript files can break the editor, so exclude Elementor files or turn that option off as a test.

Can a security plugin or firewall block Elementor?

Yes, firewalls such as mod_security, Cloudflare rules or security plugins sometimes block the requests Elementor sends when you save, which causes save errors or a stuck editor.

Signs that a firewall is involved:

  • Saving fails with a 403 or 500 error
  • The issue only happens on certain pages with lots of code or HTML widgets
  • It works on staging but not on the live server

Look in your security plugin's log for blocked requests around the time you tried to save. If you use Cloudflare, check its firewall events too.

Ask your host whether mod_security blocked anything. They can usually whitelist the rule without turning off protection for the whole site.

Elementor relies on the WordPress REST API and admin-ajax requests. If Site Health shows a REST API error, fix that first using our guide to the REST API error in Site Health.

How do you check for JavaScript errors?

Open your browser's developer tools, switch to the Console tab, reload the Elementor editor and look for red error messages that name a plugin or file.

The console often points straight at the culprit. An error that mentions a file path inside another plugin's folder tells you which plugin to test first.

To open the console:

  • Chrome or Edge: press F12 or Ctrl+Shift+J, then click Console
  • Firefox: press F12, then click Console
  • Safari: turn on the Develop menu in settings, then open the console

Mozilla's guide to the browser console explains what each message type means.

Take a screenshot of the errors. Elementor support will ask for them, along with your System Info report.

What should you do if you see a critical error?

A critical error means PHP hit a fatal error, so turn on WordPress debug logging, read the last error in the log, and disable the plugin it names.

Turn on logging by adding these lines to wp-config.php:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Then reload the broken page and open wp-content/debug.log. The WordPress debugging documentation explains each constant.

If you can't reach the dashboard, rename the plugin's folder in wp-content/plugins using your host's file manager or FTP. That deactivates it.

Our dedicated guide on fixing the Elementor critical error covers this case in more detail.

Does your theme work well with Elementor?

Most modern themes work with Elementor, but heavy themes with their own builders or old code can clash, so test with a lightweight theme such as Hello Elementor or a default WordPress theme.

Switch themes on a staging site, not the live one. If Elementor works with the test theme, the original theme is the problem.

Then you can:

  • Update the theme to its latest version
  • Ask the theme author about Elementor support
  • Move to a theme built with Elementor in mind

Our staging site setup guide shows how to make a safe copy for this kind of testing.

When should you contact Elementor or your host?

Contact your host when the problem points to memory, PHP or firewall limits, and contact Elementor support when Safe Mode, updates and cache clearing have not fixed the editor.

Before you reach out, gather:

  • Your Elementor System Info report
  • Screenshots of console errors
  • The last lines of debug.log
  • What you already tried

Elementor's common troubleshooting steps page lists the checks support will expect you to have done. Free users can also post in the Elementor support forum on WordPress.org.

Clear details get you a faster answer. Most Elementor problems come down to one of the causes above, so a short, specific report usually pinpoints it quickly.

Frequently asked questions

Why does Elementor keep loading forever?

An endless loading screen is usually caused by a plugin conflict, a low PHP memory limit or a JavaScript error. Try Safe Mode first, then check System Info for your memory limit and look at the browser console for red errors.

Why are my Elementor changes not showing on the live site?

A cache is most likely serving the old page. Regenerate Elementor's CSS files from its Tools screen, then clear your cache plugin, server cache, CDN and browser. Also check minify settings in your cache plugin.

Can I roll back Elementor to an older version?

Yes. Elementor includes a version rollback option under its Tools screen. Use it as a temporary fix if a new release breaks your site, and take a backup first. Update again once the issue is fixed.

Does Elementor need a lot of PHP memory?

Elementor uses more memory than a simple theme, especially with many widgets and add-ons. A limit of at least 256M is a sensible target for most builder sites. Your host may need to raise it if wp-config changes don't stick.

Will Safe Mode change my live website?

No. Safe Mode only affects your own editing session. Visitors still see the normal site with all plugins and your theme active, which makes it a safe first test.

Sources

  1. Debugging with Safe Mode Elementor
  2. Common troubleshooting steps Elementor
  3. Safe mode doesn't resolve issues Elementor
  4. Debugging in WordPress WordPress Developer Resources
  5. Browser Console Firefox Source Docs

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

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.