We use percent encoding: spaces become %20. Some forms use + for space; replace + with %20 if needed.

Why did my slash disappear?

Slashes are encoded as %2F so they don’t break path structure. Encode only the query or segment that needs it.

Encoded as UTF-8 percent-encoded bytes (e.g. %E2%9C%85 for ✓). Decode to get the original character.

Encode the whole URL or just part?

Encode only the dynamic part (e.g. one query value). Don’t encode the whole URL or you’ll double-encode.

Input may not be valid percent-encoding or may be a different encoding; check the source.

No. Encode and decode run in your browser.

Safely encode or decode text for URLs.

Informational only; verify critical results independently.

Paste the text you want in a URL (e.g. a query value or path segment).
Click Encode; special characters become %XX (e.g. space → %20).
Paste the encoded string into your URL or query; decode to get the original back.
Use Decode when you have a percent-encoded string and need plain text.
Copy the result; we don’t store or send your input.
Match the encoding your API or app expects (we use standard percent encoding).

Spaces vs +?: We use percent encoding: spaces become %20. Some forms use + for space; replace + with %20 if needed.
Why did my slash disappear?: Slashes are encoded as %2F so they don’t break path structure. Encode only the query or segment that needs it.
Unicode and emoji?: Encoded as UTF-8 percent-encoded bytes (e.g. %E2%9C%85 for ✓). Decode to get the original character.
Encode the whole URL or just part?: Encode only the dynamic part (e.g. one query value). Don’t encode the whole URL or you’ll double-encode.
What if decode shows weird characters?: Input may not be valid percent-encoding or may be a different encoding; check the source.
Is data sent to a server?: No. Encode and decode run in your browser.

Last updated: 2025-09-15