Skip to content
Quickora
Menu

URL Encoder and Decoder

Percent-encode text for use in URLs and query strings, or decode %20-style escapes back into readable text. Handles accents and emoji (UTF-8).

Get new free tools from Quickora

Join the list and I’ll send you new calculators, converters, and everyday utilities when they launch.

No spam. Unsubscribe anytime.

How to use it

  1. Choose Encode or Decode.
  2. Paste your text or URL.
  3. Choose “component” encoding for a single parameter value, or “full URL” to keep characters like / and ? intact.

Examples

Encoding a search term

“café & bar” encodes to caf%C3%A9%20%26%20bar as a query value — the é becomes two UTF-8 bytes and & is escaped so it isn't read as a separator.

Decoding a link

https://example.org/?q=hello%20world decodes to https://example.org/?q=hello world.

Component vs full URL encoding

URLs reserve some characters for structure: / separates path segments, ? starts the query, & separates parameters. Component encoding (encodeURIComponent) escapes those too, which is what you want for a single value. Full-URL encoding (encodeURI) leaves them alone so an entire address stays valid.

Non-ASCII characters are converted to UTF-8 bytes and each byte is written as %XX. Decoding reverses this; a malformed sequence such as a lone % is reported as an error.

Frequently asked questions

Should spaces be %20 or +?

In paths, use %20. In HTML form-encoded query strings, + also means a space. This tool produces %20, which works everywhere, and the decoder optionally treats + as a space.

Why does decoding fail?

A % must be followed by two hex digits forming valid UTF-8. Text like “100%” isn't valid encoded data; encode it first to get 100%25.

Is my data sent anywhere?

No, encoding and decoding run in your browser.

Found this useful? Quickora is free to use — buy us a coffee (opens in a new tab) to help keep it that way.

More in Text · Last reviewed October 2026