{"id":"data-transfers.is-a-large-download-checked","url":"/faq/data-transfers/is-a-large-download-checked","category":{"id":"data-transfers","title":"Data Transfers"},"subcategory":{"id":"downloads","title":"Downloads and large files"},"question":"How do I know a large download finished correctly and isn't corrupted?","alt_questions":["verify downloaded file","is the download complete and verified","download integrity check mac","corrupted download storage studio","assembled file came out the wrong size"],"short_answer":"Each piece is checked as it arrives and the finished file is checked again; the log says “…is complete and verified”. If the assembled file is wrong it isn't kept and nothing at the destination is overwritten.","answer_markdown":"Large downloads are checked before they're marked finished. Each piece is checked as it arrives, a piece that didn't arrive intact is fetched again, and when everything is put together the result is checked again. The log ends with *\"…is complete and verified\"* when all is well.\n\nIf the assembled file isn't right — for example *\"The assembled file came out the wrong size, so it wasn't kept\"* — the faulty file isn't kept and nothing at the destination is overwritten.\n\nIf the website publishes its own checksum for the file, you can also compare that yourself for extra peace of mind.\n\nRelated: [Large downloads that resume](/faq/data-transfers/large-downloads-resume-where-they-left-off)","answer_html":"

Large downloads are checked before they're marked finished. Each piece is checked as it arrives, a piece that didn't arrive intact is fetched again, and when everything is put together the result is checked again. The log ends with "…is complete and verified" when all is well.

\n

If the assembled file isn't right — for example "The assembled file came out the wrong size, so it wasn't kept" — the faulty file isn't kept and nothing at the destination is overwritten.

\n

If the website publishes its own checksum for the file, you can also compare that yourself for extra peace of mind.

\n

Related: Large downloads that resume

","answer_text":"Large downloads are checked before they're marked finished. Each piece is checked as it arrives, a piece that didn't arrive intact is fetched again, and when everything is put together the result is checked again. The log ends with \"…is complete and verified\" when all is well.\n\nIf the assembled file isn't right — for example \"The assembled file came out the wrong size, so it wasn't kept\" — the faulty file isn't kept and nothing at the destination is overwritten.\n\nIf the website publishes its own checksum for the file, you can also compare that yourself for extra peace of mind.\n\nRelated: Large downloads that resume","tags":["verification","download","integrity"],"related":[{"id":"data-transfers.large-downloads-resume-where-they-left-off","question":"Do large downloads resume where they left off if they're interrupted?","url":"/faq/data-transfers/large-downloads-resume-where-they-left-off"},{"id":"data-transfers.a-piece-couldnt-be-downloaded","question":"What does “A piece of the file couldn't be downloaded” mean?","url":"/faq/data-transfers/a-piece-couldnt-be-downloaded"}],"applies_to":"app>=4.16","last_reviewed":"2026-10-01","title":"How do I know a large download finished correctly and isn't corrupted? — Storage Studio FAQ","description":"Each piece is checked as it arrives and the finished file is checked again; the log says “…is complete and verified”. If the assembled file is wrong it isn't kept and nothing at the destination is overwritten.","crumbs":[{"name":"Home","path":"/"},{"name":"FAQ","path":"/faq/"},{"name":"Data Transfers","path":"/faq/data-transfers/"},{"name":"How do I know a large download finished correctly and isn't corrupted?","path":"/faq/data-transfers/is-a-large-download-checked"}],"jsonld":{"@context":"https://schema.org","@type":"FAQPage","url":"https://storagestudio.us/faq/data-transfers/is-a-large-download-checked","inLanguage":"en","dateModified":"2026-10-01","mainEntity":[{"@type":"Question","name":"How do I know a large download finished correctly and isn't corrupted?","alternateName":["verify downloaded file","is the download complete and verified","download integrity check mac","corrupted download storage studio","assembled file came out the wrong size"],"acceptedAnswer":{"@type":"Answer","text":"Large downloads are checked before they're marked finished. Each piece is checked as it arrives, a piece that didn't arrive intact is fetched again, and when everything is put together the result is checked again. The log ends with \"…is complete and verified\" when all is well.\n\nIf the assembled file isn't right — for example \"The assembled file came out the wrong size, so it wasn't kept\" — the faulty file isn't kept and nothing at the destination is overwritten.\n\nIf the website publishes its own checksum for the file, you can also compare that yourself for extra peace of mind.\n\nRelated: Large downloads that resume","url":"https://storagestudio.us/faq/data-transfers/is-a-large-download-checked"}}]},"fragment":"
\n
\n\n\n\n\n
\n
\n

Data Transfers · Downloads and large files

\n

How do I know a large download finished correctly and isn't corrupted?

\n

Short answer: Each piece is checked as it arrives and the finished file is checked again; the log says “…is complete and verified”. If the assembled file is wrong it isn't kept and nothing at the destination is overwritten.

\n

Large downloads are checked before they're marked finished. Each piece is checked as it arrives, a piece that didn't arrive intact is fetched again, and when everything is put together the result is checked again. The log ends with "…is complete and verified" when all is well.

\n

If the assembled file isn't right — for example "The assembled file came out the wrong size, so it wasn't kept" — the faulty file isn't kept and nothing at the destination is overwritten.

\n

If the website publishes its own checksum for the file, you can also compare that yourself for extra peace of mind.

\n

Related: Large downloads that resume

\n\n

Applies to Storage Studio 4.16 and later · Last reviewed

\n\n

Related questions

\n

Also available as Markdown and JSON.

\n
"}