Skip to developer tool
DEVELOPER TOOLKIT SECURITY & ENCODING

SHA Hash Generator

Generate a digest in the representation an API or workflow expects. Hash exact file bytes or UTF-8 text, choose an output encoding and explicitly choose the newline bytes for text.

Browser-based · No account required · Copy and export

Open workspace Read the guide
BUILT FOR THE DETAILS
  1. 01Add your input
  2. 02Inspect & adjust
  3. 03Use your result
Browse developer tools

Workspace

PixelOkay · Developer tools

SHA-1 is deprecated for security-sensitive applications. Browser Web Crypto does not provide MD5.

How to use SHA Hash Generator

  1. Choose an algorithm. Enter text or select a file; a selected file takes precedence over the text field.
  2. Choose hex, Base64 or Base64URL output. For text only, choose LF or CRLF newline bytes.
  3. Generate and inspect the digest and source-byte information. Clear a file selection to return to text input, then copy or download.

When to use this tool

Generate a digest for a text fixture or local file in the representation a system expects. This tool offers several output encodings; use File Checksum Calculator when you need an explicit expected-hash comparison.

The algorithm and representation are independent

A SHA digest is a sequence of bytes. Hex, Base64 and Base64URL display those same bytes differently; they are not different hash algorithms. Text is first encoded as UTF-8. The textarea normalizes entered line breaks; the explicit LF/CRLF setting determines the bytes used for hashing and can change the digest. File mode always hashes the selected file's exact bytes without that text transformation.

Worked example

Text: abc
SHA-256 hexadecimal:
ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad
The same digest can be represented as Base64 or Base64URL.

Limits and output checks

Web Crypto requires a secure or suitable local context. Files are read into memory and are bounded to 50 MiB here. SHA-1 is a legacy option. These fast unkeyed hashes are not password-storage functions, HMAC signatures or proof of file authenticity without a trusted comparison.

Reference: Web Crypto digest API.

Frequently asked questions

Why are text and file hashes different?

A file can contain a byte-order mark, another encoding or extra newlines. Text mode hashes the browser text encoded as UTF-8.

What does Base64URL change?

It uses URL-safe characters and removes trailing padding for display. The underlying digest bytes are unchanged.

Is the newline setting applied to files?

No. It only affects text mode. File hashing uses the original bytes.

Text bytes and original file bytes differ

Choose text or file mode and the intended digest representation. Compare the same encoding and newline convention when matching a known value.

Scope of this workflow

A file may contain a byte-order mark or different line endings. An unkeyed digest alone is not a signature or proof of origin.

File Checksum Calculator — SHA-256 & SHA-512 · All developer tools · Privacy policy · Contact PixelOkay