URL Encoder and Decoder Online

Convert special characters from any link to safe format (Percent-Encoding) or return them to their original readable state instantly and locally.

Raw Text (Readable)
Formatted URL (Encoded)
Zoom 100%
Utilities Studio

Want this utility on your website?

Customize colors and dark mode for WordPress, Notion or your own site.

Frequently Asked Questions

Which characters get encoded in a URL?

All characters not permitted in the ASCII standard for URLs are encoded: spaces, accented letters, symbols such as &, =, +, #, ?, / and others. For example, a space becomes %20 and ñ becomes %C3%B1.

What is the difference between encodeURI and encodeURIComponent?

encodeURI encodes a complete URL and leaves reserved characters such as / and ? intact. encodeURIComponent encodes all special characters including reserved ones, making it ideal for encoding individual query parameter values.

Why does my URL have %20 instead of spaces?

The HTTP protocol does not allow spaces in URLs. %20 is the Percent-Encoding representation of a space according to the ASCII standard. Some systems use the + sign as an alternative, but %20 is the most universal and safe.

Is it safe to use this tool with private URLs?

Yes, completely safe. All processing happens in your browser using native JavaScript (encodeURIComponent/decodeURIComponent). None of your URLs or parameters are sent to any external server.

# What is URL Encoding?

When browsing the internet or sending requests to servers, it is common to think of a URL (Uniform Resource Locator) as simply a "web address". However, internet protocol dictates that URLs can only be transmitted using a very restricted set of standard ASCII characters.What happens if the URL contains a space, accented letters, or special parameters such as plus (+) or equals (=) signs? To prevent systems from collapsing when trying to read illegal characters, these must be translated to their safe compatible form using Percent-Encoding.

# How Percent-Encoding Works

When you use this tool, the algorithm takes any "unsafe" character (such as a space or an accented letter like ñ) and replaces it with a percent sign % followed by two hexadecimal digits corresponding to its value in the UTF-8 standard.
  • Basic Example: A simple space will be replaced by its safe equivalent: %20.
  • Extended Support: The letter á becomes %C3%A1, and ñ becomes %C3%B1.

# Importance in APIs and GET Requests

When developing integrations, a typical mistake is passing a raw string to URL parameters. If you insert shirt&blue raw into your backend (/search?q=shirt&blue), the server will interpret blue as a new parameter, breaking all the logic.This tool performs clean, automatic calculations in your local browser. None of your URL strings need to be transmitted to third-party servers, which helps keep your tokens and analytics parameters private.

Bibliographic References