Free URL Encoder & Decoder Online

Percent-encode query strings, special characters, and non-ASCII text, or decode %20-encoded URLs instantly. 100% in your browser, no signup.

0 characters

Common Use Cases

Query Parameters

Original:
name=John Doe&city=New York
Encoded:
name=John%20Doe&city=New%20York

Special Characters

Original:
hello@world.com?ref=top#section
Encoded:
hello%40world.com%3Fref%3Dtop%23section

About URL Encoding

  • URL Encoding: Also known as percent-encoding, converts special characters to a format that can be transmitted over the Internet
  • Why encode? URLs can only contain ASCII characters. Special characters need to be encoded
  • Common encodings: Space → %20, @ → %40, # → %23, ? → %3F, & → %26
  • Use cases: Query parameters, API requests, form data, email addresses in URLs
  • Reserved characters: Characters like :, /, ?, #, [, ], @, !, $, &, ', (, ), *, +, ,, ;, = have special meaning in URLs

How to Use

  1. 1Choose between 'Encode' or 'Decode' mode using the toggle button
  2. 2Paste or type your URL or text in the input field
  3. 3Click 'Process' to encode or decode the text
  4. 4Review the output in the result area below
  5. 5Click 'Copy' to copy the result to your clipboard
  6. 6Use 'Swap' to reverse the operation quickly

URL Encoding Examples

Simple URL with Spaces

hello world → hello%20world

Spaces are encoded as %20

Email in URL

user@example.com → user%40example.com

The @ symbol is encoded as %40

Query Parameters

search?q=cats & dogs → search?q=cats%20%26%20dogs

Spaces and & symbols must be encoded in query strings

URL Encoding Tips

  • Always encode URL parameters before sending API requests
  • Use decoding to make URLs readable and understand query parameters
  • Double-encoding can cause issues - avoid encoding already encoded URLs
  • Some characters like '/', ':', '?' have special meanings in URLs
  • Form data in POST requests should be URL-encoded
  • Email addresses in mailto: links should be encoded
  • Test your encoded URLs to ensure they work correctly

Frequently Asked Questions

What is URL encoding (percent encoding)?

URL encoding converts unsafe characters in URLs to %XX hex codes so links transmit correctly. Spaces become %20, @ becomes %40, and non-ASCII characters get UTF-8 percent sequences. This free tool encodes and decodes instantly in your browser.

When should I encode a URL or query string?

Encode whenever you pass user input in query parameters (?q=...), form GET requests, redirect URLs, or API calls with special characters. Always encode values (not the whole URL structure) before appending to query strings.

What's the difference between URL encoding and Base64?

URL encoding makes text safe inside URLs and query strings. Base64 encodes binary data as ASCII text for attachments or data URIs. Use this tool for percent-encoding; use our Base64 tool for file or blob encoding.

Can I decode a double-encoded URL?

Yes. Run decode once per encoding layer. If a parameter was encoded twice, decode twice. Watch for %2520 (double-encoded space) in broken links.

Is my data private?

Yes. Encoding and decoding run 100% client-side. Nothing is sent to a server.