Windows Recall Storage: Stop Saving or Delete Snapshots

To stop Recall from saving new snapshots, turn off Save snapshots in Settings › Privacy & security › Recall & snapshots. To recover space from snapshots already saved, use the deletion controls on that page. These are separate actions: pausing collection does not mean the existing history has been removed.

First confirm that Recall is available and enabled on your PC. A Copilot app icon or a large C drive does not prove that Recall is recording anything. Microsoft's Recall overview describes its device requirements, opt-in behavior and organization policies.

Read used storage, not just the limit

The Recall settings page distinguishes storage being used from the maximum allocation. A large limit is not evidence that this amount has already been consumed. Compare the current usage with Settings › System › Storage before deciding whether Recall explains the shortage.

Microsoft's snapshot storage guide provides controls for storage capacity and retention duration. When the configured limit is reached, older snapshots are removed. Choose a smaller limit if you still use Recall but do not need as much history.

Keep the effect in mind: less retained history means fewer past moments available to search. There is no storage setting that preserves an unlimited history while using a fixed small amount of space.

Work through a storage shortage in order

First read the amount currently used by snapshots and the maximum allowed. For example, a 75 GB limit with 2 GB used does not mean Recall can release 75 GB. Those are illustrative readings, not a measurement from a particular PC. If the installation you are trying to finish needs more space than Recall actually uses, you will need to inspect another storage category as well.

If the goal is to stop accumulation and remove the current history, do the two actions in that order. Turn off Save snapshots, then open Delete snapshots and choose the intended scope. Otherwise, deleting history while collection remains enabled can be followed by new snapshots, which can look like a failed cleanup.

Microsoft currently documents deletion windows for the past hour, 24 hours, 7 days or 30 days, as well as deletion of all snapshots. These controls remove recent snapshots in the chosen window; do not read “past 7 days” as “everything older than 7 days.” Check the wording shown on the installed Windows build before confirming.

Reopen the settings after deletion and record used storage again. If the expected history remains searchable, check the selected time range and whether new collection was still enabled. If used space falls but the drive remains full, return to System Storage rather than deleting Recall's internal files. A feature-specific result and the whole drive's free-space reading answer different questions.

Keep Recall with a smaller history

Capacity and retention age provide two different limits. The capacity limit bounds the space used, while an age limit makes old snapshots expire even if space is still available. Microsoft's current storage guide lists 30, 60, 90 and 180 days, or unlimited duration. Choose a history you actually need rather than assuming unlimited is required for the feature to work.

The available capacity choices depend on the PC's storage. For example, the documented choices for a 512 GB device include 25 GB, 50 GB and a default of 75 GB. This is an allocation policy, not proof that 75 GB has been prefilled with snapshots. Use the options Windows presents for the device instead of copying a registry value from a different configuration.

A smaller limit can discard older history as the limit is enforced. It is not an archive operation, so preserve a particular piece of information in its original application before depending on Recall to retain it. If that information matters as a document, save the document rather than treating a screenshot search history as its backup.

Choose the action that matches your goal

When deleting snapshots, review the selected time range and confirm the Windows Hello prompt if requested. Treat this as deletion of the Recall history, not a move to the Recycle Bin. Save any information you still need through an appropriate app before removing its only retained copy.

Afterward, reopen the same settings page and check its used-storage reading. Also compare the available space on the same drive. Do not attribute a change in the whole C drive to Recall if updates or other large downloads ran at the same time.

Remove a particular app's history without deleting everything

The same Microsoft storage guide documents deletion from Recall's search results. Open a relevant snapshot's menu and inspect the options for deleting that snapshot or all snapshots containing the selected app or website. Read the confirmation, including the reported scope, before accepting a bulk removal.

A filter for future capture and deletion of past capture are separate decisions. Adding a website or app to a filter does not establish that its earlier snapshots disappeared. Deleting its earlier snapshots does not establish that future ones are excluded. If both are intended, complete both controls and verify each result.

This narrower route is useful when one app should not be retained but the rest of the history remains valuable. It is not a reason to bypass management policy on a work PC. If the controls are unavailable or disabled, record the Windows version and the policy message for the administrator instead of downloading a debloat script.

Uninstall Recall through Windows

Microsoft documents removal through Turn Windows features on or off. Clear Recall, confirm the change and restart when Windows requests it. Removing the feature also deletes its saved snapshots. Re-enabling the feature later does not restore that deleted history.

Save work before the restart. On a work or school PC, a policy can restrict the available controls. Ask the administrator about that policy instead of applying a registry script intended for another edition or build.

Why a broad AI removal script is unnecessary here

Recall snapshots, Copilot conversations, downloaded AI models and generated images are different data sets. Removing one feature does not establish that the others have been cleared. A script advertised as removing all Windows AI may alter many more components than the Recall storage problem requires.

Use the controls above for Recall, then inspect any remaining shortage separately. Ollama models, for example, can occupy a large folder even on a machine where Recall has never saved a snapshot. The Ollama model-location guide covers that case without changing Windows features.

If Recall usage is small, follow the C drive storage guide to find the larger owner. The useful result is identifying which files actually occupy the drive, not disabling an unrelated feature because it has AI in its name.