- Result
- Hello%2C%20Finflo!
How it works
Recognize a double-encoded space
A space encodes as %20; encoding that output again produces %2520 because the percent sign is encoded too. Decoding once returns %20, not a space. Check which encoding layer the receiving application expects before transforming again.
Encoding a URL component correctly
URL-component encoding represents characters that need special treatment inside a component such as a query value. Encoding a whole URL as one component can also encode its separators, which changes how it is used. Select encode or decode according to the input's current form. Repeated encoding can introduce additional escapes rather than fixing a malformed address.
URL component text: formula and assumptions
Percent-encode a UTF-8 URI component, or reverse that encoding.
Text is processed locally. Encoding is not encryption; do not treat encoded data as secret.
Worked example
Using the URL component text example:
- Operation
- Encode
- Text
- Hello, Finflo!
Percent-encode a UTF-8 URI component, or reverse that encoding.
Example result
Result: Hello%2C%20Finflo!
These are illustrative inputs. Change the values to explore a different scenario.
Formula references
References explain the underlying methods; they do not imply endorsement or individual professional review of Finflo.
Common questions
Should I encode an entire URL as one component?
Usually the component is a single value, such as a query parameter. Encoding a whole URL can also encode its structural separators.
Does percent-encoding make text secret or make a destination safe?
No. It only represents characters for a URL component. It does not encrypt the text or assess a destination's trustworthiness.
Prepared by Finflo. See our methodology and editorial policy.