Edge freezing — tab goes white and unresponsive, the browser stops accepting input, or “Not Responding” appears in the title bar — usually has one clear cause once you know what to look for. Start with the simplest test before anything else. We go deeper on the whole subject in our Google Chrome Errors.
Open Edge’s own task manager: Shift+Esc. Sort by CPU. Is a specific tab or extension process using 50%+ CPU? That’s your target. Close or suspend that tab. If one tab is consuming most available CPU, Edge’s overall responsiveness drops and can appear frozen when it isn’t actually crashed.
If Task Manager itself won’t open because Edge is completely frozen: Alt+F4 to close the window, then reopen. Edge should restore the previous session automatically.
The fast fixes — try these first
Disable hardware acceleration. This is the single most effective fix for Edge freezing on graphics-heavy sites, video, or WebGL content. Settings (three-dot menu → Settings) → System and performance → toggle off “Use hardware acceleration when available” → Restart Edge. If freezing stops: the GPU driver is incompatible with Edge’s renderer. Update the GPU driver from the manufacturer’s website, then re-enable hardware acceleration.
Clear cache and cookies. Ctrl+Shift+Delete → All time → check Cached images and files + Cookies → Clear now. Corrupted cache causes specific page freezes where only certain sites freeze while others load fine. After clearing: test the previously-freezing pages.
Extensions — the overlooked cause
Edge inherits Chrome’s extension ecosystem. Many Chrome extensions work in Edge, but some are poorly optimised and consume excessive resources — causing freezes on any page load, not just specific sites.
Test: click the Extensions icon → disable all extensions → browse for 10 minutes. If Edge is stable without extensions: re-enable them one at a time, testing after each. The extension that causes freezing when enabled is the culprit. Ad blockers with aggressive filter lists, VPN extensions, and cryptocurrency price trackers are the most common offenders.
An alternative test: InPrivate window (Ctrl+Shift+N). Extensions are disabled by default in InPrivate. If Edge is stable in InPrivate but not regular mode: an extension is causing it.
Edge update — check it’s current
Three-dot menu → Help and feedback → About Microsoft Edge. Edge updates automatically but the update sometimes hasn’t been applied yet — clicking this page triggers the check and shows whether an update is pending. Click Restart to update if one’s available. Some Edge freezing issues are bugs in specific versions that subsequent updates patch.
Corrupted Edge profile
Edge’s profile accumulates data over months and years. When this data becomes corrupted — corrupted cache entries, malformed extension data, or damaged browsing history — Edge can freeze during startup or when trying to load certain pages.
Create a new profile: Profile icon (top right) → Add profile → Browse as guest or create a new one → sign in with Microsoft account. Test Edge in the new profile. If it runs without freezing: the old profile has corruption. Migrate to the new profile by signing into the Microsoft account, which syncs favourites, passwords, and settings from Edge’s cloud backup.
Microsoft Edge performance mode
Settings → System and performance → “Optimize Edge for” → Performance. This mode reduces resource usage for background tabs and limits some features to improve responsiveness. Useful on machines with limited RAM (8 GB or less) where Edge is competing for memory with other applications.
Also on the same page: “Sleeping tabs” → enable. This suspends inactive tabs after a configurable period, reducing CPU and memory usage from open-but-not-active tabs that accumulate over a session.
Windows update and Edge compatibility
Edge integrates deeply with Windows 11. When Windows updates change underlying APIs that Edge depends on: Edge may freeze until an Edge update is also applied. Settings → Windows Update → check for and install any pending updates → then check for an Edge update. Running both current together is important — an outdated Edge on a recently updated Windows can have compatibility problems that wouldn’t exist if both were current simultaneously.
DNS and network causing apparent freezes
Edge appears frozen when a page is loading and the DNS lookup is taking an unusually long time — the browser waits for DNS, the UI becomes unresponsive during the wait, and it looks like a crash rather than a slow load. Switch Edge’s DNS: Settings → Privacy, search, and services → Use secure DNS → with Cloudflare (1.1.1.1) or Google (8.8.8.8).
Also worth checking: Settings → Privacy, search, and services → “Preload new tab page for faster performance” — this preloads content that may include heavy elements. Toggle it off temporarily and test if tab-opening freezes improve.
WebView2 and Edge dependencies
Edge’s engine (WebView2) powers not just the browser but also many Windows apps and Microsoft 365 integrations. When WebView2 is corrupted: Edge freezes in specific contexts, particularly when switching between page types or when Office integration features load.
Settings → Apps → Installed apps → search “WebView2” → Microsoft Edge WebView2 Runtime → if available: Modify → Repair. If no repair option: uninstall → restart → Edge reinstalls WebView2 automatically on next launch.
Our guide on Edge crashes and crashes covers the more severe crash scenarios where Edge terminates rather than just freezing — the GPU driver and profile diagnostic approaches overlap significantly. For system-level performance issues that make all browsers freeze, our memory and performance guide covers the RAM and process management that affects browser stability. Microsoft’s Edge performance documentation covers the Edge developer tools performance profiler (F12 → Performance tab) for diagnosing which specific web operations cause freezes.
Startup boost causing freeze on launch
Edge’s “Startup boost” feature keeps Edge processes running in the background even when the browser appears closed — for faster launch times. When these background processes get into a bad state (after a crash, after a system resume, or after Edge updates), launching Edge reconnects to already-broken processes rather than starting fresh, causing an immediate freeze on launch.
Settings → System and performance → toggle off “Startup boost.” Edge now fully terminates when closed and starts completely fresh each launch. Slightly slower to open, but no frozen-on-launch issue. Alternatively: Task Manager → look for Microsoft Edge processes running when Edge isn’t visibly open → end all of them → relaunch Edge fresh.
Memory and tab count
On machines with 8 GB RAM, keeping 30+ tabs open in Edge consistently causes freezes as Windows paginates Edge’s data to the page file. Edge’s Sleeping Tabs feature (Settings → System and performance → Sleeping tabs → Turn on) suspends inactive tabs after a configurable period, significantly reducing active memory usage. Edge also shows a “Tab energy and memory savings” indicator in the tab bar showing how much memory sleeping tabs have freed.
For persistent high memory usage: Edge://settings/system → “System” section → Efficiency mode → “Balanced” limits Edge’s resource usage when the machine is low on resources. This adds 100–200ms of occasional lag to tab switching in exchange for much more stable performance overall.
Edge and Copilot sidebar
Microsoft’s Copilot sidebar in Edge (the AI panel accessible from the toolbar) runs as a separate process that loads AI models and communicates with Microsoft’s servers. On slower machines or when Microsoft’s servers are slow: the Copilot panel can consume enough resources to cause the main browser window to freeze.
Disable or hide the sidebar: Settings → Sidebar → Discover sidebar → toggle off. Or right-click the Copilot icon in the toolbar → Hide from toolbar. Removing the sidebar process from Edge’s background activity improves responsiveness on machines that were marginal for Copilot’s resource requirements.
Antivirus scanning Edge’s downloads and pages
Security software that scans Edge’s downloads in real-time, or that hooks into Edge’s network requests, can cause Edge to freeze while the scan completes. The freeze is temporary — Edge waits for the scan result — but on slow machines or with large downloads, the wait is long enough to appear like a crash.
Add Edge’s profile folder (%localappdata%MicrosoftEdgeUser Data) to the antivirus exclusion list. This prevents real-time scanning of Edge’s session data files while the browser runs. Note: this doesn’t stop the antivirus from scanning files when they’re actually saved to disk — it only prevents the live scanning of Edge’s internal data that causes the freeze delay.
Edge flags and experimental features
Edge has an experimental features page at edge://flags. If flags were modified — for testing, following a forum guide, or after clicking “Enable experiments” in an error message — some combinations cause instability. Navigate to edge://flags → click “Reset all to default” → Restart. If freezing stops after the reset: an experimental flag combination was the cause. Re-enable specific flags one at a time if needed.
Freezing on specific site types
Edge freezing on streaming video (Netflix, YouTube, Twitch) is almost always hardware acceleration — the GPU driver’s video decoding path is the issue. Disabling hardware acceleration resolves it immediately.
Freezing on pages with maps, 3D, or complex animations is often WebGL — the same GPU driver issue but through OpenGL. Same fix: disable hardware acceleration while GPU driver is updated.
Freezing specifically on Microsoft 365 web apps (Teams web, SharePoint, OneNote Online): these use Edge’s integration with WebView2 and Office components. A WebView2 repair usually resolves this specific pattern when general fixes don’t.
Freezing on a specific news site or social media: that site is likely running heavy JavaScript continuously — auto-refreshing, infinite scroll, tracking, or mining scripts. Edge’s efficiency mode or an ad blocker with script blocking helps contain the impact of these pages on the rest of the browser.
Checking Edge error reports
When Edge freezes and you force-close it: Edge may log a crash report. Navigate to edge://crashes/ in Edge after reopening. Crash reports from the frozen session appear here with timestamps. Clicking a crash report shows the type of failure — GPU crash, renderer crash, or browser process crash — each pointing at a different fix. GPU crashes → hardware acceleration or driver. Renderer crashes → specific site or extension. Browser process crashes → profile corruption or Edge installation.
Reinstalling Edge
Edge is a Windows component that can’t be uninstalled from the standard UI, but it can be repaired or reset. Settings → Apps → Microsoft Edge → Modify → Repair. This reinstalls Edge’s application files without affecting profiles or settings. If repair doesn’t resolve freezing: Modify → Reset clears all settings and data (same as creating a new profile from scratch). As a last resort for persistent freezing that survives all other fixes, the reset provides the cleanest possible Edge state.
For issues that survive a reset: Edge’s integration with Windows 11 at the OS level means a Windows in-place repair (running Windows 11 setup.exe → upgrade keeping files) sometimes resolves Edge problems that aren’t fixable from within Edge or Windows settings. This is a 45–90 minute operation but definitively resolves installation-level Edge corruption.
A pattern that’s worth knowing: Edge freezing that only happens in the first 30–60 seconds after launch, then becomes stable, is usually Startup Boost background processes combined with session restore loading all previous tabs simultaneously. The fix: turn off Startup Boost (as above), reduce the number of tabs that restore on startup (Settings → Start, home, and new tabs → when Edge starts), or change Edge to open a new tab instead of the previous session. This eliminates the load spike that causes the post-launch freeze without affecting ongoing browser performance.
Edge freezes but other browsers work fine
If Chrome or Firefox work without freezing while Edge consistently does: the problem is Edge-specific rather than system-level. Focus on hardware acceleration (the most common Edge-specific freeze cause) and the Edge profile. If all browsers freeze: the problem is system-level — GPU driver, RAM pressure, or hardware — and the fix applies to all browsers rather than Edge specifically.
Testing both browsers on the same site that causes Edge to freeze takes two minutes and immediately tells you whether to focus on Edge configuration or system configuration. This cross-browser comparison is the most efficient diagnostic step for persistent Edge freezing and is worth doing before anything else if you haven’t already.
For corporate-managed Edge deployments: many Edge settings are controlled via Microsoft Intune or Group Policy and can’t be modified from within the browser. If settings appear greyed out or show a lock icon, they’re managed. Freezing caused by enforced settings (forced extensions, mandatory proxy configurations, enhanced security controls) requires IT to create exceptions or investigate at the policy level. The edge://policy/ page shows all active policies and their values — useful when reporting Edge freezing to IT with specific context about what’s locked and what isn’t. See also Stop Edge Changing Your Homepage for a related case.
