Developer Tools Guide

URL Encode/Decode Guide

Convert text and query parameters to and from RFC 3986 percent-encoding with component and full URL modes.

Overview

Encode special characters into RFC 3986 percent-encoded strings or decode encoded URLs back to human-readable text with dedicated component and full-URI modes.

When to Use URL Encode/Decode

Use URL Encode/Decode when query strings, redirects, or webhook callbacks break because reserved characters like spaces, ampersands, or question marks are not encoded properly.

Inputs, Formats & Specifications

Accepted Inputs
Raw text, query parameters, or percent-encoded URL strings
Output Formats
Percent-encoded string or decoded readable text
Supported Standards
RFC 3986 percent-encoding (e.g. `%20` for space, `%2F` for `/`, `%3F` for `?`)
Browser Limits & Scope
Malformed percent-sequences (such as a trailing `%` without two hex digits) trigger clear syntax warnings rather than silent failure.

How to use URL Encode/Decode

  1. Choose your mode: 'Encode' (Text to URL-safe percent-encoding) or 'Decode' (Percent-encoded to plain text).
  2. Select encoding scope: 'Component' (encodes slashes and query delimiters) or 'Full URL' (preserves URL structure).
  3. Paste your text or query string into the input area.
  4. View the converted result and copy it with one click.

Real-World Examples

API Query String EncodingEncode spaces, ampersands, and special characters in search parameters like `q=cats & dogs?` into `q=cats%20%26%20dogs%3F` to prevent broken API calls.
Redirect URL Parameter ParsingDecode an encoded return URL like `redirect_uri=https%3A%2F%2Fapp.example.com%2Fcallback` to verify its destination domain.

Frequently Asked Questions

What is the difference between encodeURI and encodeURIComponent?

`encodeURI` is intended for complete URLs and does not encode characters with special meaning in a URL (`:`, `/`, `?`, `#`). `encodeURIComponent` encodes all reserved characters and is intended for individual query parameter values.

How are spaces represented in URL encoding?

In standard RFC 3986 URI encoding, spaces are represented as `%20`. In legacy form query parameters (`application/x-www-form-urlencoded`), spaces are sometimes shown as `+`.

Can I decode a URL that was double-encoded?

Yes. Simply run the decode operation a second time if the first pass reveals another layer of percent-encoded characters.

Privacy & Data Security

URL Encode/Decode is designed to run in the browser. Review outputs before sharing them with any external service or workflow.

Last updated:

Related Tools