A walkthrough, end to end.
- 1
Paste your text or URL fragment.
- 2
Pick encode (text → %XX form) or decode (%XX → text).
- 3
Choose component encoding (encodeURIComponent) for safe query parameters.
Percent encoding
RFC 3986 percent-encoding maps unsafe characters to %XX hex. Spaces become %20 (or + in form data).
What you can do with this.
Query parameters
Encode user input before adding to a URL.
API requests
Properly escape special characters in REST URLs.
Reading server logs
Decode raw URLs to read them.
Mailto links
Encode subject and body parameters.
Sharing URLs in chat
Some apps mangle special characters; encode first.
Form data debugging
Inspect application/x-www-form-urlencoded payloads.
Building deep links
Encode parameters for app deep-link URLs.
URL encoding 2026 — what's current
RFC 3986 still standard; calculator wins for instant testing.
Frequently asked.
encodeURIComponent escapes more chars (?, =, &) — use it for query parameters. encodeURI preserves URI structure.
No. Encoding/decoding runs locally.
Toggle 'form data' mode to treat + as space.
Invalid percent sequences show an error message.