Microsoft's Recall Can Claim 150 GB of Your Drive. Here's What That Default Actually Costs You

Windows 11's Recall feature — the one that screenshots your screen every so often so you can search your own activity later — doesn't just cost CPU cycles and an NPU fast enough to run it locally. It reserves a chunk of your drive, and Microsoft's own support documentation lays out exactly how big that chunk is by device tier. Run the numbers on that table and a few other figures Microsoft publishes alongside it, and the real cost of turning Recall on looks different from "it uses some storage."

Illustration: a consumer SSD, representative of the fixed drive capacity Recall's storage allocation is carved out of. Photo by Jacek Halicki, via Wikimedia Commons, licensed under CC BY-SA 4.0.

The Four Numbers Microsoft Requires Before Recall Turns On

Before any snapshot gets saved, a machine has to clear a hardware floor. Per Microsoft's own Recall management documentation, a device needs a Copilot+ PC meeting the Secured-core standard, an NPU rated at 40 TOPS or greater, 16 GB of RAM, 8 logical processors, and 256 GB of storage at minimum. Tom's Hardware's original coverage of the Copilot+ PC category, published when Microsoft announced it in May 2024, lists the same three consumer-facing numbers — 16 GB RAM, 256 GB storage, 40 TOPS NPU — and as of this writing those figures haven't moved. (If 40 TOPS sounds familiar, it's the floor: TechDailyBrief covered a new wave of laptops shipping at double that NPU rating last week.)

Clearing the hardware floor isn't the same as being allowed to turn the feature on, though. Microsoft's documentation adds a separate gate: the device needs at least 50 GB of free storage before Recall can be enabled at all, on top of whatever the hardware minimum already set aside. That 50 GB figure rarely shows up in coverage of Recall's hardware requirements, but it's the number that actually determines whether a nearly full 256 GB laptop can use the feature its NPU was certified to run.

The Allocation Table Nobody Reads Past the Default Column

Once enabled, Recall doesn't use an unlimited amount of drive space — it draws from a fixed pool whose size depends on total device storage. Microsoft publishes the same figures on its consumer support page and in its IT-administrator documentation, which means this is the default behavior for an ordinary Windows 11 installation, not just an enterprise policy:

Device storage	Allocation options	Default	Default as a share of total drive
256 GB	10 GB or 25 GB	25 GB	~9.8%
512 GB	25, 50, or 75 GB	75 GB	~14.6%
1 TB or more	25, 50, 75, 100, or 150 GB	150 GB	~14.6%

Figures as published on Microsoft's support page "Manage your Recall snapshots and disk space" (updated September 28, 2026) and Microsoft Learn's "Manage Recall" enterprise documentation (dated December 10, 2025). The percentage column is this article's own calculation from those published figures, using 1 TB = 1,024 GB.

The 512 GB and 1 TB tiers reserve an identical 14.6% share of the drive by default — not a coincidence, since 75 GB is exactly half of 150 GB and 512 GB is exactly half of 1,024 GB. The 256 GB tier breaks that pattern with a smaller 9.8% share. That's probably not Microsoft deciding small drives need less Recall history; it's more likely a side effect of the two separate thresholds covered next, which only leave enough headroom on a 256 GB drive to support the smaller of the two options that tier is offered in the first place.

Run the same arithmetic on the top tier and the gap widens further. A 1 TB Copilot+ laptop accepting the 150 GB default reserves six times the gigabytes a 256 GB laptop does, but it's starting from four times the total capacity — so in practice it keeps more slack in absolute terms even after Recall takes its cut. A 1 TB drive with the same 190 GB of Windows, apps, and files used elsewhere in this article's example has roughly 834 GB free before Recall, and still around 684 GB free after the 150 GB allocation. The 256 GB drive in the same scenario has 66 GB free before Recall and roughly 41 GB after. Both drives gave up about the same share of their total capacity — but only one of them is anywhere near the 25 GB pause threshold afterward. The allocation formula looks proportionally fair across tiers; the actual breathing room it leaves behind is not.

Worked Example: What 25 GB Actually Leaves a 256 GB Laptop

Take a hypothetical — not an actual device, just a round-numbers illustration — 256 GB Copilot+ laptop where Windows 11, installed applications, and personal files already occupy 190 GB, leaving 66 GB free.

• Step 1 — the enable gate: 66 GB clears the documented 50 GB-free requirement to turn Recall on, but only by a 16 GB margin.
• Step 2 — the allocation: accepting the default 25 GB snapshot pool pulls that margin down further. Effective free space outside the Recall pool drops toward 41 GB.
• Step 3 — ordinary use: install one modern game (often 20–40 GB) or export a chunk of 4K video, and free space outside the Recall pool can fall under 25 GB.
• Step 4 — the pause: once free storage drops below that 25 GB line, Microsoft's documentation says saving new snapshots pauses automatically. Both Microsoft pages describe the pause itself; neither describes an alert, notification, or prompt that tells the person it happened.

The practical result: a feature the user deliberately turned on can go quiet after an unrelated, routine action — installing a game, moving a video project onto the drive — with no documented mechanism that flags the change. Recall doesn't fail; it just stops accumulating the history it was turned on to build, silently, until something is deleted and free space climbs back above the threshold.

Retention Isn't a Fixed Number of Days — It's Whatever the Allocation Fills In

Microsoft's management documentation lists fixed retention options of 30, 60, 90, or 180 days, but only as an administrator policy for Enterprise and Education editions. Left unconfigured — the default on a consumer machine — snapshots are instead "kept until the maximum storage allocation is reached, then the oldest are deleted first." That default isn't a day count at all; it's a function of how fast the allocated gigabytes fill up.

That matters because Recall's own documentation says a new snapshot is captured "periodically while content on the screen is different from the previous snapshot" — no fixed interval is published. A person who leaves a single document open most of the day generates far fewer new snapshots than someone switching between a browser, a video call, and a spreadsheet every few minutes. Two users with the identical default 25 GB allocation on identical 256 GB laptops can end up with meaningfully different amounts of searchable history — one stretching back weeks, the other overwritten in days — purely because of how actively their screen changes, not because either one configured anything differently.

What You're Trading for On-Device Search

Recall's pitch is local, on-device search across your own screen history, which is a real convenience Microsoft is right to point to. The documented trade-offs are just as real. On the privacy side, Microsoft's enterprise documentation describes policy-level controls to exclude specific apps or URLs from capture — useful, but confirmed here only as an Enterprise/Education administrator setting, not verified as an identical consumer-facing control. On the hardware-wear side, continuous periodic screenshotting writes data to the drive on a schedule Microsoft hasn't published, so there's no way to size its contribution to drive wear the way TechDailyBrief did for sustained write workloads in its look at SSD endurance ratings — that's a real gap in what's documented, not a claim this article can fill with an invented number.

There's also a cost dimension worth naming plainly: a buyer deciding between a 256 GB and a 512 GB configuration of the same Copilot+ laptop model is usually also deciding, without being told, between a 9.8% and a 14.6% default storage tax if they ever turn Recall on. Laptop makers generally price that jump as a meaningful add-on at checkout — often well above what the same extra capacity would cost as a standalone drive upgrade bought separately — so part of what that upsell is quietly buying back is headroom under a threshold most shoppers have never heard of before reading a support page about a feature they may not have enabled yet.

So does turning Recall off hand that reserved space back immediately? Microsoft's documentation describes the allocation as a ceiling the feature draws from while active, not a separate locked partition, so disabling Recall and deleting its snapshots should free the space for ordinary use — but that reversal isn't the part Microsoft walks through in detail, which is itself worth noting for anyone deciding whether to test the feature before committing a storage tier to it.

Weighed against the enable-and-pause mechanics above, the honest framing is this: Recall's storage design isn't reckless, but it is a feature that quietly renegotiates how much "free" space on your drive actually means free, and it does so with thresholds most users will never see in the Settings app unless they go looking for the two support pages this article is built on.

Related reading

• SSD Endurance in Years: How Long 600 TBW Lasts in Real Use
• Your New Laptop's NPU Hits 80 TOPS, Double the Copilot+ Minimum
• Gemini's New Find Hub Memory Lets Android Remember Where You Put Your Passport

Tip: If running these numbers on your own drive has you rethinking the machine it all sits on, a laptop stand keeps airflow open while Recall indexes in the background, and a wireless charger clears one more cable off a desk you are already auditing. (These are Amazon Associate links — we may earn a small commission on qualifying purchases.)

Sources

• Microsoft Support — Manage your Recall snapshots and disk space (updated September 28, 2026)
• Microsoft Learn — Manage Recall (dated December 10, 2025)
• Tom's Hardware — Copilot+ PCs: All We Know (published May 21, 2024)