You open a page in Elementor and the loading bar stops. Or it loads and the preview panel says it could not be displayed. Either way the page itself is fine on the front end, which is what makes this feel like a bug rather than a configuration problem.
It is almost always a configuration problem. Five causes cover nearly every case we see, and testing them in this order matters, because the cheapest tests are also the most likely to be the answer.
Step one: rule out the browser (thirty seconds)
Open the same edit URL in a private window with extensions disabled. Ad blockers, password managers and privacy extensions block Elementor editor requests more often than people expect.
If it loads in private browsing, you have your answer and it is not your site.
Step two: read the console before touching anything
Press F12, open the Console tab, reload the editor. A red error naming a specific file is the single most valuable thing you will get, and it usually names the offending plugin directly in the file path.
People skip this step and then spend an hour disabling plugins one by one. The console frequently just tells you.
Step three: check memory and PHP limits
Go to Elementor then System Info. Compare against the published Elementor server requirements.
- PHP memory limit below 128M will cause the editor to die silently mid load. 256M is realistic for a Pro site.
- max_execution_time below 60 will time out on template heavy pages.
- PHP version. Very old versions fail in strange ways rather than obvious ones.
A blank white editor with no console error is memory exhaustion until proven otherwise. Ask your host to raise it, or add the limit to wp-config.php if you have access.
Step four: switch the loading method
Elementor has a setting under Elementor, Settings, Advanced called Switch Editor Loader Method. It changes how the editor requests the preview, and it exists specifically because some server configurations and security modules block the default approach.
Toggle it, clear caches, retest. This is a one click fix that resolves a meaningful share of cases and costs nothing to try.
Step five: conflicts, found by halving
Now it is worth suspecting plugins, and only now. Work on a staging copy if you have one.
Switch to a default theme such as Twenty Twenty Five and retest. If that fixes it, the theme is the cause and the culprit is usually its own optimisation or script handling.
If not, deactivate everything except Elementor and Elementor Pro. Confirm the editor loads. Then reactivate half your plugins at a time rather than one at a time. Twenty plugins resolves in five rounds this way instead of twenty.
The repeat offenders in our experience are optimisation plugins combining or deferring JavaScript, security plugins blocking admin AJAX or the REST API, and firewall rules at the host level rather than in a plugin at all.
The one nobody checks: the REST API
Elementor depends on the WordPress REST API. Some security plugins and some hosts disable or restrict it, which breaks the editor while leaving the rest of the dashboard working normally.
Visit yoursite.com/wp-json/ in a browser. You should see a wall of JSON. If you get a 401, 403 or an error page, that is the cause, and the fix is in your security plugin settings rather than in Elementor.
If none of it works
Enable WordPress debug logging and reproduce the failure. The log will usually name a fatal error and a file, which turns guesswork into a specific fix.
For the broader diagnostic sequence across all Elementor issue types, see our Elementor problems guide. If the front end is also down rather than just the editor, that is a different problem and the critical error fix is the right starting point.
Frequently asked questions
Why is my Elementor editor stuck on loading?
The most common causes are insufficient PHP memory, a JavaScript conflict from an optimisation or security plugin, a blocked REST API, or a browser extension interfering. Test in a private window first, then check the browser console for a named error, then check Elementor System Info for memory limits.
How much PHP memory does Elementor need?
128M is the practical minimum and 256M is realistic for an Elementor Pro site, particularly one running WooCommerce or a template heavy build. Below 128M the editor tends to fail silently with a blank screen rather than producing a useful error.
What is the Elementor editor loader method setting?
It is found under Elementor, Settings, Advanced, and it changes how the editor requests its preview frame. Some server configurations and security modules block the default method. Toggling it, then clearing caches, resolves a meaningful proportion of loading failures with no other changes.
Can a security plugin break Elementor?
Yes, frequently. Security plugins that restrict the REST API, block admin AJAX requests, or apply aggressive firewall rules will break the editor while leaving the rest of the WordPress dashboard working normally. Check /wp-json/ in a browser to confirm the REST API responds.
How do I find which plugin breaks the Elementor editor?
Deactivate all plugins except Elementor and Elementor Pro on a staging copy and confirm the editor loads. Then reactivate half at a time and retest, halving the failing group each round. Twenty plugins narrows down in about five rounds rather than twenty separate tests.