Few things stall a website project like an Elementor editor that spins forever or a Publish button that does nothing. The good news is that almost every case comes down to a handful of causes: a plugin conflict, server limits, caching, or a security rule blocking the editor's requests.
This guide starts with quick checks that fix most problems, then works through each symptom in turn. Take a full backup before changing server settings or plugins.
Start here: five quick checks
- Reload without cache. Press Ctrl+Shift+R (Cmd+Shift+R on a Mac), or open the editor in a private window. Stale files cause more editor problems than anything else.
- Disable browser extensions. Ad blockers and privacy extensions can block the editor's scripts. A private window with extensions off is a quick test.
- Update everything. Elementor, Elementor Pro, your theme, and any Elementor add-ons should be on current, compatible versions. A Pro version far behind the free version is a common cause.
- Regenerate Elementor's files. Go to Elementor → Tools and use the button that regenerates CSS and data. It rebuilds the stylesheets Elementor generates for each page.
- Check System Info. Elementor → System Info shows your PHP version, memory limit, and any warnings Elementor has detected.
If the problem continues, find your symptom below.
The editor or widget panel won't load
The editor loads its interface and all widgets through JavaScript and background requests. When either fails, you see an endless loading screen or an empty widget panel.
Test with Safe Mode
Elementor → Tools has a Safe Mode option that loads the editor with only Elementor active and a default theme. If the editor works in Safe Mode, a plugin or your theme is causing the problem.
To find which one, deactivate your plugins (keeping Elementor and Elementor Pro active) and turn them back on one at a time until the editor breaks again. Elementor add-on packs and optimization plugins are the most common culprits.
Raise the PHP memory limit
Large pages and many active add-ons need more memory than some hosts allow by default. Add this line to wp-config.php, above the line that says "That's all, stop editing":
define( 'WP_MEMORY_LIMIT', '256M' );
If your host caps memory lower at the server level, the setting won't take effect. Ask your host to raise the PHP memory limit to at least 256 MB.
Switch the editor loader method
Some server setups interfere with how the editor loads. Under Elementor → Settings → Advanced, enable Switch Editor Loader Method, save, and try the editor again.
Read the browser console
Open your browser's developer tools (F12) and look at the Console tab while the editor loads. A red error naming a plugin's file points straight to the conflict.
Elementor isn't saving changes
When you click Update and it hangs, shows an error, or the changes disappear after a reload, the save request is failing on the server.
Open developer tools, go to the Network tab, and click Update. Look for the failed request (often admin-ajax.php, highlighted in red) and its status code:
| Status | Likely cause | Fix |
|---|---|---|
| 403 Forbidden | A firewall or security rule (such as ModSecurity or a security plugin) blocked the save | Whitelist the request in your security plugin, or ask your host to check their firewall logs |
| 500 Internal Server Error | A PHP error, often running out of memory | Raise the memory limit and check the PHP error log |
| 413 Request Entity Too Large | The page data is bigger than the server accepts | Ask your host to raise the request size limit |
| 200, but changes still don't stick | The server cut off part of the page data | Raise max_input_vars (3000 or more) and post_max_size |
Very long pages with many widgets are where request size and max_input_vars limits show up first. Splitting a huge page into saved templates also helps.
Changes are saved but don't show on the live site
If the editor shows your changes but visitors don't see them, something between the page and the browser is serving an old copy.
- Clear every cache layer: your caching plugin, your host's server cache, your CDN (such as Cloudflare), and your browser.
- Regenerate CSS: use the regenerate button in Elementor → Tools so styles are rebuilt.
- Check the CSS print method: if styles lag behind content, switching how Elementor outputs CSS (in its performance settings) and regenerating files often helps.
- Disable aggressive optimization: JavaScript combining, delaying, or minifying in optimization plugins can break Elementor pages. Exclude Elementor's files, or turn those options off one at a time to find the conflict.
- Check you're editing the right thing: a header or footer built as a theme template must be edited in the Theme Builder, not on the page itself.
"The preview could not be loaded"
This message usually means the editor can't load your page inside its preview frame. Check that WordPress Address and Site Address under Settings → General match exactly, including https:// and www. If you recently moved to HTTPS or a new domain, Elementor → Tools has a Replace URL option that updates old URLs saved in Elementor data.
Security headers that block pages from loading in frames, set by a plugin or your server, can also cause this. The editor needs to load your own site in a frame.
Prevent it from happening again
- Keep a staging site and test Elementor, theme, and plugin updates there first.
- Use fewer add-on packs, and remove ones you don't use. Every add-on loads into the editor.
- Choose hosting that meets Elementor's requirements, with generous PHP memory.
- Keep page structures lean. Containers with fewer nested levels load and save faster than deeply nested sections.
Most Elementor loading and saving problems are solved within the first few checks above. When they aren't, the cause is usually deeper in the server configuration or a specific plugin conflict, and that's the point where an experienced Elementor developer can save you hours.