エンコーディングワークベンチ
プライバシー保護ハッシュ、Base64などのエンコード/デコードを行います。
Detected Encoding Layers
No output yet
Choose an operation above or click Auto-Detect Layers.
What is Encoding vs Hashing?
Encoding transforms data into a different representation that can be reversed (decoded). Common formats include Base64 — used to transmit binary data over text channels — URL encoding, HTML entity encoding, and hexadecimal. Encoding is not encryption; it offers no confidentiality.
Hashing is a one-way mathematical transformation. A cryptographic hash function takes any input and produces a fixed-length fingerprint. You cannot reverse a hash to retrieve the original input. Hashes are used to verify file integrity, store passwords securely, and generate digital signatures.
How to Use This Tool
- Encode / Decode tab: Paste text and choose an operation (Base64, URL, HTML, Hex), or click Auto-Detect Layers to automatically unwrap multiple nested encodings.
- Hash tab: Enter text or select a file, choose algorithms, and click Hash All. Enable HMAC mode to compute keyed hashes with a shared secret.
- Identify tab: Paste an unknown hash or encoded string and click Identify to see likely algorithms with confidence ratings.
Layered Encoding Explained
Real-world data is often encoded multiple times. For example, a payload could be URL-encoded, then Base64-encoded, then placed inside a hex string. The Auto-Detect Layers feature inspects the input pattern, attempts each decoding in sequence, and visualises every step as a card so you can see exactly how the data was wrapped.
Hash Algorithm Guide
- MD5 — 128-bit output. Cryptographically broken; use only for legacy compatibility or non-security checksums.
- SHA-1 — 160-bit output. Deprecated for security use. Still found in older Git commits and certificates.
- SHA-256 — 256-bit output. General-purpose, widely used in TLS, code signing, and data integrity checks.
- SHA-512 — 512-bit output. Higher security margin; preferred for password-adjacent workflows.
- bcrypt — Adaptive password-hashing function with a configurable cost factor. Use for storing passwords; not for data integrity.