Component values are the main use case
Search terms, filenames and query parameter values are common examples where reserved characters need to be represented safely inside a larger URL.
FREE WEB TOOL
Percent-encode or decode URL text.
Your input is processed in your browser and is not sent to our server.
Percent-encode text that needs to travel safely as part of a URL, or decode percent sequences back to readable characters. It is mainly for URL components such as search text or parameter values, not for encoding an entire URL.
a b becomes a%20b. A value such as a&b can also be encoded so the ampersand is not mistaken for a query separator.Do not paste a complete URL such as https://example.com/a?x=1 and expect to keep it usable as a normal URL: characters such as :, /, ? and = will also be encoded. Encode only the component that needs escaping.
Search terms, filenames and query parameter values are common examples where reserved characters need to be represented safely inside a larger URL.
This is URL-component encoding rather than form-style plus-for-space encoding. That distinction matters when comparing the output with form submissions.
The decoder does not reinterpret + as a space. If the source uses application/x-www-form-urlencoded rules, a query parser may be a better fit.
A percent sign must be followed by a valid hexadecimal byte sequence. Broken or truncated encoded text will produce an error instead of a guessed result.
Japanese, emoji and other Unicode characters can be converted into percent-encoded URL text when needed.
Related references: HTTP status codes · MIME types · Regex cheat sheet