Real-time ConversionNo Server RequiredURI + Component Modes

How It Works

1

Paste Your Text or URL

Enter the text or URL you want to encode or decode.

2

Choose Direction

Toggle between Encode and Decode, or use quick action buttons for specific modes.

3

Copy the Result

The output updates in real-time. Copy it with one click.

Frequently Asked Questions

What is URL encoding?
URL encoding (also called percent-encoding) replaces unsafe or special characters in a URL with a percent sign (%) followed by two hexadecimal digits representing the character's ASCII code. For example, a space becomes %20 and an ampersand becomes %26.
What is percent encoding?
Percent encoding is another name for URL encoding. It gets its name from the percent sign (%) used as an escape character. Each encoded character is represented as %HH, where HH is the hexadecimal value of the character.
When should I encode URLs?
You should encode URLs whenever they contain special characters like spaces, ampersands, question marks, or non-ASCII characters like unicode. This is essential for query string parameters, form data, and any URL that will be embedded in HTML or passed as a parameter.
What special characters need encoding in URLs?
Characters that must be encoded include spaces, &, =, ?, #, %, +, and any non-ASCII characters. Reserved characters like /, :, and @ have special meaning in URLs and should only be encoded when used outside their reserved purpose.
What is the difference between encodeURI and encodeURIComponent?
encodeURI encodes a full URI but preserves characters that have special meaning in URLs (like :, /, ?, #, &). encodeURIComponent encodes everything except letters, digits, and a few special characters (- _ . ! ~ * ' ( )), making it suitable for encoding individual query parameters.
Share:

About URL Encoder

What this tool does

Encoder and decoder tools convert data between Base64, URL-encoded, HTML entities, ROT13, Morse code, binary, hex, and JWT formats. They handle both encoding (plain to encoded) and decoding (encoded back to plain).

Why use this tool

Web developers constantly encounter encoded data in APIs, URLs, tokens, and configuration files. Being able to decode a JWT payload or Base64 string instantly saves round-trips to the terminal or Stack Overflow.

How it works

Each tool applies a specific encoding algorithm to your input bytes. Base64 maps every 3 bytes to 4 ASCII characters. URL encoding escapes special characters with percent-hex pairs. JWT decoding splits the token at dots and Base64-decodes each segment.

Pro tip

When debugging JWTs, always check the "exp" (expiration) claim first. Most authentication bugs come from expired tokens, and the decoded timestamp is easy to overlook.

Love this tool? Explore 12467+ more

Free online tools for images, PDFs, text, code, and more. All running in your browser.

Explore All Tools