How the URL Encode / Decode Tool works.
encodeURIComponent maps UTF-8 bytes for reserved characters to percent escapesThe input is one URL component, not an entire URL; decoding reverses valid percent-encoded sequences.
Worked example for the URL Encode / Decode Tool.
Encoding “report name & total” as a URI component produces report%20name%20%26%20total and decoding restores the original characters.
How to read this result.
Percent encoding makes reserved or unsafe text representable inside one URL component; it is not encryption and does not validate a complete URL.
How this tool gets the answer
encodeURIComponent maps UTF-8 bytes for reserved characters to percent escapes. The input is one URL component, not an entire URL; decoding reverses valid percent-encoded sequences. Percent encoding makes reserved or unsafe text representable inside one URL component; it is not encryption and does not validate a complete URL.
A useful example
Encoding “report name & total” as a URI component produces report%20name%20%26%20total and decoding restores the original characters. A quick way to verify the calculation is: Compare the output character by character and confirm that decoding the encoded component round-trips to the exact original Unicode text.
What the result tells you
Percent encoding makes reserved or unsafe text representable inside one URL component; it is not encryption and does not validate a complete URL. The tool uses JavaScript URI-component rules and UTF-8 percent escapes. Spaces become %20 rather than the form-encoding plus sign.
Where the answer can go wrong
Malformed percent escapes or invalid encoded sequences produce an explicit decoding error instead of returning altered text. Encode individual query values or path segments, not an entire URL when separators such as colon, slash, question mark, and ampersand must retain structure.
Privacy and practical use
Encoding and decoding happen locally. Encoding is not encryption, and FigureNest does not send or store the entered value. Keep the source value and its unit with any result you save so you can reproduce the calculation later.
Inputs and edge cases to check.
Malformed percent escapes or invalid encoded sequences produce an explicit decoding error instead of returning altered text.
What this tool does not include.
Encode individual query values or path segments, not an entire URL when separators such as colon, slash, question mark, and ampersand must retain structure.
Reference guidance and methodology.
URL Encode / Decode Tool questions.
What does the URL Encode / Decode Tool do?
Percent-encode or decode one Unicode URL component locally in the browser.
How can I check the result?
Compare the output character by character and confirm that decoding the encoded component round-trips to the exact original Unicode text.
Which units and assumptions matter?
The tool uses JavaScript URI-component rules and UTF-8 percent escapes. Spaces become %20 rather than the form-encoding plus sign. Encode individual query values or path segments, not an entire URL when separators such as colon, slash, question mark, and ampersand must retain structure.
Are the entered values sent or stored?
Encoding and decoding happen locally. Encoding is not encryption, and FigureNest does not send or store the entered value.