How to Track Storage Usage Over Time

Create a Storage Baseline

Do not mix Size and Size on disk across months. Do not measure Documents one month and a different redirected library the next without noting the scope change.

The baseline is descriptive. It does not imply that any category or folder is too large.

1. Record drive capacity

   Open File Explorer > This PC and note the date, drive letter, total capacity, and available space.

   Expected result: You have a repeatable drive-level baseline.

2. Capture relevant categories

   Open Settings > System > Storage and wait for calculation. Record only categories connected to your question.

   Expected result: The drive total gains purpose-level context.

3. Measure selected folders

   Use Properties for a small set of stable personal folders and wait for recursive calculations to settle.

   Expected result: You have location-level reference points.

4. Add contextual notes

   Record major projects, installations, offline cloud changes, or archive moves.

   Expected result: Future differences can be interpreted against real activity.

Use a Table That Preserves Measurement Context

A spreadsheet makes differences easier to calculate, but a plain text record is also sufficient. Store units consistently and include the method if someone else may read the record.

In this example, available space falls by 35 GB while Videos grows by 29 GB. The context notes make that relationship plausible. Downloads rises and falls, but it is not the main driver across the period.

Compare Like with Like and Look for Sustained Change

Subtract the new available-space reading from the earlier reading to understand the broad change. Then compare relevant folder or category changes over the same period. The pieces will not always reconcile exactly because views classify data differently and were not measured at the same instant.

One change is not automatically a trend. Daily caches, updates, synchronization, and temporary project files can move values in both directions. Repeated movement in the same direction across comparable readings is more informative.

Scale matters. A 5 GB change can be expected during a video project but surprising in a folder intended for text documents. Interpret the number against the activity and the type of content.

Follow Growth Through Selected Folders

1. Compare high-level siblings

   Measure the same personal folders used in the baseline—such as Documents, Pictures, Videos, and Downloads.

   Expected result: You identify which broad branch changed.

2. Open only the growing branch

   Compare its immediate children through Properties using the same Size value.

   Expected result: The search narrows without measuring the whole drive.

3. Stop when activity explains the total

   A known project, import, archive, or offline cloud change may be a sufficient explanation.

   Expected result: The trend has context without unnecessary file-level review.

4. Review individual files only when needed

   Use Details view and size sorting within the relevant known folder.

   Expected result: File-level inspection remains connected to the trend.

Handle Measurement Differences and Unexpected Growth

• A folder total changed during calculationClose relevant applications or synchronization activity and repeat when the hierarchy is more stable.
• Storage categories do not match foldersThey classify different scopes. Use them as complementary evidence rather than one exact accounting table.
• Cloud availability changedRecord whether files became online-only or available offline; that can alter local use without changing the remote collection.
• Available space recovered on its ownTemporary data or updates may have released storage. Note the event and continue the normal schedule.
• Growth has no obvious contextRepeat the measurement, check recent installations and personal activity, and seek qualified technical guidance if other warning signs exist.