toolgarden.xyz
中文

Info Encoder / Decoder

Free online tool for Unicode, URL, UTF16, Base64, MD5, SHA1, hex, JWT, Cookie, Gzip, and string escaping

Input

Operation

Encode / Hash

Decode / Parse

Output · Encode

Result will appear here

About this tool

The information codec collects common text encodings, digests, escaping, and structure parsers in one workspace, including URL, Unicode, UTF-16, Base64, hexadecimal, HTML entities, query strings, cookies, JWT, MD5, SHA-1, and gzip modes. These operations serve different purposes: encoding represents data, escaping embeds it safely, a digest fingerprints it, and compression reduces size.

Processing happens within the current browser session and is intended for development diagnostics and one-off inspection. Identify the actual input format before choosing a mode, because repeatedly encoding an unknown value often creates `%25`, extra backslashes, or unreadable text.

How to use it

  1. Identify the input format

    Use the source context to decide whether the value is text, a URL parameter, Base64, hexadecimal, JWT, or compressed data.

  2. Choose one operation

    Select encode, decode, digest, format, or decompress instead of stacking uncertain transformations.

  3. Validate the meaning

    Check character encoding, byte length, and parsed fields, then confirm the destination can read the result.

Input and output example

One string through several encodings. Note that hashing is one-way and is not something the decoder can reverse.

Input text
hello 世界
Encoded forms
URL encoding      hello%20%E4%B8%96%E7%95%8C
Base64            aGVsbG8g5LiW55WM
URL-safe Base64   aGVsbG8g5LiW55WM
Unicode escapes   hello \u4e16\u754c
SHA-256           f5e8... (one-way, not reversible)

Supported range and limits

What it covers
Unicode escapes, URL percent-encoding, Base64, common hashes, JWT decoding, cookie parsing and Gzip
Base64 variants
The standard alphabet and the URL-safe one (- and _ replacing + and /) produce different output; mixing them fails to decode
Hashing is not encryption
Hashes are one-way and cannot be reversed. They verify integrity and compare values; they cannot protect something you need back
Two URL encoders
encodeURIComponent escapes & = ? and other delimiters, encodeURI keeps them; the wrong one breaks URL structure
JWT decoding
Decodes the header and payload and can verify an HS256 signature; the payload is Base64, not encrypted, so anyone can read it
Where it runs
Entirely in the browser; nothing you paste is uploaded

When you would use it

  • Debugging request data

    Decode URLs, query strings, cookies, or JWT payloads to find double encoding and field-boundary errors.

  • Preparing a data fragment

    Convert text to Base64, Unicode escapes, or hexadecimal for configuration, protocol, and test fixtures.

  • Checking the intermediate steps of a signature

    When an API signature is rejected, compare each stage; parameter concatenation, URL encoding, hashing; against the documentation to find where they diverge.

What to know before you start

  • Base64, hexadecimal, and URL encoding provide no confidentiality and are straightforward to reverse.
  • MD5 and SHA-1 are unsuitable for new password storage or collision-resistant security uses; keep them for compatibility and basic checks only.
  • JWT decoding does not verify a signature, and gzip decompression should avoid untrusted inputs with suspicious expansion size.

Related concepts

character encoding
The mapping between characters and bytes, which must match the convention used by the data producer.
digest
A fixed-length fingerprint computed from input; it is one-way, but older algorithms may lack adequate collision resistance.

Frequently asked questions

Does Info Encoder / Decoder upload my content to a server?
No. Encoding, decoding, hashing, and parsing all run locally in your browser, so your input is not uploaded to a server.
Which formats does Info Encoder / Decoder support?
It supports common text workflows such as Unicode, URL, UTF16, Base64, MD5, SHA1, hex, HTML entities, JWT, cookies, Gzip, URL parameters, and string escaping.
Does JWT decode also verify signatures?
By default it only decodes the JWT header and payload so you can inspect the contents quickly. Signature verification is handled in the dedicated JWT tool.
Which Gzip inputs are supported?
The tool accepts gzip data in Base64 or hex form and shows the decompressed result directly on the page for easy copying or follow-up processing.
Why did Base64 decoding fail?
Usually an alphabet mismatch. Standard Base64 uses `+` and `/`; the URL-safe variant uses `-` and `_`. JWTs and URL parameters use the latter, and decoding them with the standard alphabet fails. The next most common cause is missing `=` padding lost in copying.
Can a hash be decrypted back to the original?
No. Hashing is a one-way function and irreversible by design. Its purpose is verifying integrity and comparing values. Claims of "decrypting MD5" mean looking up a precomputed rainbow table, not mathematical recovery.

Related tools