4-tab workbench - 20+ encodings (URL/Base64/HTML/JS/CSS/hex/binary/octal/Morse/ROT-N/Atbash) + multi-view (paste once, see every format) + hashing (MD5/SHA family/HMAC) + Unix-timestamp ↔ ISO 8601 conversions.
iat / exp conversions.Encoder / Decoder is the constant-companion workbench for the format-shifting that fills a bug-bounty / pentest day. Four focused tabs: Encode & Decode (pick from 20+ formats, encode or decode with a click), All encodings (paste a payload once, see it rendered in every format simultaneously - perfect for picking the right WAF bypass), Hash (MD5 + entire SHA family + HMAC variants), Date / Time (Unix-timestamp ↔ ISO 8601 ↔ local time with live conversion).
Coverage favours bug-bounty reality: three URL-encoding variants (standard, percent-encode-all, double-encoded for WAF bypass), three HTML-entity styles (named, decimal, hex), JavaScript string escapes both \xXX and \uXXXX, CSS escape, binary / octal / decimal byte arrays, plus the cipher / obfuscation classics (ROT13, ROT-N with shift, Atbash, Morse).
Hashing covers everything the modern stack uses: MD5 (RFC 1321 pure-JS implementation verified against the spec test vectors), SHA-1, SHA-256, SHA-384, SHA-512 (Web Crypto API), and HMAC-SHA-256 / HMAC-SHA-512 with arbitrary key (verified against RFC 4231). "Hash with all algorithms" produces every digest simultaneously.
100% client-side. Pasted payloads, secrets, sensitive timestamps never leave the browser.
encodeURIComponent semantics, percent-encode all chars (every byte as %XX for WAF evasion), and double-encoded (canonical WAF bypass).-/_ for +//).&), decimal (A), hex (A). Decoder handles all three plus mixed input.\xXX for non-printable (printable as-is), \uXXXX for every char.\41 \20 hex escape format.0x prefix), 8-bit binary, octal, ASCII decimal - all space-separated for readability.iat / exp claims to readable timestamps to spot expiry-window bugs.This one is free in your browser. Sign up for server-side recon, scan history, and projects.
Create free account Sign inPure-JS port of the RFC 1321 algorithm, verified against the spec’s test vectors: empty string → d41d8cd98f00b204e9800998ecf8427e, "a" → 0cc175b9c0f1b6a831c399e269772661, "abc" → 900150983cd24fb0d6963f7d28e17f72, etc. All four canonical test vectors pass exactly.
The browser’s Web Crypto API gives constant-time, audited, hardware-accelerated implementations of SHA-1 through SHA-512 and HMAC. We use it directly; what you see is what every browser-based crypto pipeline uses.
No. 100% client-side. The encoder, decoder, hashes and date conversions all run in your browser. Pasted text never touches our infrastructure.
Yes. Click Swap to move the output to the input, then encode again. The "live" toggle is also useful for chained workflows - flip formats and see results without re-clicking.