JWT Secret Key Length Explained: Entropy, Bit Length, and RFC 7518 Standards

RFC 7518 explicitly dictates: "A key of the same size as the hash output (for instance, 256 bits for "HS256") or larger MUST be used with this algorithm." This is not an optional suggestion. For HMAC-SHA256, the minimum acceptable secret length is 256 bits (32 bytes). Using a shorter key violates the security guarantees of the underlying HMAC construction.

Many developers confuse character length with cryptographic entropy. A 32-character string composed of common dictionary words ("MySecretCompanyTokenKey2026!") does NOT possess 256 bits of entropy. True entropy comes from drawing each byte uniformly from a Cryptographically Secure Pseudo-Random Number Generator (CSPRNG).

# Generate 256 bits (32 raw bytes) of true cryptographic randomness in Hex:
openssl rand -hex 32

# Or in Base64:
openssl rand -base64 32

Here is the definitive specification matrix for HMAC algorithms defined in JSON Web Algorithms (JWA): • **HS256 (HMAC with SHA-256)**: Minimum 256 bits (32 raw bytes, 64 Hex characters, 43–44 Base64 characters). • **HS384 (HMAC with SHA-384)**: Minimum 384 bits (48 raw bytes, 96 Hex characters, 64 Base64 characters). • **HS512 (HMAC with SHA-512)**: Minimum 512 bits (64 raw bytes, 128 Hex characters, 86–88 Base64 characters). Any key below these thresholds reduces cryptographic margins and may cause modern JWT libraries to throw runtime validation warnings or exceptions.