A progress bar reaches 100%, but the application still needs to establish that the stored file matches what the user selected. For a project drawing, supplier document or large media file, verify the transfer before marking the attachment ready for downstream work.
Define what a completed upload means
Track the file reference, expected size, upload attempt and validation result. Keep a clear distinction between bytes sent, storage accepting the upload and the application approving the attachment for use. For example, a procurement portal should keep a drawing in a pending state until transfer validation finishes, then link the validated object to the submission.
Use a supported checksum across the transfer
A checksum represents the file’s bytes using a chosen algorithm. Calculate it at the sending boundary and have storage validate the supplied value when that upload path supports it. AWS documents supported checksum algorithms and full-object or composite checksum types for S3 uploads. The client, SDK and storage request must agree on the algorithm and checksum type. S3 upload integrity documentation.
Do not assume that every S3 ETag is the MD5 digest of the original file. Multipart uploads have different semantics. If a workflow uses part-level checksums, verify the completion step and the final integrity method as well. A checksum validates byte consistency. File type checks, malware scanning and access controls still need their own acceptance rules. The document upload review guide covers those requirements.
Test interrupted and conflicting attempts
- Upload a small known file and a representative large file through the actual application. Confirm the stored version and validation result are attached to the correct submission.
- Supply an intentionally mismatched checksum in a controlled test. Confirm the upload is rejected or quarantined and that the user receives an actionable status.
- Interrupt and retry an upload. Ensure the retry cannot mark an older or partial attempt as complete, and document cleanup for abandoned multipart uploads.
Keep the original file until the application confirms acceptance. If the network is unreliable in the field, the offline app sync guide explains how to show pending work clearly.
Review your file upload acceptance checks
ITZ’s API development and integration service can review the upload contract, storage validation and retry states. Describe the file types and where completion is confirmed.
Bring the storage service, typical file sizes and an example of a failed transfer. Review Your File Upload Integrity Checks