SHA-1 hash generator.
Paste text or drop a file and read its SHA-1 digest as you type. SHA-1 is the web's old standard hash, broken by a public collision in 2017 and kept for legacy ids and checksums; everything runs in your browser and nothing is uploaded.
SHA-1 hash generator.
Need the UI around it? With Pro, your AI agent builds the form, the result card and the rest of the page from a prompt.
Get ProHow it works
4 steps, no account. It runs in your browser and nothing is uploaded.
Enter text or a file
Type or paste anything, or drop a file onto the input. The digest updates with every keystroke.
Pick the algorithm and format
SHA-1 is the default; switch to SHA-1, SHA-256, SHA-384 and SHA-512, and read the digest as hex or Base64.
Key it, when you need a signature
Turn on HMAC and enter a secret to sign the input instead of hashing it.
Verify, copy or download
Paste a published digest to confirm a download, or copy and download your own.
The SHA-2 family against the others
SHA-2 is the default for a reason. The family is unbroken and everywhere; SHA-1 and MD5 are checksums, not security; SHA-3 and BLAKE3 are the alternatives.
SHA-256
256 bits, 64 hex characters, since 2001. No known attack. Fast, and hardware-accelerated on most CPUs. Checksums, TLS, Bitcoin, JWT HS256.
SHA-512
512 bits, 128 hex characters, since 2001. No known attack. Faster than SHA-256 on 64-bit CPUs for long inputs. Lockfile integrity, long-term archives.
SHA-384
384 bits, 96 hex characters, since 2001. No known attack; the same engine as SHA-512. TLS cipher suites, Subresource Integrity.
SHA-224
224 bits, 56 hex characters, since 2004. SHA-256 with other starting values, cut to 28 bytes. The 112-bit security level, where a shorter digest matters.
SHA-1
160 bits, 40 hex characters, since 1995. Broken: collisions were found in 2017. Legacy Git objects; not for anything new.
MD5
128 bits, 32 hex characters, since 1992. Broken: collisions in seconds. The fastest, and only for checksums against accidental corruption.
SHA3-256
256 bits, 64 hex characters, since 2015. No known attack. A different construction from SHA-2 (a sponge), immune to length extension; slower in software.
BLAKE3
256 bits, 64 hex characters, since 2020. No known attack. The fastest modern hash, parallel by design. Large files, deduplication.
Related tools
More hash generators. Every one free, in the browser.
Pricing
Build it with Pro
The tool is free. Pro adds 6,000+ blocks, premium templates and the MCP server, so your AI editor builds the product around it.
4.9/5 out of 5 · 150+ reviewsfrom 150+ founders and developers.
- Secure checkout via Stripe
- Code lives in your repo
- Keep what you've shipped if you cancel
- License terms
Questions and answers
Before you trust the result: what to know about the format, the limits, your data and the tools next to it.
SHA-1 is a 160-bit cryptographic hash published by NIST in 1995, written as 40 hexadecimal characters. It was the standard hash of the web's first twenty years: TLS certificates, Git object ids, PGP fingerprints and countless signatures were SHA-1.
No. In 2017 Google and CWI published SHAttered, two different PDFs with the same SHA-1 digest, and in 2020 a chosen-prefix collision (two documents of the attacker's choosing) cost about 45,000 dollars of computing. Browsers stopped trusting SHA-1 certificates in 2017; Git is moving its object format to SHA-256.
Only to identify things in systems that already use it: Git commits, old package feeds, legacy APIs that expect a SHA-1 of the payload. As a checksum against accidental corruption it still works. For anything an attacker could influence, a signature, a certificate, deduplication of untrusted files, use SHA-256.
Yes. HMAC's security does not rest on collision resistance, so HMAC-SHA-1 was not broken by SHAttered and remains in old OAuth 1.0 signatures and TOTP authenticator codes (RFC 6238 defaults to HMAC-SHA-1). New designs should still pick HMAC-SHA-256.
Git hashes a header ("commit", "blob" or "tree", a space, the length, a NUL) followed by the content, so the SHA-1 of a file's bytes is not its Git blob id. Prefix the header, or use git hash-object, to get the id Git shows.
Nothing leaves your browser. The hash is computed on your machine, by the browser's Web Crypto API or a WebAssembly build of the algorithm loaded on first use, and the page makes no request with your input. You can load the page, go offline and keep hashing.
Drop the file onto the input or choose it with the button, and the tool reads it in your browser and hashes the bytes. Files up to 1 GB work; past that the browser would need the whole file in memory, so the tool declines. Paste the published digest into the Verify field to compare.
Hex is the common form: 40 characters from 0 to 9 and a to f, the same value in upper or lower case. Base64 writes the same 20 bytes in fewer characters, and Base64url swaps + and / for - and _ with no padding. Switch the output and the digest is re-encoded, not recomputed.
Text is hashed as UTF-8 bytes, which is what every language and command line does by default. A trailing newline changes the digest, so `echo -n` or this tool's input, with no newline added, matches a command-line tool run on a file without one.
Turn on HMAC and enter the secret: the tool computes HMAC-SHA-1 over the input with that key, the standard RFC 2104 construction, so the value matches what a server-side HMAC library produces. The key is hashed as UTF-8 text.
No. The SHA-1 hash generator is free and opens without a sign-in, an account or an install.
Nothing. The SHA-1 hash generator holds your input in the page's memory, so closing or reloading the tab clears it, and it saves nothing in this browser.
The toolbar switches to SHA-256, SHA-384, and SHA-512 without leaving the page. Each one reads the same input, so you can compare digests side by side.
SHA-1 runs on the browser's own Web Crypto API, so there is nothing to download and it is the fastest path.
Yes: the File to SHA-1 page has the same algorithms and options and opens on the file pane. Files are read in your browser and never uploaded.
Not on its own. SHA-1 is built to be fast, and fast hashes are cheap for an attacker to guess against. Passwords need a salted, deliberately slow hash: use Argon2id, Argon2d, and bcrypt from the hash generators, which draw a fresh random salt each time.
Closest to the SHA-1 hash generator: File to SHA-1, MD5 hash generator, RIPEMD-160 hash generator, SHA3-256 hash generator. Each opens on its own page, free and in the browser.
The SHA-1 hash generator is one of 64 in its group. The group's page, /tools/hash, lists them all.
The tool is free. Its interface is built from shadcn.io's own components (Button, Input, Slider and the rest of the registry under /ui), which come in React, Vue, Svelte and Solid. Pro adds the blocks and templates for the product around it.
4.9 out of 5 from 150+ developers
Build the product around it
Every block, template and icon, installed by your AI agent in your theme. The tools stay free.
Get Pro





