MurmurHash3 (32-bit)
Compute a MurmurHash3 (x86, 32-bit) digest, a fast non-cryptographic hash, not for security.
Runs on your device. The file is never uploaded.
MurmurHash3 (32-bit) hashes a file with the x86 32-bit variant and prints eight zero-padded hex characters beneath a line naming the algorithm and the file. The seed defaults to 0 and only has to be a number. It is then folded to unsigned 32 bits, so 1.5 and -1 quietly become 1 and 4294967295.
Questions
Is MurmurHash3 a cryptographic hash?
No. It is a fast non-cryptographic hash for hash tables, sharding and bucketing. Collisions can be produced on purpose, so it must not be used for integrity checks, signatures, password storage, or anywhere an attacker chooses the input. For those cases use SHA-256 or BLAKE3, both available through Generate all hashes.
Which variant is implemented?
MurmurHash3 x86, 32-bit, written by hand in this project rather than taken from hash-wasm, which is why it is not part of Generate all hashes. It returns a 32-bit value shown as 8 hex characters, zero padded. The x64 128-bit variant is not offered here, and its output would be different anyway.
What does the seed do?
It sets the starting state, so the same input with different seeds gives unrelated values. The default is 0, which is what most published test vectors use. Input that is not a number is refused with "seed must be a number". The value is taken as an unsigned 32-bit integer, so both sides have to use the same seed to agree.
What does the result look like?
Two lines: MurmurHash3-32, then the filename, then the 8-character hex value on the next line, zero padded so it is always the same width. Drop several files and each gets its own result with its own filename line. There is no combined digest across a set of files, and no option beyond the seed.
Why do I get a different value from another Murmur implementation?
Check the variant and the seed first. x86 32-bit, x86 128-bit and x64 128-bit are three different functions with different outputs, and a library with a non-zero default seed will not match this one. Some libraries also print the result as a signed decimal rather than hex, which is the same number shown differently.
Where does it run?
In a Web Worker in this tab, over file bytes read from your device. The function is a few lines of arithmetic written in this project, with no WebAssembly module and no network call behind it. Nothing is uploaded and the tool works offline. Being non-cryptographic changes none of that; the file simply never leaves your machine.