URL Encoder & Decoder

Convert special characters and Unicode strings to percent-encoded URLs and back.

URL · Percent-Encode · URI

Loading tool workspace...

Overview of the Online URL Encoder & Decoder

Whenever you copy a web address containing non-ASCII characters, spaces, or symbols and see sequences like %E2%9C%93 or %20, you are looking at Percent-Encoding (RFC 3986). Because Uniform Resource Identifiers (URIs) only transmit a restricted set of unreserved ASCII characters directly, international scripts (Korean, Chinese, Japanese, accented Latin letters), whitespace, and reserved query delimiters (?, &, =, #, /, +) must be converted into UTF-8 hexadecimal byte triplets prefixed with %.

AllUtility’s URL Encoder & Decoder converts raw strings and query parameters into safe percent-encoded payloads and decodes cryptic encoded URLs back into clean, human-readable text. All operations run 100% locally inside your browser—ensuring OAuth redirect URIs, internal staging endpoints, webhook URLs, and campaign tracking links remain strictly private on your device.

Key Features

  • RFC 3986 UTF-8 Percent-Encoding: Safely encodes spaces (%20), reserved delimiters, emojis, and multibyte Unicode characters using standard encodeURIComponent rules.
  • Lossless URI Decoding: Instantly restores unreadable %XX byte sequences from browser bars, server logs, or analytics exports back into readable native text.
  • Query String & UTM Integrity: Prevents embedded &, =, #, or + symbols inside parameter values from breaking API query parsing or truncating marketing UTM tags.
  • 100% Browser-Side Execution & Live Character Counts: Zero server requests, zero data retention, real-time input/output length counters, and one-click clipboard copy.

Step-by-Step Usage Guide

  1. Enter Source Text or URL: Paste a raw parameter value, search phrase, or percent-encoded URI string into the left input field.
  2. Choose Encode or Decode: Click Encode to convert special and Unicode characters into %XX sequences, or click Decode to restore an encoded string to plain text.
  3. Inspect Output & Character Count: Review the converted result in the right pane along with exact character counts; malformed % byte sequences will trigger a clear inline error notice.
  4. Copy or Clear: Click Copy to transfer the result to your clipboard for API requests, documentation, or spreadsheets, and click Clear to reset the workspace.

Practical Example & URL Encoding Best Practices

Encoding a query parameter value that contains spaces, ampersands, and percent signs prevents downstream parsers from splitting the parameter prematurely:

Raw Parameter Value:
R&D Report 2026 (100% Verified)

Percent-Encoded Output:
R%26D%20Report%202026%20(100%25%20Verified)

Keep these two engineering rules in mind when working with URLs:

  • Encode Parameter Values, Not Always the Full URL: Encoding a complete URL like https://example.com?q=a&b converts :// into %3A%2F%2F. Full-URL encoding is ideal when passing a callback URL inside another query parameter (such as ?redirect_uri=https%3A%2F%2F...), whereas for a standalone clickable link you should encode only the individual parameter values.
  • Avoid Double Encoding: Running Encode twice on an already encoded string turns every % into %25 (for example, %20 becomes %2520), causing backend servers that decode once to receive literal %20 instead of a space.

Frequently Asked Questions

Why do readable links in my browser address bar turn into % codes when copied?

Modern browsers display decoded Unicode characters in the address bar for visual clarity, but copy the underlying RFC 3986 percent-encoded ASCII representation to the clipboard so links remain unbroken across email clients, chat apps, and HTTP headers. Paste the link here and click Decode whenever you want clean readable text.

What is the difference between %20 and + when encoding spaces?

Standard URI percent-encoding defined in RFC 3986 represents spaces as %20. In contrast, legacy HTML form submissions using the application/x-www-form-urlencoded MIME type substitute spaces with +, which is why search engine query strings frequently show word1+word2.

Should I percent-encode UTM campaign parameters for marketing links?

Yes. If utm_campaign or utm_content values contain spaces, #, &, or non-ASCII text, unencoded characters can prematurely terminate the query string or corrupt attribution reports in analytics platforms. Encoding each parameter value guarantees accurate tracking.

Are my internal URLs, OAuth callback links, or query tokens sent to a server?

Never. All encoding and decoding calculations execute exclusively inside your browser's local JavaScript runtime. No URLs or text inputs are ever transmitted over the network or logged.