Elementor Editor Not Loading
You click Edit with Elementor and the editor never arrives — a spinner runs forever or a grey screen sits there — while the live site itself looks perfectly fine.
Common signs of this issue
- Clicking "Edit with Elementor" shows the loading spinner indefinitely and the editor never appears.
- The page preview loads but the left-hand widget panel stays grey or empty.
- The public website works normally for visitors — only the editing screen is broken.
- It started after updating Elementor, Elementor Pro, another plugin, or after your host changed something.
- The editor loads on some pages but hangs on one particular large page.
- It works in one browser but not another, or works for a colleague but not for you.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- First, breathe: if the live site looks fine, visitors are not affected. This is an editing problem, not an outage, so there is no need to panic-change anything on the live site.
- Try opening the editor in a private/incognito window or a different browser. If it loads there, the culprit is a browser extension — ad blockers and privacy tools are known to block the editor's files — and the fix is telling that extension to ignore your site.
- Check whether the editor fails on every page or just one. Everywhere points to a site-wide cause like memory or a plugin conflict; one page points to that page's size or content.
- In the WordPress dashboard, open Elementor → System Info. It is written in plain text and flags the usual suspects itself — a low memory limit, an old PHP version, or Elementor and Elementor Pro versions that do not match.
- If you use Elementor Pro, check that both plugins were updated together. A half-finished update — one updated, the other not — is a classic cause of a hanging editor, and updating the lagging one usually cures it on the spot.
- Temporarily switch off any optimization plugin — caching, minify, or "speed up" plugins — and try the editor again. These plugins compress the site's JavaScript for visitors, and they sometimes break the editor's much heavier JavaScript in the process. If that fixes it, the plugin's settings usually have an option to leave Elementor alone.
- Ask your host two quick questions: what is the site's PHP memory limit, and what PHP version is it running. The editor needs far more memory than a normal page view, and both answers take the host a minute to look up and often minutes to change.
What this usually means
The Elementor editor is a heavyweight application that runs in your browser — much heavier than the pages it produces. Loading it means the server assembling a large amount of data and your browser running a lot of JavaScript, and if either side falls short, you get the eternal spinner while the light-weight public site carries on untroubled. That contrast — broken editor, healthy site — is normal and is actually a useful clue.
On the server side, the usual shortfall is memory: hosting plans tuned for serving simple pages often give PHP less memory than the editor needs, so the editor's requests quietly die partway through. An outdated PHP version causes similar grief. On the browser side, the common causes are an extension blocking the editor's files, or another plugin — most often an optimization or aggressive security plugin — mangling the editor's JavaScript before it reaches you.
The remaining classic is a version mismatch: Elementor and Elementor Pro are two separate plugins that must move in step, and when an update grabs one but not the other, the editor can hang until they are level again. Between memory, PHP version, extensions, plugin conflicts, and version mismatch, you have covered the cause of nearly every stuck Elementor editor — and the System Info screen will often name which one applies to you.
What not to do
- Don't delete Elementor to reinstall it as a first move — your page designs depend on it, and removal done wrong can leave pages displaying raw shortcode text.
- Don't start deactivating plugins in bulk on a live business site; switch off one likely suspect at a time so you know what actually mattered and can turn everything back.
- Don't edit the site's configuration files to raise memory yourself if those words are unfamiliar — a typo there takes down the whole site, and your host can make the same change safely.
- Don't assume the site is broken for visitors — check the public site in a private window before alarming anyone; almost always it is fine.
- Don't keep force-refreshing the editor for an hour hoping it catches — if it has not loaded twice, something specific is blocking it, and the checks above find it faster.
- Don't update Elementor alone if you also run Elementor Pro — updating the pair together avoids the mismatch that causes this exact problem.
When to get help
Most stuck editors yield to the checks above — incognito, matching updates, switching off an optimization plugin, or the host raising the memory limit. It is worth bringing in help when those come up empty, when the fix requires poking the server yourself and that is not your comfort zone, or when the editor breaks routinely after every round of updates, which suggests a deeper conflict between plugins that someone should identify once and properly. For a professional this is usually a short diagnostic job — the browser's error console and the server log tend to point straight at the blocker — and it is money better spent than hours of your own trial and error, or the slow tax of being unable to update your own site.
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Is this a business website? If this issue may be costing you leads, sales, or trust, you may want a direct review instead of trial and error.
Frequently asked questions
Why is Elementor stuck on the loading screen?
The editor needs far more server memory and JavaScript than a normal page, so it fails where the public site succeeds. The usual causes are a low PHP memory limit, a plugin conflict — often an optimization or security plugin — a browser extension blocking editor files, or Elementor and Elementor Pro being on mismatched versions.
Is my website down when the Elementor editor won't load?
Almost certainly not. The editor and the public site are separate: visitors see pages Elementor already built, which keep working even when the editing screen is broken. Check your site in a private browser window to confirm — this is an editing problem, not an outage.
How much memory does Elementor need?
Considerably more than a plain WordPress site. Elementor's own system requirements recommend a healthy PHP memory limit, and many budget hosting plans ship with less than the editor wants. Elementor's System Info screen flags a low limit, and your host can raise it in minutes.
Can an ad blocker stop Elementor from loading?
Yes. Ad blockers and privacy extensions sometimes block files the editor needs, leaving a spinner or an empty panel. If the editor loads in a private window with extensions off, that is your answer — set the extension to ignore your own site.
Why did Elementor stop working after an update?
Two common reasons: Elementor and Elementor Pro must run matching versions, and an update that catches one but not the other can hang the editor until both are level; or the new version conflicts with another plugin, most often a caching or optimization plugin that needs its settings adjusted or an update of its own.
Does an old PHP version break the Elementor editor?
It can. Elementor expects a reasonably current PHP version, and hosts sometimes leave sites on old ones for years. Your host can tell you what you are running and switch you to a supported version — worth doing regardless, since newer PHP is faster and more secure.