Noticing the Copilot app slowly eating hundreds of megabytes — or even gigabytes — of RAM is alarming on a laptop where every gigabyte counts. Some growth during a long conversation is normal, since the app keeps chat context, rendered images, and web-view data in memory. But memory that climbs endlessly, never drops when you close chats, or stays high with the app merely sitting in the background usually signals a leak, a stuck process, or background activity you did not ask for.

Before changing anything, open Task Manager and confirm Copilot is the actual culprit rather than a related service. If overall system RAM pressure is the complaint, also check whether Copilot’s CPU usage is abnormally high , since runaway background work often shows up in both counters at once. On Copilot+ PCs, on-device AI can legitimately use extra memory; to see whether the neural processor itself is involved, you can check if the NPU is being used by apps — note that guide covers virtual machines, but its Task Manager steps apply to physical PCs too.

The good news is that most Copilot memory problems respond to simple, reversible steps: clearing cached data, limiting background activity, and keeping the app updated. The fixes below are ordered so you try the least disruptive options first, and none of them will delete your conversations or sign you out unexpectedly. And if you notice other Windows AI features acting up while memory runs high — for example Click to Do’s translate-text option going missing — treat those as separate issues rather than symptoms of the same memory problem.

Why this happens

  • Memory leak in the app’s web view: Copilot renders its interface with a web-view component. Bugs in specific app versions can leak memory each time a chat reloads, so RAM climbs the longer the app stays open.
  • Very long conversations kept in context: Each message, image, and attachment in an open chat consumes memory. Marathon sessions with dozens of images can push usage past 1 GB entirely by design.
  • Background activity left enabled: Copilot can keep running after you close its window to deliver notifications and stay ready for the wake word. That background instance holds its full memory footprint.
  • Stuck sync or failed upload retrying: A chat that fails to sync or an attachment stuck uploading can leave worker threads spinning and retrying, pinning extra memory indefinitely.
  • Outdated app with known leak fixed later: Microsoft has patched several Copilot memory leaks through Store updates. Running a months-old version means living with bugs that are already fixed.
  • Conflicting overlay or capture software: Screen-capture tools, overlays, and some antivirus web shields hook into Copilot’s web view and prevent it from releasing memory for rendered content.

How to fix it

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

Fix 1: Restart Copilot and clear its cache

A fresh start releases leaked memory immediately and tells you whether the growth was a one-off glitch or a repeatable leak. Clearing the cache goes one step further without touching your chats.

  1. Close the Copilot window, then end any Copilot processes in Task Manager.
  2. Reopen Copilot and note its memory usage at idle in Task Manager.
  3. If usage is normal now, the spike was transient — monitor it for a day.
  4. For a deeper clean, go to Settings, then Apps, then Copilot, and choose Advanced options.
  5. Use the Repair option first, then Reset if the problem returns, and retest memory use.

Fix 2: Close long conversations and start fresh chats

Chat context is the most legitimate reason for high memory. Trimming it is the fastest way to reclaim RAM when the app is otherwise healthy.

  1. In Copilot, close or archive conversations you no longer need open.
  2. Start a new chat instead of continuing a weeks-old thread.
  3. Avoid keeping many image-heavy conversations open in tabs at once.
  4. Check Task Manager after tidying up to confirm memory dropped.
  5. If a single conversation always spikes memory, its content may be triggering a rendering bug — export what you need and delete it.

Fix 3: Turn off background activity and startup launch

If Copilot sits in memory all day without you opening it, background permissions are the reason. Disabling them costs nothing except a slightly slower first launch.

  1. Open Copilot settings and disable any run-in-background or startup options.
  2. Open Task Manager, go to Startup apps, and disable Copilot if listed.
  3. Restart the laptop and confirm no Copilot process starts on its own.
  4. Launch Copilot manually only when you need it for a few days.
  5. Compare idle memory before and after to measure the saving.

Fix 4: Update the Copilot app from the Microsoft Store

Because several memory leaks were fixed in newer releases, an update is both a diagnostic and a cure. Never skip this step.

  1. Open the Microsoft Store and check for updates to the Copilot app.
  2. Install the update, then fully close and reopen Copilot.
  3. Monitor memory over a normal day of use.
  4. If the Store shows no update, check Windows Update for related web-view runtime updates.
  5. For general app troubleshooting steps, see Copilot in Windows support .

Fix 5: Disable hardware acceleration in the web view

On some GPU driver combinations, the web view’s hardware acceleration leaks video memory that shows up as app RAM. Toggling it off is reversible and safe.

  1. Open Copilot settings and look for a hardware acceleration or graphics option.
  2. Turn hardware acceleration off and restart the app.
  3. Watch Task Manager during a normal chat session.
  4. If memory stays flat, leave the setting off until a driver or app update lands.
  5. Also consider updating your GPU driver from the vendor’s site if you use this workaround.

Fix 6: Reinstall Copilot cleanly

When nothing else sticks, a corrupted install or damaged web-view cache is the likely cause. A clean reinstall gives you a known-good baseline.

  1. Uninstall Copilot from Settings, then Apps, then Installed apps.
  2. Restart the laptop to clear any locked cache files.
  3. Reinstall Copilot from the Microsoft Store and sign in.
  4. Before restoring old habits, test memory with a single short conversation.
  5. If the fresh install still leaks, report it via Feedback Hub so Microsoft sees the pattern.

Closing

Copilot should be a lightweight assistant, not a memory hog. In most cases the fix is unglamorous — an update, a cache clear, or closing a marathon chat — but the Task Manager checks above make sure you are treating the real cause. Keep background activity off if you rarely use Copilot, and revisit the Store for updates whenever memory starts creeping again.

Frequently asked questions

How much RAM should the Copilot app normally use?
At idle with no conversation open, Copilot typically uses a few hundred megabytes. During an active chat with images or long context, usage can legitimately climb past 1 GB. Sustained usage above 2 GB at idle, or steadily climbing memory that never drops, points to a leak or a stuck background process.
Will clearing the Copilot cache delete my chat history?
No. Clearing the app cache removes temporary files, thumbnails, and web-view data, but your signed-in chat history is stored with your Microsoft account in the cloud. You will stay signed in, although you may need to reload the current conversation.
Does Copilot use more memory on Copilot+ PCs?
It can, because Copilot+ PCs run additional on-device AI models for features like Recall and Click to Do alongside the Copilot app. If total system memory pressure is high, use Task Manager to see whether Copilot itself or a related AI background service is the real consumer.
Can I stop Copilot from running in the background?
Yes. In Copilot’s settings, turn off background activity and startup launch. You can also disable it in Task Manager under Startup apps. Copilot will then only use memory while its window is actually open.