URL encoding guide
Encode URLs without breaking query parameters.
URL encoding, also called percent-encoding, replaces characters that have a special meaning in a URL with a safe representation. For example, a space commonly becomes %20, while an ampersand inside a value becomes %26 so it is not mistaken for the start of another query parameter.
How to use this URL encoder and decoder
- Paste a value, query string, or encoded text into the Input field.
- Choose URL encode query params for a query string such as
name=Jane Doe&role=API Developer. - Choose Full URL encode to encode the entire input as one URL component.
- Select Encode or Decode, then copy the output.
The conversion runs in your browser. The tool does not need a login and does not submit the text to WeDoIntegration.
Common URL encoding examples
| Character | Encoded value | Why it matters |
|---|---|---|
| Space | %20 or + | Spaces cannot appear literally in every URL context. |
& | %26 | An ampersand normally separates query parameters. |
= | %3D | An equals sign normally separates a parameter name and value. |
+ | %2B | A plus sign may be interpreted as a space in form-style query strings. |
? | %3F | A question mark normally begins the query string. |
# | %23 | A hash normally begins a page fragment. |
When should I encode a URL value?
Encode data when you place user input, JSON fragments, redirect targets, filter expressions, or other dynamic values inside a URL component. In application code, encode each value before joining the query string so the separators you intentionally add remain readable.
What does “treat + as spaces” mean?
HTML form query strings often use a plus sign for a space. Keep the option selected when decoding form-style query data. Clear it when a literal plus sign must remain a plus, such as in some identifiers or arithmetic expressions.
Should I encode a complete URL?
Usually, encode only the value being inserted—not the whole destination URL. Encoding an entire URL is useful when that URL itself becomes a parameter value, such as a redirect or callback target.
Is URL encoding encryption?
No. Anyone can decode percent-encoded text. Never use URL encoding to protect passwords, API keys, access tokens, or other secrets.