Hash Generator

Generate SHA-256, SHA-1, and MD5 hashes in your browser. No data leaves your device.

SHA-256 (Recommended)
-
SHA-1
-
MD5
-

πŸ“– How to Use

1
Enter Text

Type the text you want to hash. All hash values update in real time as you type.

2
View Hash Values

SHA-256 (recommended), SHA-1, and MD5 hashes are displayed simultaneously.

3
Copy Results

Click the πŸ“‹ Copy button for any hash algorithm to save it to your clipboard. SHA-256 is the most secure.

πŸ’‘ Tip: Hash functions are used for password storage (with salt), file integrity verification, and digital signatures. SHA-256 is the current industry standard.

About the Hash Generator

A cryptographic hash function takes an input of any size — a byte, a text file, a multi-gigabyte image — and returns a small, fixed-length fingerprint called a digest. The same input always yields the same digest, and any change, even one flipped bit, yields a completely different digest. This tool computes MD5, SHA-1, and SHA-256 in your browser through the Web Crypto SubtleCrypto API; the input never leaves your device.

How it works

Each algorithm returns a digest of a fixed bit length: MD5 is 128-bit (32 hex characters), SHA-1 is 160-bit (40 hex characters), and SHA-256 is 256-bit (64 hex characters). The digest is shown as hexadecimal because each byte maps to two 09/af characters. Most of these algorithms use the Merkle–Damgård construction: the input is padded to a multiple of a 512-bit block, a length suffix is appended, and the message is processed one block at a time through a compression function that folds each block into a running state. The final state is the digest.

The defining property is collision resistance: finding two distinct inputs that hash to the same digest must be infeasible. MD5 and SHA-1 are broken — practical collision attacks exist — so they must not protect anything of value. SHA-256 has no known practical collision attack and is the current default. Hashing is one-way: there is no decryption. You can compute a digest from data, but not recover data from a digest, which makes hashes fit for integrity checks and content addressing.

Common use cases

  • Verifying file integrity — compare a download's digest to a published checksum
  • Detecting changes in config, logs, or backups (a different digest means a change)
  • Content addressing in Git, IPFS, and content-addressable storage (the hash is the address)
  • Deduplicating data — identical content yields identical hashes
  • A building block inside keyed HMACs or digital signatures

Worked example

Hashing the single line hello gives:

Input:    hello

MD5:      5d41402abc4b2a76b9719d911017c592
SHA-1:    aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d
SHA-256:  2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824

Notice how the three algorithms return different-length digests for the same input, and how changing one character would scramble every digest completely. For storage that must resist attackers, prefer SHA-256 (or a salted scheme like bcrypt/Argon2 for passwords).

Frequently asked questions

Is hashing the same as encryption?

No. A hash is a one-way function: you can compute a digest from input but you cannot recover the input from the digest, so there is no decryption. Encryption is reversible with a key; hashing is not reversible at all. That is exactly what makes hashes suitable for verifying data without exposing it.

Which algorithm should I use?

Prefer SHA-256. MD5 (128-bit) and SHA-1 (160-bit) are considered broken because practical collision attacks exist, so they must not be used for security. SHA-256 produces a 256-bit digest with no known practical collision attack and is the current industry default for integrity and signatures.

Why are MD5 and SHA-1 still shown?

For compatibility and checksum verification of legacy systems. Many older file-integrity lists, ROM dumps, and download mirrors still publish MD5 or SHA-1 sums, so the tool computes them for matching purposes only, not for new security work.

Are hashes safe for storing passwords?

A plain hash is not enough. Use a slow, salted password-hashing scheme such as bcrypt, scrypt, or Argon2. SHA-256 alone is too fast and would let an attacker test billions of guesses per second against a stolen hash table.

Does hashing run in my browser?

Yes. This tool uses the Web Crypto SubtleCrypto API (crypto.subtle.digest), which computes SHA-256 and SHA-1 natively in the browser. The input never leaves your device.

ν•΄μ‹œ μƒμ„±κΈ°λž€?

