URL-encode and decode

A free online URL encoder and decoder that runs in your browser. Two scopes: Component (encodeURIComponent, escapes every reserved character including / ? & =) and Full URL (encodeURI, keeps URL structure intact). Optional + for space (the application/x-www-form-urlencoded variant used by HTML forms). Auto-detect flips Encode→Decode when the input contains percent sequences. UTF-8 multi-byte sequences round-trip correctly.

How to use

Pick a mode

Encode (text → percent) or Decode (percent → text). Auto-detect handles common cases.

Pick a scope

Component for query params, Full URL for whole URLs.

Paste your input

Result appears live in the right pane.

Copy or download

Copy to clipboard or save as a text file.

Component, full-URL, and form-urlencoded variants in one place

Component (encodeURIComponent — escapes / ? & = etc.) Full URL (encodeURI — keeps : / ? # @) Use + for space (form-urlencoded) Auto-detect direction

—

In: 0 Out: 0

Features

Two scopes Form-urlencoded variant Auto-detect direction UTF-8 multi-byte safe Live byte stats Honest errors

Common uses

Build a URL query parameter with safe escaping.
Inspect what a server-side encoded URL actually contains.
Convert a form-urlencoded body back to readable key=value pairs.
Escape a string for use inside a URL fragment.

Why use this one

Most browser tools only offer encodeURIComponent. This one explicitly separates Component and Full URL scopes, supports the + for space form-urlencoded variant, and auto-detects direction so you don't have to think.

Frequently asked questions

Free?

Yes — no account, no limits.

What's the difference between Component and Full URL?

Component (encodeURIComponent) escapes every reserved URL character — use for individual query parameter values. Full URL (encodeURI) keeps the URL structure intact (preserves : / ? # @) — use to escape only the "unsafe" characters in a whole URL.

When should I check "Use + for space"?

When sending data in an application/x-www-form-urlencoded form body, or matching a server that uses that format. Standard URLs use %20 for space.

Does it support binary?

Text only. For binary, encode to Base64 first via the Base64 tool, then URL-encode the Base64 string.

Why does encoded output look the same as the input?

If the input has no characters that need escaping (e.g. pure ASCII alphanumeric), output equals input. The stats overhead will be 0%.

Mobile?

Yes. Paste, copy, share.

💡 Want us to improve this tool just for you?

We can — and it's free! Just send us a quick message with your idea. If you'd like to discuss it in detail, leave your email and we'll get back to you. You can stay anonymous.

How do you rate this tool?

Thank you for your rating!

Change my rating

Want to leave a comment?

Want to share more? Leave a comment!

Thank you! Your comment will appear after moderation.

Who is this tool for?

💻 Developers & IT Pros

Published 22 May 2026