URL Encoder/Decoder

Encode query parameter values and decode percent-encoded strings without guessing which characters need escaping. Useful for API requests, redirect links, mailto strings, and debugging URLs copied from logs or browsers.

Input

Quick examples:

Client-Side Processing

Input Data Stays on Device

Instant Local Execution

Something wrong with this tool? Report it

Find this tool useful? Support the project to keep it free!

Buy me a coffee

What is URL Encoder/Decoder?

URL encoding, also called percent encoding, converts characters that can break or confuse a URL into a transport-safe format. Spaces, ampersands, question marks, hashes, non-ASCII characters, and many reserved symbols are transformed so they can move through browsers, APIs, redirects, and query strings reliably.

This matters most when you are working with parameter values rather than plain page URLs. The tool is useful because it lets you encode just the parts that need escaping, decode unreadable query strings quickly, and catch mistakes before a broken link or request reaches production.

How to Use URL Encoder/Decoder

Paste your text or URL-encoded string into the input

Click "Encode" to convert special characters to URL format

Click "Decode" to convert URL-encoded text back to normal

Copy the result using the copy button

Use the "Clear" button to start fresh

Common Use Cases

Developers encoding individual query parameters before sending search terms or callback URLs to an API.
Support teams decoding long percent-encoded links copied from logs, browser address bars, or analytics tools.
Marketers building campaign URLs that contain spaces, symbols, or UTM values entered by non-technical teammates.
Product teams creating mailto links, redirect targets, or deep links that break if reserved characters are left raw.
Backend engineers checking whether a request bug is caused by encoding the whole URL instead of only the parameter values.

Example Input and Output

This is a common case: a readable query parameter needs to become safe for a URL before it is appended to an API request or redirect target.

Readable parameter value

customer=Acme & Sons / Europe?stage=beta launch

Encoded value

customer%3DAcme%20%26%20Sons%20%2F%20Europe%3Fstage%3Dbeta%20launch

Best practice

Encode parameter values, not entire URLs, unless you know the receiving system expects a fully encoded string.

Privacy

The encoder runs locally in the browser, which helps when you are working with callback URLs, tokens, or internal links that should not leave your device.

Frequently Asked Questions

What characters get encoded?

Special characters like spaces, &, ?, #, %, and non-ASCII characters get encoded. For example: space → %20, & → %26, ? → %3F. Letters, numbers, and some safe characters like - and _ don't need encoding.

Is this the same as HTML encoding?

No. URL encoding is for URLs (spaces become %20), while HTML encoding is for HTML content (< becomes <). They serve different purposes.

Can I encode an entire URL?

Yes, but be careful. If you encode an entire URL including http://, the :// will also be encoded, breaking the URL. Usually, you only encode the query parameter values.

What is the difference between %20 and + for spaces?

Both can represent spaces in certain contexts, but %20 is the general URL-encoding form. Plus signs are common in form-encoded query strings, so use the format expected by the system you are working with.

Why does my decoded value still look wrong?

It may have been encoded more than once, or it may contain HTML entities, Base64, or another format layered on top. Decode only one layer at a time and inspect the result after each step.

Is the data I paste here sent anywhere?

No. Encoding and decoding happen in your browser, which is useful when the URL contains internal endpoints, private tokens, or sensitive callback parameters.