Recall is one of the most power-hungry features Windows 11 has ever shipped. Every few seconds it captures your screen, runs the image through on-device AI models on the NPU, indexes the content, and writes encrypted snapshots to disk. All of that is real work, and on a laptop it shows up directly in battery life — some users report losing an hour or more of runtime with Recall left on.

The tricky part is that Recall is designed to be efficient: it leans on the NPU specifically because the neural processor sips power compared to the CPU or GPU. So when battery drain is severe, something is usually off — capture running during heavy workloads, a stuck indexing job, or settings that keep Recall working when it should be resting.

This guide shows how to measure Recall’s actual power draw, which settings tame it, and when the drain signals a bug rather than normal behavior. A corrupt search index can trap Recall in a power-hungry loop — see Recall search troubleshooting if search is broken too. For the bigger picture, read AI features draining laptop battery . And be honest about your hardware: running Recall on unsupported PCs forces power-hungry CPU fallback.

Why this happens

  • Constant snapshot capture and AI indexing: Every snapshot triggers screen capture, on-device AI analysis, and encrypted writes. That pipeline runs all day by default.
  • Capture during heavy workloads: Recall keeps snapshotting while you game or render video, stacking its workload on top of an already busy system.
  • Stuck or looping index jobs: A corrupted snapshot index can send Recall’s background processing into a loop, burning CPU and NPU cycles nonstop.
  • High snapshot frequency with no idle detection issues: If Windows fails to detect idle time correctly, Recall may capture during periods it should skip.
  • Large storage allocation: Bigger snapshot stores mean more indexing work and more disk writes, both of which cost power.
  • Outdated NPU drivers: Inefficient NPU drivers force more work onto the CPU, which draws far more power for the same AI tasks.

How to fix it

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

Fix 1: Measure Recall’s actual power usage first

Never optimize what you have not measured. Recall’s power draw varies enormously between a healthy system (modest, NPU-efficient) and a sick one (a stuck indexing loop burning CPU). The battery-usage screen and Task Manager give you hard numbers in minutes, and a simple paused-versus-enabled comparison over a few hours settles the question definitively. Everything after this step depends on what the numbers say.

  1. Open Settings > System > Power & battery and check battery usage per app over the last 24 hours.
  2. Open Task Manager (Ctrl + Shift + Esc), go to Processes, and look for Recall-related background activity and its power usage trend.
  3. Compare drain with Recall paused for a few hours versus enabled — a big delta confirms it.
  4. Also check the NPU graph in Task Manager’s Performance tab to see if the neural processor is pegged.

Fix 2: Pause Recall when you need maximum battery

Recall does not need to run while you are stretching battery on a flight. Pausing halts capture, AI indexing, and encrypted writes immediately — the power savings are instant and total. Make it part of your unplugged routine alongside dimming the screen, and resume when you are back on AC power. If you rarely search old snapshots anyway, consider leaving Recall off by default and enabling it on demand.

  1. Click the Recall icon in the system tray and choose Pause, or pause it from quick settings.
  2. Make pausing part of your unplugged routine, like lowering brightness.
  3. Resume capture when you are back on AC power.
  4. If you rarely search old snapshots, consider leaving Recall off by default and enabling it only when needed.

Fix 3: Reduce the snapshot storage allocation

Every gigabyte of snapshot history is indexing work and disk writes, both of which draw power. A smaller allocation means a smaller active index and less background churn — and as a bonus, searches get faster. Match the cap to how far back you genuinely search rather than hoarding months you will never revisit.

  1. Go to Settings > Privacy & security > Recall & snapshots.
  2. Lower the maximum storage allocation to the smallest value that still covers your needs.
  3. Delete old snapshots you will never search to shrink the active index.
  4. A smaller store also makes Recall’s searches faster, a nice side benefit.

Fix 4: Update NPU and system drivers

Recall’s efficiency story depends entirely on the NPU doing the AI work at low power. With a broken or outdated NPU driver, that work spills onto the CPU, which draws several times the power for the same inference. The OEM driver matched to your exact laptop model keeps the pipeline on the efficient path, and Windows Update’s generic replacements are a common source of exactly this regression.

  1. Open Device Manager, expand Neural processors, and update the NPU driver.
  2. Better yet, get the driver from your laptop maker’s support page so it matches your exact model.
  3. Install all pending Windows updates — power-management fixes for Recall ship regularly; check Microsoft’s Windows support hub for the latest guidance.
  4. Restart after driver updates and re-measure battery drain over a full day.

Fix 5: Tame background AI processing

A corrupt snapshot index can send Recall’s background processing into a loop — indexing, failing, retrying, forever. Deleting the snapshots clears the corrupt index and breaks the cycle; the rebuild afterward is clean and far cheaper. If drain persists with Recall fully disabled afterward, you have proven the culprit is elsewhere and can move on without second-guessing.

  1. In Recall settings, delete all snapshots to clear a possibly corrupt index, then let it rebuild.
  2. Turn off other always-on AI features you do not use, covered in our AI features battery guide .
  3. Check Task Manager after the reset to confirm background activity settles.
  4. If drain persists with Recall fully off, the culprit is elsewhere — run a battery report with powercfg /batteryreport to find it.

Fix 6: Let Battery Saver throttle background AI

Battery Saver does more than dim the screen: it throttles background activity system-wide, including Recall’s indexing pipeline. Setting it to engage automatically at 30% means you stop thinking about Recall’s power draw on long unplugged days — the OS handles it. It is the closest Windows comes to a ‘manage Recall’s battery for me’ switch.

  1. Go to Settings > System > Power & battery.
  2. Set Battery Saver to turn on automatically at 30%.
  3. In Battery Saver settings, confirm background activity is limited while it is active.
  4. Use the laptop unplugged for a day and compare runtime against your baseline.
  5. Adjust the threshold up if you want earlier intervention on long travel days.

Fix 7: Hunt runaway processes in Task Manager

Normal Recall operation has a recognizable power signature; a runaway job looks completely different in Task Manager’s power-usage column. Sorting by power draw exposes a stuck indexer in seconds, and ending it provides immediate relief. If the same process immediately respawns and hogs power again, that persistence itself is diagnostic — the underlying index or store needs the reset, not the process.

  1. Press Ctrl + Shift + Esc and open the Processes tab.
  2. Click the Power usage column to sort by highest drain.
  3. Look for Recall-related or AI-indexing processes with sustained Very High usage.
  4. Right-click a runaway process and choose End task, then watch whether it respawns.
  5. If it respawns and hogs power again, reset the snapshot store to break the loop.

Closing

Recall will always cost some battery — constant on-device AI is real work — but it should not gut your runtime. Measure first, then pause strategically, trim storage, and keep drivers current. If drain stays severe with Recall disabled, look elsewhere: a proper battery report will point at the true culprit faster than guessing.

Frequently asked questions

How much battery does Windows Recall normally use?
On a healthy Copilot+ PC with current drivers, Recall’s impact is modest because the work runs on the efficient NPU. If you are losing an hour or more of runtime, that is above normal and worth troubleshooting.
Does pausing Recall stop the battery drain immediately?
Yes. Pausing halts snapshot capture and the associated AI processing right away. It is the quickest way to confirm Recall was the cause and to stretch battery when unplugged.
Why does Recall use the NPU instead of the CPU?
The neural processing unit is designed for AI workloads at a fraction of the power draw of a CPU or GPU. Keeping Recall on the NPU is exactly what keeps its battery impact manageable.
Can I schedule Recall to only run on AC power?
Windows does not offer a built-in schedule for Recall, but pausing it manually when you unplug — or leaving it off and enabling it on demand — achieves the same result with one click.