Browser 106

max 100MB

Inspector security/hash-generator

Hash Generator

Overview

This hash generator computes MD5, SHA-1, SHA-256, SHA-384 and SHA-512 from the same input in one pass, so there is no algorithm to pick: paste text or drop a file and all five digests appear together, each on its own row with its own copy button. A compare field takes the checksum a download page published and answers in words — match, or no match — rather than leaving you to read two long hex strings character by character; paste the line as it came, since output from sha256sum, shasum, certutil and BSD md5 is recognised, filename and all. Hashing uses the browser's own Web Crypto, so the file is read on your device and neither it nor the digests are uploaded.

Verifying a DownloadHash the file you just downloaded and paste the publisher's checksum into the compare field; the verdict comes back as a word rather than as two strings to eyeball.
Satisfying Several Checksum FormatsA mirror lists MD5, a release page lists SHA-256, an internal system wants SHA-512. All five come from one read of the input, so you copy whichever one is being asked for.
Detecting a Silent ChangeHash a config file or a dataset before and after a move, a backup or an edit, and confirm that not a byte differs.
Deriving a Stable IdentifierTurn a string or a file into a fixed-length key for deduplication, cache busting, or a content-addressed storage prototype.
Reading an Older Checksum ListPlenty of long-lived distributions still publish MD5 or SHA-1 only. Both are computed here alongside the modern digests, so an old list can be checked without installing anything.

Set

Security Tools 26

Neighbours

01 AES File & Text Encryptor 02 Base64 Decode 03 Base64 Encode 04 CSR Generator 05 DER to PEM Converter 06 JWT Sign

Specification

Command: security.hash_generator
Set: Security
Input: MIXED
Output: PLAIN
Max file: 100MB
Batch: single file

PLAIN OCTET-STREAM

Runtime

Engine: WebCrypto · OpenPGP.js
Threads: single
Isolated: —
WebGPU: —
Memory: —

Transport 0 B

The file is opened, worked on and written back inside this tab. No upload step exists in this tool — there is nowhere for the bytes to go.

Keys

Search: ⌘K
Panels: ⌘1 · ⌘2
Full width: F
All keys: ⌘/

How it works

Paste text or drop a file

Type or paste text into the input, or drop a file onto it. The file is read in your browser; nothing is uploaded.

Read all five digests

MD5, SHA-1, SHA-256, SHA-384 and SHA-512 are computed from the same input in one pass, so there is no algorithm to choose. Each digest sits on its own row with its own copy button.

Compare it with a published checksum

Paste the checksum from a download page into the compare field and the answer comes back in words: match, or no match. Paste the line as it came — output from sha256sum, shasum, certutil and BSD md5 is recognised, filename and all.

Frequently asked

Which of the five digests should I use?

You do not have to choose — all five are computed from the same input at once. Match whichever one the other side published. SHA-256 is the usual modern choice; MD5 and SHA-1 are shown because older release pages still list them, not because they are recommended.

Are hash functions reversible?

No. A hash is one-way: the digest does not carry enough information to rebuild the input. A short or guessable input can still be found by trying candidates, which is why a bare hash is not a password store — that needs a slow, salted function such as bcrypt or argon2.

Why would I hash something?

Almost always to check that bytes did not change. A publisher posts the SHA-256 of a download, you compute it yourself, and the two either match or they do not. The same idea covers confirming a backup copied cleanly, spotting an edited config file, and deriving a stable identifier from content.

Is my data secure during hashing?

Yes. Text and files are read and hashed in your browser. Neither the input nor the digests are sent anywhere, so a confidential document can be hashed here without leaving your device.

Can two different inputs have the same hash?

For SHA-256 and above, no collision has ever been found and none is expected. For MD5 and SHA-1 collisions are not theoretical — two different files with the same digest have been constructed deliberately — so treat those two as checks against accidental corruption, not against tampering.

Keys

Search: ⌘K
Panels: ⌘1 · ⌘2
Full width: F
All keys: ⌘/

Related · Security Tools