Windows Search has a hidden appetite for SSD space. Its index database, Windows.db, can quietly grow to several gigabytes, even if you rarely use the feature. A recent experiment proved just how easily you can shrink it: one user cut their database from 1.3GB to 687MB—a 613MB savings—by simply switching a single setting and rebuilding the index. No third-party tools, no risky service shutdowns. Just a smarter configuration that better matches how most people actually search their PCs.

If you’ve noticed your SSD filling up without an obvious cause, or if you use a third-party launcher like Raycast or PowerToys Run and rarely touch Windows’ built-in search, this two-minute adjustment could be your easiest space-saving win of the week. And it doesn’t break anything.

The Hidden Culprit: Windows.db

On Windows 11, the search index lives in a protected system folder:
C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.db

This file is the heart of Windows Search. It stores a catalog of file names, properties, and even text content so that when you type into the Start menu or Explorer, results appear almost instantly. Microsoft likens it to the index at the back of a book—a prebuilt lookup table that saves you from scanning every page.

The problem: the more files you have, the larger the index grows. And it’s not just about total storage; a folder with thousands of tiny files can bloat the index far more than a few large videos. Microsoft warns that the database “can grow substantially” once indexed items exceed 400,000, regardless of their actual disk size.

Even worse, the database file’s reported size can be misleading. Because Windows uses sparse file techniques, File Explorer may show a logical size that doesn’t match the physical space occupied. For an accurate measure of how much SSD capacity the index really consumes, you need to check the “Size on disk” property rather than the raw file size.

Why Your Search Index Grows Out of Control

Windows offers two indexing scopes:

  • Classic: only indexes common user folders—Documents, Pictures, Music, Desktop, and the Start menu. This is the default and covers what most home users need.
  • Enhanced: indexes the entire PC. Every file on every internal drive becomes searchable. This is useful if you deliberately scatter active work across multiple locations and rely on Windows Search as your primary navigation tool.

Many users end up on Enhanced without realizing it, whether by accepting a prompt, upgrading from an older Windows version that enabled it, or following online advice. Once enabled, Windows dutifully catalogs everything: OneDrive caches, backup folders, game libraries, VM images, developer dependency directories like node_modules, even old installer archives you’ve long forgotten.

The result? A bloated index that eats space while seldom being used. The original How‑To Geek experimenter, for example, was using Raycast for 90% of his search needs. The bloated Windows.db was pure waste until he switched to Classic and rebuilt.

The Fix: Switch to Classic and Rebuild

The solution isn’t to disable Windows Search—that cripples Start menu responsiveness and file content search. Instead, you narrow the index scope to what you actually search, then force a rebuild. The outcome is a leaner, faster database that still works where you expect it.

Here’s how to do it, step by step.

Step 1: Measure Your Current Index Size

Open Windows Terminal as administrator (right-click Start → Terminal (Admin)). Paste this command and press Enter:

Get-Item "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.db" -Force |
Select-Object Name,@{Name="Size (MB)";Expression={[math]::Round($_.Length / 1MB,1)}}

This reads the file’s logical size without modifying anything. Take note of the number—later you’ll compare it to see how much you saved.

Caveat: this shows logical size, not physical size on disk. For a true before‑and‑after comparison, right-click the file (you may need to copy it to a temporary location to access it) and check “Size on disk” in Properties. The difference can be significant, as Microsoft acknowledges.

Step 2: Switch from Enhanced to Classic

Go to Settings → Privacy & security → Searching Windows. Under “Find my files,” you’ll see two options: Classic and Enhanced. If Enhanced is selected, choose Classic. This immediately restricts indexing to your Documents, Pictures, Music, Videos, Desktop, and Start menu shortcuts.

Note: If you rely on Windows Search to instantly find files scattered across multiple drives, you might want Enhanced. But if you use third-party launchers, browse files manually, or only search common folders, Classic is almost certainly enough. You can still add extra folders in the next step.

Step 3: Customize Indexed Locations

Still in the same settings page, click Customize search locations → Modify. This opens the classic Indexing Options panel. You’ll see a list of currently indexed locations. Uncheck any folders you rarely search:

  • Old backup directories
  • OneDrive folders (if you don’t search them)
  • Downloads (full of old installers)
  • Video libraries with huge media metadata
  • Game libraries
  • Virtual machines and snapshot folders
  • Developer project caches (e.g., node_modules)

