Generate File Manifest
Generate File Manifest creates a JSON array in the page rather than downloading a manifest file. For every selection it records name, exact byte size, browser-reported type or null, and a lowercase SHA-256 digest. It does not include paths, modification times, permissions, directory structure, signatures, or a hash over the manifest itself.
Runs locally — files stay on your deviceWhat fields are included for each file?
name, size, type, and sha256.
A manifest is an inventory, not proof of origin
Names and sizes describe selected File objects while SHA-256 identifies their bytes. Authenticity requires the manifest itself to be protected or signed elsewhere.
How it works
Every file is fully read and hashed, records are serialized as indented JSON in selection order, and the result can be copied.
Key concepts
One record per selection
Duplicate names remain separate array entries.
Manifest integrity is separate
Anyone able to edit the JSON can replace its hashes.
When to use it
- Create a small transfer inventory.
- Record hashes before moving a batch.
- Compare later copies against known byte identifiers.
When not to use it
- Do not call an unsigned manifest tamper-proof.
- Do not expect relative folder paths.
- Do not use browser MIME labels as security validation.
Worked examples
Two assets
- Input
logo.svg and app.js- Expected output
Two JSON objects
Selection order is retained.
Unknown type
- Input
Extensionless file- Expected output
type: null
The browser returned no MIME string.
Renamed copy
- Input
Same bytes under new name- Expected output
Different name, same sha256
Names are recorded but not hashed into the digest.
Common mistakes
Expecting a download
JSON is displayed for copying. Correction: Copy and save it deliberately.
Treating MIME as detected bytes
File.type is only browser metadata. Correction: Validate contents separately.
Publishing sensitive filenames
Names can disclose project or personal context. Correction: Review the manifest before sharing.
Best practices
- Protect or sign the saved manifest when trust matters.
- Use exact paths from another workflow if hierarchy matters.
- Recompute hashes after transfer.
Related operations and differences
Add Prefix to Filenames
Choose Add Prefix to Filenames when you need to add a prefix to selected filenames.; use Generate File Manifest specifically for manifest.
Add Suffix to Filenames
Choose Add Suffix to Filenames when you need to add a suffix before every extension.; use Generate File Manifest specifically for manifest.
Compare Two Files
Choose Compare Two Files when you need to compare two files securely by SHA-256.; use Generate File Manifest specifically for manifest.
File Checksum Comparator
Choose File Checksum Comparator when you need to compare a file digest with an expected checksum.; use Generate File Manifest specifically for manifest.
File Hash Calculator
Choose File Hash Calculator when you need to calculate a local cryptographic file digest.; use Generate File Manifest specifically for manifest.
File Size Calculator
Choose File Size Calculator when you need to inspect exact and human-readable file sizes.; use Generate File Manifest specifically for manifest.
Limitations and privacy
- No automatic file download, paths, timestamps, permissions, folder hierarchy, manifest signature, or aggregate hash.
- All files are buffered for hashing.
- MIME type can be absent or inaccurate.
Processing happens in this browser. Selected file contents are not uploaded by this tool.
Downloads and copied results remain on this device; handle them according to their sensitivity.
Frequently asked questions
Is the manifest downloaded?
No, it is shown as copyable JSON.
Are folders represented?
No.
Can duplicate filenames appear?
Yes.
Does SHA-256 include the filename?
No.