What is the difference between encoding a component and a full URI?

Component encoding escapes characters like &, =, ? and / because they're part of a single value. Full-URI encoding leaves those structural characters intact so a complete URL stays valid.

Why do spaces become %20 or +?

In URL paths a space becomes %20. In query strings, the application/x-www-form-urlencoded format uses +. This tool uses %20 for reliable, spec-compliant results.

Developer ToolsRuns in your browser

URL Encoder / Decoder

Percent-encode text for safe use in URLs, or decode an encoded string back to plain text.

Input

Output

What this does

Encode text so it can be placed safely inside a URL or query string, or decode a percent-encoded string back to readable characters. Choose between component encoding (for a single value) and full-URI encoding.

How to use it

1Enter the text or URL you want to convert.
2Pick Encode or Decode, and component or full-URI mode.
3Copy the converted result.

Examples

hello world → hello%20world
a=1&b=2 encoded for use inside a query value

Frequently asked questions

What is the difference between encoding a component and a full URI?: Component encoding escapes characters like &, =, ? and / because they're part of a single value. Full-URI encoding leaves those structural characters intact so a complete URL stays valid.
Why do spaces become %20 or +?: In URL paths a space becomes %20. In query strings, the application/x-www-form-urlencoded format uses +. This tool uses %20 for reliable, spec-compliant results.

More developer tools

View all

JSON FormatterFormat, validate and minify JSON.UUID GeneratorGenerate v4 and v7 UUIDs instantly.Base64 Encoder / DecoderEncode and decode Base64 text.Unix Timestamp ConverterConvert Unix time to dates and back.