-jul-984- It Started When I Happened To My Step... May 2026

Client-side tool to generate/verify password hashes with realistic parameters. Helpful for debugging integrations and understanding how salts, memory, and iterations affect cost. Runs locally—no passwords leave your browser.

Your data security is our top priority. All hashing and verification happen in this browser. This tool does not store or send your password nor hashes outside of the browser. See source code in: https://github.com/authgear/authgear-widget-password-hash

More Developer Tools

The entry, dated July 984th (which made no sense on any calendar), read: "She doesn't know what she stepped into. But the circle recognized her blood."

Here’s a coherent piece assembled from your fragment, expanding it into a narrative opening:

I happened to my stepfather's secret that afternoon, and by evening, the shadows in our house had begun to whisper my name.

It started when I happened to —the one bound in cracked leather, stamped with the code "-JUL-984-" on the spine. I wasn't snooping; the book simply fell from a high shelf in the garage, landing open at a page that made my blood run cold.

How to use the Password Hash Generator

Step 1.
Enter a password
  • Open the Generate tab and type a demo password (avoid real credentials).
Step 2.
Select an algorithm
  • For new systems, Argon2id is generally recommended.
Step 3.
Set parameters:
  • Argon2id: Memory (MiB), Iterations (t), Parallelism (p).
  • bcrypt: Cost (2cost rounds).
  • scrypt: N (power of two), r, p.
  • PBKDF2: Iterations and digest (SHA-256/512).
Step 4.
Generate Password Hash
  • Click Generate Password Hash. Copy the encoded string.
Step 5.
Verify Password Hash
  • Switch to Verify Password Hash to test a password + encoded hash pair.
-JUL-984- It started when I happened to my step...

Is it safe to use this with real passwords?

All hashing happens locally in your browser. For your own safety, avoid using production secrets in any online tool.
-JUL-984- It started when I happened to my step...

Which hashing function should I use?

For new systems, Argon2id is generally recommended. bcrypt and scrypt are widely deployed; PBKDF2 is a compatibility fallback. Always benchmark and choose parameters that meet your latency targets.
-JUL-984- It started when I happened to my step...

How long should hashing take?

Many teams target ~250–500ms in the authentication path. Pick the slowest settings that still keep UX smooth on your production hardware.
-JUL-984- It started when I happened to my step...

Why won’t my framework verify the hash?

Common issues: whitespace/line endings, encoding mismatch (hex vs Base64), bcrypt prefix differences ($2a$ vs $2b$), or forgetting a pepper.
-JUL-984- It started when I happened to my step...

What salt length should I use?

16–32 bytes of random data is standard. The tool defaults to secure randomness and shows length and encoding.

-jul-984- It Started When I Happened To My Step... May 2026

The entry, dated July 984th (which made no sense on any calendar), read: "She doesn't know what she stepped into. But the circle recognized her blood."

Here’s a coherent piece assembled from your fragment, expanding it into a narrative opening:

I happened to my stepfather's secret that afternoon, and by evening, the shadows in our house had begun to whisper my name.

It started when I happened to —the one bound in cracked leather, stamped with the code "-JUL-984-" on the spine. I wasn't snooping; the book simply fell from a high shelf in the garage, landing open at a page that made my blood run cold.

-jul-984- It Started When I Happened To My Step... May 2026

Open source Auth0/Clerk/Firebase alternative. Passkeys, SSO, MFA, passwordless, biometric login.

Star us on
-JUL-984- It started when I happened to my step...
Close