Windows says Installed apps are huge. Which app is using the space?

Start with Large installed apps

Scan the affected drive and open SizeTrend's Overview pane. Large installed apps combines registered Windows desktop applications, Microsoft Store packages, Steam and Epic titles, supported portable applications, Scoop packages, Meta/Oculus games, and Google Play Games storage into a drive-based list measured from their known locations.

This does not replace the application's own management data. It gives you a consistent physical measurement so a 90 GB game and a 20 GB desktop tool can be compared even when their launchers report size differently.

Expand applications with more than one location

SizeTrend 3.2 uses a related-data catalog covering 300+ applications and release channels. It can recognize supported custom Firefox and Thunderbird profiles and selected ProgramData locations, including NVIDIA App data. An application can appear for its known data on the scanned drive even when its binaries are installed elsewhere.

An application can have a main installation folder, shared components, downloadable content, package data, or another registered location on the same drive. Expand the Overview row to see the locations included in SizeTrend's measurement.

Data under AppData may be cache, persistent account state, offline content, projects, or user-created files. Recognized related data contributes to the application footprint; narrower cleanup or review categories may describe the same storage separately. Attribution does not make all of it disposable, and section totals can overlap.

Use Uninstall or Manage instead of deleting folders

SizeTrend hands Steam and Epic titles back to their launchers and uses the registered uninstall or management path for desktop and Microsoft Store applications. The application still owns the decision and can remove services, manifests, shortcuts, registry data, and shared components correctly.

Deleting a large folder in Explorer can leave an application registered but broken. It may also leave the launcher unable to distinguish an intentional removal from damaged or missing files.

Shared folders and installer estimates

For applications sharing an installation root, SizeTrend uses Windows Installer component evidence to identify more specific product folders when possible. Resolved folders show measured allocation; unresolved member rows are labeled as installer estimates. The shared total is counted once, and member values need not add up to it.

Registered package storage may also appear under Windows Installer Packages. Read the installer-cache guide before deciding how to manage those files.

If no registered app owns the folder

Follow the largest folders in the main scan and check Review to Free Up Space. The space may belong to a portable application, old installer, abandoned game library, local database, virtual machine, user profile, or data folder that was never registered as an installed application.

SizeTrend can recognize some unregistered applications from executable product information in supported application locations. Their Manage action opens a folder for review; absence from Windows Installed apps does not mean an application is unused. Scoop packages use Scoop for removal and preserve persistent data. Identify the program and verify that the data is not shared before removing it. A folder named after an application is useful evidence, but it is not the same as a supported uninstall path.

Separate applications from recordings and caches

Game recordings, browser profiles, media caches, downloaded models, build artifacts, and application caches can be larger than the executable that created them. SizeTrend can include known related data in application footprints while also showing specific cleanup or review categories. The applicable action depends on the data, not just the application name.

Uninstalling an application may leave personal projects or reusable data behind. Cleaning a recognized cache may preserve the installed application entirely. Review both before deciding which action actually solves the storage problem.