URL Encoder

Percent-encode text and URLs, live.

Plain text
Encoded
Need the reverse? Decode a URL

Use Component for a single value like a query parameter; use Full URL to encode a whole address while leaving its structure intact.

Sample Copy result Download Clear

About the URL Encoder

What is URL encoding?

URLs can only contain a limited set of characters. Anything outside that set — a space, an ampersand, an accented letter, a slash inside a value — has to be written as a percent-code like %20 or %26. That's URL encoding (also called percent-encoding), and it's what keeps links from breaking when they carry search terms, names or other free text.

This encoder converts text to its percent-encoded form as you type, correctly turning Unicode characters into their UTF-8 byte sequences. It all happens in your browser, so nothing you paste is ever sent anywhere.

Component vs Full URL

Choosing the right mode matters:

  • Component encodes everything that isn't a plain letter or digit, including : / ? & =. Use it for a single piece of a URL — one query value, a path segment, a form field. This matches JavaScript's encodeURIComponent.
  • Full URL leaves the characters that give a URL its structure (: / ? & = #) alone and only encodes the rest. Use it when you have a whole address with spaces or accents that you want to make valid without breaking it apart. This matches encodeURI.

Common Use Cases

  • Query strings: safely put a search term or email into ?q=.
  • APIs: build request URLs that won't break on special characters.
  • Links in emails or docs: fix addresses that contain spaces or accents.
  • Debugging: see exactly how a value will look once it's in a URL.

Need to read an encoded link? Use the URL Decoder. Working with binary or file data instead? Try the Base64 Encoder and Decoder.

Frequently Asked Questions

What's the difference between the two modes?

Component mode encodes reserved characters like & and = too, which is right for a single value. Full URL mode preserves those so a complete address stays usable. When in doubt for a single field, use Component.

Does it handle spaces and accented characters?

Yes. A space becomes %20, and Unicode characters are encoded as their UTF-8 bytes — for example é becomes %C3%A9.

Why is a space sometimes shown as + elsewhere?

In the query part of some forms, spaces are written as + (application/x-www-form-urlencoded). Percent-encoding uses %20, which is valid everywhere in a URL and is what this tool produces.

Is my text uploaded anywhere?

No. Encoding happens entirely in your browser, so your text never leaves your device.