Be selective. Leaving a folder unchecked doesn’t delete anything; it just tells Windows Search to ignore it. Searches inside that folder via File Explorer may take longer, but the trade‑off is usually worth it for archival or high‑volume storage areas.

Step 4: Rebuild the Index

After adjusting the scope, the old bloated database still exists. You need to rebuild it so Windows creates a fresh, leaner version based on the new scope.

In the same Indexing Options window, click Advanced → approve the administrator prompt. Under the Index Settings tab, go to the Troubleshooting section and click Rebuild. Confirm the warning.

Microsoft says a full rebuild can take up to 24 hours, depending on how many files remain indexed and your system’s usage. During that time:

  • Start‑menu searches may return incomplete results.
  • File content searches will be inconsistent.
  • The PC might use slightly more CPU and disk I/O.

Let the process finish while the computer is plugged in and preferably idle. You can continue using the PC, but the rebuild will slow down during active use.

Once Indexing Options reports “Indexing complete,” run the PowerShell command again. You should see a dramatically smaller number. The original user’s database dropped from 1.3GB to 687MB—a 47% reduction.

What the Change Means for Your Daily Workflow

Switching to Classic and pruning unnecessary folders doesn’t cripple Windows. Apps launch from the Start menu just as fast. Documents, pictures, and music in your user folders remain instantly findable. The only thing that changes is that Windows Search no longer knows about every backup archive and old installer you’ve accumulated.

If you later need to search a folder you excluded, just open File Explorer, navigate inside, and use the search bar there. It will be slower than an indexed search, but how often do you need to find a file inside a five‑year‑old backup? For most people, the answer is “rarely to never.”

For power users who lean on tools like Everything, PowerToys Run, or Raycast, the benefit is even clearer: you keep Windows Search functional for the few times you press the Windows key, without duplicating the mass file indexing you already get elsewhere.

Maintaining a Lean Index Over Time

This isn’t a one‑time fix. As your storage usage changes, the index can creep up again. Set a calendar reminder to check Windows.db every few months, or whenever you add a large new data source (e.g., syncing a massive cloud storage folder).

Key maintenance habits:

  • Periodically review indexed locations via Indexing Options.
  • Resist the urge to re‑enable Enhanced unless you genuinely need whole‑PC search every day.
  • If you notice Windows.db swelling again, repeat the customization and rebuild.

Also, don’t mistake rebuilding for a routine disk cleanup. Rebuilding every week isn’t necessary; Windows can add and remove individual file entries on its own. Only rebuild when you change scope or suspect corruption.

What to Avoid

The web is full of more aggressive “fixes” that can do more harm than good:

  • Disabling the Windows Search service entirely breaks Start menu search, Cortana, and many modern app search features. It’s overkill unless you’re troubleshooting a specific issue.
  • Manually deleting Windows.db can work, but if the service is running or you lack permissions, you’ll get errors or an automatic recreation that may be even larger. The built‑in Rebuild button is safer.
  • Running offline ESE database defragmentation (esentutl) is for advanced users when Windows refuses to reclaim space internally. It’s an arcane command‑line procedure that most SSD‑constrained users will never need.

Stick with the official UI path. It’s designed for exactly this scenario.

The Bigger Picture: Storage Policy Is Personal

Your search index is essentially a storage policy decision. Every folder you let Windows Search index costs a bit of SSD space in exchange for instant search access. If you never search a folder, you’re paying for nothing. The Classic/Enhanced toggle is the easiest way to align that cost with your behavior.

For the user in the original story, switching saved 613MB on a system that probably had ample room anyway. But on a 128GB or 256GB laptop, where every gigabyte counts for updates, system restore points, and app data, that’s a tangible relief. Microsoft’s own documentation underscores the point: if a large index is caused by abundant content, “the primary way to reduce disk use is to index less content and then rebuild the database.”

As Windows 11 continues to mature, and as our drives fill with cloud mirrors, AI caches, and ever‑growing game installations, such small optimizations add up. The settings are already there. It only takes a few clicks to make them work for you rather than against you.