SHA-1 Generator
Generate a 40-character SHA-1 digest from UTF-8 text, then check newline, encoding and Git object differences when results do not match.
SHA-1 Generator
Generate a 40-character SHA-1 digest from UTF-8 text, then check newline, encoding and Git object differences when results do not match.
About the SHA-1 generator
Create a 160-bit text digest
The tool encodes the entered text as UTF-8 and returns a 160-bit SHA-1 digest as 40 hexadecimal characters. Use it to reproduce a known text checksum or a legacy integration fixture. It hashes the text itself, not a Git object or the original bytes of an arbitrary file. The examples below help you check the exact input before comparing results.
Keep it out of new security designs
SHA-1 is deterministic and one-way, but known collision attacks make it unsuitable for new security workflows. Use it for compatibility checks only, and choose SHA-256, HMAC, signatures, or password hashing algorithms when protection is required.
FAQ
Common questions and answers about this topic.
What is SHA-1?
SHA-1 produces a 160-bit (40-character hex) hash. It was widely used in Git commits and certificates but is now considered weak for cryptographic use.
Is SHA-1 secure?
SHA-1 is deprecated for cryptographic purposes due to known collision attacks. Use SHA-256 or SHA-3 for non-password integrity checks, and use a password hashing algorithm for password storage.
Can I reverse a SHA-1 hash?
No, hash functions are one-way.
Is my data sent to any server?
No, SHA-1 hashing runs entirely in your browser. Your input data is hashed locally with JavaScript and never sent to any external service.
Why does a trailing newline change my SHA-1 result?
Example hashes are grouped in blocks of 10 characters for readability; remove the spaces before comparing. A newline is part of the input bytes. The text abc with no trailing newline produces a9993e3647 06816aba3e 25717850c2 6c9cd0d89d. The same text followed by one LF newline produces 03cfd74366 1f07975fa2 f1220c5194 cbaff48451. Check spaces, letter case and line endings before comparing; command-line echo commonly adds a trailing newline.
How is Chinese text encoded, and can I compare a file checksum?
Example hashes are grouped in blocks of 10 characters for readability; remove the spaces before comparing. This tool uses UTF-8. The two characters 中文, without quotes, spaces or a trailing newline, produce 7be2d2d20c 106eee0836 c9bc2b9398 90a78e8fb3. Another encoding produces different bytes. A file checksum matches only when the hashed bytes are identical, including any byte-order mark and line endings; pasting decoded text does not preserve arbitrary binary file bytes.
Why does this result differ from git hash-object or a commit ID?
Example hashes are grouped in blocks of 10 characters for readability; remove the spaces before comparing. In a SHA-1 repository, Git hashes an object header plus its content, not just the text. A blob header contains its type, byte length and a zero byte. For abc with no trailing newline, this text tool returns a9993e3647 06816aba3e 25717850c2 6c9cd0d89d, while the Git blob ID is f2ba8f84ab 5c1bce84a7 b441cb1959 cfc7093b7f. A commit object contains additional data such as tree and parent references, author information and its message. This tool does not recreate Git objects.