SHA-256 File Checksum
Compute real SHA-256 and SHA-512 over selected raw file bytes via WebCrypto or tested incremental local library; keep file names out of digest.
SHA-256 File Checksum workspace
MD5 is a legacy checksum, not secure for authenticity. CRC32 detects accidental corruption and is not authentication. A matching checksum does not prove provenance.
Limits: 12 files, 20 MiB each, 64 MiB input; 2,000 archive entries, 32 MiB per decoded file, 128 MiB total, maximum 100× expansion. Choose files or a folder; empty folders may be unavailable. Folder selection varies by browser; the file picker is the fallback.
Candidate workspace — select local files to begin.
Progress counts files read; native codec completion has no reliable time estimate. Cancel terminates this job's worker.
How to use SHA-256 File Checksum
Multiple-file table, algorithm select, uppercase/lowercase output, copy/export, processing progress. Select local files, inspect the preview, adjust settings, then process and review the actual result before exporting. Reset clears the job and restores defaults.
Compatibility and safe processing
Hash fixture bytes match Python hashlib exactly (including empty file and Unicode filename). All processing happens locally in a disposable worker. ZIP supports Store and Deflate, UTF-8 paths, CRC checks and safe regular files. ZIP64, legacy non-UTF8 paths, alternate Unicode path fields, encrypted entries and unsupported methods fail closed. TAR supports USTAR and bounded local PAX path records; special entries are rejected. GZIP is one stream, not a multi-file archive; concatenated members are unsupported. Decompression limits apply to actual output. Unicode path comparisons use NFC and case folding. CSV is UTF-8 RFC4180 with optional BOM. Selected folder trees omit empty folders unavailable to browser APIs. No tool can inspect unselected directories.