• EasyStackTools191+ Free Tools
    • Blogs
    • Docs
    • About
    • Privacy
    • Terms
  1. Home
  2. Documentation
  3. Tool guides
  4. Developer Tools
  5. Calculate NTLM Hash

How to Use Calculate NTLM Hash

Use tool

On this page

  • What is the NTLM Hash tool?
  • Key features
  • How to use
  • When to use NTLM hash
  • Limitations
  • Frequently asked questions
  • What is NTLM hash?
  • What input does the tool accept?
  • Is NTLM secure?
  • Is my password sent to a server?
  • When should I use NTLM hash?
  • Why does my hash not match?
  • Try the tool

Related tools

  • Hash Generator·
  • Calculate MD4 Hash·
  • Calculate SHA-256 Hash·
  • Calculate All Hashes at Once·

Calculate NTLM Hash – Free Online NTLM Hash Generator

Compute NTLM (NT) hash from a password in your browser. Client-side only. For Windows compatibility and testing.

What is the NTLM Hash tool?

This tool computes the NTLM (NT) hash of text (typically a password). The NT hash is MD4 of the password encoded as UTF-16LE—the same as Windows uses for NTLM authentication. All hashing runs in your browser; your password never leaves your device.

Key features

  • Client-side — No server uploads. Your password is never sent anywhere.
  • UTF-16LE — Password is encoded as UTF-16LE before MD4, matching Windows NTLM.
  • Instant — Hash updates as you type.
  • Copy — One-click copy of the NT hash.

How to use

  1. Open Calculate NTLM Hash.
  2. Enter the password (or text) to hash.
  3. Copy the NTLM (NT) hash. Use for testing, migration, or compatibility as needed.

When to use NTLM hash

  • Windows compatibility — Generate or verify NT hashes for NTLM.
  • Testing — Check that a password produces the expected NT hash.
  • Migration — Precompute hashes when moving to or from Windows auth. Prefer modern auth (Kerberos, OAuth) for new systems.

Limitations

NTLM is weak. Use only for legacy Windows compatibility. Do not rely on it for new applications.

Frequently asked questions

What is NTLM hash?

The NTLM (NT) hash is MD4 of the password encoded as UTF-16LE. It is used in Windows authentication.

What input does the tool accept?

The password or text to hash. It is encoded as UTF-16LE and then hashed with MD4.

Is NTLM secure?

NTLM is considered weak. Use only for compatibility with legacy Windows systems. Prefer modern auth (e.g. Kerberos, OAuth).

Is my password sent to a server?

No. Hashing runs in your browser. Your password never leaves your device.

When should I use NTLM hash?

When you need to generate or verify an NT hash for Windows compatibility, testing, or migration.

Why does my hash not match?

Ensure the password is identical and that you are comparing NT hash (MD4(UTF-16LE)), not LM or NTLMv2.

Try the tool

Use Calculate NTLM Hash. See MD4 Hash, Hash Generator, or All Hashes.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    { "@type": "Question", "name": "What is NTLM hash?", "acceptedAnswer": { "@type": "Answer", "text": "The NTLM (NT) hash is MD4 of the password encoded as UTF-16LE. It is used in Windows authentication." } },
    { "@type": "Question", "name": "What input does the tool accept?", "acceptedAnswer": { "@type": "Answer", "text": "The password or text to hash. It is encoded as UTF-16LE and then hashed with MD4." } },
    { "@type": "Question", "name": "Is NTLM secure?", "acceptedAnswer": { "@type": "Answer", "text": "NTLM is considered weak. Use only for compatibility with legacy Windows systems. Prefer modern auth (e.g. Kerberos, OAuth)." } },
    { "@type": "Question", "name": "Is my password sent to a server?", "acceptedAnswer": { "@type": "Answer", "text": "No. Hashing runs in your browser. Your password never leaves your device." } },
    { "@type": "Question", "name": "When should I use NTLM hash?", "acceptedAnswer": { "@type": "Answer", "text": "When you need to generate or verify an NT hash for Windows compatibility, testing, or migration." } },
    { "@type": "Question", "name": "Why does my hash not match?", "acceptedAnswer": { "@type": "Answer", "text": "Ensure the password is identical and that you are comparing NT hash (MD4(UTF-16LE)), not LM or NTLMv2." } }
  ]
}