Scrypt Hash + Verify

Scrypt (RFC 7914) was one of the first memory-hard password-hashing algorithms: it deliberately requires a lot of RAM, not just CPU time, to make parallel brute-forcing on GPUs and ASICs harder.

How to use it

• Hash: enter a password and tune the parameters (N — memory cost, r — block size, p — parallelism) to get a hash.
• Verify: paste a password and an existing scrypt hash to check whether they match.
• Every hash uses a fresh random salt, so the same password produces a different hash each time.

Common uses

• Checking that a backend correctly hashes passwords with scrypt before storing them.
• Generating a test scrypt hash for fixtures or seed data during development.
• Comparing scrypt against bcrypt and Argon2 when choosing a hashing algorithm for a new project.

Things to keep in mind

The N parameter (memory cost) increases both required memory and compute time exponentially — tune it to your server's actual capacity.

Scrypt has been superseded by Argon2 (the official Password Hashing Competition winner) as the recommended choice for new systems, though scrypt itself still isn't considered unsafe.