Microsoft Edge is a good browser with a bad habit: on some Windows 11 laptops it sits at 20–40% CPU doing apparently nothing, draining battery and spinning fans while you read a static page. Because Edge is Chromium-based, the causes are familiar — runaway tabs, greedy extensions, misconfigured efficiency settings — but Edge has its own specific knobs (Sleeping tabs, Efficiency mode, Startup boost) that change the diagnostic path.

This guide uses Edge’s own built-in tools to find the hog, then applies the fixes in order of impact.

Why this happens

  • Runaway scripts or miners in a tab: A single tab running heavy JavaScript, video, or a cryptominer burns CPU invisibly in the background.
  • Extension overload: Each extension injects code into pages; a dozen extensions compound into constant overhead.
  • Sleeping tabs not working: If sleeping tabs are disabled or misconfigured, dozens of background tabs stay fully active.
  • Efficiency mode disabled or misfiring: Without throttling, background tabs consume far more than they should.
  • Hardware acceleration conflicts: A buggy GPU driver interaction makes the renderer work the CPU instead of the GPU.
  • Startup boost + background processes: Edge preloading and running background apps keeps processes alive after you close the window.
  • Corrupted profile or cache: A damaged user profile causes persistent high CPU that survives restarts.
  • Multiple Edge processes from PWAs: Installed web apps each run Edge processes that add up silently.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Use Edge’s built-in task manager

In Edge, press Shift+Esc to open the browser task manager — it shows CPU per tab, per extension, and per subprocess. Sort by CPU and let it sit for a minute. The culprit is usually obvious: one tab at 30%+, or an extension name you barely recognize. This is the single most valuable diagnostic step — it turns “Edge is slow” into “this specific tab/extension is slow.” Note the offender’s name before touching any settings. For system-wide (non-browser) CPU hogs, the same diagnose-first approach applies — see the laptop speed-up guide .

  1. In Edge: Shift+Esc → browser task manager.
  2. Sort by CPU; observe for 1–2 minutes.
  3. Identify the specific tab, extension, or subprocess hogging CPU.
  4. Target your fix at that offender — not at Edge generally.

Fix 2: Kill or fix the runaway tab

If a tab is the hog: close it, and if it’s a site you need, try it in an InPrivate window (no extensions) to see if an extension was amplifying it. For video sites, lower the playback resolution — 4K video decode on an unsupported codec burns CPU. Check whether the site is mining or running heavy ads (an ad blocker test tells you). If a work web app is the permanent hog, that’s a site problem to report to its developers — but sleeping-tab settings (Fix 3) can at least contain it when it’s in the background.

  1. Close the hogging tab; test the site in InPrivate.
  2. Lower video resolution on media-heavy pages.
  3. Test with an ad blocker to identify ad/script-driven load.
  4. For permanently heavy work apps: contain with sleeping tabs (next).

Fix 3: Enable and tune Sleeping tabs + Efficiency mode

Edge Settings → System and performance: turn On “Save resources with sleeping tabs,” set tabs to sleep after 5 minutes of inactivity, and enable “Fade sleeping tabs.” Turn On Efficiency mode with maximum savings. Add sites that must stay live (music, web apps, video calls) to the “Never put these sites to sleep” list. This combination is Edge’s biggest built-in CPU saver for tab-heavy users — background tabs drop to near-zero CPU instead of idling expensively.

  1. Settings → System and performance → enable Sleeping tabs.
  2. Set sleep timeout to 5 minutes; enable fading.
  3. Enable Efficiency mode (maximum savings).
  4. Whitelist sites that must stay live.

Fix 4: Audit extensions ruthlessly

Edge Settings → Extensions: disable everything, then use the browser normally for an hour with the browser task manager open. If CPU is calm, re-enable extensions one at a time, giving each 15 minutes. Keep only what you actively use — each extension is code running on every page. Pay special attention to coupon finders, price trackers, and “new tab” replacements, which are disproportionately heavy. Remove (don’t just disable) the ones you cut; disabled-but-installed extensions still update and occasionally wake. Chrome users with the same complaint follow the same logic — see Chrome high RAM usage .

  1. Disable all extensions; test for an hour.
  2. Re-enable one at a time with 15-minute observation windows.
  3. Remove (not just disable) extensions you don’t need.
  4. Keep the final set minimal.

