SHA256 hash

SHA256 encoded string


Your last 10 encodings

sha256['AWK' 'CSR' 'SPI' 'LNG' 'WLKP' 'KOPN' 'ACRE']0c2c83da902b9a0a8d3ff7586f6bef1c87532610f2502c61f464afa0126e3fcc

String encoded to other algorithms

Here you can view hashes for "['AWK' 'CSR' 'SPI' 'LNG' 'WLKP' 'KOPN' 'ACRE']" string encoded with other popular algorithms

MD2 b5cbf14de1b683a5c275230685ee3e72
MD4 d820579b3b2130b3f4bed64805dd9492
MD5 70cc50f71c1510b82fadb8e3bcf51ce6
SHA1 1934439af99b751b915d1d8110078872ab8a5e86
SHA224 65c396f23614c4c579799783c14560ccd15b4d768beaff866d58b04c
SHA256 0c2c83da902b9a0a8d3ff7586f6bef1c87532610f2502c61f464afa0126e3fcc
SHA384 70b2775448eed2dc93a885d450b72900b167cf7afb97e964731811218f87a02a90a682ee1f72bf1b5e1232ef6f7216a7
SHA512/224 f922656fee2b49dd0f849abe3edcd01b566648761e7429c391e55f48
SHA512/256 d028b7c4d4b730e5e2651503482cd30f9c736ffb02c05741b0244bdc61e9b9e0
SHA512 58bb5938350c9cb6a0aa94c3f6d9fc216239fdac50818d7195e84977bcb377edd23da5ec3014e93a8c20014999d698079622a1785a1a8bb2a44220bedbf8c846
SHA3-224 f9381dc32cb7a036815d03a4b1e0a9894a3be2ed3e64781c87405e23
SHA3-256 c709e94aa890876f002dc6b9a247d33e8faf39c29c536109ee9c1a1493237238
SHA3-384 79f256e98ab04cf8850b513be851f8a1717da096aeec247506f8e3ba4f953b5977b4d5ffdc3920ffc99dbef5baaaf536
SHA3-512 05ae37009b59dc6c01c63948573c17e39a254912bd6482cac07c843b26df1b9630977b5aa78c05ded98b2eebf822ee5e262ddd895609b991ba575a72deb04205
RIPEMD128 11b248c23ee8428e7997768820bd7999
RIPEMD160 b604059f2b708a6e309a1efb0c4ba4febf513a1d
RIPEMD256 624c6a7b883adc9fdc1ad2652d483bfdc911ae8da710e83f6f52ef8aade3e48a
RIPEMD320 c614289b4c0d401e7e8196433abed99a8f8102315f384aa61f9c3b233ed3a63546115347cc960cf3
WHIRLPOOL 36b925ceb4b27b1c7f24c1370aea276494ef4f0b7a316a827d9a41883a5f686d11176872755eb819b4eb0d64b68d54155436f4039c7a302de9c1d6dd124d97db
TIGER128,3 8aedfebc2e1e08ec41c8d1d8d4b3d44d
TIGER160,3 8aedfebc2e1e08ec41c8d1d8d4b3d44dae967700
TIGER192,3 8aedfebc2e1e08ec41c8d1d8d4b3d44dae96770063ee5a1f
TIGER128,4 776908394ad849493481fbb8c172cb87
TIGER160,4 776908394ad849493481fbb8c172cb87d62107c8
TIGER192,4 776908394ad849493481fbb8c172cb87d62107c8cc7fb606
SNEFRU 9aa9055da04a8e44607bd951bc17d1b575c6ddb782cf3ee7e2b39ac337a3573f
SNEFRU256 9aa9055da04a8e44607bd951bc17d1b575c6ddb782cf3ee7e2b39ac337a3573f
GOST c9112b30e74f447473d1ba1f7b85a70152ef415f00682245da5df219fa0d1b3d
GOST-CRYPTO bf9075d65305f91d64d2e872edecca46b2dff78c7deb52765209dd86a792748f
ADLER32 fb550ac4
CRC32 386698c6
CRC32B 1de38f39
FNV132 99ac8dc8
FNV1A32 2262868e
FNV164 295216393230e168
FNV1A64 5c0a2a0b2e22e68e
JOAAT 76aedc58
HAVAL128,3 6aaa6d2669f24d3f2aaff1b0a66ec3ea
HAVAL160,3 4b9d04378458aeb2114f828ce629d88b08a93846
HAVAL192,3 cdbc607627d23c3aec30b771facf8fb5158088eca5da53a6
HAVAL224,3 bad72ca7393cd699804c7dbae947ab631523820cd511a01a7ce669f0
HAVAL256,3 92fe70cb800b7bb9b4fed0153f6b0e51209fce4d844c01cc389f7f7a6ae73fa9
HAVAL128,4 24b02541548cffefb46a88cead99e3b9
HAVAL160,4 5ce7fb113762b6794105a44c1dd7f388780905a3
HAVAL192,4 1e82d4c8b8484e080e33b6912828a0d45fbc9fa393d02307
HAVAL224,4 7b1e90750182e5b0d42a1aff23545e942b7959171ea1ad78d98589f4
HAVAL256,4 1a29f48a355b2ed1aea16412375380f8832f56336585307eb3e5fa6833af25a7
HAVAL128,5 7b5ae8cd8b6bae7bf82804635977849a
HAVAL160,5 82f573dbb0f789fd89136915c0cd37f885072683
HAVAL192,5 8685ddff81b9527377dddca6c93f51aa5212567eace1d93a
HAVAL224,5 6837962e968c47337307e034cd6693041e2b5c6f43d533b4eaf2f2e1
HAVAL256,5 1e3021fcd62e0380356de3f8e42b97169cd444ebb4ecdbdf3ec876ebfb969289

