ToolQiva
PDF ToolsImage ToolsDocument ToolsOCR ToolsSocial Media ToolsYouTube ToolsRSS ToolsSEO ToolsDeveloper ToolsText ToolsCalculator ToolsQR & BarcodeColor ToolsDate & TimeWeb UtilitiesIndia ToolsGovernment JobsStudent ToolsFinance ToolsCareer ToolsBusiness ToolsUSA ToolsUK ToolsCanada ToolsAustralia ToolsCurrency Tools

Developer Tools

URL Encoder / Decoder

Safely percent-encode text for use in URLs and query strings, decode an encoded URL back to readable text, or parse a full URL into its protocol, host, path and query parameters.

Your data is processed locally in your browser and is never uploaded to our server.

How to use url encoder / decoder

  1. Paste the text or URL

    Enter the value you want to encode, the encoded string you want to read, or a full URL to break apart.

  2. Choose the scope

    Use Component for a single value, Full URL to keep separators intact, or Form for HTML query-string encoding (spaces become +).

  3. Encode, decode or parse

    Click the action you need — Parse URL breaks a full link into its protocol, host, path and query parameters.

Features

Three encoding modes

Component and full-URL modes cover encodeURIComponent/encodeURI; Form mode matches how HTML forms and query strings encode spaces as +.

URL parser

Breaks a full URL into protocol, host, port, path, hash and a readable table of decoded query parameters.

Decode friendly

Turns %20 and other escapes back into readable characters, including non-Latin scripts.

No server round-trip

Everything happens locally, so long or sensitive URLs stay on your device.

Supported formats and limitations

Text and structured input supported by this tool.

Use cases include personal workflows, content preparation, and quick checks. Review output before relying on it for legal, financial, accessibility, or production decisions.

Frequently asked questions

What's the difference between the three modes?

Component mode (encodeURIComponent) escapes characters like / ? & = so it's right for a single value. Full-URL mode (encodeURI) leaves those separators alone. Form mode matches application/x-www-form-urlencoded — the encoding browsers use for HTML form submissions and query strings — which also turns spaces into + instead of %20.

Why are spaces turned into %20 or +?

Spaces aren't allowed in URLs, so they're percent-encoded to %20. Inside a query string built the HTML-form way, + is used instead — that's what Form mode replicates.

Can it decode a whole messy link?

Yes — paste the encoded URL and click Decode to see the human-readable version.

What does Parse URL show?

It splits a full URL into its protocol, host, port and path, then lists every query parameter as a decoded key/value pair — handy for debugging a long tracking or API link.