“Recall storage is full.” It’s a confusing warning — your drive might show plenty of free space, yet Windows insists Recall has run out of room. Welcome to quota-based storage: Recall gets its own allocation, and when snapshots fill it, you get the warning regardless of what the rest of the disk looks like.
Recall’s appetite is real. Continuous screenshots plus AI-generated text indexes accumulate fast — tens of gigabytes in weeks of heavy use is normal, and the default allocation can reach 150GB on big drives. On a 512GB laptop that’s a third of your disk eaten by a timeline you may never scroll. This guide explains the storage model, shows you how to shrink it, clear it, and stop the warnings — without breaking anything. For the broader Recall troubleshooting picture (not working, not saving), our Recall guides cover those; here it’s purely about disk space. If you’re considering the nuclear option, how to disable Recall in Windows 11 is the off switch.
And if the storage pressure comes with heat and noise, AI PC running hot fix addresses the thermal side of heavy snapshot processing.
Why this happens
- Snapshots accumulate relentlessly: Every few seconds of screen time becomes a stored snapshot — thousands per day of active use.
- AI indexes double the cost: Each snapshot also gets an AI-generated text description and searchable index, roughly doubling storage per snapshot.
- Default allocation is generous: Windows grants Recall a large quota by default (scaled to drive size), normalizing huge usage you’d otherwise notice.
- Quota ≠ free space: The “storage full” warning triggers at the Recall quota, independent of overall disk free space — hence the confusion.
- No automatic aggressive pruning: Recall prunes oldest-first only when hitting limits, and its retention is longer than most users expect.
- Encryption overhead: Snapshots are encrypted and access-controlled, adding metadata overhead versus plain image files.
How to fix it
Work through these in order — understand, shrink, clear, then prevent.
Fix 1: See exactly what Recall is storing
Before changing anything, look at the numbers. The Settings page shows allocation, usage, and options in one place.
- Open Settings > Privacy & security > Recall & snapshots.
- Note “Storage” section: current usage vs. maximum allocation.
- Check your overall disk: Settings > System > Storage to see total free space for context.
- Decide your target: most users are happy with 10–25GB allocation instead of the default.
- Remember this page — you’ll return here for every fix below.
Fix 2: Shrink Recall’s storage allocation
The highest-leverage change: cap how much disk Recall may ever consume. Windows enforces the new cap by pruning oldest snapshots first.
- On the Recall & snapshots page, find “Maximum storage for snapshots” (or similarly worded control).
- Lower it to 25GB (or 10GB if you rarely use the timeline).
- Confirm — Windows will delete oldest snapshots to fit the new cap.
- Wait a few minutes for the pruning to complete, then re-check usage.
- The “storage full” warning should clear once usage drops below the new cap.
Fix 3: Delete snapshots selectively or entirely
Pruning by age is automatic under a cap, but manual deletion gives immediate relief and a clean slate.
- On the Recall & snapshots page, click “Delete snapshots.”
- Choose a range if offered (last week, last month) or delete all for maximum space.
- Confirm — deletion is quick but the index rebuild afterwards can take a few minutes of background work.
- Verify the freed space in Settings > System > Storage.
- Set a monthly reminder if you’re a heavy Recall user — a periodic purge beats quota warnings.
Fix 4: Exclude apps and websites from snapshots
Not everything needs snapshotting. Exclusions reduce both storage growth and privacy exposure in one move.
- On the Recall & snapshots page, find “Filter” or exclusion lists for apps and websites.
- Add apps with sensitive or high-churn content (banking, password managers, video players).
- Add websites similarly — streaming and social feeds generate enormous snapshot volume.
- Excluded content is never captured, so it never consumes storage.
- Review exclusions quarterly — your app mix changes, and so should the list.
Fix 5: Pause snapshotting during storage crunches
When disk space is tight overall, pausing snapshot capture stops the bleeding immediately.
- Toggle “Save snapshots” off on the Recall & snapshots page.
- Existing snapshots remain searchable until you delete them — pausing only stops new captures.
- Free up general disk space too: Settings > System > Storage > Cleanup recommendations.
- Re-enable snapshotting once you’ve cleared room, with the smaller allocation from Fix 2.
- Consider leaving it paused permanently if you never actually use the timeline — many users don’t.
Fix 6: Disable Recall storage entirely
If the timeline isn’t worth any disk space to you, the clean answer is off — not a tiny quota you keep hitting.
- Toggle “Save snapshots” off permanently.
- Click “Delete snapshots” and remove everything.
- Set the storage allocation to its minimum if the control remains.
- Confirm in Storage settings that Recall’s footprint is zero.
- For the complete AI teardown (services and all), follow disable Windows AI services .
Closing
Recall’s “storage full” warning is a quota message, not a disk emergency — but the tens of gigabytes behind it are real. Shrink the allocation to what your actual timeline usage justifies (10–25GB for most), exclude high-churn apps and sites, and purge periodically. If you never scroll the timeline, the honest answer is off entirely — zero gigabytes, zero warnings, zero background processing. (On a Surface, storage pressure sometimes tags along with broader AI issues — see Surface Laptop AI features not working if that’s your machine.)
