Black FridayCyber Monday 2026
14Days
15Hrs
04Mins
06Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
Elementor

Elementor Stuck on Loading Screen? 9 Fixes to Try

Elementor stuck on the loading screen? Work through nine fixes in order, from your browser and caches to plugins, the server and editor-specific causes.

wpallsolution 14 min read

Elementor stuck on loading screen means the editor opens to a blank grey panel and never shows your page. Elementor’s own documentation describes this as a grey screen that can have several different causes. That is why the fastest route is not to try everything at once. Work through the layers one at a time: your browser, the caches between you and your site, plugins and theme, the server, and finally the editor itself.

Quick answer: test one layer at a time

Open the editor in a private window with extensions off. If it still hangs, read the browser console, purge every cache layer and stop your CDN from rewriting scripts, then switch on Elementor Safe Mode. After that, check the server (PHP version, memory limit and the editor loader method). Only then look at editor-specific causes such as mismatched Elementor and Elementor Pro versions or a corrupted widget. Change one thing, test, and write down the result before you change the next.

This guide helps site owners, freelancers and developers who can log in to WordPress as an administrator. Where a step needs server access, it says so and tells you what to ask your host.

How this guide was prepared: the steps follow Elementor’s help articles and the WordPress developer documentation listed under Sources, which were read on October 19, 2026. We have not reproduced this problem on a live Elementor site for this guide, so treat every step as research-based. Menu names and screens change between Elementor, WordPress and hosting versions, and no single fix works in every setup.

Before you change anything

  • Take a backup you can restore. Files and database both. If you are unsure yours is reliable, read Is your WordPress backup really safe? first.
  • Use a staging copy for anything risky, such as switching themes, deactivating many plugins or editing wp-config.php. On a live store or a busy site, do not experiment during opening hours.
  • Change one variable at a time. If you change three things and the editor loads, you will not know which one mattered.
  • Never share passwords, API keys, customer data or full logs publicly. Redact anything private before you ask anyone for help.

Elementor stuck on loading screen: the decision tree

Use these five questions in order. Each one rules out a whole layer, so you never test the server before you have ruled out your own browser.

Flowchart of five questions to find why the Elementor editor is stuck on a grey loading screen: browser, console, cache or CDN, Safe Mode and theme, then server settings, ending with editor-specific causes
Five questions, asked in order, point to the right fix.
  1. Does the editor load in a private window with extensions off? If yes, the cause is your browser (Fix 1).
  2. What does the browser console show? It tells you which script or request fails (Fix 2).
  3. Does it load after you purge caches and stop the CDN from rewriting scripts? If yes, the cause is a cache, optimisation or CDN setting (Fixes 3 and 4).
  4. Does it load in Safe Mode, or with a default theme? If yes, a plugin, the theme or custom code is involved (Fixes 5 and 6).
  5. If not, check the server limits and settings (Fixes 7 and 8), then the editor-specific causes (Fix 9).

Symptoms and likely causes

What you seeLikely layerStart with
Works in a private window, hangs in your normal browserBrowser cache or an extensionFix 1
Red console errors that name a file in a plugin or theme folderPlugin, theme or custom code conflictFixes 5 and 6
Front end is fine, but the editor hangs after you enabled minify, “delay JavaScript” or Rocket LoaderCache, optimisation or CDNFixes 3 and 4
Errors such as err_content_decoding_failed or err_empty_responseServer configurationFix 8
Hangs on every page after a host change or PHP changePHP version or memory limitFix 7
Started right after updating only Elementor or only Elementor ProVersion mismatchFix 9
Only one page or template hangsCorrupted widget or contentFix 9

9 fixes to try, from safest to most advanced

Fix 1: Rule out your browser (cache and extensions)

Browser add-ons such as ad blockers can block the scripts the editor needs, and cached files can be out of date. This costs you nothing and is completely safe.

  1. Open a private or incognito window (Ctrl+Shift+N in Chrome, Cmd+Shift+N on a Mac).
  2. Log in to WordPress inside that window and open the page with Elementor.
  3. If it loads, go back to your normal browser, clear its cache, then disable extensions one at a time until you find the one that interferes.
  4. Try a second browser (Chrome, Firefox, Safari or Opera) to confirm.

If it still hangs: the browser is not the cause. Go to Fix 2.

Fix 2: Read the browser console and network requests

The console turns “it is stuck” into a specific clue. Right-click the grey page and choose Inspect, then open the Console tab. In Chrome the shortcut is Ctrl+Shift+J (Cmd+Option+J on a Mac); in Firefox it is Ctrl+Shift+K (Cmd+Option+K).

  • Look for messages in red. Note the file name in the message. A path under /wp-content/plugins/ or /wp-content/themes/ names the plugin or theme involved.
  • Open the Network tab and reload. A request that fails, especially with a 403 or 500 status, points at the server or a security rule rather than the browser.
  • Write down the first error, not only the last. Later errors are often side effects.

