We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
SHA Hash Calculator
Was this tool helpful to use?
Your feedback helps us make it better
Online hash generator and verification tool supporting SHA1, SHA256, and SHA512 algorithms, featuring advanced salting and multi-round iteration options.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This SHA hash calculator takes text and produces a digest using SHA-1, SHA-256, SHA-384, or SHA-512. A hash function maps input data to a fixed-size result. The digest is useful for comparing a text value with a separately known digest, but it is not encrypted text: there is no decryption key that restores the original input.
After you enter text and choose an algorithm, the result is shown in lowercase hexadecimal, uppercase hexadecimal, and Base64. These are different encodings of the digest bytes. Changing capitalization in the hex display changes only its presentation; changing even one input character or the algorithm changes the digest.
The four variants produce different digest lengths: SHA-1 is 160 bits, SHA-256 is 256 bits, SHA-384 is 384 bits, and SHA-512 is 512 bits. A hex character represents four bits, so the corresponding hexadecimal outputs contain 40, 64, 96, and 128 characters. Choose the same algorithm and output form used by the checksum, documentation, or system you are comparing against.
NIST describes SHA-2, including SHA-256, SHA-384, and SHA-512, in its hash-function guidance and recommends SHA-256 at minimum for interoperability. NIST is also transitioning away from SHA-1 for cryptographic protection. See the NIST hash-function policy and its SHA-1 transition announcement, both checked September 28, 2026.
For the text abc, SHA-256 has the hexadecimal digest ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad. The uppercase field is the same sequence of hex digits in capital letters, and Base64 is another representation of the same digest bytes. This known input is useful for checking that you selected SHA-256 and are reading the correct output field.
If your result differs, inspect the input for an extra space, line break, or punctuation mark before assuming the algorithm is wrong. Text that looks identical can contain different characters.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Type or paste the string you want to hash. Spaces, punctuation, capitalization, and line breaks are part of the input.
Use the variant selector to match the expected digest. The available choice matters: a SHA-256 digest cannot be compared directly with a SHA-512 digest.
For these SHA variants, the digest updates as you edit the text. The three displayed encodings appear together.
Use the copy control beside the lowercase hex, uppercase hex, or Base64 result. When checking a published value, compare the entire digest and ensure that both values use the same variant and encoding.
Use cases
See how the tool fits into real work and everyday tasks.
When a document or application gives you a digest for a text token, select the named SHA variant, enter the exact token, then compare like-for-like hex or Base64 output.
When documenting a test value, record the algorithm and exact input alongside the digest. That makes it possible for another person to reproduce the same result.
If two digests look different, first confirm there is no leading or trailing whitespace and that the algorithm and output encoding agree. Hex letter case alone does not change the underlying digest.
Q&A
Find concise answers to common questions and confusing cases.
No. Hashing produces a one-way digest; encryption is designed to be reversed with the appropriate key. This calculator displays a digest and cannot recover the source text.
No. This page accepts text and calculates a plain SHA digest. It does not upload or hash a file, create a keyed HMAC, or offer a separate verification mode.
No. A single fast SHA digest is not a password-storage scheme. Use a purpose-built password hashing method with suitable parameters in an application designed for credential storage.
Notes
Review scope, result limitations, and important precautions before use.
A matching digest can help establish that the compared text produces the same result under the same algorithm. It does not authenticate who supplied the text or prove that a file is safe. Because the calculator accepts text only, a file checksum workflow would require a separate, appropriate file-hashing method.
SHA-1 remains available here for matching older references, but it should not be selected for new cryptographic designs. NIST’s transition plan states that it is moving away from SHA-1 for cryptographic protection; follow the requirements of the system you are working with when handling existing SHA-1 values.
Related
Discover related tools, collections, and available API capabilities.