IT operations

URL Encode / Decode

Encode or decode URL components so spaces and reserved characters travel safely, while keeping percent-encoding separate from security controls.

Last reviewed May 18, 2026 by ToolSpilo Editorial Team.

Review method: Reviewed against URI percent-encoding rules, implemented behavior, and worked examples.

Calculator tool

How this calculator works

Use the explanation to understand the formula, assumptions, and practical limits behind the calculator result.

What URL Encoding Does

URLs reserve certain characters for structure. Percent-encoding represents characters that need escaping as % followed by hexadecimal bytes, so text can be placed safely inside a URL component.

Components Matter

The calculator follows component-style encoding behavior. That is appropriate for values such as query parameters, but it is not the same as rebuilding an entire URL by hand.

Common Examples

Plain textEncoded form
space%20
&%26
?%3F
#%23

What Encoding Does Not Do

Percent-encoding is not encryption and not full security sanitization. Applications still need proper validation, escaping, and safe handling for the context where the decoded value will be used.

Frequently asked questions

Why do spaces become %20?

Because a literal space is not safe inside a URL component, so it is written as its percent-encoded value instead.

Is URL encoding the same as HTML escaping?

No. They solve different problems. URL encoding is for URL components, while HTML escaping is for placing text safely inside HTML.

Should I encode a whole URL at once?

Usually no. Encode only the component that needs it, such as a query value, instead of encoding separators that give the URL its structure.

Does URL encoding make unsafe input safe?

No. It changes representation only. Security still depends on validation and context-appropriate handling after decoding.