μ•”ν˜Έν•™μ  ν•΄μ‹œ ν•¨μˆ˜λŠ” 1λ°”μ΄νŠΈ, ν…μŠ€νŠΈ 파일, 수 GB λ””μŠ€ν¬ 이미지 λ“± μž„μ˜ 크기의 μž…λ ₯을 λ°›μ•„ κ³ μ • 길이의 μž‘μ€ 지문인 λ‹€μ΄μ œμŠ€νŠΈλ₯Ό λ°˜ν™˜ν•©λ‹ˆλ‹€. 같은 μž…λ ₯은 항상 같은 λ‹€μ΄μ œμŠ€νŠΈλ₯Ό λ‚΄κ³ , 1λΉ„νŠΈλ§Œ λ’€μ§‘ν˜€λ„ μ™„μ „νžˆ λ‹€λ₯Έ λ‹€μ΄μ œμŠ€νŠΈκ°€ λ‚˜μ˜΅λ‹ˆλ‹€. 이 λ„κ΅¬λŠ” MD5, SHA-1, SHA-256을 λ™μ‹œμ— κ³„μ‚°ν•˜λ©°, λͺ¨λ“  μ²˜λ¦¬λŠ” λΈŒλΌμš°μ €μ˜ Web Crypto SubtleCrypto API둜 이루어져 μž…λ ₯이 κΈ°κΈ°λ₯Ό λ– λ‚˜μ§€ μ•ŠμŠ΅λ‹ˆλ‹€.

μž‘λ™ 방식

각 μ•Œκ³ λ¦¬μ¦˜μ€ κ³ μ •λœ λΉ„νŠΈ 길이의 λ‹€μ΄μ œμŠ€νŠΈλ₯Ό λƒ…λ‹ˆλ‹€. MD5λŠ” 128λΉ„νŠΈ(16μ§„μˆ˜ 32문자), SHA-1은 160λΉ„νŠΈ(16μ§„μˆ˜ 40문자), SHA-256은 256λΉ„νŠΈ(16μ§„μˆ˜ 64문자)μž…λ‹ˆλ‹€. λ‹€μ΄μ œμŠ€νŠΈλŠ” 16μ§„μˆ˜ ν…μŠ€νŠΈλ‘œ ν‘œν˜„λ˜λŠ”λ°, 각 λ°”μ΄νŠΈκ°€ 09/af 두 문자둜 κΉ”λ”νžˆ λŒ€μ‘λ˜κΈ° λ•Œλ¬Έμž…λ‹ˆλ‹€. 이 μ•Œκ³ λ¦¬μ¦˜ λŒ€λΆ€λΆ„μ€ 머클–λ‹΄κ³ (Merkle–Damgård) ꡬ쑰 μœ„μ— κ΅¬μΆ•λ©λ‹ˆλ‹€. μž…λ ₯을 512λΉ„νŠΈ λΈ”λ‘μ˜ 배수둜 νŒ¨λ”©ν•˜κ³  길이 접미사λ₯Ό 뢙인 λ’€, λ©”μ‹œμ§€λ₯Ό ν•œ 블둝씩 μ••μΆ• ν•¨μˆ˜λ‘œ μ²˜λ¦¬ν•΄ 각 블둝을 λˆ„μ  μƒνƒœμ— μ ‘μŠ΅λ‹ˆλ‹€. κ·Έ μ΅œμ’… μƒνƒœκ°€ λ‹€μ΄μ œμŠ€νŠΈμž…λ‹ˆλ‹€.

결정적인 λ³΄μ•ˆ 속성은 좩돌 μ €ν•­(collision resistance)μž…λ‹ˆλ‹€. 같은 λ‹€μ΄μ œμŠ€νŠΈλ₯Ό λ‚΄λŠ” 두 개의 μ„œλ‘œ λ‹€λ₯Έ μž…λ ₯을 μ°ΎλŠ” 것이 ν˜„μ‹€μ μœΌλ‘œ λΆˆκ°€λŠ₯ν•΄μ•Ό ν•©λ‹ˆλ‹€. MD5와 SHA-1은 μ‹€μš©μ μΈ 좩돌 곡격이 μ‘΄μž¬ν•΄ κΉ¨μ§„ κ²ƒμœΌλ‘œ κ°„μ£Όλ˜λ©°, κ°€μΉ˜κ°€ μžˆλŠ” 것을 λ³΄ν˜Έν•˜λŠ” 데 μ“°λ©΄ μ•ˆ λ©λ‹ˆλ‹€. SHA-256은 μ•Œλ €μ§„ μ‹€μš©μ  좩돌 곡격이 μ—†μ–΄ ν˜„μž¬ κΈ°λ³Έκ°’μž…λ‹ˆλ‹€. κ²°μ •μ μœΌλ‘œ ν•΄μ‹œλŠ” 단방ν–₯μž…λ‹ˆλ‹€. λ³΅ν˜Έν™”κ°€ μ—†μŠ΅λ‹ˆλ‹€. λ°μ΄ν„°λ‘œλΆ€ν„° λ‹€μ΄μ œμŠ€νŠΈλŠ” 계산할 수 μžˆμ–΄λ„ λ‹€μ΄μ œμŠ€νŠΈλ‘œλΆ€ν„° 데이터λ₯Ό 볡ꡬ할 수 μ—†μœΌλ©°, κ·Έλž˜μ„œ 무결성 검사와 μ½˜ν…μΈ  μ–΄λ“œλ ˆμ‹±μ— μ ν•©ν•©λ‹ˆλ‹€.

