How to use the URL Encoder and Decoder.
Encode the appropriate URL component, not an entire URL indiscriminately. Preserve the distinction between path separators and characters inside a value.
Make the workflow fit your task.
Choose the URL component being encoded and preserve structural separators outside that component. Specify UTF-8 and the destination's query conventions. Decode only when needed, and compare the resulting value without treating percent encoding as validation of a destination.
- What you provide
- Text or encoded URL component.
- What you get
- Percent-encoded or decoded component with UTF-8 handling.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Encode the query value red mug.
Completed example
red%20mug
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should I encode a whole URL with a component encoder?
Usually encode individual values instead. Encoding every slash and colon can turn the URL structure into one opaque value.
Why does a space appear as plus in one query and %20 in another?
Form-style query encoding and URI component encoding use different conventions. Match the receiving parser rather than replacing characters blindly.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