Data Encoding & Decoding

Decoder

The Decoder tool encodes and decodes data in various formats: URL, HTML, Base64, Hex, Octal, Binary, and Gzip. It also supports chaining multiple encoding operations, which is essential for decoding multi-layer obfuscated payloads.

Encoded data hides malicious payloads from simple signature-based detection. The Decoder helps you see through the obfuscation during manual testing.

Using the Decoder

Open Decoder from the top menu or the Window menu. Paste your data into the input field, choose the operation, and see the output live.

1

Decode

Convert encoded data back to its original form. Use when you find suspicious encoded strings in requests/responses.

2

Encode

Convert raw data into a specific format. Useful when you need to generate a payload that matches the target encoding.

3

Smart Decode

Attempts multiple decode operations automatically to peel layers of obfuscation.

4

Smart Encode

Auto-applies appropriate encoding based on context (URL, HTML, both).

Supported Encodings

EncodingDecodeEncodeExample
URL Encodedecode URL-encoded textURL-encode text%20%3C%3E
HTML Encodedecode HTML entitiesHTML-encode special chars<script>
Base64decode Base64 to raw bytesencode to Base64SGVsbG8gV29ybGQ=
Hexhex → ASCII/UTF-8ASCII/UTF-8 → hex48656c6c6f
ASCII Hexhex chars representing ASCII bytesASCII bytes to hex chars0x48 0x65 0x6c 0x6c 0x6f
Octaloctal → texttext → octal110 145 154 154 157
Binarybinary string → texttext → binary string01001000 01100101
Gzip Compressdecompress gzipped datacompress with gzipcompressed blob

Common Use Cases

Decode obfuscated JavaScript

Web applications often obfuscate malicious payloads. Use Decoder to reverse encoding chains.

STEPS

Paste obfuscated code → try Base64 decode → try URL decode → try HTML decode. Repeat until readable.

Decode JWT tokens

JWTs use Base64URL encoding. Decode the payload to read claims before tampering.

STEPS

Copy JWT → Base64 decode (URL-safe variant) → JSON pretty-print → modify claims → re-encode.

Convert CSRF token to hex

Some APIs require token in hexadecimal instead of raw. Use Encoder to convert.

STEPS

Paste token string → Hex encode → use hex value in request.

Decompress gzipped response

Some servers gzip responses. View raw content by decompressing.

STEPS

Copy gzipped blob (from raw response view) → Gzip decompress → view clear text.

Chaining Encodings

Some payloads are encoded multiple times. The chain feature lets you apply several encodings in sequence:

Example: Double-encoded XSS payload
Original: <script>alert(1)</script>
Step 1 (HTML encode): &lt;script&gt;alert(1)&lt;/script&gt;
Step 2 (URL encode): %26lt%3Bscript%26gt%3Balert(1)%26lt%3B/script%26gt%3B
To decode: paste double-encoded → URL decode → HTML decode → clean XSS.

Tip

Always try Smart Decode first — it automatically attempts common encoding layers and often reveals the underlying payload in one click.