URL Encoder Decoder Online Free
Encode or decode text and URLs with standard JavaScript (encodeURIComponent, encodeURI) and UTF-8 Base64. Below, the URL parser breaks the link into protocol, host, path, UTM and query parameters, and fragment in a clear table — handy for landing pages, redirects and support, without leaving the browser.
Everything runs 100% locally: your strings are not sent to our servers. Real-time output and one-click copy.
URL Encoding
100% in your browser — no data sent to server.
Examples: space → %20 · & → %26 · = → %3D · @ → %40
Companion tool
URL parser
URL parser: paste a full address (with ?, &, UTMs, hash after #) to show protocol, domain, path, fragment and a key / value table of every query parameter — useful for marketing links, tracking and technical debugging.
How it works
- Encode: pick the right mode (parameter value →
encodeURIComponent; full URL →encodeURI; other → Base64). - Decode: paste percent-encoding or Base64; detection is automatic.
- URL parser: paste the link in the second panel; read every segment and parameter (utm_source, utm_medium, gclid, etc.) without a spreadsheet or extension.
- Copy: the blue button under each result copies the “Result” field to the clipboard.
Frequently asked questions
- How to encode a URL online?
- Encode mode: paste the text and choose the type; the result is real-time.
- What is the difference between encodeURI and encodeURIComponent?
- encodeURI keeps the URL structure; encodeURIComponent encodes each value segment.
- How to decode an encoded URL?
- Decode mode: the browser tries decodeURIComponent, decodeURI or Base64 depending on the content.
- How to encode to Base64?
- Select Base64 in Encode mode.
- How to decode URL parameters?
- Use the URL parser: the table lists each key and value in the query string, including UTMs.
- What is the URL parser for?
- It visually splits protocol, host, path, fragment and parameters. Handy to verify a landing URL, compare two links or explain a redirect — all locally.
- When should I use encodeURIComponent instead of encodeURI?
- For a value (password, label, token) to put in a query string, use encodeURIComponent. encodeURI suits a structured URL you want to keep readable.
- Is my data sent to your servers?
- No: encoding, decoding and parsing use JavaScript only in your browser.
- How do I spot double encoding?
-
If you see sequences like
%2520instead of%20, the string was encoded twice. Start from plain text, encode once, or use Decode mode to inspect. - Does Decode mode handle Base64?
- Yes, when the input looks like Base64 (no
%and no URL scheme), the output is UTF-8 decoded text. - Why encode characters in a URL?
-
Spaces, non-ASCII characters and reserved symbols (
&,=,#) must be percent-encoded so servers and browsers interpret the request correctly.