32-Character Random String JWT Secret Generator
This 32-character secret is sampled uniformly from a 74-symbol alphabet covering uppercase, lowercase, digits, and common punctuation. It's the best choice when a human will read, transcribe, or paste the value into a UI that rejects Base64's '+' and '/' characters. At 32 characters it supplies roughly 198 bits of entropy, positioning it in the "minimum" tier for HMAC-based JWT signing (HS256).
Generating…
Why 32 characters?
32 characters sits right at the security floor most standards bodies recommend for HMAC — enough to make brute-force and length-extension style guessing attacks computationally infeasible, but with no slack if your alphabet turns out to be smaller than expected.
Storage & performance: Negligible performance impact: HMAC-SHA256 hashes the key once per verification regardless of its length up to the hash's block size, so 32 bytes costs the same CPU time as 8.
Random strings are used verbatim as the HMAC key material — no decoding step, which makes them the simplest format to reason about in any language.
When to use / when to avoid
Use a 32-char Random String secret when…
- You need the smallest secret that still meets HS256's security bar.
- You're prototyping locally and want a quick, copy-pasteable value.
- Your secrets manager or CI variable has a tight character limit.
Consider a different length when…
- Skip it if your framework recommends a larger default (some scaffolds ship 64+).
- Avoid if you plan to derive multiple subkeys from this single secret via HKDF.
Generate a 32-char Random String secret in code
Each snippet below produces the same shape of secret as the tool above: a 32-character random string string using each language's cryptographically secure RNG.
import crypto from "node:crypto"; const alphabet = "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-_.~!@#$%^&*"; const bytes = crypto.randomBytes(32); let secret = ""; for (let i = 0; i < 32; i++) secret += alphabet[bytes[i] % alphabet.length]; console.log(secret); // 32-char random string
import secrets
alphabet = (
"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-_.~!@#$%^&*"
)
secret = "".join(secrets.choice(alphabet) for _ in range(32))
print(secret) # 32-char random stringpackage main
import (
"crypto/rand"
"fmt"
"math/big"
)
const alphabet = "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-_.~!@#$%^&*"
func main() {
out := make([]byte, 32)
for i := range out {
n, _ := rand.Int(rand.Reader, big.NewInt(int64(len(alphabet))))
out[i] = alphabet[n.Int64()]
}
fmt.Println(string(out)) // 32-char random string
}import java.security.SecureRandom;
String alphabet =
"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789-_.~!@#$%^&*";
SecureRandom random = new SecureRandom();
StringBuilder sb = new StringBuilder(32);
for (int i = 0; i < 32; i++) {
sb.append(alphabet.charAt(random.nextInt(alphabet.length())));
}
String secret = sb.toString();
System.out.println(secret); // 32-char random stringSecurity notes
- Generated locally with crypto.getRandomValues — nothing is sent to a server, logged, or cached.
- Regenerate before first use in production; treat any secret shown on shared screens as compromised.
- Store it in a secrets manager or git-ignored .env file, never in source control or client-side code.
- Rotate on a schedule and support at least one overlapping "next" secret to allow zero-downtime rotation.
FAQ
Why does this generator produce 32-character Random String strings specifically?
32 characters sits right at the security floor most standards bodies recommend for HMAC — enough to make brute-force and length-extension style guessing attacks computationally infeasible, but with no slack if your alphabet turns out to be smaller than expected. The exact length is fixed at 32 so the output is deterministic to copy into configuration without manual trimming.
How many bits of entropy does a 32-character Random String secret carry?
A–Z, a–z, 0–9, and common symbols (74-symbol alphabet) yields about 6.2 bits per character, so 32 characters work out to roughly 198 bits of entropy — comfortably above the 256-bit floor commonly cited for HMAC-SHA256 keys.
Which JWT algorithm should I pair with a 32-char Random String secret?
HS256. This is the floor RFC 7518 implies for HMAC-SHA256: 256 bits of key material, one bit per output bit of the hash.
Random String vs. other formats at 32 characters — which should I pick?
Cryptographically random alphanumeric + symbol characters drawn from a 74-character alphabet (~6.2 bits/char). Random strings are used verbatim as the HMAC key material — no decoding step, which makes them the simplest format to reason about in any language. Pick a different format only if your framework or secrets manager has a stated preference.
Does the 32-character length affect signing or verification performance?
Negligible performance impact: HMAC-SHA256 hashes the key once per verification regardless of its length up to the hash's block size, so 32 bytes costs the same CPU time as 8.
Where should I store a 32-character Random String JWT secret?
Use a secrets manager (Doppler, AWS Secrets Manager, GCP Secret Manager, HashiCorp Vault, 1Password) or a git-ignored .env file. Never commit it to source control, and rotate it on a schedule appropriate for HS256.
Is this 32-char Random String secret generated securely?
Yes — it's produced entirely in your browser with the Web Crypto API's crypto.getRandomValues, a cryptographically secure PRNG. No network request is made and the value is never transmitted or logged.
Can I reuse this Random String secret for something other than JWTs?
Yes. A 32-character Random String string is a general-purpose high-entropy secret — it also works as an API key, session-encryption key, or CSRF token secret needing around 198 bits of randomness.
Related generators & tools
Recent articles
Guides on JWT secrets, signing algorithms, and token security.