File to MD4.

MD4 is a 128-bit hash Ronald Rivest designed in 1990 (RFC 1320), the ancestor of MD5, SHA-1 and RIPEMD. It was built for speed on 32-bit CPUs: three rounds over 512-bit blocks, and it still runs over a gigabyte a second in software.

Completely. Hans Dobbertin found collisions in 1996; by 2004 Wang's attack produced them by hand, and today a full collision takes microseconds. Preimage attacks are also known at reduced cost. It must not be used for anything that needs security.

NTLM. Windows stores a user's password as the MD4 of its UTF-16LE encoding, and NTLM authentication, Kerberos RC4 keys and pass-the-hash attacks all turn on that value; the eDonkey network also identified files by an MD4-based hash. To match an NTLM hash, encode the password as UTF-16LE first; this tool hashes UTF-8.

Only to reproduce a value a legacy system expects, or to study how hash functions evolved. For a checksum, CRC32 or xxHash is faster and honest about what it is; for security, SHA-256 or BLAKE3.

Nothing leaves your browser. The file is read on your machine and hashed there, by the browser's Web Crypto API or a WebAssembly build of MD4 loaded on first use; the page makes no request with its bytes. You can load the page, go offline and keep hashing.

Drop the file onto the pane or choose it with the button. It is read into memory and hashed at once, with no size steps and no upload progress because there is no upload. Files up to 1 GB work; a 100 MB file takes well under a second on MD4.

Paste the digest the publisher gave you into the Verify field, in hex of either case, with or without spaces, colons or a 0x prefix, or in Base64. The tool says whether it matches the file you dropped. A match means the bytes are exactly the ones that were published.

Hex by default, 32 characters; Base64 and Base64url are one click away and re-encode the same 16 bytes. The download button saves a line in the `digest filename` form that sha256sum-style tools read.

Yes: turn on HMAC and enter the secret, and the file is signed with HMAC-MD4 rather than hashed, the same construction a server uses to sign an upload or a webhook payload.

No. The "File to MD4" tool is free and opens without a sign-in, an account or an install.

Nothing. The "File to MD4" tool holds your input in the page's memory, so closing or reloading the tab clears it, and it saves nothing in this browser.

The toolbar switches to MD5, SHA-1, and RIPEMD-160 without leaving the page. Each one reads the same input, so you can compare digests side by side.

MD4 is computed by a WebAssembly build from the hash-wasm library, which the page loads the first time you hash something and reuses after that.

Yes: the MD4 hash generator page has the same algorithms and options and opens on the text box. This page opens on the file pane.

Not on its own. MD4 is built to be fast, and fast hashes are cheap for an attacker to guess against. Passwords need a salted, deliberately slow hash: use Argon2id, Argon2d, and bcrypt from the hash generators, which draw a fresh random salt each time.

Closest to the "File to MD4" tool: MD4 hash generator, MD5 hash generator, SHA-1 hash generator, SHA-256 hash generator. Each opens on its own page, free and in the browser.

The "File to MD4" tool is one of 64 in its group. The group's page, /tools/hash, lists them all.

The tool is free. Its interface is built from shadcn.io's own components (Button, Input, Slider and the rest of the registry under /ui), which come in React, Vue, Svelte and Solid. Pro adds the blocks and templates for the product around it.