Encoded URL
{{ urlObj.hostname }}
{{ seg }}
KeyValue
{{ p.key }} {{ p.value }}
Scheme{{ urlObj.protocol.replace(':','') }}
User info{{ urlObj.username ? urlObj.username + ' : ' + urlObj.password : '—' }}
Host{{ urlObj.hostname }}
Port{{ urlObj.port }}
Path{{ urlObj.pathname || '/' }}
Fragment{{ urlObj.hash.slice(1) }}
Total length{{ encodedOutput.length }} chars
Single-encoded{{ onceEncoded }}
Double-encoded{{ twiceEncoded }}
Base64{{ base64 }}
URL-safe Base64{{ urlSafeB64 }}
Categories: Encoder / Decoder
Export to PDF Fullscreen

Introduction

Uniform Resource Locators often carry reserved characters, whitespace and multilingual scripts that confuse gateways, shells or APIs. URL encoding converts every unsafe symbol to a percent-escaped hexadecimal byte, preserving semantic meaning while guaranteeing round-trip safety across browsers, email clients, monitoring tools and automated test suites that would otherwise misinterpret the raw string.

This single-page utility performs canonicalisation before encoding, ensuring predictable output. It lower-cases hosts, converts Internationalised Domain Names to ASCII Punycode, trims redundant slashes, reorders query parameters alphabetically and offers up to eight successive encoding passes. All logic runs inside the browser with a lightweight reactive engine, eliminating network requests, server logs or privacy worries for highly sensitive links.

Use this encoder when preparing links for automated pipelines, clipboard sharing, storing them in configuration files or embedding within other encoded payloads, and rest assured that each transformed address will survive copy-paste cycles, logging systems and analytic trackers without corruption; always double-check unfamiliar URLs for malicious redirections before distributing them widely.

Technical Details:

The reactive interface binds checkbox options to a live encoding pipeline written in modern JavaScript. A standards-based URL parser deconstructs the address, applies canonical transforms, then iteratively encodes it up to eight times before displaying results. Processing happens entirely in your browser; nothing is transmitted or stored.

Real-time canonicalisation

The parser lower-cases hosts, trims trailing slashes and sorts query parameters each time you toggle an option.

IDN → Punycode support

International characters convert to ASCII-compatible encoding, ensuring compatibility with legacy systems.

Multi-level encoder

Apply up to eight successive encodeURIComponent passes until further encoding yields no change.

Space replacement mode

Optionally swap %20 with plus signs for form-style encoding.

Comprehensive analysis tabs

Switch between Info, Parameters, Components and Encodings to inspect every part of the processed URL.

Step-by-Step Guide:

Follow these steps to encode and inspect a link.

  1. Enter your link in the URL to encode field.
  2. Click the Advanced toggle to reveal extra options.
  3. Enable Multi-level encode or other switches as required optional.
  4. Copy the finished result with the Copy button or open it directly via Open.

FAQ:

Find quick answers below.

What is URL encoding?

URL encoding converts characters outside the unreserved set into %-escaped bytes so that every system interprets the link safely.

When should I double-encode?

Use double or multi-level encoding when embedding a URL inside another URL or query string that will be encoded again by downstream services.

Is my data stored?

No. All processing runs locally in your browser; the tool never uploads or logs your input.

Why convert IDN to Punycode?

Legacy systems and some libraries only accept ASCII domain names; Punycode keeps multilingual domains functional across platforms.

What does “Replace %20 with +” do?

It substitutes encoded spaces with plus signs, which many web forms interpret as space characters within query parameters.

Troubleshooting:

Resolve common issues quickly.

  • Invalid URL error — Ensure the input starts with http:// or https://.
  • Unexpected characters — Disable Replace %20 with + if target service expects percent escapes.
  • Length grows too fast — Limit encoding depth or review nested URLs.
  • Punycode appears garbled — Untick Convert IDN → Punycode to keep Unicode domains.
  • Copy button seems inactive — Verify clipboard permissions in your browser settings.

Advanced Tips:

Enhance your workflow with these pointers.

  • Bookmark the page with pre-filled query parameters to save frequent options.
  • Drag the encoded output into terminal sessions to avoid shell escaping mistakes.
  • Test redirects by opening the canonical link in a private window.
  • Pair the analysis tabs with browser developer tools to inspect live network requests.
  • Enable parameter sorting before comparing two links for easier diff reading.

Glossary:

Key terms used in this utility.

Canonicalisation
Process of converting different URL forms into a single standard representation.
IDN
Internationalised Domain Name containing non-ASCII characters.
Punycode
ASCII encoding that represents IDNs for legacy compatibility.
Percent encoding
Replacing bytes with % followed by two hexadecimal digits.
Query parameter
Key-value pair in a URL after the question mark.
Embed this tool into your website using the following code: