Storing a password using a secure algorithm like bcrypt (cost 10) or Argon2 typically consumes how much storage per user?

Unlike simple hashing algorithms like MD5 (16 bytes) or SHA-256 (32 bytes), secure password KDFs (Key Derivation Functions) like bcrypt or Argon2 include significant metadata in their output. A standard bcrypt hash is exactly 60 characters long, encoding the algorithm version, the 'work factor' (cost), a 128-bit random salt, and the resulting 184-bit hash. While storing 60 bytes instead of 16 seems like a 4x increase in storage, it is a mandatory trade-off for security. This metadata ensures that even if two users have the same password, their hashes look completely different, preventing attackers from using 'Rainbow Tables' to crack the database.