How Does aria2 Manage Chunk Validation?

The multi-protocol download utility aria2 optimizes file transfers by splitting files into segments and downloading them concurrently, but its ability to validate chunks and recover from corruption depends heavily on the download protocol and metadata provided. While BitTorrent and Metalink transfers natively support robust, piece-by-piece cryptographic validation to isolate and re-download only the corrupted segments, standard HTTP(S) and FTP protocols lack inherent chunk-level checksums. For standard web downloads, aria2 relies on a companion .aria2 control file to track progress, but it can only validate the absolute integrity of the completed file against an entire-file hash, meaning a single corrupted byte in a plain HTTP transfer often requires restarting the entire download.

Protocol-Level Differences in Validation

The strategy aria2 uses to handle corrupted data segments is fundamentally tied to the structural information available within the chosen download protocol.

• BitTorrent and Metalink: These protocols supply explicit “piece hashes” within their metadata (the .torrent or .metalink file). Because the cryptographic signature for every individual chunk is known beforehand, aria2 evaluates each segment immediately upon receipt.
• Standard HTTP(S)/FTP: Plain web transfers do not send piece-by-piece cryptographic metadata through standard headers. Consequently, aria2 cannot instantly pinpoint exactly which byte sequence suffered transit or storage corruption during a standard multi-connection HTTP download.

The Role of the .aria2 Control File

To coordinate downloading different segments simultaneously, aria2 creates a binary sidecar file with a .aria2 extension alongside the target file.

This control file is responsible for tracking chunk byte offsets, connection statuses, and allocated blocks. If a network drop or system crash occurs, aria2 reads this control file to safely resume writing exactly where it left off, avoiding full re-downloads. However, the control file merely maps download progress; it does not serve as a cryptographic validation matrix for individual HTTP chunks unless paired with explicit piece-hash metadata.

Automatic Repair via Chunk Hashes

When utilizing BitTorrent or a Metalink configuration with the validation flag activated (--check-integrity=true), aria2 actively protects against localized data corruption.

If a specific chunk fails its hash validation check upon download, aria2 discards that segment immediately. It then flags that specific byte range as uncompleted within its internal tracker and allocates the exact same block to be re-downloaded from available mirrors or peers. This micro-targeted correction loop ensures that corrupt segments are fixed on the fly without altering or slowing down the valid segments being fetched in parallel.

Entire-File Checksums vs. Full Re-downloads

For standard HTTP(S) downloads where individual piece hashes are completely absent, users can still provide a full-file signature using the --checksum flag (such as specifying sha-256=DIGEST).

In this scenario, aria2 cannot validate chunks dynamically during transit. It must wait until the file is completely assembled to match its total length. Once the download finishes, it runs a full integrity check. If a single segment was silently corrupted by a flaky network or a faulty storage drive, the final full-file hash check will fail. Because aria2 lacks the piece-level granularity to identify which connection brought down the bad data, it is forced to mark the entire file as corrupt and download it from scratch.