URL Encoder & Decoder
Percent-encode URLs for safe transport or decode encoded strings — instantly, in your browser.
Why Use PixConvert URL Encoder
The fastest URL encoder/decoder — native browser APIs, zero latency.
Percent-Encoding Standard
Uses RFC 3986 compliant percent-encoding. Converts spaces to %20, & to %26, and all reserved characters correctly.
Full URI Mode
Toggle Full URI mode to preserve :// slashes and domain structure while encoding only the unsafe characters.
100% Private
Native encodeURIComponent/decodeURIComponent runs in your browser. Nothing leaves your device.
Swap in One Click
Paste encoded output back as input and decode it with a single Swap click.
Query String Friendly
Encode entire query strings or individual parameter values for safe inclusion in links.
Instant Results
No button required — output updates as you type. Click Encode/Decode to apply selected mode.
When to URL-Encode
URL encoding is required any time user-supplied text enters a URL.
Query Parameters
Encode search queries, form values, and user-submitted text before appending to URLs.
- Encode search queries safely
- Preserve special characters in filters
- Avoid breaking URL structure
Redirect URLs
Double-encode URLs used as redirect_uri parameters in OAuth flows.
- OAuth redirect_uri encoding
- OpenID Connect callback URLs
- Safe URL embedding in other URLs
API Development
Inspect or decode URL-encoded webhook payloads and form submissions.
- Decode webhook payloads
- Inspect form POST bodies
- Debug API redirect parameters
How to Encode or Decode a URL
Select Encode or Decode mode. Paste your text or URL-encoded string into the input.
Click Encode or Decode. Copy the output with one click.
Switch between component (encodeURIComponent) and full URI modes depending on whether you encode a parameter or a whole URL.
Explore More Tools
Discover other free tools that work great alongside this one
Base64 Encoder
Encode and decode Base64 strings
JSON Formatter
Format, validate, and minify JSON instantly
JWT Decoder
Decode and inspect JSON Web Tokens
Hash Generator
Generate MD5, SHA-1, SHA-256 hashes
Regex Tester
Test and debug regular expressions live
UUID Generator
Generate v4 UUIDs and ULIDs
Frequently Asked Questions
URL encoding and decoding explained.
What's the difference between encodeURI and encodeURIComponent?
encodeURI encodes a full URL, preserving :, /, ?, #, &, = characters. encodeURIComponent encodes a URL component (a single parameter value), encoding everything including those characters. Use encodeURIComponent for parameter values and encodeURI for full URLs.
Why does a space sometimes appear as + and sometimes as %20?
HTML forms encode spaces as + (application/x-www-form-urlencoded format). RFC 3986 URL encoding uses %20. Both are valid in different contexts. Our tool uses %20 (standard percent-encoding).
Is URL encoding the same as Base64?
No. URL encoding replaces unsafe characters with %XX hex sequences and is designed for URLs. Base64 encodes binary data as printable ASCII and produces a longer string. They solve different problems.
When should I use Full URI mode?
Full URI mode uses encodeURI instead of encodeURIComponent. Use it when you have a complete URL and only want to encode characters that are invalid in URLs (spaces, non-ASCII), while preserving the URL structure (://, /, ?, &, =).
What characters need to be percent-encoded?
Characters outside the unreserved set (A-Z, a-z, 0-9, -, _, ., ~) must be percent-encoded in URL components. Reserved characters like /, ?, #, &, = are safe in URL structure but must be encoded when used as data values.