Uniform Resource Locator (URL) Encoder

Introduction:

A URL is not just a line of text. It is a structured address where some characters identify the destination and other characters separate parts of the address. The same slash, question mark, ampersand, equals sign, or hash can be a delimiter in one position and ordinary data in another. URL encoding is the escape system that keeps those two roles from colliding.

Percent-encoding writes unsafe or ambiguous bytes as a percent sign followed by two hexadecimal digits. A space can become %20, a literal ampersand can become %26, and non-ASCII text is converted to UTF-8 bytes before each byte is escaped. That byte rule is why a single visible character such as é can turn into several percent escapes.

URL component

One address part, such as a query value, fragment value, or path segment, where delimiters may need to travel as data.

Reserved character

A character such as /, ?, #, &, or = that can change how a URL is parsed.

Unreserved character

A letter, digit, hyphen, period, underscore, or tilde that can normally stay readable in a URI.

Form-style value

A query value convention where spaces may be written as + instead of %20.

Context is the common source of mistakes. Encoding a whole URL should keep the scheme, host, path separators, query marker, and fragment marker visible. Encoding a single query value should usually escape the same delimiter characters so the value does not split into new parameters. Encoding a path can be different again because a slash may be either a separator between path segments or a literal slash inside one segment.

Unicode can add a second kind of surprise. Two strings can look the same while using different underlying code points, and normalization can change the bytes that later become percent escapes. Normalization is useful when equivalent text should compare consistently, but it is risky for signed links, exact identifiers, fixture data, and other byte-sensitive handoffs.

URL encoding is a representation step, not a security review. It does not remove tracking parameters, prove that a domain is safe, prevent redirects, or guarantee that every server will parse repeated keys and plus signs the same way.

How to Use This Tool:

Start by deciding where the text will be inserted. A value meant for one query parameter needs a different pass than a complete URL that already has its own structure.

1. Paste the source text into Text or URL. Turn on Trim outer whitespace only when leading and trailing spaces are accidental.
2. Choose Encoding target before reading the result. Use URL component for one query value, token, fragment value, or similar field.
3. Switch to Full URL when the pasted text is already a complete address, to Form/query value when the receiver expects plus signs for spaces, or to Path with slashes when slash characters should remain path separators.
   For a search value such as coffee beans & tea, encode the value as a component before placing it after q=. Whole-URL mode can leave & with parameter-separator meaning.
4. Leave Unicode normalization off for signed URLs, test fixtures, and exact identifiers. Choose NFC or NFKC only when you intentionally want equivalent Unicode text normalized before encoding.
5. Use Advanced for exact handoff rules. Strict RFC 3986 escapes also escapes !, ', (, ), and *; Preserve existing %XX escapes keeps valid existing escape triplets from being encoded again.
   Preserving escapes is helpful for already-encoded text such as %2F. Leave it off when the percent sign itself is literal data that must be escaped as %25.
6. Review Encoded URL Text for the value to copy and Character Map for the per-character reason each visible character was kept or escaped.
7. Use Query Preview when the output parses as a URL with query parameters, and use QR Handoff only for outputs short enough to scan reliably.

Interpreting Results:

The summary gives the selected target, input length, output length, percent-escape count, and space policy. Those numbers are useful for review, but they do not prove that the chosen target was correct. A high escape count can simply mean the input contains spaces, reserved characters, emoji, accented text, or strict-mode characters.

Encoded URL Text is the final text output. Character Map explains each source character, its class, its UTF-8 bytes, and the escaped value. Use that map when a slash, literal percent sign, plus sign, line break, tab, emoji, or accented character changes in a way that looks unexpected.

Query Preview parses URL-shaped output and shows the query keys and values that a typical URL parser sees. It is especially useful when a value contains &, =, a literal plus sign, or repeated parameter names. Treat the preview as a parsing check, not as a promise that every server-side framework will interpret the query identically.

Open URL is available only for outputs that parse as HTTP or HTTPS addresses. It is a convenience check for syntax, not a reputation or phishing check. The QR surface follows the same rule: it can hand off encoded text, but the destination still needs normal link review.

Technical Details:

URI syntax separates data characters from delimiter characters. Unreserved characters can normally stay visible because they do not define generic URL structure. Reserved characters are different: they can be valid text in a URL, but their meaning changes by component. Encoding or decoding a reserved character can change the parsed address.

Percent-encoding works on bytes. Text is prepared, optionally normalized, converted to UTF-8, and then bytes that cannot remain visible in the selected context are emitted as % plus two hexadecimal digits. Uppercase and lowercase hex digits represent the same byte, but uppercase escapes are the conventional normalized form.

Target Behavior

Output Length

Each unescaped visible character contributes one output character. Each escaped byte contributes three characters. Form-style spaces are the exception because a space written as + occupies one character instead of three.

Here L is output length, K is the count of kept visible characters, E is the count of percent-escaped bytes, and F is the count of form-style spaces written as plus signs. A non-ASCII character may add more than one escaped byte because UTF-8 can use multiple bytes for one displayed character.

Review Rules

Worked Examples:

One query value with delimiters

Paste coffee beans & tea/latte?size=large and choose URL component. The encoded value becomes coffee%20beans%20%26%20tea%2Flatte%3Fsize%3Dlarge. The ampersand, slash, question mark, and equals sign are escaped because they are data inside one value.

Form value with a literal plus sign

Paste coffee beans + tea and choose Form/query value. Spaces become plus signs, while the literal plus sign becomes %2B, producing coffee+beans+%2B+tea. That distinction matters when the receiver treats plus as a space.

Path text that keeps separators

Paste docs/team notes/2026 and choose Path with slashes. The output is docs/team%20notes/2026. The spaces are escaped, but the slash separators continue to divide the path into segments.

Avoiding double encoding

Paste docs%2Fteam notes in component mode. With preservation off, the existing percent sign is escaped and the output becomes docs%252Fteam%20notes. With Preserve existing %XX escapes on, the existing slash escape stays as %2F and the output becomes docs%2Fteam%20notes.

FAQ:

Glossary:

Percent-encoding

The URI escape format that writes a byte as % followed by two hexadecimal digits.

Reserved character

A character that may act as URL syntax, such as /, ?, #, &, or =.

Unreserved character

A character that can normally stay visible in a URI: letters, digits, hyphen, period, underscore, and tilde.

UTF-8

The byte encoding commonly used before non-ASCII text is emitted as percent escapes.

Unicode normalization

A text process that can convert equivalent or compatibility characters into a consistent form before encoding.

Query parameter

A key-value item in the query string after a question mark, often separated from other parameters by ampersands.

References:

• RFC 3986: Uniform Resource Identifier (URI): Generic Syntax, IETF, January 2005.
• URL Standard, WHATWG.
• Unicode Standard Annex #15: Unicode Normalization Forms, Unicode Consortium.