Do not delete the whole AppData folder to fix a full C drive. Find the application and subfolder responsible for the space, then clear confirmed temporary data or use that application's own cleanup controls. AppData holds settings and saved data as well as caches, so the useful target is a specific category, not the parent directory.
Open the right folder without hunting hidden files
Press Win + R, enter the following location, and press Enter:
%USERPROFILE%\AppData
This opens AppData for your current account, including when the folder is hidden in File Explorer. On a standard profile its location is C:\Users\<username>\AppData; the environment variable avoids guessing the account name or profile drive.
You will normally see Local, LocalLow, and Roaming. Open one branch at a time and inspect the larger application folders. Right-click a folder > Properties to check its size, or use a disk analyzer such as TreeSize, WizTree, or WinDirStat to see which branches are large.
Record the actual path of the large subfolder. “AppData is huge” is a starting observation; “this application's cache directory is the largest branch” is a useful cleanup lead. Avoid adding the size of a parent to the sizes of its children, because that counts the same files twice.
Folder-size calculations may take time. An incomplete calculation is not a reason to start deleting while the tool is still scanning. Let it finish, then compare a few candidates instead of treating the first visible large number as the whole problem.
Treat the three branches as clues
Local often holds data associated with this machine, including caches and sometimes application installations. Roaming commonly contains application settings and other profile data. LocalLow is another application-data location used by programs running with lower permissions.
Those broad descriptions are navigation clues, not deletion rules. A file under Local can be important, and a file under Roaming is not automatically backed up somewhere else. The word “local” does not mean “temporary,” and “roaming” does not prove that your account has cloud synchronization.
Do not delete a folder because its name looks random or because you do not recognize its publisher. Application identifiers and package names can be unfamiliar. Inspect the owner, the full path, and the contents before deciding what the data represents.
A working rule is to ask three questions: which application owns it, what creates it, and how that application expects it to be removed. If you cannot answer those questions, keep the folder and investigate.
Start with a confirmed temporary location
Save your work, close applications, and finish any installations before inspecting temporary files. Press Win + R and open:
%TEMP%
Read the resolved address in File Explorer before doing anything. It commonly points inside AppData\Local\Temp, but the configured location can differ. Keep this operation inside the directory that the variable actually opens.
Review the contents and remove unneeded temporary items, leaving the Temp directory itself in place. Use normal Delete rather than Shift + Delete if you want the Recycle Bin route where available. Skip files reported as in use or inaccessible; do not force them out by changing permissions.
Deleting temporary data can remove material an application still needs, especially during active work. Stop if you find a file whose purpose is unclear. If an ordinary deletion placed an item in the Recycle Bin, restore it there before emptying the bin; not every deletion method offers that recovery path.
For an alternative, use Start > Settings > System > Storage > Temporary files. Review the categories before clicking Remove files, and leave Downloads unselected unless you have checked those files separately. Built-in cleanup does not provide a general restore button, so preserve anything needed first.
Separate caches from the files you meant to keep
A large application directory may mix reusable cache with a local database, account settings, installed components, or saved work. Clearing the whole directory can discard all of them at once.
Start in the application's settings and look for its storage or cache controls. Read what the control says it removes. A cache-only action and an action that deletes downloads, history, or offline content are different decisions, even when both reduce a displayed storage total.
Save work and close the application before any manual cleanup that its documentation supports. Keep backups of valuable local data. If there is no documented removal method, avoid inventing one from a directory name.
Browser storage is a useful example of the distinction. Cached page resources are different from saved passwords, browsing history, and site data. Clearing more checkboxes than necessary can sign you out or remove information you wanted to keep. Choose the category that matches your goal rather than the widest deletion option.
For developer storage with a known owner, the npm cache guide gives a separate inspection and cleanup procedure. Its commands apply to npm's cache, not every directory that a JavaScript tool creates.
An uninstalled application can still leave useful data
A leftover folder is not proof that everything inside is disposable. It may contain an exported configuration, an archive, or data shared with another installed component. Check the contents and whether you plan to reinstall the application.
If you identify a genuinely obsolete data folder, back up anything you might need before deleting that specific folder. Do not widen the selection to its publisher's entire AppData directory unless you have checked every affected application.
Normal deletion may send files to the Recycle Bin, but large items or other deletion methods may not. Read the confirmation message. Keep the backup until you are confident that the applications and data you retained still work.
If the largest folder is not a cache
Stop trying to solve every storage problem through deletion. A large local installation or dataset may need to remain intact. Investigate the application's supported storage-location controls instead of dragging its live AppData folder to another drive.
Moving a folder and leaving a junction involves compatibility and drive-availability decisions. It is not a generic fix for the entire user profile. A new storage location also needs enough capacity; moving files to another partition does not increase the total capacity of the physical disk.
After each change, check C: free space and reopen the affected application. If the same folder grows again, identify the activity rebuilding it. A cache returning during normal use is different from an abandoned archive that stays gone.
The general Windows cleanup guide covers other categories when AppData is not the main source of pressure.
Identifying folders with AiCleanDisk Pro
AiCleanDisk Pro shows a folder tree with sizes and cleanup advice, and matches known folders against a database reviewed by an engineer. Unknown folders can receive AI explanations and advice about cleaning or moving; AI requires consent and sends paths, names, and sizes, never file contents. System-drive scanning and auto clean, except AI auto-clean, are free. Other-drive scanning, AI analysis, AI auto-clean items, and folder moving require a license. Access costs $4.99 for 30 days, $16.90 for six months, or $19.90 for one year, paid once without automatic renewal.