password_hash

Creates a password hash

&reftitle.description; `string` `password_hash` `string` `password` ``string``int``null```algo` `array` `options`[]

`password_hash` creates a new password hash using a strong one-way hashing algorithm.

The following algorithms are currently supported:

- `PASSWORD_DEFAULT` - Use the bcrypt algorithm (default as of PHP 5.5.0). Note that this constant is designed to change over time as new and stronger algorithms are added to PHP. For that reason, the length of the result from using this identifier can change over time. Therefore, it is recommended to store the result in a database column that can expand beyond 60 characters (255 characters would be a good choice).

- `PASSWORD_BCRYPT` - Use the `CRYPT_BLOWFISH` algorithm to create the hash. This will produce a standard `crypt` compatible hash using the "$2y$" identifier. The result will always be a 60 character string, &return.falseforfailure;.

- `PASSWORD_ARGON2I` - Use the Argon2i hashing algorithm to create the hash. This algorithm is only available if PHP has been compiled with Argon2 support.

- `PASSWORD_ARGON2ID` - Use the Argon2id hashing algorithm to create the hash. This algorithm is only available if PHP has been compiled with Argon2 support.

Supported options for `PASSWORD_BCRYPT`:

- `salt` (`string`) - to manually provide a salt to use when hashing the password. Note that this will override and prevent a salt from being automatically generated.

  If omitted, a random salt will be generated by `password_hash` for each password hashed. This is the intended mode of operation.

  The salt option is deprecated. It is now preferred to simply use the salt that is generated by default. As of PHP 8.0.0, an explicitly given salt is ignored.

- `cost` (`int`) - which denotes the algorithmic cost that should be used. Examples of these values can be found on the `crypt` page.

  If omitted, a default value of `10` will be used. This is a good baseline cost, but you may want to consider increasing it depending on your hardware.

Supported options for `PASSWORD_ARGON2I` and `PASSWORD_ARGON2ID`:

- `memory_cost` (`int`) - Maximum memory (in kibibytes) that may be used to compute the Argon2 hash. Defaults to `PASSWORD_ARGON2_DEFAULT_MEMORY_COST`.

- `time_cost` (`int`) - Maximum amount of time it may take to compute the Argon2 hash. Defaults to `PASSWORD_ARGON2_DEFAULT_TIME_COST`.

- `threads` (`int`) - Number of threads to use for computing the Argon2 hash. Defaults to `PASSWORD_ARGON2_DEFAULT_THREADS`.

  Only available when PHP uses libargon2, not with libsodium implementation.

&reftitle.parameters;

`password`

- &password.parameter.password;

  Using the `PASSWORD_BCRYPT` as the algorithm, will result in the `password` parameter being truncated to a maximum length of 72 bytes.

`algo`

- &password.parameter.algo;

`options`

- &password.parameter.options;

  If omitted, a random salt will be created and the default cost will be used.

&reftitle.returnvalues;

Returns the hashed password.

The used algorithm, cost and salt are returned as part of the hash. Therefore, all information that's needed to verify the hash is included in it. This allows the `password_verify` function to verify the hash without needing separate storage for the salt or algorithm information.

&reftitle.changelog;

&Version; | &Description;
8.0.0 | `password_hash` no longer returns &false; on failure, instead a `ValueError` will be thrown if the password hashing algorithm is not valid, or an `Error` if the password hashing failed for an unknown error.
8.0.0 | The `algo` parameter is nullable now.
7.4.0 | The `algo` parameter expects a &string; now, but still accepts &integer;s for backward compatibility.
7.4.0 | The sodium extension provides an alternative implementation for Argon2 passwords.
7.3.0 | Support for Argon2id passwords using `PASSWORD_ARGON2ID` was added.
7.2.0 | Support for Argon2i passwords using `PASSWORD_ARGON2I` was added.

&reftitle.examples;

### `password_hash` example

    <?php
    /**
     * We just want to hash our password using the current DEFAULT algorithm.
     * This is presently BCRYPT, and will produce a 60 character result.
     *
     * Beware that DEFAULT may change over time, so you would want to prepare
     * By allowing your storage to expand past 60 characters (255 would be good)
     */
    echo password_hash("rasmuslerdorf", PASSWORD_DEFAULT);
    ?>

&example.outputs.similar;

    $2y$10$.vGA1O9wmRjrwAVXD98HNOgsNpDczlqm3Jq7KnEd1rVAGv3Fykk1a

### `password_hash` example setting cost manually

    <?php
    /**
     * In this case, we want to increase the default cost for BCRYPT to 12.
     * Note that we also switched to BCRYPT, which will always be 60 characters.
     */
    $options = [
        'cost' => 12,
    ];
    echo password_hash("rasmuslerdorf", PASSWORD_BCRYPT, $options);
    ?>

&example.outputs.similar;

    $2y$12$QjSH496pcT5CEbzjD/vtVeH03tfHKFy36d4J0Ltp3lRtee9HDxY3K

### `password_hash` example finding a good cost

    <?php
    /**
     * This code will benchmark your server to determine how high of a cost you can
     * afford. You want to set the highest cost that you can without slowing down
     * you server too much. 10 is a good baseline, and more is good if your servers
     * are fast enough. The code below aims for ≤ 350 milliseconds stretching time,
     * which is an appropriate delay for systems handling interactive logins.
     */
    $timeTarget = 0.350; // 350 milliseconds

    $cost = 10;
    do {
        $cost++;
        $start = microtime(true);
        password_hash("test", PASSWORD_BCRYPT, ["cost" => $cost]);
        $end = microtime(true);
    } while (($end - $start) < $timeTarget);

    echo "Appropriate Cost Found: " . $cost;
    ?>

&example.outputs.similar;

    Appropriate Cost Found: 12

### `password_hash` example using Argon2i

    <?php
    echo 'Argon2i hash: ' . password_hash('rasmuslerdorf', PASSWORD_ARGON2I);
    ?>

&example.outputs.similar;

    Argon2i hash: $argon2i$v=19$m=1024,t=2,p=2$YzJBSzV4TUhkMzc3d3laeg$zqU/1IN0/AogfP4cmSJI1vc8lpXRW9/S0sYY2i2jHT0

&reftitle.notes;

It is strongly recommended that you do not generate your own salt for this function. It will create a secure salt automatically for you if you do not specify one.

As noted above, providing the `salt` option in PHP 7.0 will generate a deprecation warning. Support for providing a salt manually has been removed in PHP 8.0.

It is recommended that you test this function on your servers, and adjust the cost parameter so that execution of the function takes less than 350 milliseconds on interactive systems. The script in the above example will help you choose a good cost value for your hardware.

Updates to supported algorithms by this function (or changes to the default one) must follow the following rules:

- Any new algorithm must be in core for at least 1 full release of PHP prior to becoming default. So if, for example, a new algorithm is added in 7.5.5, it would not be eligible for default until 7.7 (since 7.6 would be the first full release). But if a different algorithm was added in 7.6.0, it would also be eligible for default at 7.7.0.

- The default should only change in a full release (7.3.0, 8.0.0, etc) and not in a revision release. The only exception to this is in an emergency when a critical security flaw is found in the current default.

&reftitle.seealso;

- `password_verify`
- `password_needs_rehash`
- `crypt`
- `sodium_crypto_pwhash_str`