URL Encode/Decode

Percent-encode a URL or decode an encoded query string back to text. Pure JavaScript, runs in your browser — your redirect URLs never leave the device.

Conversions

Encode

About URL Encode/Decode

URL Encode/Decode swaps between a raw URL or query string and its percent-encoded form — the one browsers and servers expect. Encode a redirect parameter that contains spaces, slashes, or ampersands before sending a test request; decode an already-encoded URL you received in a webhook to see what the user actually clicked. The tool uses JavaScript's encodeURIComponent/decodeURIComponent with proper UTF-8 handling, so non-Latin characters round-trip correctly. Everything runs locally in your browser, so redirect URLs with sensitive tokens or session IDs stay on your device.

Best for

Building test requests with query params that contain spaces or special chars
Decoding a webhook URL parameter to see the redirect destination
Encoding a URL inside a URL (next= parameter) without breaking the outer URL

Pros

+RFC 3986 percent-encoding with proper UTF-8 support
+Bidirectional — encode raw to %XX, or decode %XX back to raw
+Local JavaScript only — sensitive redirect URLs stay on your device

Cons

−No automatic parsing of which characters to keep vs encode — pick modes
−Mixed encoding (already-encoded URLs encoded twice) is a common mistake

How to use URL Encode/Decode

1
Select or upload the source files from your local device storage.
2
Specify conversion settings, options, or target output formats.
3
Wait for the client-side browser logic to process the files securely.
4
Download the finalized outputs directly to your system.

Frequently Asked Questions

What's the difference between encodeURI and encodeURIComponent?

encodeURIComponent encodes everything including '?' and '&' — for query values. encodeURI keeps scheme separators so the URL still works。This tool defaults to encodeURIComponent for the most common case (encoding a single value); switch modes if you need an entire URL passed safely.

Why are spaces sometimes '+' and sometimes '%20'?

The '+' form comes from application/x-www-form-urlencoded (HTML form submissions); '%20' is the strict RFC 3986 form. Most modern APIs prefer '%20'; the older '+' form still works but can be misinterpreted by some servers. This tool uses the modern '%20' form by default.

Can I decode a URL that's been encoded twice?

Yes — just run the decode button twice. Each pass strips one layer of encoding. Watch out if you accidentally double-encode an already-encoded URL when building test requests.

Does this handle non-ASCII characters?

Yes. UTF-8 percent-encoding is used by default, so accented Latin, Cyrillic, Arabic, CJK, and emoji characters all encode to valid sequences and decode back correctly. Older ISO-8859-1 endpoints may misinterpret them — match the server's expected charset.

Are my redirect URLs and tokens uploaded?

Never. Encode and decode run via JavaScript encodeURIComponent/decodeURIComponent in your browser. URLs containing session IDs or next= redirect targets stay on your device the whole time.

Related tools

FREE

100% Free

No hidden fees, no subscriptions, and no limits. Enjoy complete access to all features gratis.

SIGNUP

No Signup Required

Start converting immediately without creating an account or sharing email address.

PRIVACY

Private & Secure

Your files never leave your device. All processing is completed locally for maximum privacy.

BATCH

Batch Conversion

Convert multiple files simultaneously to save time. Fast and efficient multi-file queue.

LOCAL

Runs in Browser

Utilizes advanced client-side WebAssembly technology to process files directly inside your tab.

FORMATS

200+ Formats

Supports a wide variety of formats including images, documents, audio, video, and more.

USER REVIEWS