Elementor Editor Not Loading

Quick fix: open the browser console before reloading the editor, record the first red error and failed Network request, then try Elementor Safe Mode. If Safe Mode works, test the theme and other plugins on staging. If it does not, check memory, WordPress URLs, Core/Pro versions and server logs.

Do not clear every cache and disable everything at once. Change one layer, reproduce the problem, and keep evidence of what changed.

Identify the exact symptom

Elementor loading problems commonly appear as:

• an endless Elementor logo spinner;
• a blank or gray editor panel;
• widgets that never populate;
• a 400, 403, 500 or 503 request in Network;
• the editor opening but preview remaining blank;
• “Preview could not be loaded.”

Test a second page. If one document fails while a new draft opens, the problem may be corrupted content or one widget. If every page fails, investigate the environment.

Check the browser console and Network panel

Open Developer Tools, enable Preserve log, reload the editor and inspect the first error—not the cascade after it.

Useful clues include:

• a JavaScript file blocked by a security or optimization tool;
• 403 from a firewall;
• 500 from PHP;
• mixed HTTP/HTTPS requests;
• an iframe blocked by X-Frame-Options or Content Security Policy;
• REST or admin-AJAX requests returning HTML instead of JSON.

Save the request URL, response status and response body. This is more actionable than “Elementor is stuck.”

Try Elementor Safe Mode

Safe Mode loads the editor in an isolated context to help distinguish Elementor from the active theme and other plugins.

If the editor works in Safe Mode:

1. create a current backup;
2. clone the issue to staging;
3. switch temporarily to a compatible default or Hello theme;
4. disable non-Elementor plugins;
5. re-enable components one at a time until the error returns.

Do not perform a live conflict test on checkout, membership or high-traffic sites.

Match Elementor Core and Pro versions

Elementor Pro depends on Elementor Core. Update them using the vendor’s supported order and confirm the Pro license can retrieve authentic packages. A failed partial update can leave mismatched JavaScript and PHP APIs.

If the issue began immediately after an update, use staging to test the previous trusted release or restore the pre-update backup. Do not download old packages from unofficial websites.

Check WordPress memory and PHP errors

Review Tools → Site Health, Elementor → System Info and the server’s PHP log. A fatal error or memory exhaustion should name the component and file.

Enable private WordPress logging only long enough to reproduce the failure. Our WordPress debug mode guide shows how to log errors without displaying them to visitors.

If the log explicitly reports Allowed memory size exhausted, follow How to Increase WordPress Memory Limit. Raising memory without evidence can hide a plugin that consumes resources without bound.

Verify WordPress URLs and HTTPS

Under Settings → General, WordPress Address and Site Address should describe the intended HTTPS site unless the installation deliberately separates them. Reverse proxies and CDNs must tell WordPress that the original request was HTTPS.

Mixed schemes, an old staging hostname or inconsistent www settings can break the editor iframe and API requests. Correct the source configuration instead of adding several redirects around it.

Test cache and optimization features

Temporarily bypass, rather than permanently delete:

• browser cache;
• WordPress page/asset optimization;
• hosting cache;
• CDN cache;
• JavaScript delay or combination;
• Cloudflare Rocket Loader.

Elementor’s current troubleshooting guidance notes that optimization features and Cloudflare script handling can interfere with the editor. Its Safe Mode follow-up guide also covers the alternate editor loader method and frame restrictions.

Exclude authenticated editor, REST and admin requests from full-page caching. Never publicly cache wp-admin responses.

Regenerate Elementor files only when relevant

When the editor opens but styling or preview assets are stale, use Elementor’s tools to regenerate CSS/data, then clear the cache that serves those files. This is not a fix for a PHP fatal error or blocked iframe.

If the public page is stale while the editor works, use WordPress Changes Not Showing.

Inspect security headers and firewalls

A WAF may block large editor requests or JSON payloads. Check firewall events before whitelisting anything. Narrow any exception to the required authenticated endpoint and method.

For a gray iframe, inspect X-Frame-Options and CSP frame-ancestors. Do not remove clickjacking protection site-wide without understanding which origin needs to frame the preview.

Recovery checklist

After the editor loads again:

1. disable public debug output;
2. remove temporary firewall bypasses;
3. re-enable optimization one feature at a time;
4. test editing, preview and the logged-out page;
5. document the failing component and versions;
6. repeat the final configuration on staging before production.

If neither Safe Mode nor environment checks identify the issue, export Elementor System Info and the relevant log lines for vendor or host support. Do not send passwords, license keys or complete unredacted configuration files.