Skip to tool
Security

Hash, HMAC & Checksum Studio

Calculate and verify digests for text and files with streaming workers.

Web Worker Local onlyTools
Input0 characters
Result0 characters
Ready

Byte evidence laboratory · tools, not magic

The digest begins before the algorithm.

A hash consumes bytes. If a checksum does not match, first prove that both systems hashed the same encoding, normalization, newline sequence, and file contents—then compare algorithms and output notation.

Intake manifest#BYTES-0514
TEXT · UTF-8

Characters are encoded into bytes

FILE · UNTOUCHED

The selected ArrayBuffer is transferred directly

Café43 61 66 C3 A9
你好E4 BD A0 E5 A5 BD
LF0A
CRLF0D 0A

Visually similar text can have different Unicode normalization or invisible trailing bytes. The receipt records the source, not just the result.

Two instruments

Digest and HMAC answer different questions.

INSTRUMENT 01

PLAIN DIGEST

message → H(message)

Anyone with the message can reproduce it.

Integrity comparison only

INSTRUMENT 02

KEYED HMAC

secret + message → HMAC

Only parties sharing the secret can reproduce it.

Integrity + shared-secret authentication

Algorithm status rack

Output width is not the whole security story.

SHA-256256 bitsCURRENT

General integrity and content-addressing

SHA-384384 bitsCURRENT

Protocol or policy compatibility

SHA-512512 bitsCURRENT

Wide SHA-2 output

SHA-1160 bitsLEGACY

Compatibility checks only; collision-vulnerable

MD5128 bitsLEGACY

Old checksum compatibility; collision-vulnerable

Mismatch autopsy

Same-looking input, different evidence.

Newline

LF 0ACRLF 0D 0A

Unicode

é · U+00E9e + ◌́ · U+0065 U+0301

Text encoding

UTF-8UTF-16LE

Representation

hex lowercaseBase64 with padding

File handling

raw bytestext-mode conversion

Digest

complete valuetruncated prefix

Verification receipt

Compare the complete normalized representation.

SOURCErelease.tar.zst · raw bytes
ALGORITHMSHA-256
EXPECTED64 hex characters
ACTUAL64 hex characters
VERDICTMATCH / MISMATCH
COMPLETE VALUE REQUIRED

A match ties the local bytes to the expected value you supplied. Publisher identity still depends on how that expected value was authenticated.

Direct answer

What is Hash, HMAC & Checksum Studio?

Hash UTF-8 text or untouched local file bytes, generate HMACs, and compare complete SHA-256, SHA-384, SHA-512, SHA-1, or MD5 digests without uploading data.

What can it do?

  • Hash
  • HMAC
  • Verify

How to use Hash, HMAC & Checksum Studio

  1. 01

    Choose a task

    Select Hash, HMAC, and Verify in the workspace.

  2. 02

    Provide the input

    Enter text or choose a file. The input stays in the browser processing path.

  3. 03

    Review the result

    Run the tool, inspect its result and diagnostics, then copy or download the output when the page offers that action.

Frequently asked questions

What is Hash, HMAC & Checksum Studio?
Hash UTF-8 text or untouched local file bytes, generate HMACs, and compare complete SHA-256, SHA-384, SHA-512, SHA-1, or MD5 digests without uploading data.
What can Hash, HMAC & Checksum Studio do?
Hash, HMAC & Checksum Studio supports Hash, HMAC, and Verify. Each mode is available directly in the page workspace.
Does Hash, HMAC & Checksum Studio upload my data?
Hash, HMAC & Checksum Studio processes your input locally in the browser. DevSexy does not add an upload, account, or server-processing step to this workflow.
DevSexy processes tool input locally. No paste tracking, accounts, or upload step.