Percent-encode a string or decode it (RFC 3986).

Percent-encoding and decoding (RFC 3986) run entirely in your browser — nothing is uploaded.

Plain text
Encoded
The input could not be decoded.

About URL Encode / Decode

This URL encoder and decoder percent-encodes strings according to RFC 3986 and decodes them back, live in two panes. Type plain text on one side and the encoded form appears on the other; paste an encoded query value and it is decoded instantly. A swap button reverses direction.

Percent encoding replaces characters that are unsafe in URLs — spaces, accents, ampersands, slashes and other reserved characters — with %XX escape sequences. The tool encodes strictly (spaces become %20, not +), which is the correct form for path segments and modern query strings.

It runs entirely in your browser, so callback URLs, signed links and query strings containing tokens are never sent to a server. Use it to url encode online before building links, or to make an unreadable %-riddled parameter human-readable again while debugging.

How to use URL Encode / Decode

  1. Type or paste the text or URL component you want to encode in the plain-text pane.
  2. Read the percent-encoded result in the other pane — it updates as you type.
  3. To decode, paste the encoded string into the encoded pane instead.
  4. Use Swap to flip direction, then Copy the side you need.

Frequently asked questions

Encode individual components — a query value, a path segment, a redirect target — not the full URL. The encoder escapes reserved characters like / and ?, so running a complete URL through it would break its structure.

It follows RFC 3986, where a space is %20. The + convention only applies to the legacy application/x-www-form-urlencoded format. %20 is safe in both contexts, which is why strict encoders prefer it.

No. Encoding and decoding run entirely in your browser, so URLs containing session tokens, API keys or personal data stay on your machine.

Yes — free and unlimited, no sign-up required.

Decoding fails when a % sign is not followed by two valid hex digits — usually because the string was truncated or double-encoded. Fix the malformed sequence or decode twice if the value was encoded twice.


Popular searches
url encode url decode percent encode url encoder online decode url string encode uri component
Need help?
Found an issue with this tool? Let our team know.
Report an issue

Add this free tool to your own website — copy and paste the code below.