URL Encode Decodeurlenocdedecode.com
100% Client-Side • Free Online URL Encode Decode Tool • RFC 3986

URL Encode Decode Online

The complete online url encode decode tool. Safely url encode and url decode full web addresses, query string parameters, UTF-8 text, and percent-encoded tokens directly in your browser.

0 chars
ResultReady
0 chars

Smart URL Inspector

Live structural breakdown of URI components

Waiting for URL
Protocol
—
Host / Domain
—
Port
—
Pathname
—
Fragment (#)
—
Origin
—

Query Parameter Inspector

Live structured key-value table from search parameters

Key / ParameterValueActions
No query parameters detected in input. Enter a URL with query strings (e.g. ?key=value) or click "Add Parameter".
Comprehensive Technical Guide

Complete Guide to URL Encode & Decode Operations

Master percent-encoding standards, understand RFC 3986 compliance, and learn how to safely encode and decode URLs and query parameters online.

What is URL Encoding and Decoding?

URL encoding (also formally known as percent-encoding) is a standardized mechanism defined by the Internet Engineering Task Force (IETF) in RFC 3986. The primary objective of URL encoding is to convert non-ASCII characters, spaces, and reserved syntax delimiters into a universal, internet-safe representation consisting exclusively of valid US-ASCII characters.

Conversely, URL decoding is the reverse process: it analyzes percent-encoded sequences (such as %20, %3F, or %26) and reconstructs the original human-readable text, UTF-8 strings, and query arguments. Together, these two processes form the foundation of modern web communication, ensuring that browsers, web servers, API gateways, and microservices correctly interpret web addresses without corruption or data truncation.

Whether you need to url encode decode complex query strings, construct secure OAuth 2.0 redirect URIs, or troubleshoot REST API parameters, utilizing a fast, reliable url encode decode online tool guarantees that your web addresses conform strictly to global networking standards.

Why Do URLs Require Percent-Encoding?

A Uniform Resource Identifier (URI) is syntactically divided into several distinct components: protocol scheme, host authority, port, path segments, query strings, and fragment identifiers. Certain characters are designated as reserved characters because they serve as structural delimiters within the URI grammar:

  • Colon (:) and Slash (/): Separate the protocol scheme (e.g., https://) and define directory path segments.
  • Question Mark (?): Demarcates the boundary between the URL pathname and the beginning of query parameters.
  • Ampersand (&) and Equals (=): Bind keys to values (key=value) and separate multiple query key-value pairs.
  • Hash (#): Marks the start of a client-side document anchor or fragment.

If your query parameter contains any of these characters as raw data (for example, searching for C++ & Web Development), an unencoded ampersand would prematurely split your search query into two broken parameters. By choosing to url encode online, special symbols are converted into safe hexadecimal tokens (turning & into %26 and + into %2B), preserving the integrity of your application logic.

How to URL Encode and URL Decode Online

Using our online url encode decode tool is straightforward, instantaneous, and operates completely inside your web browser. Here is how you can perform both operations seamlessly:

1

How to URL Encode

Paste your raw URL, text, or query parameter into the input area. Click Encode URL to apply URI-level encoding (preserving structural slashes and colons), or click Encode Component if you are encoding an individual query parameter value.

2

How to URL Decode

Paste any percent-encoded text or URL containing %20, %3D, or hex triplets into the editor. Click Decode URL or Decode Component. Our url decode tool immediately transforms the hex codes back into clear text.

If you need to verify both directions, you can easily url decode encode back and forth using the instant Swap button to inspect how characters change dynamically across transformations.

encodeURI vs. encodeURIComponent: When to Use Which?

One of the most frequent sources of bugs in web applications is confusing whole-URI encoding with component-level encoding. Understanding the difference is vital for every developer:

encodeURI(fullUri)

Intended for complete, absolute, or relative URIs. It assumes the input is already an assembled web address and intentionally does not encode reserved protocol delimiters (:, /, ?, &, #, =). It only encodes illegal characters such as spaces and multi-byte UTF-8 symbols.

encodeURI("https://example.com/search?q=hello world")
// → "https://example.com/search?q=hello%20world"
encodeURIComponent(componentValue)

Intended for an individual query parameter key or value. Because it is part of a larger URL, it encodes all reserved delimiters including &, =, /, and : so that the value cannot break out of its parameter boundary.

encodeURIComponent("https://callback.com/auth?token=123")
// → "https%3A%2F%2Fcallback.com%2Fauth%3Ftoken%3D123"

Common Real-World Use Cases for URL Encoding & Decoding

Engineers and marketers encounter URL encoding across numerous everyday digital workflows:

OAuth 2.0 & SSO Callbacks

When passing a destination URL inside a redirect_uri parameter during OAuth authorization flows, component encoding prevents nested query parameters from breaking the authentication exchange.

REST API & Microservice Queries

Passing email addresses, search terms with spaces, JSON filters, or timestamps containing colons (2026-09-01T12:00:00Z) requires precise encoding to prevent 400 Bad Request HTTP errors.

Digital Marketing & UTM Tracking

Campaign parameters such as utm_campaign=summer 2026 launch & sale must be encoded properly so analytics platforms like Google Analytics (GA4) capture accurate attribution without splitting strings.

Web Scraping & Data Normalization

When web crawlers extract links from HTML source code containing escaped entities (like &), an online url decode step is necessary to reconstruct clean, canonical destination URLs.

Why Choose Our 100% Client-Side URL Encode Decode Online Tool?

Unlike older web utilities that submit your text and URLs to a remote server for processing, our url encode decode online tool executes 100% locally inside your browser's native JavaScript runtime.

This guarantees complete confidentiality for confidential API tokens, passwords, customer emails, internal staging URLs, and proprietary search queries. No inputs are ever logged, cached, transmitted, or stored on external cloud infrastructure. Enjoy lightning-fast, zero-latency conversions with complete peace of mind.

RFC 3986 Standard

Why Do URLs Need Encoding and Decoding?

Uniform Resource Identifiers (URIs) are constrained by the RFC 3986 specification to a limited subset of the US-ASCII character set. Any character outside this allowed range—including spaces, Unicode symbols, and reserved structural characters—must be converted into percent-encoding.

01

Syntax Preservation

Characters like ?, &, =, and / have special delimiter meanings in URLs. Without proper encoding, passing these in a query parameter will break URL parsing and truncate data.

02

UTF-8 & Unicode Safety

Modern international characters, accents (like é or ü), and emojis (🚀) are multi-byte UTF-8 sequences. Percent-encoding converts each UTF-8 byte into a safe hexadecimal representation.

03

Whitespace Handling

Literal space characters are invalid in raw URLs. In standard URL component encoding, space is encoded as %20 (or occasionally + in application/x-www-form-urlencoded query strings).

Difference Between encodeURI() and encodeURIComponent()

Choosing the right JavaScript function is critical to avoid broken links or double-encoded parameters.

FeatureencodeURI()encodeURIComponent()
Intended PurposeEncodes a complete, full URLEncodes a single query parameter value
Does NOT Encode (Preserved), / ? : @ & = + $ # ; ~ - _ . ! * ' ( ) [ ]- _ . ! ~ * ' ( )
Encodes Delimiters (&, =, ?)No (preserves URL routing)Yes (e.g. → %26, %3D, %3F)
Best Used WhenYou have an entire URL string with spacesConstructing search terms, callbacks, or UTM tags
ASCII Quick Reference

Common Percent-Encoding Hex Reference Table

Click any hex code below to instantly copy it to your clipboard.

Practical Scenarios

Real-World URL Encoding & Decoding Examples

Study common URL patterns or copy them directly for testing in your applications.

Example 1: Search Query with Spaces and Special Characters

Raw / Decoded
https://example.com/search?q=developer tools & apis
Encoded
https://example.com/search?q=developer%20tools%20&%20apis

Notice how encodeURI() encodes spaces as %20 while preserving standard URL structure, but encodeURIComponent() encodes every delimiter.

Example 2: Nested OAuth / SSO Redirect URL

Raw / Decoded
https://auth.example.com/login?redirect_uri=https://app.example.com/dashboard?view=analytics&user=123
Encoded
https://auth.example.com/login?redirect_uri=https%3A%2F%2Fapp.example.com%2Fdashboard%3Fview%3Danalytics%26user%3D123

When nesting a URL inside another query parameter, the inner URL must be component-encoded so its ampersands and colons do not break the outer OAuth flow.

Example 3: International Characters & Multi-byte UTF-8

Raw / Decoded
https://example.com/destinations?city=München&currency=€&status=🚀
Encoded
https://example.com/destinations?city=M%C3%BCnchen&currency=%E2%82%AC&status=%F0%9F%9A%80

Multi-byte characters produce multiple percent-encoded hex sequences (e.g. 🚀 becomes %F0%9F%9A%80 across 4 bytes).

Example 4: UTM Marketing Campaign Link

Raw / Decoded
https://urlenocdedecode.com/blog/url-guide?utm_source=newsletter&utm_medium=email&utm_campaign=summer 2026 launch
Encoded
https://urlenocdedecode.com/blog/url-guide?utm_source=newsletter&utm_medium=email&utm_campaign=summer%202026%20launch

Ensures marketing tracking URLs work smoothly across email clients, ad networks, and browser address bars.

Toolkit Directory

Explore All URL & Query String Tools

Fast, client-side developer utilities designed for privacy, speed, and accuracy.

URI / Component

URL Encoder

Encode full URLs with encodeURI() or parameters with encodeURIComponent().

Fast & Safe

URL Decoder

Decode percent-encoded URI strings and query components back into human text.

Structural

URL Parser & Inspector

Deconstruct any URL into protocol, host, port, path, parameters, and fragments.

Key-Value

Query String Parser

Extract query parameters (?k=v) into editable structured key-value tables and JSON.

Visual Editor

Query String Builder

Visually construct query strings from key-value pairs with automatic percent encoding.

Privacy

URL Cleaner & Stripper

Remove UTM tags, tracking parameters (fbclid, gclid), and empty query keys.

RFC 3986

URL Validator

Check RFC 3986 compliance, protocol validity, and address syntax errors.

Marketing

UTM Campaign Builder

Generate Google Analytics campaign tracking URLs with standard UTM parameters.

Analytics

UTM Parameter Parser

Inspect and extract utm_source, utm_medium, utm_campaign, and related tags.

JSON Export

URL to JSON Converter

Transform any URL structure and query parameters into cleanly formatted JSON.

JSON to URL

JSON to Query String

Convert JSON key-value objects directly into valid encoded URL query strings.

Frequently Asked Questions

Frequently Asked Questions About URL Encode & Decode

Clear, technical answers to essential questions regarding percent-encoding, decoding mechanics, RFC standards, and hex characters.

What is URL encode and decode?

URL encode and decode are bidirectional web processes defined by RFC 3986 for transmitting data safely within Uniform Resource Identifiers (URIs). URL encoding converts characters that are disallowed or reserved in URLs (such as spaces, punctuation, symbols, and non-ASCII glyphs) into percent-encoded hexadecimal sequences like %20 or %26. URL decoding performs the inverse operation, scanning percent-encoded triplets and translating them back into their original human-readable text and UTF-8 characters.

How do I decode a URL?

To decode a URL online: (1) Copy the encoded URL or query string containing percent-encoded sequences (such as %20 or %3D). (2) Paste the string into the input field of our free online URL Decode tool. (3) Click Decode URL (to decode full web addresses) or Decode Component (for individual parameter values). (4) Instantly copy the resulting plain text. In code, you can use JavaScript's native decodeURI() or decodeURIComponent(), Python's urllib.parse.unquote(), or PHP's urldecode().

What is the difference between encoding and decoding?

Encoding is the forward transformation of plain text, data, or symbols into a standardized, machine-readable format to ensure safe transmission across networks and URI parsers without breaking syntax rules. Decoding is the reverse extraction process, converting the standardized encoded sequences back into the original raw text, symbols, or binary content. In URLs, encoding turns "hello world" into "hello%20world", while decoding turns "hello%20world" back into "hello world".

What is %27 in URL encoding?

In URL encoding, %27 represents the single quote or apostrophe character ('). In the US-ASCII table, the single quote character has a decimal code of 39, which corresponds to hexadecimal 27. When a URL parameter contains an apostrophe (for example, "John's Car"), it is percent-encoded as "John%27s%20Car" to prevent syntax ambiguities and potential database or query parsing issues.

How to decode an encoded URL?

You can decode an encoded URL using an online URL decoder tool or programmatically in software. Online: Paste your encoded link into our interactive URL Decoder tool and click Decode URL. The tool automatically identifies percent-encoded tokens and reconstructs the decoded URL. In JavaScript: Call decodeURI(encodedUrl) for full URLs, or decodeURIComponent(encodedParam) for query parameters. In Python: Use import urllib.parse; decoded = urllib.parse.unquote(encoded_url). In PHP: Use $decoded = urldecode($encoded_url);.

What is URL encoding and decoding?

URL encoding and decoding (percent-encoding) is an internet protocol mechanism that ensures web browsers, servers, and APIs exchange data unambiguously. URLs are restricted by RFC 3986 to a subset of ASCII characters. Encoding replaces unsafe characters, spaces, and reserved delimiters with % followed by two hexadecimal digits representing the character's UTF-8 byte. Decoding reads these %XX hexadecimal values and restores the original characters so applications and users can read the information.

What is an example of decode?

A practical example of URL decoding is converting the percent-encoded string: "https://example.com/search?q=developer%20tools%20%26%20apis" back into its human-readable form: "https://example.com/search?q=developer tools & apis". In this example, %20 is decoded into spaces and %26 is decoded into the ampersand symbol (&).

How to decode encoding?

To decode any URL percent-encoding: (1) Identify the percent-encoded sequences consisting of a % sign followed by two hexadecimal characters (e.g., %2F, %3A, %20). (2) Use an online URL decoder or a programming language's decoding function (like decodeURIComponent() in JS or urllib.parse.unquote() in Python). (3) The decoder translates each hex pair back to its byte value and decodes multi-byte UTF-8 sequences into the correct character or emoji.

What does "decode" mean?

In computing and web architecture, decode means converting encoded or escaped data back into its original, understandable, and uncompressed representation. When applied to URLs, decoding specifically means taking percent-escaped byte sequences (%XX) and converting them back to original text characters, words, spaces, and Unicode glyphs.

How do I encode a URL?

To encode a URL online: (1) Paste your raw URL, text, or query parameters with spaces and special characters into our URL Encoder tool. (2) Click Encode URL (using encodeURI() to keep standard routing slashes / and colons :) or Encode Component (using encodeURIComponent() to escape all reserved characters in query parameter values). (3) Copy the resulting percent-encoded string for use in APIs, HTML links, or OAuth redirects.

How does URL decoding work?

URL decoding works by parsing the input string sequentially from left to right. Whenever the decoder encounters a percent sign (%), it reads the following two hexadecimal digits (e.g., 20), converts the hexadecimal value to a byte number (0x20 = decimal 32), and maps it to the corresponding ASCII or UTF-8 character (space). If the hex bytes represent a multi-byte UTF-8 character (like %C3%A9 for é or %F0%9F%9A%80 for 🚀), the decoder combines the consecutive byte sequences into the single target Unicode glyph.