Story.3.avi -

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

Check out the snippet below and let us know: Does the digital grain add to the story, or do you prefer a polished 4K finish?

Our latest project, , is more than just a video; it’s an exploration of [Insert Theme, e.g., digital isolation / the evolution of memory / AI-driven surrealism]. What went into this version?

#DigitalStorytelling #Animation #Story3AVI #VisualArts #AILiteracy #CreativeProcess

Why AVI? We wanted to lean into that raw, uncompressed feel—honoring the "raw data" of the storytelling process.

Sharpening the focus to ensure the human voice isn't lost in the "corporate soup" of generic AI output.

In this chapter, we focus on the moment when [mention a specific plot point or "The Tension," as Avi Ashkenazi discusses in design].

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.
Story.3.avi

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.
Story.3.avi

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.
Story.3.avi

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.
Story.3.avi

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.
Story.3.avi

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.

Story.3.avi -

Check out the snippet below and let us know: Does the digital grain add to the story, or do you prefer a polished 4K finish?

Our latest project, , is more than just a video; it’s an exploration of [Insert Theme, e.g., digital isolation / the evolution of memory / AI-driven surrealism]. What went into this version?

#DigitalStorytelling #Animation #Story3AVI #VisualArts #AILiteracy #CreativeProcess

Why AVI? We wanted to lean into that raw, uncompressed feel—honoring the "raw data" of the storytelling process.

Sharpening the focus to ensure the human voice isn't lost in the "corporate soup" of generic AI output.

In this chapter, we focus on the moment when [mention a specific plot point or "The Tension," as Avi Ashkenazi discusses in design].

Story.3.avi -

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

Star us on
Story.3.avi
Close