Usage FAQ

Usage from Address Bar

You can use direct access to this page from your browser address bar. Type string that you need to encode with algorithm according to next schema:<ALGORITHM>/<PHRASE> For example to visit page that contains hash of "hello world" you can just visit url: The another cool thing is that you can specify "json" or "plain" mode into URL and you will get only HASH in response. Schema of this future:<ALGORITHM>.<OUTPUT:plain|json>/<PHRASE> Example: Will output only: "5eb63bbbe01eeed093cb22bb8f5acdc3"

If you have string that contains complicated urlencoded characters you can send it directly via params to avoid processing of our url parser. Use:
str - for string to encode
algo - for algorithm
output - for output type (empty, "json" or "plain")<ALGORITHM>&str=<PHRASE>&output=<OUTPUT:plain|json>

Usage from Javascript

We have removed CORS restriction so you can use direct access to hash calculator in your javascript applications via AJAX.


var toEncode = 'hello world';
var xhr = new XMLHttpRequest();
xhr.onreadystatechange = function () {
if (xhr.readyState == 4 && xhr.status == 200) {
console.log('JSON of "'+toEncode+'" is "'+JSON.parse(xhr.response)+'"');
};'GET', ''+encodeURIComponent(toEncode), true);
Will output: JSON of "hello world" is "5eb63bbbe01eeed093cb22bb8f5acdc3"

Usage from PHP

You can use direct access to hash in your applications.

PHP Example: <?php
$str = 'hello world';
$url =''.urlencode($str);
$md5hash = file_get_contents($url);
echo 'Hash of "'.$str.'" is "'.$md5hash.'"';
Will output: Hash of "hello world" is "5eb63bbbe01eeed093cb22bb8f5acdc3"

Chains of algorithms

In some cases you can need encode string with two or more algorithms. For these cases we have introduced chains of algorithms. For example if you need to encode string according to this schema md5(sha512(sha1('hello world'))) you can do this by connecting algorithms with a double dash: If you will do this in your address bar you can also use semicolon instead of double dash.;sha512;sha1/hello+world Pay attention that semicolon should be encoded in url, so if you use it not in your browser, you should use '%3B' instead Such approach can be also used with "plain" and "json" mode;sha512;sha1.json/hello+world

You can also use special chain item "b64d" or "base64decode" to make base64 decode. It can help to hash any of not printable characters. Example: will be the same: 5eb63bbbe01eeed093cb22bb8f5acdc3

Carriage Return and Line Feed characters

At present time our text editor doesn't have functionality that can take into account which of those characters you want to keep in string. This problem come from browsers which normalize all of the line endings to "CRLF" ("\r\n") format according to "HTML specification". It means that if you paste from buffer string
"hello\nword" and press "Encode", your browser will convert it to "hello\r\nword" and only after this your browser send FORM to us. As a result we will show you hash of "hello\r\nword" but not "hello\nword"

You can avoid this with encode string to "base64" on your side and use "Chains of algorithms" that described above.

Example 1: Hash from string with only Line Feed (LF) character Text: hello\nworld
Text encoded to BASE64: aGVsbG8Kd29ybGQ=
RESULT: 9195d0beb2a889e1be05ed6bb1954837

Example 2: Hash from string with Carriage Return (CR) and Line Feed (LF) character. This result you will have if you use editor with CR, LF or CRLF symbols.
Text: hello\r\nworld
Text encoded to BASE64: aGVsbG8NCndvcmxk
RESULT: 6a4316b18e6162cf9fcfa435c8eb74c1

How to calculate sha256 hash in PHP with hash function

Since version 5.1.2 PHP contains function hash() that you can use to get sha256 hash from strings.

    $str = '¡Hola!';
    $hash = hash('sha256', $str, false);
    echo '<pre>';
    echo $str.PHP_EOL
         .' &rarr; '.$hash.PHP_EOL
    echo '</pre>';
Please read the privacy policy (agreement of the cookies usage, other websites embedded content, etc.). If you continue to use the site, we will assume that you agree with our privacy policy.
OkPrivacy Policy