Free Online URL Encoder & Decoder

Encode and decode URLs, query strings, and percent-encoded parameters with RFC 3986 compliance and an interactive query parameter inspector.

⚡ In-browser processing100% FreeNo Account Required
Loading editor…

Rate URL Encoder & Decoder

Feedback

Save a personal rating in this browser.

Choose a rating

How to use URL Encoder & Decoder

  1. 1Select 'URL Encode' to percent-encode reserved characters, or 'URL Decode' to restore percent-encoded strings to clear plaintext.
  2. 2Choose your encoding scope: 'Component' (for query values & parameters), 'Full URL' (preserving ://, ?, &, and # delimiters), or 'Form (+)' for HTML form submissions.
  3. 3Paste your raw string or complex URL into the input pane, or click 'Sample' to test a standard API endpoint with query arguments.
  4. 4Review the parsed 'URL Components & Query Inspector' table to examine individual keys, values, and protocol metadata.
  5. 5Click 'Copy' to copy the encoded or decoded URL to your clipboard, or click 'Save' to export to a text file.

Key Features & Highlights

  • •RFC 3986 Strict Encoding: Accurately escapes non-alphanumeric characters including !, ', (, ), and * which are often skipped by legacy implementations.
  • •Three Tailored Modes: Toggle easily between Component (query parameter values), Full URL (entire links with structural preservation), and Form (+) application/x-www-form-urlencoded spaces.
  • •Interactive Query Parameter Inspector: Automatically parses full URLs and extracts query keys and values into an organized, copyable data table.
  • •Detailed URL Component Diagnostics: Breaks down and verifies URL protocols, hostnames, directory paths, and fragment identifiers.
  • •Percent-Escape Counter: Real-time telemetry displaying the exact number of %XX hexadecimal escape sequences generated.
  • •Bi-Directional Instant Swap: Switch between encoded output and decoded input instantly for rapid debugging cycles.
  • •100% Client-Side Privacy: No URLs, session tokens, or query parameters are ever uploaded or transmitted across the network.
Quick summary

Encode A&B as a query-parameter value to get A%26B. Encode the value before attaching it to the URL so the ampersand inside the value stays distinct from the separators between parameters.

How URL Percent-Encoding and Decoding Works

The architecture of the World Wide Web relies on Uniform Resource Identifiers (URIs) defined by RFC 3986. Because URIs use specific characters as structural delimiters (such as :, /,?, &, and =), any arbitrary data containing these characters—as well as non-ASCII alphabets, spaces, and emojis—must be percent-encoded to prevent ambiguous parsing.

Percent-encoding transforms unsafe characters into a percent sign followed by the two-digit hexadecimal representation of their underlying UTF-8 byte. For example, a standard space character (ASCII 32) becomes %20, an ampersand becomes %26, and an emoji like 🚀 (4 bytes) becomes %F0%9F%99%82.

Choosing the Right Mode: Component vs. Full URL vs. Form (+)

Using the wrong encoding method is a primary cause of broken API integrations:

  • Component Mode (encodeURIComponent): Use this when encoding individual query parameter values (e.g., ?query=hello%20world%26more). It escapes delimiters like & and = so they are not misinterpreted as secondary query keys.
  • Full URL Mode (encodeURI): Use this when encoding an entire web address. It leaves structural URL separators (like https://, /, ?, and #) intact while escaping invalid characters in paths and arguments.
  • Form (+) Mode (application/x-www-form-urlencoded): Standard HTML form submissions historically encode spaces as plus signs (+) instead of %20. Use this mode when testing legacy form endpoints or OAuth 1.0/2.0 token requests.

Strict RFC 3986 vs. Standard JavaScript Functions

Native JavaScript functions (encodeURIComponent) leave certain punctuation marks unescaped for historical reasons, specifically: !, ', (, ), and *. In strict RFC 3986 implementations (such as AWS Signature Version 4 or OAuth authorization headers), these unescaped characters cause signature mismatches. BrivTools provides strict RFC 3986 compliance, ensuring reliable interoperability with modern cloud APIs.

Related Developer & Security Tools

Processing and privacy

This tool processes its inputs in your browser. Supported inputs and practical limits depend on the tool and your device.

Frequently Asked Questions

Common questions about URL Encoder & Decoder usage, file handling, security, and limits

What is URL percent-encoding and why is it necessary?+

Uniform Resource Identifiers (URIs) are constrained by RFC 3986 to a specific subset of ASCII characters. Characters outside this set (such as spaces, emojis, or international alphabets) and characters with syntactic meaning (like '?', '&', '=', and '/') must be encoded into a percent sign followed by a two-digit hexadecimal representation of their UTF-8 byte (for example, a space becomes '%20'). This prevents parsing errors and protects the integrity of transmitted data.

What is the difference between encodeURI() and encodeURIComponent()?+

encodeURI() is meant for complete URLs; it leaves functional URL delimiter characters intact (such as 'http://', '?', '&', '=', and '#'). In contrast, encodeURIComponent() encodes every reserved character, making it safe for query string values where an unencoded '&' or '=' would otherwise break the query parser.

Why do some spaces encode as '%20' while others encode as '+'?+

In standard RFC 3986 URI paths and modern web standards, spaces are encoded as '%20'. However, the legacy HTML form standard (application/x-www-form-urlencoded) traditionally replaces spaces with '+' in query strings. Our tool provides a dedicated 'Form (+)' option so you can test and generate both formats.

Why does Strict RFC 3986 encode !, ', (, ), and *?+

JavaScript's default encodeURIComponent() function does not encode !, ', (, ), and * for historical compatibility. However, RFC 3986 considers these reserved in certain subcomponents. Enabling 'Strict RFC 3986' ensures that these characters are percent-encoded into %21, %27, %28, %29, and %2A for maximum interoperability across OAuth signatures and strict API gateways.

Are my sensitive API query parameters safe?+

Yes. All encoding, decoding, and parsing occurs 100% inside your local web browser sandbox. No URLs, query parameters, API keys, or session tokens are ever sent to a remote server or logged in any database.

Related Free Utilities

Tools for related tasks

View all tools →