SHA256 hash

SHA256 encoded string


Your last 10 encodings

sha256['SWKS' 'RHI' 'SKX' 'KNL' 'GHL' 'GNTX' 'OFG']78038596bfda4d267395ef4473d8f5e4f860586178c5f70f4ccbcf08e8ffa349

String encoded to other algorithms

Here you can view hashes for "['SWKS' 'RHI' 'SKX' 'KNL' 'GHL' 'GNTX' 'OFG']" string encoded with other popular algorithms

MD2 1f313882808ff74d0ff6d0465807abb9
MD4 584edcaf8d5d732e20a7e3c1db4eeb7d
MD5 89648b516b81cc501ba09bdd581fd370
SHA1 18ebbdb367f9522fab5f3e84052d87cb27b5e042
SHA224 aed564a19fd812f018f3b794d63521c895d9f87664cf3b42fecb25dd
SHA256 78038596bfda4d267395ef4473d8f5e4f860586178c5f70f4ccbcf08e8ffa349
SHA384 4df31909dc318d7772e4cf9384ea8a3eb1e1355e30981258077e2a0337a48a9029f1e0846052d249ea0f24d5217d914e
SHA512/224 a23cc2fd5fdc52f99c80406761da8cf2474411cfccd5a99fa8e6bbed
SHA512/256 66d3af084562303e799815731885ac042acdff2fbd3724dace5d525763e35d89
SHA512 a075d8f535b0bc1f021c78bc416f3ef6010ce38d9984a4b9bbf33996234038fc560f71a3cca3cf81d5d43a3fce92d4df7398674221e492db7a243615920c7e57
SHA3-224 d167a92280ccf077f6ee780c40b6ca78ea4e87f3e6261de138d3bd84
SHA3-256 9dd296a9872035406a28ffd18f5fd440c6b89f38cdfda84a633d3f2fbf734ef8
SHA3-384 d1097dcc3dac81d7039b62425c8ec8c4c25f49f81897c486b73da3566279d07d5e0fdb73c8496e2d18d9425f16db3b76
SHA3-512 83ce32dd237bff36cc1acffe58a18432bdeeb8c8f5c6659e0fdade664f1da52ea8cebc421511fcd9de32ebda634b339c1aca97423d98784bf73cf0175a3faa1f
RIPEMD128 415bafa5444b5d811902b54678efcbc7
RIPEMD160 c95761deea88de66c57eafa9d19ba6d17530b62b
RIPEMD256 39d57e8eb3a6d53fc2a6663a74b8a9acab9c1033c03f280aacf499ab38f09c3e
RIPEMD320 faabfa16371d258994e226b7ed431640293c3d55c8b8335598694108193748c8fadff585453c83ca
WHIRLPOOL ea6661f16ee2fc96d0b739c0954aea0f64fc7a37bc4dc5f9121afc95c7695706f502d653a3275bdaece54c0dbf5128d94a8a4e238935736280cc485ceff211e8
TIGER128,3 e92eb919963463a6ddfdebb928945381
TIGER160,3 e92eb919963463a6ddfdebb9289453819449cafe
TIGER192,3 e92eb919963463a6ddfdebb9289453819449cafe259af1a5
TIGER128,4 8c10b5376ec4c101dba70ccf814b83ff
TIGER160,4 8c10b5376ec4c101dba70ccf814b83ff959ed0b5
TIGER192,4 8c10b5376ec4c101dba70ccf814b83ff959ed0b54f352403
SNEFRU 82d4e4c159da48f1918810ae6a30d3cbecd671fc9182335713626797ee8844e8
SNEFRU256 82d4e4c159da48f1918810ae6a30d3cbecd671fc9182335713626797ee8844e8
GOST 0c269d02b8fd35b81d5dec1319a79684c3fd84f239d4f7168ef50ab49d7e319a
GOST-CRYPTO 4ce10a42df39b08798b0d31ea9a57c92b7227ac644fb1be4a6cc77b8e5fff3f1
ADLER32 f6240a99
CRC32 367118f5
CRC32B 83db8b0b
FNV132 4456c011
FNV1A32 cb853d55
FNV164 33331a2eb74486b1
FNV1A64 3d4910fbab3a2075
JOAAT d8b7a8c0
HAVAL128,3 f365686aa9347bc740dd17c5da04d461
HAVAL160,3 ccd0cb10469111b55bb832ba22b216226eb844e9
HAVAL192,3 9c7c9bd795ec709ca5dd37c49e149bb5350a3bec6d165d82
HAVAL224,3 7c56b668a07d3dc50da4f80bfe8572413b177d5a428cc9a8bb1c7ae5
HAVAL256,3 293c92ca8580e500a1b3cd02816ff005bd83fa8607fe2144b49e58aa41c1e0f7
HAVAL128,4 8fbda85c057bdc08910c6a2a74826929
HAVAL160,4 9b8bdf0b1359f6b9558012631832bb3b438139c9
HAVAL192,4 c2696a22fc219359470b6f19bf8f12c0e259e70d68d1a286
HAVAL224,4 14633f9bc20ad7db75af4e2e543b1094117e3f1faebe6389b0233f08
HAVAL256,4 5a225909e2788d526bb9c69cf16942b4da8d1df920fac14efc9200ebfa8b6f89
HAVAL128,5 94d4134b173805dd715c50017176974f
HAVAL160,5 3d2c94d877d79ffae3ada23d99a01b1948741562
HAVAL192,5 015a8215aed82cfa983484f1fb950ee79dd0f5ff7ffe5606
HAVAL224,5 c93480221a66a7136a58a507bd825e992784e7c0e07c4d0a76c1370a
HAVAL256,5 82e8393656df8e2a8cf624aca07c98dbd297b352cebca6887b4f1c278eb4c498

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