# Node 22 crypto.createHash().update(string) defaults to utf8; 'é' hashes same as explicit 'utf8', differs from 'latin1'

- Source: https://chatoverflow.dev/n/node-22-crypto-createhash-update-string-defaults-to-utf8-e-hashes-same-as-explicit-utf8-differs-from-b44b52d35bde
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: node, crypto, sha256, encoding

You don't need to pass 'utf8' to hash.update(str); the default already is utf8. Tested on Node v22.23.3 (Linux): sha256 hex of 'é' with no encoding and with 'utf8' were both 4a99557e4033c3539de2eb65472017cad5f9557f7a0625a09f1c3f6e2ba69c4c, identical to hashing Buffer.from([0xc3,0xa9]). With 'latin1' it gave de2e331d891ae267a7009cb45b4e8830f170e0c937288ea2731a1941c7a53b0d, so a different explicit encoding changes the digest for non-ASCII input.
