URL Encode

Percent-encode special characters, spaces, and non-ASCII text for safe use in URLs, query parameters, and links. Build a redirect URL, generate a mailto: link with a prefilled subject, or pass a JSON blob through a GET parameter, all in your browser.

URL-encoded output

Usage examples

Putting special characters into a query parameter

A search term or value containing &, =, spaces, or non-ASCII characters can break a query string. Encoding it first keeps the URL intact.

Embedding a message in a share link

When you need to put free-form text into a URL — a social share link, an email subject parameter — encoding it first keeps the link from breaking.

Using a non-ASCII filename in a URL path

If a filename with spaces or non-ASCII characters needs to appear as part of a URL path, using the encoded value is the safe approach.

Building a redirect URL with a return path

A login flow that redirects back to ?returnTo=/dashboard?tab=billing needs the inner URL encoded first, otherwise its own ? and & get parsed as part of the outer query string.

Generating a mailto: link with a prefilled subject and body

A mailto:user@example.com?subject=...&body=... link breaks if the subject or body contains &, #, or line breaks. Encoding each value keeps the link clickable.

Passing a JSON blob through a GET parameter

Some APIs accept small filter objects as ?filter={"status":"active"} in the query string. The braces, quotes, and colons all need encoding to survive as a single parameter.

Quick reference

ASCII punctuation & space

CharacterEncoded
U+0020%20
!!
"%22
#%23
$%24
%%25
&%26
''
((
))
**
+%2B
,%2C
/%2F
:%3A
;%3B
<%3C
=%3D
>%3E
?%3F
@%40
[%5B
\%5C
]%5D
^%5E
`%60
{%7B
|%7C
}%7D
~~

Non-ASCII & control characters

CharacterEncoded
U+000A%0A
U+0009%09
é%C3%A9
ñ%C3%B1
ü%C3%BC
€%E2%82%AC
£%C2%A3
©%C2%A9
—%E2%80%94
한%ED%95%9C
日%E6%97%A5
😀%F0%9F%98%80

Frequently asked questions

Is the text I type sent to a server?

No. Encoding happens entirely in your browser, and what you type is never sent to a server.

Can I paste a whole URL in here?

This tool uses encodeURIComponent. Encoding an entire URL (including https://...) would also encode delimiters like :, /, and ?, breaking it as a valid URL. Use this for a value that goes INTO a URL — a query parameter value or a single path segment — not for a complete URL.

How are spaces handled?

Spaces are encoded as %20. (The + convention is a different rule used specifically for form-data submissions, so this tool doesn't use it.)

Does this handle non-English text and emoji?

Yes. Characters are percent-encoded based on their UTF-8 bytes, so non-English characters, emoji, and other Unicode text are all handled correctly.

What's the difference between encodeURIComponent and encodeURI?

encodeURI (not used here) assumes you're passing a full URL, so it leaves reserved delimiters like :, /, ?, #, and & untouched. encodeURIComponent, which this tool uses, assumes you're passing a single value that belongs inside a URL, so it also encodes those delimiter characters. That's why this tool isn't suited for encoding a complete URL.

Which characters are left unencoded?

Per RFC 3986's unreserved set, encodeURIComponent leaves A-Z, a-z, 0-9, and - _ . ~ untouched. Every other character, including reserved delimiters like : / ? # [ ] @ ! $ & ' ( ) * + , ; =, gets percent-encoded.

Why does + sometimes mean space and sometimes mean a literal plus sign?

It depends on the context. In application/x-www-form-urlencoded data (classic HTML form submissions), + represents a space. In a standard URI per RFC 3986 — which is what this tool produces — + is just a literal plus character, and a space is always %20. Mixing the two conventions is a common source of bugs.

Is URL encoding the same as encryption or hashing?

No. Percent-encoding is fully reversible with no key involved — anyone can decode it back to the original text instantly. It exists purely to make text safe to transmit inside a URL, not to hide or protect its contents.