UTF-8 BOM Changes Hash – Invisible BOM SHA-256 Check

Local only

Detect a leading byte-order mark that changes the exact text hashed by the browser.

6 chars · 1 line

Waiting for input

Loading hash algorithms…

Invisible Unicode hash differences

Can a UTF-8 BOM change a text hash?

Yes. A leading U+FEFF character is part of the text VetaTool hashes. It can be invisible in an editor while still changing the SHA-256 digest. This tool is free to use. No account or payment is required.

Last updated

What you can do here

  • MD5 text digests
  • SHA-1 text digests
  • SHA-256 text digests
  • SHA-512 text digests
  • Exact text byte sensitivity
  • Browser-local hashing

Steps

  1. Inspect the first code point for U+FEFF.
  2. Hash the text with and without the marker.
  3. Remove a BOM only when the data contract says it is not part of the payload.

A BOM is still input data when it reaches the text field

VetaTool does not strip U+FEFF before hashing. Two strings that render as hello can therefore represent different Unicode sequences and produce different digests.

BOM + hello vs hello

The first value begins with U+FEFF even though it may look identical on screen.

Input comparison

U+FEFF + hello
hello

SHA-256 digests

BOM + hello: 7489ebbcc2a00056ddaaaac190bce473e5c03696ea1bd8ed83cf59a174283862
hello: 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824

Common questions

Frequently asked questions

Does VetaTool remove a BOM before hashing?

No. If U+FEFF is present in the text input, it participates in the digest.

Is a BOM always visible?

No. It is commonly invisible, which is why it can cause confusing hash mismatches.

Debugging a specific Hash issue? Browse Hash troubleshooting.