Skip to workspace
PixelOkay
File Integrity StudioAll tools
Tools
DEVELOPER TOOLS / LOCAL-FIRST SECURITY

File Integrity Studio

Compute cryptographic checksums, check release manifests, and build audit-ready reports. Your files never leave this browser.

Private by designNo upload · No account · No deletion
0Files queued
0Hashed
—Verified checks
—Verification issues
Add files to begin. Nothing has been uploaded or processed.

File workspace

View calculated hashes and verification status

FilenameSizeStatusSHA-256SHA-512
No files yet. Add a few to see checksums here.

Verify a checksum

Compare a selected file against a checksum copied from a trusted source.

Choose a hashed file and enter its expected checksum.

Export & reports

Manifests include completed checksums; reports include current verification status and failed scans.

How File Integrity Studio works

01 · Generate

Calculate standard SHA-256 and/or SHA-512 digests from the exact file bytes, reading in bounded chunks to limit memory use.

02 · Verify

Import a publisher’s checksum manifest or paste a trusted expected digest. Missing and ambiguous filenames are flagged, never guessed.

03 · Document

Export GNU-compatible manifests and structured verification results for audits, releases, archives and downloads.

Files are processed inside this browser using a dedicated Web Worker. The application does not store or send file data, and never modifies your originals. Using a verified checksum from an untrusted source does not establish authenticity.

Using File Integrity Studio

Hash batches of local files with SHA-256/SHA-512, compare digests or imported manifests, and export checksum and verification reports.

Workflow

  1. Select files for a checksum batch and review which entries were processed and which were skipped or ambiguous.
  2. Compare computed digests with a trusted publisher value or import a checksum manifest, then inspect each match, mismatch, missing, or unprocessed state.
  3. Export a checksum manifest or report, keeping the expected digest and its source alongside the results.

Worked example

Select a downloaded software archive and compare its SHA-256 value with the digest published through a trusted channel. Review the filename and verification status, then export a manifest for your records.

Limits and data handling

A matching digest establishes agreement with the expected value; it does not prove that the publisher or expected digest is trustworthy, nor does it establish malware safety. The tool does not change or delete the selected files. Batches support up to 2,000 entries and a 100 GiB per-file cap; those limits are not performance guarantees. Worker and secure-context Web Crypto behavior need real-origin acceptance. Re-scans invalidate old manual verification.

Frequently asked questions

Does a matching hash prove that a file is safe or authentic?

No. It confirms the file matches the expected digest you supplied; trust depends on the source and integrity of that expected digest.

Can the tool change or delete the files it hashes?

No. It reads the selected files for hashing and comparison; it does not modify or delete them.

Related tools