FormatFlow

No tool matches “”

Try a format (“webp”, “mp3”) or a verb (“merge”, “compress”).

Loading index

↵to open

Developer Tools · Updated October 20, 2026

SHA Hash Generator

You can generate SHA-1, SHA-256, SHA-384 and SHA-512 hex digests from text or a file in your browser, with all four results shown together and a copy button for each one.

Runs in your browserFree · No sign-up · No watermark
SHA-1/256/384/512Runs in your browser
Loading the tool…

Everything runs locally in this tab. No file is uploaded while the tool loads.

This tool runs in your tab. Nothing is uploaded and no copy is stored.

How files are handled

At a glance

Works with
SHA-1/256/384/512
Processing
In your browser
Max size
Up to 100 MB per file
Price
Free, no account
Updated
October 20, 2026
All Developer Tools

About Hash Generator

Checksums prove that a download or a config file is exactly what it should be, and a hash generator is the quickest way to get one. SHA-256 is the usual choice for verifying files and signing API requests, while SHA-1 appears in older manifests and SHA-384 and SHA-512 in certificate tooling. This tool computes all four from one input and shows every digest at once, so you can compare against a published checksum without switching modes.

Hashing runs through the Web Crypto API that every current browser ships, so no extra library is loaded and the page works offline once open. Text is hashed as UTF-8 bytes exactly as typed, and files are read locally with the File API, which means a 90 MB installer can be checked without sending any part of it over the network. MD5 is deliberately absent because Web Crypto does not implement it.

What this tool does

The details that matter when you use Hash Generator for real work.
  • Four algorithms at once

    SHA-1, SHA-256, SHA-384 and SHA-512 are computed from the same input and shown side by side, with the bit size and hex length of each digest labeled.

  • Hash a file without uploading it

    Drop any file up to 100 MB and its bytes are read with the File API and hashed in the tab, so the file never leaves your device.

  • Text hashed as UTF-8

    Text is encoded as UTF-8 before hashing with no hidden newline added, so the digest matches the bytes a UTF-8 file with the same content would have.

  • Digests update as you type

    Text results refresh after a short pause on every edit, so there is no separate Hash button to remember and no stale result to copy.

  • One copy button per digest

    Every algorithm card has its own copy button that briefly confirms the copy, which matters when four long hex strings sit on the same screen.

  • Works offline after loading

    Once the page is open, hashing makes no network requests at all, so the tool also works on a locked-down network or with the connection off.

How to use Hash Generator

No account, no installation — the whole job happens in this browser tab.
  1. 01

    Choose text or file

    Pick the Text tab for a value you can paste, or the File tab to hash the raw bytes of a file on disk.

  2. 02

    Provide the input

    Type or paste the text, or drop a file into the drop zone; files up to 100 MB are read locally, never uploaded.

  3. 03

    Read the four digests

    Each algorithm card shows the full hexadecimal digest, its bit size and how many hex characters it contains.

  4. 04

    Press Hash file when hashing a file

    Text is hashed automatically, but files start only when you press Hash file so a large file is never read by accident.

  5. 05

    Copy or compare

    Use the copy button next to a digest and compare it with a published checksum; hex digests are case-insensitive.

How this tool works

Works with
SHA-1/256/384/512
Processing
Client-side, in your browser. Nothing is uploaded.
Maximum size
Up to 100 MB per file
Requirements
Chrome, Edge, Firefox or Safari · Secure context (HTTPS or localhost) for Web Crypto

Limitations worth knowing

  • No MD5: Web Crypto does not implement it, and no third-party hash library is loaded.
  • Plain digests only: there is no HMAC, no salt, no keyed hashing and no password hashing.
  • Files are capped at 100 MB because the whole file is read into memory before the digest is computed.
  • Text is hashed as UTF-8 with no added newline, and file hashes cover raw bytes, so line endings and hidden whitespace change the result.

Privacy and file handling

Text and files are hashed inside this browser tab using the Web Crypto API. Nothing is uploaded, stored, logged or cached, and no digest leaves the page unless you copy it. Hashing makes no network request, so the tool also works offline once the page has loaded.

Read the full privacy policy

Hash Generator FAQ

Short, direct answers to the questions people ask before using this tool.
What is the difference between SHA-1, SHA-256, SHA-384 and SHA-512?
All four are SHA algorithms, but they produce digests of different sizes: 160, 256, 384 and 512 bits. SHA-256 is the normal default for file checksums and API signatures. SHA-1 still works as a checksum but is no longer collision-resistant, so avoid it for security decisions.
Why is there no MD5 option in this hash generator?
MD5 is not part of the Web Crypto API, so supporting it would mean loading a separate JavaScript implementation. MD5 is also broken for security purposes because practical collisions exist. Use the md5sum command on Linux or Get-FileHash -Algorithm MD5 in PowerShell when you need that legacy checksum.
Can I hash a file without uploading it?
Yes. The file is read with the browser File API and hashed with Web Crypto inside the tab. No bytes are sent to FormatFlow or anyone else, and the only limit is the 100 MB cap that keeps the tab's memory use predictable.
Why does the digest of a file differ from the digest of the same text?
A file is hashed as its exact bytes, including line endings and any trailing newline. The text tab hashes the UTF-8 encoding of what you type, with no newline added. Copying file content into the text tab can therefore produce a different digest.
How do I check a downloaded file against a published hash?
Copy the digest of your file and compare it with the checksum published by the vendor. Hex digests are case-insensitive, and checksum files commonly use the format hash, two spaces and the filename, so compare the hash part only.
Is hashing the same as encryption?
No. Encryption is reversible with the right key, while hashing is one-way, so the original input cannot be recovered from the digest. That is why hashes suit integrity checks and why plain SHA hashes are not a good way to store passwords on their own.
Does the tool salt the hash or add an HMAC key?
No. These are plain unkeyed digests, which is what a checksum comparison needs. For message authentication use HMAC with a secret key in your own code, and for password storage use a dedicated password hashing function such as Argon2 or bcrypt.
Can two different files produce the same hash?
A collision is always theoretically possible because a fixed-length digest cannot encode every possible input. For SHA-256, SHA-384 and SHA-512 no practical collision is known. SHA-1 collisions have been demonstrated, which is why it is marked legacy here.

Background reading

Format guides that explain the trade-offs behind Hash Generator.