Troubleshooting · Troubleshooting
How to Fix the Elementor Editor Not Loading
Short answer
To fix the Elementor editor not loading, first test Safe Mode to rule out a plugin or theme conflict. Then raise the WordPress memory limit to 512 MB and enable the Switch Editor Loader Method under Elementor, Settings, Advanced. If the editor still sticks, turn off Cloudflare Rocket Loader and clear the cache.
Key takeaways
- A stuck Elementor editor usually shows a blank or grey screen with a spinning loader, while the live site still works.
- Elementor lists 256 MB as the minimum WordPress memory limit, with 512 MB recommended and 768 MB for best performance, as of November 2026.
- Safe Mode loads the editor without your theme and third-party plugin scripts, so it can prove a conflict.
- The Switch Editor Loader Method is under Elementor, Settings, Advanced, and it changes how the editor loads its data.
- Cloudflare Rocket Loader defers JavaScript, and Cloudflare says to disable it and retest if you see JavaScript issues.
- If the editor fails in Safe Mode too, the cause is more likely memory, server settings, or a blocked preview.
What does the Elementor editor not loading mean?
The Elementor editor not loading means the editing screen opens but the canvas stays blank, grey, or stuck on a spinning loader.
The front of your site can still work while the editor fails, because the editor loads extra scripts and a live preview in an iframe. Elementor's guide to the stuck loading screen lists a blank or grey screen as the main sign of this failure.
A loading editor is not the same as a page that will not open at all. If the page itself returns an error on the live site, that is a different fault, and the fix steps here may not apply.
Why does the Elementor editor stay on the loading screen?
The editor usually sticks because the server runs out of memory, a plugin or theme script breaks it, or a security or speed layer blocks the preview.
Elementor lists a WP Memory Limit of 256 MB as the minimum for Elementor and Elementor Pro, with 512 MB recommended and 768 MB for best performance, as of November 2026 (Elementor system requirements). A site below that limit can stall when the editor loads.
Other common causes are a plugin conflict, a theme preloader, custom code, an X-Frame-Options block, or Cloudflare Rocket Loader. Elementor's stuck loading screen guide names plugin and theme conflicts, browser add-ons, custom code, preloaders, frame restrictions, and Rocket Loader as causes.
| Symptom | Likely cause | First check |
|---|---|---|
| Grey screen with a spinning loader | Low memory or a plugin conflict | Safe Mode, then memory limit |
| Blank white editor screen | Blocked preview or a script error | Browser console, then frame settings |
| Editor loads in Safe Mode only | Plugin or theme conflict | Reactivate plugins one at a time |
| Editor fails in Safe Mode too | Memory, server, or URL fault | Memory limit, loader method, site URLs |
| Editor sticks only with Cloudflare on | Rocket Loader or cache | Turn Rocket Loader off and purge the cache |
How do you check whether the problem is one page or every page?
Test one simple page, one complex page, and a new draft page, because the pattern points to the cause.
If only one page sticks, the fault is likely in that page, such as a widget, a template, or custom code on it. If every page sticks, the fault is more likely memory, a plugin, the theme, or the server.
Also check the blog archive page. Elementor's editing guide states that you cannot edit the blog archive page with Elementor, so a failure there is expected.
Use a desktop computer for this check. Elementor states that you cannot edit with Elementor on mobile phones and tablets at this time, and you can only edit pages on desktop computers (Elementor system requirements).
How do you use Safe Mode to find a plugin or theme conflict?
Safe Mode loads the editor without your active theme and third-party plugin scripts, so it can show whether one of them is the cause.
To turn it on, go to Elementor, then Tools, set Safe Mode to Enable, and save the change. You can also accept the Safe Mode prompt that Elementor shows on the failed editor screen.
If the editor loads in Safe Mode, a plugin or your theme is the cause. Elementor's editing guide gives this order: deactivate all plugins except Elementor and Elementor Pro, then reactivate each plugin one at a time until the problem returns.
The last plugin you reactivate before the fault returns is the likely cause. Update it, check its settings, or ask its developer for a fix, and keep it off until then.
If the editor still fails in Safe Mode, a plugin or theme conflict is less likely. Move on to memory, the loader method, and the site URLs, because those faults sit below the theme and plugin layer.
How do you raise the WordPress memory limit for Elementor?
Raise the WordPress memory limit to 512 MB in wp-config.php, then check the new value in Elementor System Info.
WordPress tries to raise PHP memory to 40 MB for a single site and 64 MB for multisite by default, so a site that never set a higher value can run far below what Elementor needs (WordPress wp-config.php handbook).
PHP itself lists 128M as the default for its memory_limit setting (PHP manual on php.ini directives).
Follow these steps:
- Back up the site, then open wp-config.php in the site root with your host file manager or FTP.
- Add this line above the line that reads “That's all, stop editing! Happy publishing.”:
define( 'WP_MEMORY_LIMIT', '512M' ); - Add this line on the next line for admin screens:
define( 'WP_MAX_MEMORY_LIMIT', '512M' ); - Save the file, then open Elementor, System Info, and check the memory value under WordPress Environment.
If the value does not rise, your host may cap PHP memory below 512 MB. Ask the host to raise the PHP memory_limit, because WordPress cannot use more memory than PHP allows. For more on the limits involved, see this guide to the allowed memory size error.
How do you switch the Elementor editor loader method?
Enable the Switch Editor Loader Method under Elementor, Settings, Advanced, then reload the editor.
This setting changes how the editor loads its data, and Elementor points to it when the preview URL or the loader is the fault. Elementor's editing guide says to go to Elementor, Settings, Advanced and switch the editor loading method to Enabled.
The steps are:
- In wp-admin, go to Elementor, then Settings, then Advanced.
- Find Switch Editor Loader Method and set it to Enable.
- Save the changes and open the stuck page in the editor again.
If the editor loads after this change, leave the setting on. If it makes no difference, turn it back to its old value and keep working through the other fixes, so you change only one thing at a time.
How do you fix a Cloudflare Rocket Loader block?
Turn Rocket Loader off in Cloudflare, purge the cache, and reload the editor to see if the loader was the block.
Rocket Loader defers the loading of all JavaScript until after rendering, which can break scripts that the editor needs (Cloudflare Rocket Loader docs). Cloudflare says that if you observe JavaScript or jQuery issues, you should disable Rocket Loader and retest your website.
Follow these steps:
- Open the Cloudflare dashboard for your domain and go to Speed, then Optimization.
- Set Rocket Loader to Off.
- Purge the Cloudflare cache for the site.
- Hard refresh the editor page in your browser and try to edit again.
Also turn off JavaScript delay or defer settings in a caching plugin while you test, because two layers that rewrite scripts can hide the real cause. A guide to Elementor performance settings can help you review those options once the editor works again.
How do you check the preview, URLs, and browser console?
Check the site URLs, the browser console, and the frame settings, because a blocked preview iframe looks like a stuck editor.
First, open Settings, then General, and confirm that the WordPress Address and Site Address match and use the same http or https form. Elementor's Safe Mode guide lists matching Site and WordPress URLs under General Settings as one of the fixes when Safe Mode does not solve the problem.
Next, right-click the stuck editor page, choose Inspect, and open the Console tab. Look for red error messages, which often name the blocked script or file.
A frame block is one common console finding. Elementor states that a Content-Security-Policy frame-ancestors value of none breaks the Elementor editor, because it blocks the iframe used for the editor preview (Elementor system requirements). If you or your host set that header, ask the host to allow framing from your own domain.
Finally, re-save the permalink settings. Go to Settings, then Permalinks, and click Save Changes without changing anything. Elementor's preview error guide lists re-saving permalinks as one of its quick fixes, along with Safe Mode, a 512M memory limit, and turning off Rocket Loader.
How do you know the editor is fixed?
The editor is fixed when it opens on a complex page, the widget panel loads, and you can save a small change and see it on the live page.
Test in this order:
- Open the page that stuck before and wait for the full canvas and widget panel to appear.
- Change one word in a text widget, click Update, and wait for the save to finish.
- Open the live page in a private browser window and check that the change shows.
- Repeat the check on a second page, then turn back on any plugin you left off only if it does not break the editor.
If the editor opens but a change does not show on the live page, the fault may be cache, not the editor. See this guide to changes not showing on a site before you change more settings.
When should you contact your host or Elementor support?
Contact your host when the memory limit will not rise, the editor fails in Safe Mode on every page, or the console shows a server or frame header block you cannot change.
Give the host the exact facts: the memory value in Elementor System Info, whether Safe Mode helped, whether the loader method helped, and any red console error. That list lets the host check the PHP limit, the server settings, and the security headers without guessing.
Contact Elementor support when the host confirms that memory, PHP, and headers are fine, but the editor still sticks on every page. Include the Elementor version, the WordPress version, and the steps you already tried.
Before you contact either one, check that your PHP version meets the floor Elementor lists. Elementor's Safe Mode guide says to confirm the site runs PHP 7.4 or higher, MySQL 5.6 or higher, and has active PHP cURL and GD modules.
If PHP is below that floor, ask the host to update it; see this guide to updating the PHP version.
What mistakes should you avoid?
Do not change five settings at once, because you will not know which change fixed the editor or broke it again.
Avoid these mistakes:
- Raising the memory limit in wp-config.php but never checking whether the host cap blocked it.
- Leaving every plugin off after a Safe Mode test instead of finding the one plugin that caused the fault.
- Turning Rocket Loader back on right after the editor works, without testing the editor first.
- Editing wp-config.php without a backup, since a typing error in that file can break the whole site.
- Trying to edit the blog archive page or edit on a phone, when Elementor does not support either one.
Work through one fix, test the editor, and write down the result before you move to the next fix. That order also helps your host or Elementor support if you need to ask for help. For context on how much memory WordPress sites need, see this guide to WordPress RAM needs.
Frequently asked questions
Why is my Elementor editor stuck on the loading screen but my site still works?
The live site and the editor load different code. The editor needs extra scripts, a live preview in an iframe, and more memory than a normal page view. Low memory, a plugin conflict, or a blocked preview can stop the editor while visitors still see the site normally.
How much memory does Elementor need to load the editor?
Elementor lists 256 MB as the minimum WordPress memory limit, with 512 MB recommended and 768 MB for best performance, as of November 2026. Set WP_MEMORY_LIMIT to 512M in wp-config.php, then check the value in Elementor System Info to confirm it took effect.
Does Safe Mode change what visitors see on my site?
No. Safe Mode only changes the editor session for the logged-in user who turns it on. Visitors still see the normal theme and plugins. That is why it is a safe first test: it can prove a plugin or theme conflict without changing the live site.
What should I do if the editor still will not load in Safe Mode?
Work on the server side next. Raise the memory limit to 512 MB, enable the Switch Editor Loader Method, check that the WordPress and Site addresses match, and look for a frame or security header block in the browser console. If those do not help, ask your host to check the PHP limit and headers.
Can Cloudflare really stop the Elementor editor from loading?
Yes. Rocket Loader defers JavaScript until after rendering, and that can break the scripts the editor needs. Turn Rocket Loader off in the Cloudflare dashboard, purge the cache, and reload the editor. If the editor then loads, leave Rocket Loader off or ask for help excluding the editor scripts.
Sources
- Elementor stuck on loading screen Elementor
- Can't Edit with Elementor - What Should I Do? Elementor
- System Requirements to Use Elementor Elementor
- How to Fix the 'Preview Could Not Be Loaded' Error Elementor
- Safe Mode Activation Isn't Solving My Problem Elementor
- Editing wp-config.php WordPress Developer Resources
- Rocket Loader Cloudflare
- Description of core php.ini directives PHP
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.
Thanks — we review requests within 3 business days.