자주 μ“°λŠ” 경우

  • 파일 무결성 검증 — λ‹€μš΄λ‘œλ“œμ˜ λ‹€μ΄μ œμŠ€νŠΈλ₯Ό 곡개된 체크섬과 비ꡐ
  • μ„€μ •, 둜그, λ°±μ—…μ˜ λ³€κ²½ 감지 (λ‹€μ΄μ œμŠ€νŠΈκ°€ λ‹€λ₯΄λ©΄ λ³€κ²½λœ 것)
  • Git, IPFS, μ½˜ν…μΈ  μ£Όμ†Œ κ°€λŠ₯ μ €μž₯μ†Œμ˜ μ½˜ν…μΈ  μ–΄λ“œλ ˆμ‹± (ν•΄μ‹œκ°€ κ³§ μ£Όμ†Œ)
  • 데이터 쀑볡 제거 — 같은 μ½˜ν…μΈ λŠ” 같은 ν•΄μ‹œ
  • ν‚€κ°€ μžˆλŠ” HMACμ΄λ‚˜ λ””μ§€ν„Έ μ„œλͺ…μ˜ ꡬ성 μš”μ†Œλ‘œ μ‚¬μš©

μ‚¬μš© 예

단일 쀄 helloλ₯Ό ν•΄μ‹±ν•˜λ©΄:

Input:    hello

MD5:      5d41402abc4b2a76b9719d911017c592
SHA-1:    aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d
SHA-256:  2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824

같은 μž…λ ₯에 λŒ€ν•΄ μ„Έ μ•Œκ³ λ¦¬μ¦˜μ΄ μ„œλ‘œ λ‹€λ₯΄κ³  길이도 λ‹€λ₯Έ λ‹€μ΄μ œμŠ€νŠΈλ₯Ό λ‚΄λŠ” 것, 그리고 ν•œ κΈ€μžλ§Œ 바꿔도 λͺ¨λ“  λ‹€μ΄μ œμŠ€νŠΈκ°€ μ™„μ „νžˆ λ’€μ„žμ΄λŠ” 점을 ν™•μΈν•˜μ„Έμš”. 곡격을 막아야 ν•˜λŠ” μ €μž₯μ—λŠ” SHA-256을(λΉ„λ°€λ²ˆν˜ΈλΌλ©΄ bcrypt/Argon2 같은 μ†”νŠΈ 방식을) ꢌμž₯ν•©λ‹ˆλ‹€.

자주 λ¬»λŠ” 질문

ν•΄μ‹œκ°€ μ•”ν˜Έν™”μ™€ 같은 κ±΄κ°€μš”?

μ•„λ‹™λ‹ˆλ‹€. ν•΄μ‹œλŠ” 단방ν–₯ ν•¨μˆ˜μž…λ‹ˆλ‹€. μž…λ ₯으둜 λ‹€μ΄μ œμŠ€νŠΈλŠ” 계산할 수 μžˆμ–΄λ„ λ‹€μ΄μ œμŠ€νŠΈμ—μ„œ μž…λ ₯을 볡ꡬ할 수 μ—†μœΌλ―€λ‘œ λ³΅ν˜Έν™”κ°€ μ—†μŠ΅λ‹ˆλ‹€. μ•”ν˜Έν™”λŠ” ν‚€λ‘œ κ°€μ—­μ μ΄μ§€λ§Œ ν•΄μ‹œλŠ” μ „ν˜€ 가역적이지 μ•ŠμŠ΅λ‹ˆλ‹€. κ·Έλž˜μ„œ 데이터λ₯Ό λ…ΈμΆœν•˜μ§€ μ•Šκ³  κ²€μ¦ν•˜λŠ” μš©λ„μ— λ”± λ§žμŠ΅λ‹ˆλ‹€.

