SHA-256 hash generator
Type text or choose a file to get its SHA-256 hash at once, in hex and Base64, and check a download against its published checksum.
Runs in your browser. Your text and files are hashed on your device and never uploaded to EpiFive.
How to use it
- Choose Text and type, or A file and pick the file you downloaded.
- The SHA-256 hash appears in lowercase hex. Tick Uppercase hex if the publisher lists capitals.
- Paste the published SHA-256 into the compare box and look for the green match.
- Tap Show all algorithms if you also need MD5, SHA-1, SHA-384 or SHA-512.
What SHA-256 is used for
- Checksums for operating system images, installers and packages (the SHA256SUMS files on download pages).
- TLS certificates and code signing, where the signature covers the SHA-256 of the data.
- HMAC-SHA256 for signing API requests and webhooks, and the HS256 and RS256 algorithms in JWTs.
- Content addressing: Docker image digests, Git SHA-256 repositories and Bitcoin blocks.
Not for passwords on its own
SHA-256 is designed to be fast, and a modern graphics card can try billions of guesses a second. That is ideal for checksums and bad for passwords. Store passwords with a slow, salted password hash such as Argon2, scrypt or bcrypt, which your framework almost certainly provides.
Test values
- SHA-256 of
abc:ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad - SHA-256 of an empty input:
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
For a longer hash try the SHA-512 generator, or see every algorithm at once in the hash generator.
Related tools
- Hash generator: MD5, SHA-1, SHA-256 and SHA-512 hashes of text or files, and checksum verification.
- SHA-512 hash generator: SHA-512 hash of text or a file in hex and Base64 (for SRI and npm integrity), with checksum verification.
- MD5 hash generator: MD5 hash of text or a file, with checksum verification. For checksums only, not for passwords.
- SHA-1 hash generator: SHA-1 hash of text or a file, as used by Git and older download pages, with checksum verification.
- JWT decoder: Decode a JSON Web Token’s header and payload and read its expiry times. Decode only, no verification.
Questions people ask
What is SHA-256?
SHA-256 is part of the SHA-2 family designed by the NSA and published by NIST in 2001. It turns any input into a 256-bit hash written as 64 hexadecimal characters. It is the standard checksum for software downloads, and it is used inside TLS certificates, code signing, Bitcoin and Git’s newer repository format.
Is SHA-256 secure?
Yes, for integrity and signatures. There is no known practical way to find two inputs with the same SHA-256 hash or to work back from a hash to the input. It is still a fast hash, though, so on its own it is the wrong choice for storing passwords: use bcrypt, scrypt or Argon2, which are deliberately slow.
How do I verify a SHA-256 checksum?
Choose the downloaded file, then paste the SHA-256 value from the publisher’s site into the compare box. A green match means the file is byte-for-byte what was published. If it does not match, delete the file and download it again from the official source.
How do I get a SHA-256 hash on Windows, macOS or Linux?
On Windows, run certutil -hashfile file.exe SHA256 in Command Prompt, or Get-FileHash file.exe in PowerShell. On macOS, run shasum -a 256 file.dmg. On Linux, run sha256sum file.iso.
Why is my SHA-256 different from another tool’s?
Hashes change with every byte. A trailing newline, Windows line endings (CRLF) instead of LF, a different text encoding or an extra space all give a different hash. This page hashes text as UTF-8 exactly as typed, which matches echo -n "text" | sha256sum.