If the Elementor editor loads correctly in Chrome but hangs on the loading screen, shows a blank canvas, or never finishes initializing specifically in Firefox, this is a known, browser-specific issue that Elementor's own GitHub issue tracker has open reports about, without an official permanent fix at the plugin level. The practical workaround that resolves it for most people: open Firefox's DevTools, enable "Disable Cache," and reload the editor while DevTools stays open. This isn't a permanent setting — it's a way to break a caching-related race condition that seems to affect how Firefox loads Elementor's editor assets.

Symptoms

  • The Elementor editor shows its loading screen (the animated logo) indefinitely and never finishes, only in Firefox.
  • The same page opens and edits normally in Chrome, Edge, or another Chromium-based browser on the same computer.
  • A normal page refresh (Ctrl/Cmd+R) doesn't fix it — the editor gets stuck again on reload.
  • Browser console (Firefox DevTools → Console tab) may show JavaScript errors related to a script failing to load or an unexpected null/undefined reference during editor initialization, though the exact error can vary.

Likely causes, in order of how often they actually happen

  1. A browser-caching race condition specific to Firefox's asset-loading behavior for the Elementor editor's JavaScript bundle. This is the issue tracked in Elementor's public GitHub repository — it appears intermittently and specifically in Firefox, and is understood to be related to how Firefox caches and re-requests certain script chunks during the editor's initial load sequence, rather than a bug in the editor's actual code logic.
  2. A stale or corrupted Firefox cache entry for one of Elementor's editor assets, which is closely related to cause #1 but persists across normal refreshes because the browser keeps re-serving the same broken cached file until the cache is explicitly cleared or bypassed.
  3. A Firefox extension interfering with the editor's iframe or script loading (ad blockers and privacy extensions are the most commonly implicated categories in user reports), which is less common than the caching issue but worth ruling out if the DevTools fix below doesn't resolve it.

Fix it: lowest-risk steps first

Step 1 — Open DevTools, enable Disable Cache, and reload

This is the fix most commonly reported to resolve the issue, and it doesn't require clearing your entire browser cache or changing any settings permanently.

  1. With the stuck Elementor editor page open in Firefox, press F12 (or right-click anywhere on the page → Inspect) to open DevTools.
  2. Click the Network tab inside DevTools.
  3. Check the Disable Cache checkbox near the top of the Network panel (it's only active while DevTools is open, which is expected).
  4. With DevTools still open and Disable Cache still checked, reload the page (Ctrl/Cmd+R, or F5).
  5. Wait for the editor to load normally. Once it finishes loading successfully, you can close DevTools — you don't need to keep it open for the rest of your editing session, only for this one reload.

Step 2 — If Step 1 didn't work, clear Firefox's cache for the site specifically

  1. Go to Firefox's address bar and open about:preferences#privacy.
  2. Under Cookies and Site Data, click Clear Data, and choose to clear Cached Web Content (you can leave cookies checked or unchecked depending on whether you also want to be logged out of other sites — for this fix, cached content is the relevant one).
  3. Reload the Elementor editor page and try again.
  4. Alternatively, for a more targeted clear without affecting other sites, use a private/incognito Firefox window to open the editor — a fresh private window has no existing cache for the site and will load assets clean, which is a good way to confirm the cache is the actual cause before clearing anything.

Step 3 — Rule out a Firefox extension conflict

If Steps 1 and 2 don't resolve it:

  1. Open the Elementor editor in a Firefox private window with extensions disabled by default (Firefox private windows don't run most extensions unless you've explicitly allowed them to).
  2. If the editor loads correctly in that private window, an extension is involved — go back to your normal window, open about:addons, and disable ad blockers or privacy/tracking-protection extensions one at a time, retesting the editor after each, until you identify which one is responsible.
  3. Once identified, you can either leave that extension disabled while editing, or check whether it offers a per-site exception/allowlist feature so you can keep it active everywhere except your WordPress admin domain.

Step 4 — Standard cache-and-conflict cleanup as a fallback

If the issue persists across all of the above, treat it as a general WordPress-side asset-loading issue rather than a purely browser-specific one:

  1. Clear any server-side caching plugin's cache and Elementor's own cache (Elementor → Tools → Regenerate CSS).
  2. Temporarily deactivate other plugins one at a time and retest the Firefox editor load after each, since a plugin enqueueing conflicting JavaScript can sometimes produce browser-specific loading failures that only manifest in one engine's stricter script-execution timing.

Verify the fix

  1. Reload the Elementor editor in Firefox a few times in a row (a normal refresh, not with DevTools open) to confirm it now loads consistently, not just once.
  2. Test on a couple of different pages/post types you edit regularly, since the issue has been reported to be intermittent rather than tied to one specific page.
  3. If you disabled an extension in Step 3, confirm the editor still loads correctly a day or two later, since intermittent issues can be easy to mistake as "fixed" after only one successful reload.

If you need to roll back

There's nothing to roll back — this fix only toggles a temporary DevTools setting and clears browser cache data, neither of which affects your WordPress site, your Elementor pages, or any server configuration. If you disabled a browser extension in Step 3 and want it back, simply re-enable it from about:addons.

Related fixes

FAQ

Is this a bug in Elementor, or in Firefox?

It's tracked as an open issue on Elementor's public GitHub repository, and based on user reports it behaves like a caching/asset-loading timing difference specific to Firefox's engine rather than a logic bug in Elementor's editor code — which is why there's no official permanent patch yet and the DevTools workaround is the most reliable fix in the meantime.

Do I need to keep DevTools open every time I edit in Firefox?

No. Once the editor loads successfully with Disable Cache active, you can close DevTools and continue editing normally. The issue tends to reappear only after enough time has passed for the browser cache to go stale again, at which point repeating Step 1 resolves it again.

Why does this only happen in Firefox and not Chrome or Edge?

Chromium-based browsers (Chrome, Edge, Brave) share the same underlying engine and asset-caching behavior, which appears to not trigger this particular race condition. Firefox uses a different engine (Gecko) with its own caching implementation, which is where the reported issue is specific to.

Should I just switch to Chrome permanently for editing instead of fixing this?

That's a valid short-term workaround if you edit infrequently and don't want to deal with the DevTools step, but it's not necessary — the Disable Cache fix is quick, doesn't require any settings changes, and lets you keep using Firefox as your default browser for everything else.