Encode/decode url formatted strings

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from Encode/decode url formatted strings

Encode/Decode URL Formatted Strings translates text to percent-encoded form and decodes supported percent escapes back into characters. Encoding is useful when a value contains spaces or reserved punctuation that must travel inside a URL component. A complete URL and a single query value need different treatment, so be clear about which part you are preparing. Text and string utilities help make small transformations explicit and repeatable. The important details are often invisible: newlines, spaces, quotation marks, character encoding, and punctuation can all affect the result. Keep the input nearby and try a short example before working with a longer document. When the output will be used in code, a URL, or another structured format, validate it in that destination as well. Readable output alone does not guarantee that every character has the meaning you intended.

Guide updated October 13, 2026

How to use this tool

1. Paste a short input containing the characters you need to handle. Include a space, punctuation, or non-ASCII character when these occur in the real data.
2. Choose encoding or decoding, paste the value, and inspect spaces, punctuation, and non-ASCII characters in the output.
3. Review the example below and compare its expected behavior with a small sample of your own input before continuing.
4. Compare the output character by character where needed, then copy it into the intended destination and verify that it is interpreted correctly.

SEE IT IN PRACTICE

A worked example

Hello world

Hello%20world

The space is represented by its percent-encoded byte value for a URL component; ordinary letters remain recognizable.

Encode components rather than an undifferentiated URL

A URL contains structural separators such as a scheme delimiter, slashes, a question mark, and ampersands. If you encode the entire address as one query value, those separators become data rather than structure. That is correct when nesting a URL inside a parameter, but wrong when you simply want to open the original address. Identify whether you are encoding a path segment, query value, or complete nested URL before choosing how to use the result.

Plus signs and repeated encoding

A plus sign can represent a space in form-style encoding, while a literal plus has its own meaning in a raw component. Percent decoding and form decoding are related but not always identical operations. Test those characters explicitly when moving values between systems. A percent sign in an already encoded sequence can itself become encoded, producing familiar double-encoding symptoms such as %2520. Preserve the original value and apply only the layer required by the next parser in the workflow.

When this tool is useful

• Prepare a query-parameter value
• Read percent-encoded text from a URL
• Diagnose a double-encoding problem

Tips for a better result

• Check ampersands, slashes, plus signs, and Unicode, then test the resulting component inside the intended URL structure.
• Avoid repeated conversion unless you deliberately need another encoding layer. Double escaping or double encoding often turns a correct value into a visibly different string.
• Keep the source and the settings used for this result together. That makes a later comparison or correction easier, especially when another person needs to reproduce the same outcome.

Frequently asked questions