Fix 5: Toggle hardware acceleration and update the GPU driver

Edge Settings → System and performance → “Use hardware acceleration when available”: try it off, restart Edge, and test for an hour — then try on again. On some GPU/driver combos, acceleration helps enormously; on others it’s the problem. Whichever is better, keep. Simultaneously, update your GPU driver (Intel via the Intel Driver & Support Assistant ; NVIDIA/AMD via their apps) — renderer CPU spikes are often really driver bugs. Test video playback specifically, since decode paths are where acceleration matters most.

  1. Toggle hardware acceleration off; restart Edge; test 1 hour.
  2. Toggle it back on; compare.
  3. Keep whichever setting performs better.
  4. Update the GPU driver regardless; retest video playback.

Fix 6: Disable Startup boost and background running

Edge Settings → System and performance: turn Off “Startup boost” and “Continue running background extensions and apps when Microsoft Edge is closed” — unless you rely on Edge PWAs running in the background. These features keep Edge processes alive 24/7, which is pure overhead if you don’t need instant launches. Also check edge://apps for installed PWAs you forgot about; each is a standing process. Close Edge completely after these changes and verify in Task Manager that no msedge.exe processes linger.

  1. Disable Startup boost.
  2. Disable “Continue running background apps when Edge is closed.”
  3. Review edge://apps; remove forgotten PWAs.
  4. Close Edge; confirm no msedge.exe lingers in Task Manager.

Fix 7: Reset Edge or rebuild the profile

If CPU is still high with no tabs, no extensions, and fresh settings: Edge Settings → Reset settings → “Restore settings to their default values.” If that fails, create a new Edge profile (profile icon → Add profile) and test there — a clean profile with high CPU means a system-level issue (GPU driver, OS), while a calm new profile means your old profile is corrupted; migrate bookmarks and abandon the old one. As a final data point, Microsoft documents Edge performance settings on the Windows support site .

  1. Reset Edge settings to defaults; retest.
  2. If still bad: create a new Edge profile; test there.
  3. Calm new profile → migrate to it, abandon the old.
  4. Bad in new profile too → system-level cause (drivers/OS).

Closing

Edge high CPU is almost always a who, not a what — a specific tab, extension, or setting, identifiable in sixty seconds with Shift+Esc. Work from the browser task manager outward: fix the hog, enable sleeping tabs and Efficiency mode, prune extensions, and only then touch acceleration and profiles. A tuned Edge idles near zero and sips battery; there’s no reason to accept a browser that runs hot reading static pages.

Frequently asked questions

Why does Edge use so much CPU even with only a few tabs open?
A few tabs can still be expensive: background tabs running scripts, extensions injecting code into every page, efficiency mode misfiring, or a single tab with a runaway script or crypto miner. Edge’s built-in task manager (Shift+Esc) shows per-tab and per-extension CPU, so you can see exactly which tab or extension is the hog instead of guessing.
Does Edge's Efficiency mode actually reduce CPU usage?
Yes, when it works as intended — it throttles background tabs and reduces activity for inactive pages, which measurably cuts CPU on tab-heavy sessions. But on some systems it misbehaves or users disable it chasing responsiveness. Try it enabled first with the ‘maximum savings’ timing; if a specific workflow suffers, add that site to the never-sleep list rather than disabling the feature.
Can browser extensions cause constant high CPU?
Absolutely — extensions are the number-one browser CPU culprit. Ad blockers with huge filter lists, price trackers, and poorly written utilities run code on every page you visit. Test by disabling all extensions for an hour: if CPU normalizes, re-enable one at a time. Keep your extension count minimal and remove anything you don’t actively use.
Should I just switch browsers if Edge is slow?
Switching rarely fixes the underlying issue, since Chrome and Edge share the Chromium engine — the same runaway tab or extension will misbehave in both. Fix the actual cause first (extensions, sleeping tabs, hardware acceleration). If Edge is still worse than Chrome with identical extensions, then a browser switch is a reasonable experiment, not a first step.