Why does a trailing newline change the checksum?

The newline changes the input bytes. Text is UTF-8 encoded exactly as entered; a file digest uses the file bytes rather than the displayed filename.

Does a matching digest prove who published a file?

No. It compares bytes with a supplied expected value. Obtain that value through a trusted channel; plain hashes can be recomputed by anyone.

When is HMAC different from a plain digest?

HMAC uses a shared secret to authenticate a message under that key. A plain digest has no secret. The published examples deliberately use plain SHA-256 and contain no private key.

Security

Hash, HMAC & Checksum Studio

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

Online tools Pricing

Input0 characters

Result0 characters

Prefer a native workflow?

Keep Hash, HMAC & Checksum Studio one shortcut away.

DevSexy for Mac puts the same private workflow in a focused desktop app, with global shortcuts and no browser tab to manage.

Global shortcutOffline-readyLocal processing

Try the Mac app free

This browser tool remains free.

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.

Run a reproducible example

Compute the known SHA-256 digest of abc and verify the full expected representation.

Using an example replaces the current input, reference input, operation, and options. Public demonstration data only.

Hash exactly three UTF-8 bytes

SHA-256, hexadecimal, no trailing newline. Plain digest mode has no secret.

Input

abc

The output matches the complete public SHA-256 vector for abc.

ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad

Compare a complete checksum

Use the full hexadecimal expected digest and no HMAC key.

Input

abc

MATCH confirms equality with the supplied digest; it does not authenticate the publisher.

Verdict: MATCH

Continue with a related task

Base64 Text

Encode and decode UTF-8 text with standard and URL-safe Base64 variants.

Text Diff

Compare two texts by line, word, or character in a local worker.

X.509 Certificate & PEM Inspector

Decode certificates, SANs, key usage, and validity without sending private material away.

Repeat the task in DevSexy for Mac

Use the native app for repeated offline work and direct Option shortcuts.

Direct answer

What is Hash, HMAC & Checksum Studio?

Calculate hashes and HMACs online for UTF-8 text or local file bytes, then compare complete SHA-256, SHA-384, SHA-512, SHA-1, or MD5 checksum values.

What can it do?

Hash
HMAC
Verify

How to use Hash, HMAC & Checksum Studio

01
Prepare the input
Choose exact source bytes, including any line endings or normalization.
02
Choose the operation
Select digest versus HMAC, the algorithm, and the output representation.
03
Review the evidence
Verify a complete expected value from a trusted source and keep authentication separate from byte equality.

Frequently asked questions

Why does a trailing newline change the checksum?: The newline changes the input bytes. Text is UTF-8 encoded exactly as entered; a file digest uses the file bytes rather than the displayed filename.
Does a matching digest prove who published a file?: No. It compares bytes with a supplied expected value. Obtain that value through a trusted channel; plain hashes can be recomputed by anyone.
When is HMAC different from a plain digest?: HMAC uses a shared secret to authenticate a message under that key. A plain digest has no secret. The published examples deliberately use plain SHA-256 and contain no private key.