{ }
DevToolsLabs

URL Encoder & Decoder (Percent-Encode URLs Online)

URLs can only be sent over the Internet using the ASCII character set. If your tracking link or API endpoint contains spaces, emojis, or reserved characters (like & or ?), they must be mathematically translated into a valid percent-encoded format. This tool instantly drives bi-directional URL encoding completely in your local browser.

100% Private & Secure

This tool runs completely inside your browser using client-side WebAssembly and JS. Zero data is ever sent to our servers.

Raw String / URL

Encoded Output

How to use this tool

  1. Select your operation via the top buttons: 'URL Encode' or 'URL Decode'.
  2. Paste your raw string or fully percent-encoded URI into the left box.
  3. The tool will instantly execute standard RFC 3986 encoding on your string.
  4. The converted output automatically appears on the right side. Click Copy to use it.

Example Usage

Input
hello world @ 2026
Output
hello%20world%20%40%202026
Input
https%3A%2F%2Fsite.com%2F%3Fq%3Dmy%20search
Output
https://site.com/?q=my search

When to use this tool

  • Preparing a complex JSON payload string to be passed securely as a URL query parameter without breaking the HTTP router.
  • Decoding a massive Google Analytics or Facebook Pixel tracking URI to read the hidden UTM marketing tags.
  • Sanitizing user input text (like a blog post title) to construct a safe, clickable URL slug parameter.

Frequently Asked Questions

Is this secure for API keys?

Yes. The encoding logic runs entirely via your browser's native JavaScript `encodeURIComponent()` engine. No data is sent over the network. Your sensitive tokens remain exclusively in your local device memory.

What is Percent (%) Encoding?

Percent-encoding is a mechanism defined in RFC 3986 for encoding information in a Uniform Resource Identifier (URI). When a character isn't allowed in a URL (like a space or an emoji), it's replaced by a '%' followed by its two-digit hexadecimal equivalent (e.g., a space becomes '%20').

Why does it convert the + sign to a space during decoding?

In legacy HTML form submissions (application/x-www-form-urlencoded), spaces are historically converted into the '+' symbol instead of '%20'. Our decoder intelligently detects the '+' symbol and parses it back into a standard space character to ensure maximum compatibility.

Does it encode ALL characters?

Standard URL encoding ignores unreserved characters: alphabetic characters, decimal digits, hyphens, periods, underscores, and tildes. Everything else, including reserved delimiter characters like ':' and '/', is strictly percent-encoded.

More Developer Tools