The console does not fix anything by itself, but it tells you which of the next fixes to try first.

Fix 3: Clear caches in layers and pause optimisation

Elementor’s documentation lists active caching or optimisation while editing (page cache, object cache, and JavaScript or CSS optimisation) among the causes of widget data getting out of sync. Cache can sit in four places, and each has its own purge button:

  1. Your browser (done in Fix 1).
  2. A caching plugin on your site.
  3. Your hosting provider’s cache, usually in the hosting control panel.
  4. A CDN in front of the site.

Purge page cache and object cache. Then, only for testing, turn off the options that combine, minify, delay or defer JavaScript and CSS. The names differ by plugin and host. Test the editor again. If it loads, switch the options back on one at a time and test after each, so you learn which setting breaks the editor, then exclude the editor from that feature if your plugin allows it.

Fix 4: Stop the CDN from rewriting scripts (Cloudflare Rocket Loader)

Elementor’s help centre explains that Cloudflare’s Rocket Loader changes scripts to load asynchronously, which can break the editor. Two ways to deal with it:

  • Create Cloudflare rules that bypass Rocket Loader for Elementor pages (yoursite.com/*elementor*) and for templates (yoursite.com/?elementor_library=*).
  • Or turn Rocket Loader off in the Cloudflare dashboard under Speed → Optimization while you test.

Then clear the CDN cache and reload the editor. Other CDNs may have similar script-optimisation features. Elementor’s documentation only covers Cloudflare here, so check your CDN’s own settings.

Fix 5: Turn on Safe Mode, then isolate the plugin

Safe Mode loads a clean version of the editor without the WordPress front end and without third-party plugins, which makes it the quickest way to separate “Elementor” from “something else on the site”.

  1. In WP Admin, go to Elementor → Editor → Tools, which is where Elementor’s current documentation places it. If you do not see it, your version may label the menu differently.
  2. Set Safe Mode to Enable and save the changes.
  3. Open the page. Only administrators can enable Safe Mode (Super Admins on a multisite network).

If the editor loads in Safe Mode, something third-party is involved. On a staging copy, or at a quiet time on a live site:

  1. Go to Plugins → Installed Plugins, select every plugin except Elementor and Elementor Pro, and choose Deactivate from Bulk actions.
  2. Test the editor. If it loads, reactivate the plugins one by one and test after each.
  3. The plugin that brings the problem back is the conflict. Report it to the plugin developer and keep the exact versions you used.

Our guide How to find the plugin that broke your site walks through the same one-at-a-time method in more detail. Note that deactivating a plugin does not delete your pages, but anything it provides (shortcodes, custom widgets) will not display while it is off.

Fix 6: Rule out the theme, a preloader and custom code

If Safe Mode does not help, or the editor loads in Safe Mode but not otherwise, check what the theme adds:

  • Test with Hello Elementor. Activate the Hello Elementor theme under Appearance → Themes (on staging, because it changes how the front end looks). If the editor now loads, your theme code is involved.
  • Disable a theme preloader. Elementor’s documentation says a page preloader built into a theme can interfere with the editor. Turn it off in the theme options or the Customizer.
  • Disable custom code. If you use Elementor’s Custom Code feature, set the snippets to Draft, update, then reload the editor. Also remove custom JavaScript from HTML widgets temporarily.
  • Check the page template. A custom theme should use the standard WordPress loop. If it does not, ask the theme developer.

Fix 7: Check the PHP version and memory limit

Elementor’s system requirements page (read on October 19, 2026) lists WordPress 6.8 or newer, PHP 7.4 or newer with PHP 8.3 or newer recommended, and MySQL 5.6 or MariaDB 10.5 or newer. For memory it lists a WordPress memory limit of 256 MB for Elementor and Elementor Pro alone, 512 MB recommended, and 768 MB for best performance. It adds that sites running other heavy plugins, such as WooCommerce, may need 512 MB to avoid loading issues.

  1. Find your current values under Elementor → Editor → System, or Tools → Site Health → Info.
  2. If PHP or memory is below the requirement, ask your host to change it, or change it in the hosting control panel if you can.
  3. If your host allows it, you can raise WordPress’s own memory limit in wp-config.php, as described in the WordPress documentation. Back up the file first and add the line above the comment that says to stop editing:
    define( 'WP_MEMORY_LIMIT', '512M' );

    To undo it, delete that line. Many hosts cap memory at the server level, so the value may not change anything. In that case, ask them.

Check the PHP error log too. WordPress can write errors to a log without showing them to visitors. The WordPress debugging documentation gives this example for wp-config.php:

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

Reload the editor once, then read wp-content/debug.log. A message such as “Allowed memory size exhausted” points to memory, and a fatal error names the file at fault. Redact private details before sharing any of it, and turn debugging off again when you are done (set WP_DEBUG back to false or remove the lines).

  • Switch Editor Loader Method. Go to Elementor → Settings → Advanced and set Switch Editor Loader Method to Enable. According to Elementor’s documentation, this helps with an editor stuck on the loading screen, with 404 errors, and with errors such as err_content_decoding_failed and err_empty_response, particularly on servers with few resources that struggle to read long JSON. It says you can leave it enabled.
  • Check X-Frame-Options. If the console mentions a frame or cross-origin restriction, Elementor’s help says a header such as X-Frame-Options: DENY can stop the editor rendering, and asks you to have your host set it to SAMEORIGIN. This is a server or security-plugin setting, so ask your host or check your security plugin rather than guessing.
  • Re-save permalinks. Go to Settings → Permalinks and click Save Changes without changing anything. This regenerates the rewrite rules.
  • Look for redirects and permission limits. Make sure the page you are editing is not redirected by a redirection plugin or a server rule, and that your user role can edit Elementor pages if a membership plugin limits access.

If the Network tab showed blocked requests (for example a 403), ask your host to look at their firewall or security logs for that request. Do not ask them to disable security protection for the whole site.

Fix 9: Editor-specific causes (versions, a corrupted widget, V4 elements)

  • Mismatched versions. Elementor and Elementor Pro should both be up to date. Different versions can cause editor problems. Back up and update on staging first. Our guide to updating WordPress plugins safely covers the routine.
  • V4 elements. Elementor’s documentation says V4 elements are in beta and can lead to loading screen errors. If you use them, deactivate V4 and see whether the page loads.
  • A corrupted widget. If only one page or template hangs, a widget’s stored settings may be out of step with your site, for example after a plugin update or because the dynamic content it points to was removed. Elementor’s example is a Loop Grid widget: disable the Loop feature in Elementor → Element Manager, open the page and save it without Loop widgets, re-enable the feature, then rebuild the widget from scratch. Add custom code back gradually.
  • Still stuck? Download your System Info (Elementor → Editor → System) and send it to Elementor’s support team or your host, together with the first console error you wrote down.

Version and hosting differences

  • Menu paths can differ by version. Elementor’s current documentation places Safe Mode under Elementor → Editor → Tools and System Info under Elementor → Editor → System. If your menu looks different, search the Elementor sidebar for those names.
  • Some hosts add their own page cache, firewall or PHP limits. A fix that works on one host may need a support ticket on another.
  • Elementor Hosting, shared hosting, VPS and managed WordPress hosting expose different settings. When a step needs a server change, your host is the right person to ask.

How to verify the fix

  • The editor loads fully: the widget panel appears, you can select a widget and the Update button saves.
  • It loads in your normal browser, in a private window and on another device or network.
  • The live page still looks the same after you save.
  • Anything you switched off for testing (optimisation options, plugins, a theme) is back on, one item at a time, with a test after each.
  • Your notes record what the cause was and what fixed it.

How to prevent it from happening again

  • Update Elementor and Elementor Pro together, on staging first, with a restorable backup.
  • Keep PHP and the memory limit at or above Elementor’s requirements.
  • Exclude the editor from JavaScript delay, combine and Rocket Loader features where your tools allow it.
  • Keep the number of third-party add-ons small. Our guide to keeping Elementor sites fast explains why.
  • Record every settings change with a date, so the next problem has a trail.

Frequently asked questions

Is a grey editor screen the same as the white screen of death?

Not necessarily. A grey editor panel means the editor did not finish loading. A completely blank page more often points to a PHP error, so check the error log (Fix 7).

Will deactivating plugins delete my pages?

No, your pages stay. But features a plugin provides will not display while it is off, so test on staging or at a quiet time.

Can I raise the memory limit myself?

Sometimes. It depends on your host, and many hosts set a server-level cap. If your change has no effect, ask them.

Does a CDN always cause this?

No. A CDN is one of several layers. That is why Fix 3 and Fix 4 come after the browser and console checks, not before.

What to do next

Work through the fixes in order and stop at the first one that works. If Elementor is still stuck on loading screen after all nine, send your System Info and the first console error to Elementor support or your host. If you would rather have a person look at your setup, wpallsolution offers independent plugin support for conflicts, errors and update problems, and our Elementor development page explains how we build and tidy Elementor sites. We cannot promise a fix without seeing your site.

Sources and official documentation

Last reviewed: October 19, 2026. Elementor is a trademark of its owner. wpallsolution is not affiliated with or endorsed by Elementor.

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us