Recall is supposed to be a quiet background companion, snapping and indexing your screen while you work. So when Task Manager shows its processes devouring gigabytes of RAM and your Copilot+ PC starts stuttering, something has gone off the rails. High memory usage from Recall doesn’t just slow the feature itself — it starves your browser, your apps, and the NPU-accelerated AI tasks the laptop was built for.

Some memory use is legitimate — Recall processes screenshots and runs on-device AI models. The problem cases are when usage is far beyond normal, keeps growing without limit, or spikes the moment Recall starts. This guide helps you tell normal from abnormal, then walks through six fixes that bring Recall’s footprint back to sane levels — without forcing you to give up the timeline.

Before diving in, make sure Recall itself is actually healthy. A damaged snapshot store can send the service into a resource-hungry retry loop; if you also see timeline errors, read the corrupted Recall database fix first. Otherwise, start here.

Why this happens

  • Snapshot frequency too high: Capturing and processing snapshots aggressively multiplies the indexing workload and its memory footprint.
  • Huge snapshot backlog: A large, unpruned history forces the service to hold a bigger working index in RAM.
  • Memory leak in the service: Buggy builds can leak memory, with usage climbing steadily until the service is restarted.
  • Excluded-app churn: Rapidly switching between many apps, especially browsers with heavy pages, floods the snapshot pipeline.
  • On-device AI model loaded constantly: The models Recall uses for text extraction and search stay resident in memory by design.
  • Too many apps included: Letting Recall snapshot everything — games, video players, remote desktops — maximizes processing load.

How to fix it

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

Fix 1: Measure what’s actually normal first

You can’t fix what you haven’t measured. Establishing a baseline tells you whether Recall is genuinely misbehaving or just doing normal background work during an indexing burst.

  1. Open Task Manager with Ctrl + Shift + Esc and switch to the Details or Processes tab.
  2. Sort by Memory and note the Recall-related processes and their current usage.
  3. Leave Task Manager open for 30 minutes of normal use without interacting with Recall.
  4. Check again: stable usage in the low hundreds of MB is normal; steady climbing past 1–2 GB is not.
  5. Note the pattern: constant high use, gradual growth, or sudden spikes.

Fix 2: Reduce snapshot frequency and prune storage

The fastest legitimate way to cut Recall’s memory footprint is to give it less work. Fewer snapshots mean less indexing, a smaller working set, and lower RAM use — with your existing timeline untouched.

  1. Open Settings, go to Privacy & security, then the Recall & snapshots page.
  2. Lower the snapshot frequency or increase the interval between captures if options are available.
  3. Reduce the maximum storage allocated to snapshots to prune the oldest history.
  4. Wait an hour for the service to process the smaller backlog and release memory.
  5. Re-check Task Manager to confirm the working set has dropped.

Fix 3: Exclude heavy apps from snapshots

Browsers with dozens of tabs, games, and video editors generate the most expensive snapshots to process. Excluding apps you never need in your timeline cuts the indexing workload dramatically. Microsoft’s Windows support pages explain the exclusion controls in the Recall settings.

  1. On the Recall & snapshots settings page, find the app exclusion or filter list.
  2. Add your browser if you keep many tabs open — you rarely need every web page in your timeline.
  3. Exclude games, video players, and video conferencing apps, whose snapshots are costly to index.
  4. Exclude remote desktop and virtual machine windows, which duplicate content from other machines.
  5. Restart the Recall service or reboot so exclusions take full effect.
  6. Monitor Task Manager over the next day to confirm lower, stable memory use.

Fix 4: Restart the Recall service to clear a leak

If memory climbs endlessly and never comes back down, you’re likely looking at a leak rather than workload. Restarting the service releases everything and tells you whether the growth repeats — the key diagnostic for leak behavior.

  1. In Task Manager, find the Recall background service or related processes.
  2. End the tasks, or restart the PC cleanly from the Start menu.
  3. After reboot, note the service’s memory usage immediately — this is your clean baseline.
  4. Use the PC normally for a few hours, then check whether usage has ballooned again.
  5. If it grows unbounded a second time, check Windows Update for a newer build — leaks are often patched.

Fix 5: Reset the snapshot store to clear index bloat

A bloated or partially damaged index can keep far more data resident in memory than a healthy one. Resetting the snapshot store rebuilds the index from scratch — you lose old history, but the service returns to a lean, correct state. If you’re also reviewing what Recall stores, see Recall not filtering sensitive info .

  1. Open the Recall & snapshots settings page and toggle Recall off.
  2. Wait for the service to fully stop, then restart the PC.
  3. Delete the snapshot data from the settings page if a delete option is offered.
  4. Toggle Recall back on and let it rebuild its index over several hours.
  5. Confirm in Task Manager that memory usage stays modest during the rebuild.
  6. Re-apply your app exclusions from Fix 3 so the new index stays lean.

Fix 6: Cap background load and update everything

When nothing else explains the usage, the remaining levers are system-wide: make sure Windows, drivers, and firmware are current, and reduce competing background load. Some users mistake this for a Copilot subscription problem, like Copilot Pro features not working , but local RAM pressure is a device issue.

  1. Run Windows Update and install all pending updates, then reboot.
  2. Update your chipset and NPU drivers from the manufacturer or the Intel driver assistant .
  3. In Task Manager’s Startup apps tab, disable programs you don’t need at boot.
  4. Close memory-heavy background apps you aren’t using during the test period.
  5. Consider adding more RAM only if the whole system — not just Recall — is consistently starved.
  6. Re-measure Recall’s usage after a clean boot to confirm the improvement.

Closing

Recall’s RAM usage should be a background hum, not a headline in Task Manager. In most cases the fix is workload, not hardware: fewer snapshots, smarter exclusions, a pruned backlog, and an occasional service restart keep the footprint modest while the timeline stays useful. Reserve the snapshot-store reset for genuine bloat or leak behavior, and keep Windows and drivers current. If your Copilot+ PC still feels sluggish, the walkthrough for AI background processes on Windows 11 covers the wider cast of AI services competing for your memory.

Frequently asked questions

How much RAM should Recall normally use?
Recall’s background service typically uses a few hundred megabytes, with brief spikes when processing new snapshots. Sustained usage above 1–2 GB, or a steady climb that never drops, indicates something is wrong.
Will limiting Recall's RAM break my timeline?
No. Reducing snapshot frequency, excluding apps, or capping storage only means Recall captures less — it never corrupts existing snapshots. Your current timeline stays intact while memory pressure drops.
Is high RAM usage a sign of a memory leak?
It can be. If the Recall service’s memory climbs indefinitely without ever releasing, especially after a Windows update, that’s classic leak behavior and usually fixed by restarting the service, updating Windows, or resetting the snapshot store.
Should I just disable Recall to save RAM?
Only as a last resort. The fixes in this guide — fewer snapshots, app exclusions, storage caps — cut memory use dramatically while keeping Recall functional. Disable it only if you never use the timeline feature.