URL Encoder / Decoder

Developer

Percent-encode special characters for safe URL usage, or decode encoded URLs back to readable format.

URLLn 1UTF-8

URLLn 1

Works great for

🔗

Encoding query string parameters

Percent-encode spaces, ampersands, and special characters in query parameters before appending them to a URL. Essential when building API request URLs or constructing search query strings dynamically.

📲

Building deep links with special characters

Encode user names, product titles, and UTM campaign values that contain slashes, plus signs, or Unicode characters. Ensures deep links open correctly across mobile apps and web browsers.

↩️

Preparing and debugging redirect URLs

Encode full URLs that appear as the value of a redirect_uri or return_url parameter in OAuth flows and login redirects. Decode percent-encoded redirect targets to verify they point to the right destination.

📋

Encoding HTML form POST data

Validate that form field values are correctly percent-encoded before submitting multipart or application/x-www-form-urlencoded requests. Useful when manually crafting curl commands or Postman bodies.

🔬

Debugging URL parsing issues

Decode a mangled or double-encoded URL to see its original components and identify where encoding went wrong. Helps diagnose 400 Bad Request errors caused by incorrectly escaped characters.

🔖

Creating bookmarklets and data URIs

Encode JavaScript bookmarklet code or Base64 data URIs that need to be embedded in href attributes. Handles all reserved characters that would otherwise break the enclosing HTML tag.

url encoderurl decoderpercent encodeurl encodeurl decodeuri encodequery string encodepercent encodingurl escapeencode url

Frequently asked questions

How do I percent-encode a URL with special characters?

Paste the URL or text into the input box and the percent-encoded version, with spaces, ampersands, and other reserved characters escaped, appears immediately. Toggle to decode mode to reverse an already-encoded URL.

What is the difference between URL encoding and URI encoding?

They refer to the same percent-encoding scheme defined for URLs and URIs: reserved characters like spaces, question marks, and ampersands are replaced with a percent sign followed by their hex code so a string is safe inside a query string or path.

Is URL encoding safe to use for passwords or tokens in query strings?

Percent-encoding makes a value safe to transmit inside a URL, but it is not encryption or security, anyone can decode it back instantly. Avoid putting sensitive credentials in a URL at all, encoded or not.

Why does my decoded URL still show %20 or other codes?

That usually means the string was double-encoded. Run it through decode mode a second time to fully resolve nested percent-encoding, or check that the original encoder did not escape characters twice.