If Elementor is not loading, meaning the editor is stuck on the spinner, shows a grey screen or says “Preview could not be loaded”, the cause is usually one of four things: low PHP memory, a plugin or theme conflict, a caching or security tool blocking the editor, or a server error. Work through the fixes below in order.
Site down and losing money right now? Our Elementor specialists can diagnose and fix it for you at a fixed price.
First: Identify Which “Not Loading” You Have
| Symptom | Most likely cause | Start at |
|---|---|---|
| Endless loading spinner in the editor | Memory limit, plugin conflict, JavaScript error | Fix 1 |
| Grey/blank editor panel | JavaScript conflict, caching or minification | Fix 4 |
| “Preview could not be loaded” | Wrong site URL, redirects, security or firewall rules | Fix 7 |
| “Server error (500)” in the editor | PHP memory or execution limits, PHP fatal error | Fix 1 |
| Editor loads, but changes won’t save | Firewall (ModSecurity), max_input_vars | Fix 9 |
| Live site broken, not just the editor | Critical error or update problem | See our critical error guide |
Before changing anything, take a full backup with your host’s backup tool or a backup plugin.
Fix 1: Check Elementor’s System Info
Go to Elementor > System Info in your WordPress dashboard. It lists your PHP version, memory limit, WordPress version and any warnings in red. Copy this report, because it’s the first thing any developer will ask for.
Look for:
- PHP memory limit below 256M
- An outdated PHP version (check Elementor’s current requirements; we recommend PHP 8.1 or newer on a host that supports it)
- Elementor and Elementor Pro versions that don’t match (see Fix 6)
Fix 2: Increase the PHP Memory Limit
Elementor is a JavaScript-heavy editor, and a low memory limit is the most common reason it stalls. 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 PHP memory at the server level, the line won’t help on its own. Ask your host to raise memory_limit to at least 256M (512M for WooCommerce sites with many plugins). Reload the editor afterwards.
Fix 3: Use Elementor Safe Mode
If the editor is stuck, Elementor often offers an Enable Safe Mode button on the loading screen after a short wait. You can also turn it on under Elementor > Tools > Safe Mode. Safe Mode loads the editor with only Elementor active and a default theme.
- Editor works in Safe Mode: A plugin or your theme is causing the conflict. Go to Fix 4.
- Still broken in Safe Mode: The problem is server-side, such as memory, PHP or a firewall. Go to Fixes 7-10.
Remember to switch Safe Mode off when you’re done.
Fix 4: Find the Conflicting Plugin
Deactivate all plugins except Elementor and Elementor Pro, then test the editor. If it loads, reactivate plugins one at a time until it breaks again. The last plugin you activated is the culprit.
On a live site, use the free Health Check & Troubleshooting plugin instead. Its troubleshooting mode disables plugins only for your logged-in session, so visitors aren’t affected.
The usual suspects:
- Optimization plugins that minify, combine or delay JavaScript
- Several Elementor add-on packs at once
- Security plugins with aggressive rules
- Outdated plugins that haven’t been updated in a year or more
Fix 5: Test With a Default Theme
Switch temporarily to the Hello Elementor theme, or a default WordPress theme, and test again. If the editor loads, your theme or child theme is the cause. Check for a theme update, or for custom code in functions.php that loads scripts in the editor.
Fix 6: Match Elementor and Elementor Pro Versions
Elementor Pro depends on the free Elementor plugin. When one is updated and the other isn’t, the editor can fail to load. Update both to the latest versions from Dashboard > Updates. If the problem started right after an update, roll back under Elementor > Tools > Version Control to the previous version, then check the changelog for known issues.
Fix 7: Check Your Site URLs and Redirects
“Preview could not be loaded” often means the editor can’t reach your page’s preview URL. Check:
- Settings > General: Both the WordPress Address and Site Address should use the same protocol (https) and the same www/non-www version.
- Redirect plugins, or a rule that redirects logged-in users, aren’t redirecting the preview
- The page you’re editing isn’t set to private or password-protected in a way that blocks the preview
Fix 8: Exclude the Editor From Caching and Minification
Caching and optimization tools can serve stale or broken scripts to the editor.
- Clear all caches: plugin cache, server cache and CDN (for example Cloudflare).
- Exclude /wp-admin/ and URLs containing elementor-preview from page caching.
- If you use Cloudflare, turn off Rocket Loader and test again. It’s a common cause of grey editor screens.
- Temporarily disable JavaScript minification, combining and “delay JS” options.
Fix 9: Check Firewall and Security Rules
Server firewalls like ModSecurity, and security plugins, can block the AJAX requests Elementor uses to load and save. That shows up as 403 or 500 errors in the browser console. Ask your host to check the firewall logs for blocked requests to admin-ajax.php or the REST API while you open the editor, and to whitelist the rule if needed.
Fix 10: Raise PHP Limits (max_input_vars and max_execution_time)
Long Elementor pages send a lot of data. If max_input_vars is low, pages may load but fail to save, or lose sections. Ask your host for a max_input_vars of at least 3000 and a max_execution_time of at least 60-120 seconds.
Fix 11: Switch the Editor Loader Method
Elementor has a setting called Switch Editor Loader Method for servers where the editor won’t load. You’ll find it in Elementor’s Settings under the Advanced tab (or Elementor > Editor > Settings in newer versions). Enable it, save and try again.
Fix 12: Read the Browser Console
Open the editor, press F12 (or right-click and choose Inspect) and open the Console tab. Red errors usually name the file causing the problem. A path containing /plugins/plugin-name/ points straight at the conflicting plugin. Also try an incognito window with browser extensions disabled, because ad blockers can break the editor.
Still Not Loading? When to Call a Specialist
If you’ve worked through all 12 fixes, or you’d rather not experiment on a live site, the problem is usually a deeper server configuration issue, a corrupted database entry or a custom code conflict. That’s where an Elementor specialist saves hours.
- Emergency Elementor repair: Diagnosis, fixed price and a fix on a backed-up copy.
- Elementor maintenance plans: Updates tested on staging (Growth and Commerce), so this doesn’t happen again. Plans start at $29/month.
How to Stop Elementor Breaking Again
- Update Elementor and Elementor Pro together, and never on a Friday afternoon
- Test updates on a staging site first
- Keep daily backups you can restore in one click
- Keep add-on plugins to a minimum
- Stay on a supported PHP version
What to Send a Developer (So It Gets Fixed Faster)
If you hand the problem over, these details cut diagnosis time from hours to minutes:
- The System Info report (Elementor > System Info, then copy and paste)
- A screenshot of the browser console with the editor open (F12 > Console)
- What changed recently: updates, new plugins, a host migration, a PHP upgrade or a new security or caching tool
- Whether Safe Mode works, which immediately tells the developer whether it’s a conflict or a server issue
- Temporary access: a separate admin user (not your own login) and SFTP or hosting access, which you can delete afterwards
Never send passwords by plain email if you can avoid it. Use a password manager’s secure share instead.
Need an Elementor specialist? Get a free quote, ask for a free site audit or chat with us on WhatsApp. We reply within 1-3 hours. Using a specific theme? Find it in our Themes A to Z directory.
Frequently Asked Questions
Why is Elementor stuck on the loading screen?
The most common causes are a PHP memory limit below 256M, a plugin or theme conflict, caching or JavaScript optimization interfering with the editor, or a firewall blocking Elementor’s requests. Enable Safe Mode to tell whether it’s a conflict or a server issue.
How do I fix “Preview could not be loaded” in Elementor?
Make sure your WordPress Address and Site Address match (same https and www setting), disable redirect rules that affect the preview, clear all caches and check that no security rule is blocking the preview URL.
Does increasing the memory limit fix Elementor not loading?
Often, yes. Elementor needs at least 256M of PHP memory for reliable editing. If your host caps memory at a lower level, adding the WP_MEMORY_LIMIT line won’t be enough, and you’ll need your host to raise the server limit.
Can a plugin update stop Elementor from loading?
Yes. A plugin or theme update that loads incompatible JavaScript, or an Elementor Pro version that doesn’t match the free plugin, can stop the editor from loading. Rolling back the last update usually confirms the cause.
Is it safe to troubleshoot Elementor on a live site?
Deactivating plugins on a live site can break features for visitors. Use a staging copy or the Health Check & Troubleshooting plugin, which disables plugins only for your session, and always take a backup first.
Need It Fixed Today?
Send us your URL and a screenshot. You get a diagnosis and fixed price quickly, and nothing is charged until you approve.
Get emergency Elementor help · Contact us · Chat on WhatsApp
