Hash and Checksum Generator

Hash exact text or batches of files with one algorithm or all six supported algorithms.

On-device No sign-up Free to use

Hash the input controls

Showing an example. Edit to see your own.

?

The exact bytes are hashed, so a trailing space or a different line ending changes the result.

Drop your files here

or choose them from your device

The raw file bytes are hashed. The file stays on this device.

    ?

    Optional. Paste the digest published by the source you downloaded, and spaces or colons are ignored.

    ?

    SHA-2 algorithms use the browser crypto interface. The legacy algorithms are computed in this page.

    Processed in your browser. Your inputs stay on this device.

    Result

    Showing an example.

    Compute the SHA-256 digest of the exact UTF-8 text Example text to check.

    SHA-256 digest of the text: 31f0ef775b516f35fc5ad53602967b050c629c2b1b519a6081814e8bb2e14022. No expected value was supplied, so nothing was compared.

    Loading the tool. Your result will appear here.

    https://usefreetools.net/hash-checksum-generator · 20 November 2026

    Was this helpful?

    How to use Hash and Checksum Generator

    1. Choose Text typed or pasted here, or A file from this device.
    2. Set Algorithm. SHA-256 is the default.
    3. Enter the text or select the file, and paste an expected value if you have one.
    4. The digest updates when you change the text, selected files or algorithm. Check the algorithm and any comparison result before copying it.

    Example: Hash and Checksum Generator

    Compute the SHA-256 digest of the exact UTF-8 text Example text to check.

    You add
    What to hash: text; Algorithm: sha-256; Text: Example text to check; Uppercase digest display: false
    You get
    SHA-256 digest of the text: 31f0ef775b516f35fc5ad53602967b050c629c2b1b519a6081814e8bb2e14022. No expected value was supplied, so nothing was compared.

    Options

    What to hash
    Choose Text typed or pasted here, A file from this device.
    Algorithm
    SHA-2 algorithms use the browser crypto interface. The legacy algorithms are computed in this page.
    Text
    The exact bytes are hashed, so a trailing space or a different line ending changes the result.
    Files
    The raw file bytes are hashed. The file stays on this device.
    Uppercase digest display
    Displays hexadecimal letters as A–F instead of a–f. The underlying digest bytes do not change.
    Expected value to compare
    Optional. Paste the digest published by the source you downloaded, and spaces or colons are ignored.

    Supported inputs and limits

    • Text up to 5,000,000 characters, or up to 20 files totaling 64 MiB.
    • Text is UTF-8 encoded; files use their raw bytes.
    • All-algorithm mode runs MD5, SHA-1, SHA-256, SHA-384, SHA-512 and CRC32.
    • SHA-2 needs Web Crypto; legacy choices run in the page.
    • Expected-value comparison supports one file and one algorithm at a time.
    More details

    Uppercase changes display only.

    MD5 and SHA-1 are legacy choices, and CRC32 checks corruption rather than security.

    A match is meaningful only relative to the expected value's trustworthiness; it does not establish file safety.

    SHA-3 is not included.

    Where your input is processed

    This tool does not upload your inputs. See the limits for anything saved on your device.

    What a matching checksum proves

    A hash maps bytes to a fixed-length value. A matching secure digest from an independently trusted source is strong evidence that the bytes agree, but hashes can have collisions and legacy checksums have weaker guarantees. A digest does not establish whether a program contains malware or whether its publisher is trustworthy.

    Why one changed byte changes everything

    A secure hash spreads a small input change across the whole output, so abc and abd share no visible structure. That is what catches a truncated download or a converted line ending.

    Questions about Hash and Checksum Generator

    When should I choose MD5?

    Only when matching an existing legacy checksum that requires MD5. It is unsuitable for passwords, signatures or security verification. A match does not prove a file is safe.

    A file matches its checksum but will not open. Why?

    The bytes match what the publisher hashed. That says nothing about whether the file is valid or safe.

    Do spaces or colons in a pasted value break the comparison?

    No. They are removed before the comparison, and letter case is ignored.

    Can I hash files larger than 64 MiB?

    Not here. Use sha256sum on Linux, certutil -hashfile on Windows, or shasum on macOS.

    Page updated · Project managed by Tony Hines · Report a problem with Hash and Checksum Generator

    Related reading

    All guides