Skip to main content
100% private — runs in your browser

URL Encode / Decode

Encode or decode URLs and query parameters safely in your browser.

Input

Output

How to use URL Encode / Decode

  1. Paste text or a URL

    Enter the string you want to encode or decode.

  2. Choose the mode

    Select component or full-URI mode and whether to treat + as space when decoding.

  3. Encode/Decode and copy

    Run the conversion and copy the result.

Frequently asked questions

What is the difference between encodeURI and encodeURIComponent?

encodeURIComponent escapes reserved characters and is best for parameter values; encodeURI preserves URL structure characters like : / ? & = #.

Why does %20 sometimes appear as +?

In HTML form/query-string encoding, spaces may be represented as +. Use the decode option to interpret + as a space when needed.

Is my data sent anywhere?

No. Encoding and decoding run locally in your browser.

Why do I get an error when decoding?

The input likely contains an invalid percent-escape sequence. Check for stray % characters or truncated encoded text.

Should I double-encode a URL?

Usually no. Encode once at the appropriate level (component or full URL) to avoid producing %25 sequences and broken links.

About URL Encode / Decode

The URL Encode / Decode tool converts text to percent-encoded form and back, helping you build and debug URLs, query strings, and API requests. It supports encoding full URIs as well as individual components, and can interpret `+` as a space when decoding form-style query strings. Everything runs locally in your browser, so parameters and tokens you inspect stay on your device.

Percent-encoding basics

URLs can only contain a limited set of characters. Reserved or unsafe characters — such as spaces, ampersands, question marks, and non-ASCII text — must be percent-encoded (for example, a space becomes `%20`). Proper encoding ensures that servers and browsers interpret parameters correctly. Without it, a value containing `&` or `=` can break a query string or be parsed as multiple parameters.

Component vs full URI encoding

Use component encoding (`encodeURIComponent`) for individual query parameter names and values, because it escapes characters like `&`, `=`, and `?`. Use full URI encoding (`encodeURI`) when you want to encode spaces and unsafe characters in an entire URL while preserving its structure (`://`, `/`, `?`, `#`). Choosing the right mode prevents double-encoding or broken URLs.

Decoding and common pitfalls

Decoding reverses percent-encoding, but malformed sequences (like a stray `%`) will cause errors — the tool reports these clearly. In `application/x-www-form-urlencoded` data, spaces are often encoded as `+`; the optional toggle lets you decode those correctly. Since encoding is reversible and not security, avoid pasting secrets into untrusted tools — this one runs entirely locally for privacy.

Use URL Encode / Decode on your site

This tool runs free and private in the browser. Paste it anywhere — blog posts, documentation, team wikis — and your visitors will use it without leaving your site. The embed includes a small "Made with The Tools Today" credit link.

Open the tool page →

Your privacy, your choice

We use cookies to understand how the site is used and to show relevant ads. Every tool on this site runs entirely in your browser, so the files and text you process are never uploaded. Read our privacy policy.