Percent-encode text for links, or decode a messy URL back to readable text. Full UTF-8, runs in your browser.
Web addresses can only contain a limited set of characters, so spaces, symbols and non-English letters must be percent-encoded (a space becomes %20). Use Component mode for a single query value and Full URL mode to encode a whole address while keeping its structure. Everything runs locally.
URLs can only contain a limited set of characters, so anything outside that set, spaces, accented letters, and symbols like &, ?, / and # that have special meaning in a web address, must be percent-encoded: replaced by a % followed by its character code. A space becomes %20, for example. This is what lets a search query or a filename with spaces travel safely inside a link.
Reserved versus unreserved. Some characters are "reserved" because they structure the URL: ? starts the query string, & separates parameters, / separates path segments. If those appear inside a value rather than as structure, they must be encoded or the URL is misread. Letters, digits and a few symbols are "unreserved" and never need encoding.
Where it bites. The classic bug is a query parameter containing an ampersand or a plus sign that is not encoded, which silently truncates or corrupts the value on the server. Any time you build a URL from user input or data, encode each value first. The tool above encodes and decodes both whole URLs and individual components.
URL encoding, or percent-encoding, replaces characters that are unsafe in a web address with a percent sign followed by hex codes. For example a space becomes %20. It lets you put spaces, symbols and non-English text into links and query strings safely.
Encode component (encodeURIComponent) escapes everything including slashes and ampersands, ideal for a single query value. Encode full URL (encodeURI) leaves valid URL structure like :// and ? intact, ideal for encoding a whole address.
No. Encoding and decoding run locally in your browser. Nothing is uploaded.