{"id":"freeing-space.why-was-less-freed-than-expected","url":"/faq/freeing-space/why-was-less-freed-than-expected","category":{"id":"freeing-space","title":"Freeing up space"},"subcategory":{"id":"free-up-space-wizard","title":"Free Up Space wizard and button"},"question":"Why did a clean-up free less space than Storage Studio predicted?","alt_questions":["It freed less than it said it would","Didn't reach my target","Freed figure lower than promised","Why is the result smaller than the review said?","Storage Studio fell short"],"short_answer":"The result is measured, not predicted. Gaps usually come from your Mac holding freed space in local backups for a while, an item skipped or only partly moved, or new files written during the run.","answer_markdown":"Because the result is measured on your disk, not taken from the plan — and Storage Studio tells you when the two differ rather than claiming success either way.\n\nThe common reasons:\n\n- Your Mac may keep some of the freed space in its own local backups for a while; it usually comes back within about a day, or you can release it in [Local Snapshots](/faq/freeing-space/what-is-the-local-snapshots-manager).\n- An item was stopped, skipped because an app was using it, or only partly moved.\n- New files were written elsewhere during the run.\n\nIf an item only partly moved, its row offers **Put the link back** to finish it — see [repairing a half-finished move](/faq/freeing-space/what-is-put-the-link-back).","answer_html":"

Because the result is measured on your disk, not taken from the plan — and Storage Studio tells you when the two differ rather than claiming success either way.

\n

The common reasons:

\n\n

If an item only partly moved, its row offers Put the link back to finish it — see repairing a half-finished move.

","answer_text":"Because the result is measured on your disk, not taken from the plan — and Storage Studio tells you when the two differ rather than claiming success either way.\n\nThe common reasons:\n\n- Your Mac may keep some of the freed space in its own local backups for a while; it usually comes back within about a day, or you can release it in Local Snapshots.\n- An item was stopped, skipped because an app was using it, or only partly moved.\n- New files were written elsewhere during the run.\n\nIf an item only partly moved, its row offers Put the link back to finish it — see repairing a half-finished move.","tags":["freed space","results","snapshots"],"related":[{"id":"freeing-space.why-does-the-freed-figure-lag-behind","question":"Why does the freed figure lag behind while files are still moving?","url":"/faq/freeing-space/why-does-the-freed-figure-lag-behind"},{"id":"freeing-space.what-is-put-the-link-back","question":"What does \"Put the link back\" mean on a half-finished move?","url":"/faq/freeing-space/what-is-put-the-link-back"}],"applies_to":"all","last_reviewed":"2026-10-01","title":"Why did a clean-up free less space than Storage Studio predicted? — Storage Studio FAQ","description":"The result is measured, not predicted. Gaps usually come from your Mac holding freed space in local backups for a while, an item skipped or only partly moved, or new files written during the run.","crumbs":[{"name":"Home","path":"/"},{"name":"FAQ","path":"/faq/"},{"name":"Freeing up space","path":"/faq/freeing-space/"},{"name":"Why did a clean-up free less space than Storage Studio predicted?","path":"/faq/freeing-space/why-was-less-freed-than-expected"}],"jsonld":{"@context":"https://schema.org","@type":"FAQPage","url":"https://storagestudio.us/faq/freeing-space/why-was-less-freed-than-expected","inLanguage":"en","dateModified":"2026-10-01","mainEntity":[{"@type":"Question","name":"Why did a clean-up free less space than Storage Studio predicted?","alternateName":["It freed less than it said it would","Didn't reach my target","Freed figure lower than promised","Why is the result smaller than the review said?","Storage Studio fell short"],"acceptedAnswer":{"@type":"Answer","text":"Because the result is measured on your disk, not taken from the plan — and Storage Studio tells you when the two differ rather than claiming success either way.\n\nThe common reasons:\n\n- Your Mac may keep some of the freed space in its own local backups for a while; it usually comes back within about a day, or you can release it in Local Snapshots.\n- An item was stopped, skipped because an app was using it, or only partly moved.\n- New files were written elsewhere during the run.\n\nIf an item only partly moved, its row offers Put the link back to finish it — see repairing a half-finished move.","url":"https://storagestudio.us/faq/freeing-space/why-was-less-freed-than-expected"}}]},"fragment":"
\n
\n\n\n\n\n
\n
\n

Freeing up space · Free Up Space wizard and button

\n

Why did a clean-up free less space than Storage Studio predicted?

\n

Short answer: The result is measured, not predicted. Gaps usually come from your Mac holding freed space in local backups for a while, an item skipped or only partly moved, or new files written during the run.

\n

Because the result is measured on your disk, not taken from the plan — and Storage Studio tells you when the two differ rather than claiming success either way.

\n

The common reasons:

\n
  • Your Mac may keep some of the freed space in its own local backups for a while; it usually comes back within about a day, or you can release it in Local Snapshots.
  • An item was stopped, skipped because an app was using it, or only partly moved.
  • New files were written elsewhere during the run.
\n

If an item only partly moved, its row offers Put the link back to finish it — see repairing a half-finished move.

\n\n

Last reviewed

\n\n

Related questions

\n

Also available as Markdown and JSON.

\n
"}