- C:
- Users
- <utilisateur>
- AppData
- Local
- Packages
FolderRisk: Caution
Packages C:\Users\<utilisateur>\AppData\Local\Packages
The %LOCALAPPDATA%\Packages folder: per-user data of Store apps (UWP, MSIX), one subfolder per package family.
What it’s for
Each packaged application (Microsoft Store, UWP, MSIX) gets an isolated, per-user data folder here. Apps store their settings and state without the developer having to know the path, because Windows manages it.
What it contains
- One subfolder per package family, named
<Name>_<publisher ID>(for exampleMicrosoft.WindowsCalculator_8wekyb3d8bbwe). - Inside each one, depending on the app:
LocalState,RoamingState,TempState,Settings(settings file) and other cache folders. - Windows components (Start menu, Search, shell experience) keep their data here too.
- Sizes vary widely: mail clients, games or Teams can pile up gigabytes of cache.
Risks and best practices
- The data lives only as long as the app: uninstalling erases it, and temporary storage can be purged at any time.
- Emptying a folder by hand makes the app lose its settings or even fail to start. To start from scratch, use Settings > Apps > Advanced options, then Repair or Reset.
- Leave the folders of system components (shell, search) alone, or the interface can become unstable.
- Only
TempStateand internal caches are reasonable to clean, with the app closed.
Useful commands
# The 10 largest foldersGet-ChildItem "$env:LOCALAPPDATA\Packages" -Directory | ForEach-Object { [pscustomobject]@{ Package = $_.Name SizeMB = [math]::Round((Get-ChildItem $_.FullName -Recurse -Force -File -ErrorAction SilentlyContinue | Measure-Object Length -Sum).Sum / 1MB, 1) }} | Sort-Object SizeMB -Descending | Select-Object -First 10
# Map a folder to its appGet-AppxPackage | Select-Object Name, PackageFamilyName