URL Encoder

Query strings break when a value contains a space, an ampersand, or a non-English character. URL Encoder percent-encodes the text you paste, using the same rules as encodeURIComponent.

Encode the value, not the whole address

encodeURIComponent escapes almost everything that is not a letter, digit, or the set - _ . ! ~ * ' ( ). Spaces become %20, not a plus sign. Slashes, question marks, and colons are escaped too. If you paste https://example.com/a?q=hello world, the structure of the URL is escaped and the result is no longer a URL you can open. Paste only the part that belongs in one parameter, then put it back after q= yourself. A plus sign in the input becomes %2B, which is what you want when the plus is data rather than a stand-in for a space.

Percent encoder, and the reverse

People also call this a percent encoder because the output is % followed by two hex digits. URL Decoder runs decodeURIComponent the other way. If a value was encoded twice, one decode still shows percent signs and you run it again. Base64 Encoder is a different alphabet for embedding bytes, not for query strings. Morse Encoder and JWT Encoder solve other encodings. Do not percent-encode a token and assume that hides it. The token is still in the URL for anyone who can read the address bar.

Characters that surprise people

A hash mark starts a fragment in a real URL, so it must be encoded when it is part of a value. An ampersand starts the next parameter, so an unencoded ampersand splits your value in two. Unicode is encoded as UTF-8 bytes, which is what browsers expect. This page does not build the rest of the query, add UTM tags, or choose application/x-www-form-urlencoded plus-for-space behavior.