ToolzyLab
Encode or decode any URL safely and instantly. Clean messy links, convert reserved characters, inspect URL parts, review query parameters, and copy or download the final result directly in your browser.
Paste a raw link, encoded URL, query string, or file content and instantly convert it the way you need. Great for developers, SEO work, redirect testing, APIs, tracking links, and debugging broken URLs.
Paste a URL, encoded string, query string, or upload a .txt file to process instantly.
📄 .txt · ⚡ instant convert · 🔍 parse URL parts · 📥 download result · 🔒 no uploadUse the left side for raw input and the right side for the encoded or decoded result.
1
1
Quickly inspect protocol, host, path, query string, hash, and decoded parameter values.
Use URL Component mode when encoding pieces like search terms, query values, tokens, or slugs. Use Full URL mode when you want to preserve the main link structure but safely encode the parts that need escaping.
See what happened to the current result, including structure, characters, and encoded signs.
It can encode unsafe characters, decode already-encoded strings, auto-detect likely encoded input, show output in a clean scrollable box, parse query parameters, and help you inspect URLs without turning the whole page into a giant scroll mess.
Percent encoding represents bytes that are not allowed or would have special meaning in a URI component. Choose encode or decode, whole-URL or component mode, space behavior, repeat count, and cleanup from the exact destination, then inspect percent signs, slashes, question marks, ampersands, equals signs, fragments, and UTF-8 characters.
Encoding an entire URL can hide structural delimiters such as colon, slash, question mark, ampersand, and equals. Encode dynamic values before assembling them into the URL with a URL API. A query parameter value and a path segment may require different treatment, especially for slash and plus.
General URI percent encoding commonly uses %20, while application/x-www-form-urlencoded uses plus for spaces and encodes literal plus separately. Non-ASCII text should first become UTF-8 bytes and then percent-encoded. The receiving framework's parser determines the correct convention.
Double encoding turns a percent sign into %25 and can create values such as %252F. Repeated decoding can reveal reserved delimiters and alter path or query interpretation. Decode after separating URI components, validate the result, and protect against traversal or redirect vulnerabilities in application code.
Parse and test the generated URL with the same API or server that will receive it.
Technical references: RFC 3986 URI syntax
Usually encode dynamic components such as a query value or path segment, then assemble them with a URL API. Encoding the whole URL can hide required delimiters.
%20 is the percent-encoded space byte. Plus represents space in form-style query encoding, where a literal plus must be encoded separately.
Each percent triplet represents one byte as a percent sign followed by two hexadecimal digits. Unicode text commonly produces several UTF-8 byte triplets.
It occurs when an already encoded percent sign is encoded again, so %2F becomes %252F. Decode or encode only at the defined application boundary.
Reserved characters act as URI delimiters. Decoding them before parsing components can turn data into structure and change routing or query meaning.
No. Applications must validate allowed schemes, hosts, paths, and decoded values. Encoding is representation, not authorization or sanitization.