Extension NavigatorFILE EXTENSION LIBRARY
日本語
Home›Generic / Ambiguous Data›.sha256
THE FILE FIELD GUIDE
.sha256

SHA-256 Checksum List

Generic / Ambiguous Data

A .sha256 file generally lists hashes and target names. It is neither the payload nor repair data; a match does not authenticate an untrusted source.

Main use
Check downloaded-file integrity
Data type
Text data
All sections, questions and sources

Content reviewed： · Editor：Kai

Opening steps

Choose your environment or purpose to see its steps.

sha256sum or equivalent checker

Preserve the original and inspect a working copy in a compatible application.

  1. Inspect target names and 64-digit hexadecimal values.
  2. Place the matching payloads in the expected paths.
  3. Use sha256sum --check for a supported list format.
Inspect the received file and its requirements

Establish dependencies and settings before proceeding.

  1. Match release version and filenames.
  2. Obtain the list from the official distribution route.
  3. Verify a signed list’s signature separately.

Menu labels and support vary by app, OS and version. Preserve the original before making changes.

Troubleshooting by symptom

  • FAILED: check version and name before redownloading.
  • No such file: check relative paths and working directory.
  • Format error: distinguish a bare digest from a list.
  • Matches but untrusted: verify origin/signature.

SHA256 → verification result

  1. Compute payload hashes and compare them with the list.
  2. Reopen the output and check it against the preservation points in this guide before handoff.

The list cannot reconstruct damaged data.

Suffix versus list syntax

The suffix does not fix the syntax; lists may use GNU or tagged formats.

Source for these steps：GNU · sha2 utilities / GNU · GNU Coreutils manual — checksums

Worked example: checks before handoff

Example: verify a release ZIP and archive it with the matching list.

Source for these steps：GNU · sha2 utilities / GNU · GNU Coreutils manual — checksums

Related-format differences

Related-format differences
Format / methodPurpose and preserved information
.sha256Check downloaded-file integrity
SFV / ASCCRC32 list / signatures, keys or other text.
SHA256 → verification resultThe list cannot reconstruct damaged data.

Handling and security

Authenticate the distribution source rather than trusting a matching pair alone.

Questions and answers

Is 64 the file size?

It is the hexadecimal digest length.

Does a match prove safety?

It confirms matching content, not safety.

Can it repair data?

It detects mismatch, not repair.

Format facts: name, steward and MIME type
Formal name
SHA-256 Checksum List
Steward / specification
GNU
MIME type
Consult the producer or delivery system. The extension alone does not establish a MIME type.

Primary and official sources