Elementor: The preview could not be loaded / Server Error 500 / Preview Debug
Elementor’s editor couldn’t load the page preview in its iframe — PHP errors, memory limits, mixed URLs, or plugin conflicts.
Seen on:
WordPress
Meaning
The preview is a frontend request inside the editor. Fatal errors, low memory, siteurl/home mismatches (http vs https), X-Frame-Options/CSP blocking iframes, or caching/optimisation plugins break it.
Common causes
- PHP memory too low (Elementor recommends 256M+)
- PHP fatal error from a plugin/theme
- siteurl/home mismatch or mixed content
- Security headers blocking same-origin iframes
- Cache/optimisation plugins interfering
⚡ Quick fix
- Raise WP_MEMORY_LIMIT
- Enable WP_DEBUG_LOG and read errors while loading the editor
- Check Elementor → System Info and Preview Debug; disable conflicting plugins
Detailed fix by platform
WordPress
- php
define('WP_MEMORY_LIMIT', '512M'); define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); define('WP_DEBUG_DISPLAY', false);
How to diagnose
- Log — debug.log errors
- URLs — siteurl/home
- Headers — X-Frame-Options/CSP
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Call to undefined function (WordPress) WordPress: Fatal error: Uncaught Error: Call to undefined function wp_get_current_user() / add_action() / get_header()
- Call to undefined function create_function() WordPress on PHP 8: Fatal error: Uncaught Error: Call to undefined function create_function() / each()
- Critical error WordPress: There Has Been a Critical Error on This Website
Most viewed in WordPress
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026