In this article
A small .app can accompany gigabytes of downloads or project data elsewhere. A file can also describe more bytes than are physically allocated to it. Before looking for something to delete, establish which of these differences explains your comparison.
Compare the same app and scope first
In Finder, open Applications, select the app, and choose File → Get Info or press Command-I. Note its location and size. If a size calculation is still in progress, let it finish before recording the result. Apple documents this native inspection in Get file, folder, and disk information.
Next, open System Settings → General → Storage and inspect the relevant category and item. Record the exact label: the Applications category total, one application entry, and a disk’s available space answer different questions. Do not assume every Storage view attributes every supporting file to its parent app.
Check for duplicate copies too. Finder may have selected an app in Downloads while another view refers to its installed copy. Matching the name is insufficient when the paths or versions differ.
A useful comparison note has four fields: path, measurement, unit, and time. “Example.app, Get Info size, bytes, 10:00” is more useful than “the app is huge.” Quit an app that is actively downloading files before comparing its data at two different moments, if doing so will not interrupt work you need to save.
The app bundle is only one location
A macOS application bundle contains the app’s executable code and bundled resources. It is not necessarily a container for everything the app has downloaded or created since installation.
Apple’s file-system directory guide describes separate locations for application support files and caches. An app may also use a sandbox container, a shared group container, or folders you selected for projects and downloads.
| What you inspect | What the total can describe | What it cannot establish alone |
|---|---|---|
One .app bundle | Files inside that selected bundle | All user data associated with the app |
| A support-data folder | Files in that selected location | Whether they are expendable |
| A Storage category | macOS’s current classification of storage | Ownership of every file in a large folder |
| Free or available disk space | A volume-level capacity measurement | The size of one application |
For example, an app bundle may remain roughly the same size while its downloaded content grows. That does not require the bundle’s Get Info total to increase. The next step is to inspect the app’s own storage or download settings, where supported, and identify the content’s location.
For ownership questions, see Containers versus Group Containers. A shared location especially deserves care: more than one component may rely on it.
Logical bytes and allocated space can differ
Logical size describes a file’s length. Allocated space describes storage assigned to the file. Filesystem allocation, sparse regions, and other storage features can make those numbers differ in either direction.
We measured two disposable files on an APFS volume on macOS 15.7.5 on October 2, 2026. One contained a single byte. For the other, we wrote one byte, sought to the end of a 64 MiB span, and wrote another byte, leaving a sparse region between them.
| Test file | Logical length | Allocated bytes reported in our test |
|---|---|---|
| One-byte file | 1 byte | 4,096 bytes |
| Sparse 64 MiB file | 67,108,864 bytes | 16,384 bytes |
We read logical length from stat and multiplied its allocated-block count by 512; du -k separately reported 4 KiB and 16 KiB. These are observed results for these files and this filesystem, not guaranteed allocation sizes for every Mac.
The tiny file occupied more storage than its content length. The sparse file occupied much less than its logical length. Apple’s APFS format comparison confirms support for sparse files. This experiment illustrates the distinction; it does not prove that a particular app uses sparse files.
An allocated total is also not a promise of how much free space deletion will produce. APFS can share storage between file clones, and snapshots can retain data. Apple’s APFS FAQ explains copy-on-write cloning. Avoid adding up file totals and treating the sum as uniquely reclaimable capacity.
Check units before explaining a small mismatch
Decimal GB and binary GiB use different divisors. One billion bytes is 1 GB, but about 0.93 GiB. A difference near that scale may be a presentation issue; a 200 MB app compared with 80 GB of storage needs a broader explanation.
For a selected folder, Terminal’s native du can provide another read-only observation:
du -sk "/Applications/Example.app"
Replace the placeholder with the exact path. On macOS, -s requests a summary and -k reports usage in 1,024-byte units. This is a filesystem-usage observation, not a list of everything owned by that app and not a safe-deletion recommendation.
If a scan reports access errors, retain them. A partial result should not be compared as though it were a complete inventory. Do not grant broad permissions just to make two differently scoped numbers match.
Turn the comparison into a specific decision
Work through this short checklist before removing anything:
- Match the path. Confirm the selected bundle or data folder, including duplicates.
- Match the scope. Separate bundled code, app-created data, and whole-disk totals.
- Match the measurement. Record logical or allocated size and the displayed units.
- Identify the content. Use the app’s own controls to inspect downloads or projects where available.
- Plan recovery. Back up important data and confirm what a removal would affect.
If Application Support is the large location, use the retention checklist in Can you delete Application Support files?. A folder’s size does not tell you whether it holds disposable cache or irreplaceable local work.
VaultDog’s Storage view can bring the app bundle and discovered related locations together. Its scanner measures allocated file sizes within bounded scans; protected or unmeasured locations can make the result a lower bound. That is useful context for finding the next folder to investigate, not an exact disk-accounting or reclaimable-space guarantee.
The useful outcome is an explained difference: “this is the bundle, that is downloaded content,” or “these tools use different measurements.” Once the scope is clear, you can make a focused decision about actual files instead of trying to force every total to agree.
