🔧

Générateur de hachage

Encodage & Chiffrement · Outil en ligne gratuit

Générer des hachages MD5, SHA-1, SHA-256, SHA-512.

Équipe CoderNewbieDernière mise à jour : 2026-09-20

Entrée22 caractères

SHA-256 Digest (hex)

0 caractères

Click "Generate" to compute the SHA-256 hash...

Propulsé par Web Crypto

SHA-1/256/384/512 utilisent l'API native crypto.subtle — rapide, accélérée matériellement et auditée.

MD5 inclus

MD5 est implémenté en JavaScript pur (RFC 1321) car Web Crypto ne le supporte plus. Utile pour les checksums hérités.

Compatible UTF-8

L'entrée est encodée en UTF-8 via TextEncoder — les caractères CJK et emoji produisent des hashes cohérents entre plateformes.

Comment utiliser Générateur de hachage

1Enter or paste your data into the input field.
2Select the desired encoding, hashing, or encryption options.
3Click the action button to process your data.
4Copy the result from the output field.

Fonctionnalités

✓100% gratuit — sans inscription, sans abonnement, sans publicité
✓Fonctionne entièrement dans votre navigateur — vos données ne quittent jamais votre appareil
✓Rapide et léger — résultats instantanés
✓Multiplateforme — compatible ordinateur, tablette et mobile

Qu'est-ce que Générateur de hachage ?

Cryptographic hashing is a one-way function that maps input data of any size to a fixed-length digest. Defined by NIST FIPS 180-4 (SHA family) and RFC 1321 (MD5), hashing is deterministic, fast to compute, and infeasible to reverse. Common algorithms: MD5, SHA-1, SHA-256, SHA-512.

Comment fonctionne Générateur de hachage ?

The input is padded and split into fixed-size blocks. Each block is processed through a compression function that updates an internal state. The final state is output as the hash digest. The avalanche effect ensures changing one bit changes ~50% of output bits.

Cas d'usage courants

✓File integrity — verify downloads match expected checksums
✓Password storage — store hashes (with salt) instead of plaintext
✓Git commit IDs — SHA-1 hashes identify commits
✓Data deduplication — identical data produces identical hashes

MD5 vs SHA-256

MD5 (128-bit, RFC 1321) is broken for security purposes — collisions can be found in seconds. It remains acceptable for non-security checksums. SHA-256 (256-bit, FIPS 180-4) is cryptographically secure and recommended for all security applications including password hashing (with bcrypt/Argon2 preferred) and digital signatures.

Sécurité et confidentialité

This tool runs entirely in your browser. For password storage, NEVER use plain MD5 or SHA — use bcrypt, scrypt, or Argon2 with a unique salt per user. Hashing is one-way; you cannot recover the original input from a hash.

Détails techniques

MD5: 128-bit (RFC 1321), broken. SHA-1: 160-bit (FIPS 180-4), deprecated for security. SHA-256: 256-bit, recommended. SHA-512: 512-bit, 64-bit optimized. Output is hexadecimal (0-9, a-f). HMAC (RFC 2104) combines a key with a hash for message authentication. Avalanche effect: 1-bit input change → ~50% output bits change.

Questions fréquentes

Can I reverse a hash to get the original?

No. Hashing is one-way by design. You can only verify if a given input produces the same hash (verification), not recover the input from the hash.

Is MD5 safe for passwords?

No. MD5 is broken and fast to brute-force. Use bcrypt, scrypt, or Argon2 with per-user salts for password storage.

What is HMAC?

HMAC (Hash-based Message Authentication Code, RFC 2104) combines a secret key with a hash function to verify both data integrity and authenticity. It is used in API signing (e.g., AWS SigV4).