μ–΄λ–€ μ•Œκ³ λ¦¬μ¦˜μ„ 써야 ν•˜λ‚˜μš”?

SHA-256을 ꢌμž₯ν•©λ‹ˆλ‹€. MD5(128λΉ„νŠΈ)와 SHA-1(160λΉ„νŠΈ)은 μ‹€μš©μ  좩돌 곡격이 μ‘΄μž¬ν•΄ λ³΄μ•ˆ μš©λ„λ‘œλŠ” κΉ¨μ§„ κ²ƒμœΌλ‘œ κ°„μ£Όλ©λ‹ˆλ‹€. SHA-256은 μ•Œλ €μ§„ μ‹€μš©μ  좩돌 곡격이 μ—†λŠ” 256λΉ„νŠΈ λ‹€μ΄μ œμŠ€νŠΈλ₯Ό λ‚΄λ©° 무결성과 μ„œλͺ…μ˜ ν˜„μž¬ μ‚°μ—… κΈ°λ³Έκ°’μž…λ‹ˆλ‹€.

μ™œ MD5와 SHA-1도 μ—¬μ „νžˆ 보여 μ£Όλ‚˜μš”?

λ ˆκ±°μ‹œ μ‹œμŠ€ν…œκ³Όμ˜ ν˜Έν™˜ 및 체크섬 검증 λ•Œλ¬Έμž…λ‹ˆλ‹€. 였래된 파일 무결성 λͺ©λ‘, ROM 덀프, λ‹€μš΄λ‘œλ“œ 미러 λ§Žμ€ 곳이 μ—¬μ „νžˆ MD5λ‚˜ SHA-1 합계λ₯Ό κ²Œμ‹œν•˜λ―€λ‘œ, 이 λ„κ΅¬λŠ” 일치 확인 λͺ©μ μœΌλ‘œλ§Œ κ³„μ‚°ν•˜λ©° μƒˆ λ³΄μ•ˆ μš©λ„λ‘œλŠ” μ“°μ§€ μ•ŠμŠ΅λ‹ˆλ‹€.

λΉ„λ°€λ²ˆν˜Έ μ €μž₯에 ν•΄μ‹œκ°€ μ•ˆμ „ν•œκ°€μš”?

평문 ν•΄μ‹œλ§ŒμœΌλ‘œλŠ” λΆ€μ‘±ν•©λ‹ˆλ‹€. bcrypt, scrypt, Argon2 같은 느리고 μ†”νŠΈκ°€ μžˆλŠ” λΉ„λ°€λ²ˆν˜Έ ν•΄μ‹œ 방식을 μ‚¬μš©ν•˜μ„Έμš”. SHA-256 단독은 λ„ˆλ¬΄ λΉ¨λΌμ„œ ν•΄μ‹œ ν…Œμ΄λΈ”μ„ νƒˆμ·¨ν•œ κ³΅κ²©μžκ°€ μ΄ˆλ‹Ή μˆ˜μ‹­μ–΅ 번의 좔츑을 μ‹œλ„ν•  수 μžˆμŠ΅λ‹ˆλ‹€.

해싱이 제 λΈŒλΌμš°μ €μ—μ„œ μ‹€ν–‰λ˜λ‚˜μš”?

λ„€. 이 λ„κ΅¬λŠ” λΈŒλΌμš°μ €μ—μ„œ SHA-256κ³Ό SHA-1을 λ„€μ΄ν‹°λΈŒλ‘œ κ³„μ‚°ν•˜λŠ” Web Crypto SubtleCrypto API(crypto.subtle.digest)λ₯Ό μ‚¬μš©ν•©λ‹ˆλ‹€. μž…λ ₯은 κΈ°κΈ°λ₯Ό λ– λ‚˜μ§€ μ•ŠμŠ΅λ‹ˆλ‹€.