URL Encoder Decoder — Percent-Encode & Decode URLs Instantly

URLs can only safely contain a limited set of characters. Anything outside that set — spaces, ampersands, question marks, special symbols, accented letters, or characters from non-Latin alphabets — has to be converted into a special format before it can travel through a web address without breaking. This conversion process is called URL encoding, or percent-encoding, and it is something every web developer, SEO professional, and digital marketer runs into sooner or later. Our Free URL Encoder Decoder handles both directions of this conversion instantly — turning plain text and unsafe characters into proper percent-encoded URLs, and converting percent-encoded URLs back into readable plain text — all processed locally in your browser following the official RFC 3986 standard.

No account required. No payment. No data sent to any server. Just paste your text or URL and convert it instantly.

What Is This Free URL Encoder Decoder?

This is an online text conversion tool that converts plain text and special characters into percent-encoded URL format, and converts percent-encoded URLs back into readable plain text. It uses the same encoding logic built into modern web browsers — specifically the encodeURIComponent() and decodeURIComponent() functions — to ensure full compatibility with how real browsers and servers handle URL encoding.

When you use this tool, you can:

• URL Encode — convert plain text or URLs with special characters into percent-encoded format
• URL Decode — convert percent-encoded URLs back into readable plain text
• Instant Conversion — see your encoded or decoded output immediately as you work
• Copy Output — copy your converted text to your clipboard in one click
• Clear — reset the input field instantly to start a new conversion
• Load Sample — load example text to see the tool in action before using your own content
• Common Encoding Reference — a built-in lookup table showing the percent-encoded value for every commonly used special character
• RFC 3986 Compliance — encoding that follows the official internet standard for URI syntax, ensuring compatibility with all modern browsers and web servers
• 100% Client-Side Processing — all encoding and decoding happens directly in your browser; no data is ever sent to or stored on any server

What Is URL Encoding and Why Does It Exist?

URL encoding — also called percent-encoding — is the process of converting characters that are not allowed or have special meaning within a URL into a format that can be safely transmitted as part of a web address. It works by replacing the character with a percent sign (%) followed by two hexadecimal digits representing that character’s value.

URLs follow a strict syntax defined by internet standards. Certain characters are reserved because they have specific structural meaning — for example, the question mark (?) separates the path from the query string, the ampersand (&) separates multiple query parameters, and the forward slash (/) separates path segments. If these characters appear as literal data within a URL rather than as structural separators, they need to be encoded so the browser and server can correctly distinguish between URL structure and URL content.

Beyond reserved characters, URLs are also technically limited to a specific subset of ASCII characters. Spaces are not allowed in URLs at all. Characters from non-Latin alphabets, accented letters, emoji, and many symbols also need to be encoded before they can be included in a URL.

A simple example:

If you want to create a URL that includes a search query for “coffee & tea”, the space and ampersand need to be encoded because a literal space would break the URL and a literal ampersand would be misread as a parameter separator. The properly encoded version becomes:

coffee%20%26%20tea

When a browser or server receives this encoded string, it decodes it back to “coffee & tea” before processing the actual search query — preserving the original meaning while keeping the URL structurally valid throughout transmission.

How Percent-Encoding Works

Percent-encoding represents any character as a percent sign followed by the character’s value in hexadecimal (base-16) notation, based on its position in the ASCII or UTF-8 character encoding system.

The basic format: %XX

Where XX is a two-digit hexadecimal number representing the character being encoded.

Example breakdown:

• The space character has an ASCII value of 32 in decimal, which is 20 in hexadecimal — so a space becomes %20
• The ampersand character has an ASCII value of 38 in decimal, which is 26 in hexadecimal — so an ampersand becomes %26
• The colon character has an ASCII value of 58 in decimal, which is 3A in hexadecimal — so a colon becomes %3A

For characters beyond the basic ASCII set — accented letters, characters from other alphabets, emoji, and other Unicode characters — the character is first converted into its UTF-8 byte representation, and each byte of that representation is then percent-encoded separately. This is why some single special characters can result in multiple percent-encoded sequences when they fall outside the basic ASCII range.

The Complete URL Percent-Encoding Reference Table

Here is the complete reference of commonly used special characters and their percent-encoded equivalents:

Character	Encoded Value	Character	Encoded Value
space	%20	!	%21
“	%22	#	%23
$	%24	%	%25
&	%26	‘	%27
(	%28	)	%29
*	%2A	+	%2B
,	%2C	–	%2D
.	%2E	/	%2F
:	%3A	;	%3B
<	%3C	=	%3D
>	%3E	?	%3F
@	%40	[	%5B
]	%5D	^	%5E
{	%7B	|	%7C
}	%7D	~	%7E

Important note on the space character: While %20 is the technically correct percent-encoding for a space character anywhere in a URL, you may also see a + symbol used to represent a space — but only specifically within URL query strings (the part after the ?), following an older encoding convention called application/x-www-form-urlencoded that is commonly used in HTML form submissions. Outside of query strings, + represents a literal plus sign, not a space. This tool follows the encodeURIComponent() standard, which consistently uses %20 for spaces — the more universally correct and unambiguous approach recommended by current standards.

Reserved Characters vs. Unreserved Characters

URL syntax standards classify characters into two categories that determine whether encoding is required:

---

Unreserved Characters — Never Need Encoding

These characters have no special meaning in URL syntax and can always be used directly without encoding:

• Uppercase letters: A through Z
• Lowercase letters: a through z
• Digits: 0 through 9
• Hyphen: –
• Underscore: _
• Period: .
• Tilde: ~

This is why you will never see these characters encoded in any properly formatted URL — they are always safe to include as-is.

Reserved Characters — Have Structural Meaning

These characters have specific structural meaning within URL syntax and must be encoded whenever they appear as literal content rather than serving their structural purpose:

Character	Structural Purpose in URLs
/	Separates path segments
?	Begins the query string
#	Begins the fragment identifier
&	Separates query parameters
=	Separates parameter names from values
:	Separates the scheme from the rest of the URL, and used in port numbers
@	Separates user info from the host in some URL formats
+	Historically used to represent a space in query strings

When any of these characters needs to appear as actual data — for example, an ampersand that is part of a search query rather than separating two parameters — it must be percent-encoded to avoid being misinterpreted as URL structure.

How to Use This Free URL Encoder Decoder

Using the tool takes just seconds. Here is the complete process for both directions of conversion:

Encoding Text or URLs Into Percent-Encoded Format

Step 1 — Switch to the Encode Tab Click the 🔒 URL Encode tab at the top of the tool if it is not already selected.

Step 2 — Enter Your Plain Text or URL Type or paste your plain text into the input box. This can be a search query, a URL parameter value, a string with special characters, or any text you need to safely include as part of a URL.

Step 3 — Click “Encode to URL Format” Click the ✨ Encode to URL Format button. The tool instantly processes your text using encodeURIComponent() logic, converting every special character into its correct percent-encoded equivalent.

Step 4 — Review Your Encoded Output The percent-encoded, URL-safe version of your text appears in the output box, ready to be used as part of a URL, query string, or API request.

Step 5 — Copy Your Result Click the 📋 Copy button to copy the encoded output to your clipboard, ready to paste directly into your URL, code editor, or browser address bar.

Decoding Percent-Encoded URLs Back Into Plain Text

Step 1 — Switch to the Decode Tab Click the 🔓 URL Decode tab at the top of the tool.

Step 2 — Enter Your Percent-Encoded Text Paste text containing percent-encoded sequences — for example, a URL you copied from your browser’s address bar, a query string from server logs, or an exported link containing codes like %20, %3A, or %2F.

Step 3 — Click “Decode to Plain Text” Click the ✨ Decode to Plain Text button. The tool converts every percent-encoded sequence back into its original readable character.

Step 4 — Review Your Decoded Output The plain, readable text version of your URL or content appears in the output box, with all percent-encoded sequences converted back to their original characters.

Step 5 — Copy Your Result Click the 📋 Copy button to copy your decoded plain text to your clipboard.

Additional Tool Features

Clear Button Use the 🗑️ Clear button on either tab to instantly reset the input field and start a new conversion.

Load Sample Button Use the 📝 Load Sample button to load example text into the input field, giving you an immediate, practical demonstration of how the tool works before you use your own content.

Common Use Cases for URL Encoding and Decoding

Building Search Query URLs

Many websites, including search engines, accept search terms as URL parameters. If your search term contains spaces or special characters, those need to be encoded for the URL to function correctly. For example, searching for “best coffee shops near me” needs the spaces encoded as %20 to become a valid query parameter: best%20coffee%20shops%20near%20me.

Working With Query String Parameters

When passing data through URL parameters — for tracking codes, filter settings, search terms, or any value appended after a ? in a URL — any special characters within those values need encoding to prevent the URL from breaking or being misinterpreted. This is especially common when building UTM tracking parameters for marketing campaigns that include spaces or special characters in campaign names.

API Requests and Development

When building API requests that include parameters in the URL itself (rather than in a request body), any data values that contain spaces, special characters, or reserved URL characters must be properly encoded. This is a routine task for developers integrating with REST APIs, building webhook URLs, or constructing dynamic links programmatically.

Creating Shareable Links With Special Characters

If you need to create a shareable link that includes special characters — a file name with spaces, a search query with punctuation, or a parameter containing symbols — encoding ensures the link works correctly when clicked, regardless of which browser or platform the recipient is using.

Decoding URLs From Server Logs and Analytics

Server access logs, referrer data, and analytics platforms often display URLs in their percent-encoded form. Decoding these URLs makes them human-readable, which is particularly useful when reviewing what search terms or referring content brought visitors to your site, or when investigating specific requests in raw server log files.

International and Non-Latin Characters in URLs

URLs containing characters from non-Latin alphabets — Chinese, Arabic, Cyrillic, Japanese, and others — or accented Latin characters need to be percent-encoded based on their UTF-8 byte representation. This is essential for international websites, multilingual content, and any URL containing non-English characters in paths, filenames, or query parameters.

Handling File Names With Special Characters in URLs

If a file name on your server contains spaces or special characters — like “annual report 2026.pdf” — the URL pointing to that file needs the special characters properly encoded to load correctly: annual%20report%202026.pdf.

Debugging Broken Links

If a link is not working correctly and you suspect encoding issues — perhaps a redirect is failing, or a query parameter is not being read correctly by a server — encoding or decoding the URL components helps you isolate exactly which part of the URL structure may be causing the problem.

URL Encoding vs. HTML Encoding — What Is the Difference?

This is one of the most common points of confusion for developers, since both involve converting special characters into safer formats — but they serve completely different purposes:

Feature	URL Encoding	HTML Encoding
Purpose	Safely include special characters within a URL	Safely display special characters within HTML page content
Format	%XX (percent followed by hex code)	&entity; or &#number;
Example for space	%20	(non-breaking space)
Example for ampersand	%26	&
Used in	URLs, query strings, API requests	HTML page content, attribute values
Standard	RFC 3986	HTML5 specification

URL encoding is what this tool handles — converting characters for safe inclusion in web addresses. HTML encoding is a separate process used specifically for displaying special characters correctly within HTML page content, preventing both display issues and cross-site scripting (XSS) vulnerabilities. The two encoding systems are not interchangeable — using HTML entities within a URL, or percent-encoding within HTML page content, will not work correctly. If you need to safely display text content on a webpage rather than include it in a URL, use a dedicated HTML encoder instead.

RFC 3986 — The Official URL Encoding Standard

RFC 3986 is the official internet standard published by the Internet Engineering Task Force (IETF) that defines the generic syntax for Uniform Resource Identifiers (URIs), including the complete specification for percent-encoding.

This standard defines exactly which characters are reserved, which are unreserved, and the precise rules for how percent-encoding must be applied to ensure URLs work consistently across every browser, server, and internet-connected system in the world.

Why standard compliance matters:

Following RFC 3986 ensures that:

• Your encoded URLs work correctly across all modern browsers (Chrome, Firefox, Safari, Edge)
• Your encoded URLs are correctly interpreted by web servers and APIs
• Encoding and decoding produce consistent, predictable results
• Your URLs are compatible with international web standards

This tool uses the browser-native encodeURIComponent() and decodeURIComponent() JavaScript functions, which are built directly into web browsers specifically to provide RFC 3986-compliant encoding. This means the encoding behavior you see in this tool matches exactly what happens inside real browsers and web applications — giving you confidence that your encoded output will work correctly in production use.

Privacy and Data Security

This tool processes all encoding and decoding entirely within your browser using client-side JavaScript. Your text and URLs are never transmitted to, processed by, or stored on any external server.

This client-side approach matters for several practical reasons:

Privacy for sensitive data If you are encoding or decoding URLs that contain sensitive information — internal API endpoints, authentication tokens, private query parameters, or proprietary data — none of that information ever leaves your browser or touches any server.

Speed Because there is no server round-trip required, encoding and decoding happen instantly as you type or click, with no network latency.

Reliability The tool works entirely offline once the page has loaded, since all processing happens locally rather than depending on an active connection to a backend server for each conversion.

Who Should Use This URL Encoder Decoder?

Web Developers Use this tool for quick, manual encoding and decoding tasks during development — preparing query string parameters, testing how specific characters will encode, debugging URL-related issues, or building dynamic links programmatically without writing custom code for a one-off conversion.

SEO Professionals Build correctly encoded URLs for canonical tags, redirects, and internal links that contain special characters. Decode percent-encoded URLs found in Google Search Console, server logs, or analytics reports to understand exactly what search terms or referring URLs are associated with your traffic.

Digital Marketers Build UTM tracking parameters and campaign URLs that include spaces, special characters, or punctuation in campaign names. Properly encoded tracking URLs ensure your analytics correctly capture campaign performance data without broken or misread parameters.

API Developers and Integrators When constructing API requests that pass data through URL parameters, use this tool to quickly encode parameter values containing special characters, ensuring your API calls are correctly formed and the receiving server interprets your data accurately.

QA Testers When testing how applications handle URL parameters containing special characters, edge cases, or international text, use this tool to quickly generate properly encoded test URLs and verify that decoding behaves as expected within the application under test.

Students Learning Web Development Understanding URL encoding is a foundational web development concept that connects to how the entire internet’s addressing system functions. This tool provides immediate, hands-on feedback that makes the abstract concept of percent-encoding concrete and easy to understand.

Content Managers and Webmasters When troubleshooting broken links containing special characters, file names with spaces, or international content, this tool helps you quickly identify and correct encoding issues that may be causing links to fail.

Anyone Working With Exported Data or Logs If you regularly review server logs, exported analytics data, or any content containing percent-encoded URLs, this tool quickly converts that data into readable form for analysis and reporting.

Frequently Asked Questions

Q: Is this URL encoder decoder completely free? Yes — 100% free with no account required, no subscription, and no usage limits. Encode and decode as many URLs as you need.

Q: What does percent-encoding mean? Percent-encoding is the official term for URL encoding — the process of representing special or reserved characters as a percent sign (%) followed by two hexadecimal digits that correspond to the character’s value. For example, a space becomes %20 and an ampersand becomes %26.

Q: Why do spaces become %20 in URLs? URLs cannot contain literal space characters because spaces are used as delimiters in many contexts and are not part of the standard set of characters allowed directly in a URL. %20 is the percent-encoded representation of a space, based on its ASCII value (32 in decimal, which is 20 in hexadecimal).

Q: Should I use %20 or + for spaces in URLs? %20 is the universally correct percent-encoding for a space anywhere in a URL, following the RFC 3986 standard used by this tool. A + symbol is sometimes used to represent a space specifically within query strings, following an older convention from HTML form submissions, but this is context-dependent and less universally reliable. Using %20 consistently, as this tool does through encodeURIComponent(), is the safer and more broadly compatible approach.

Q: What is the difference between URL encoding and HTML encoding? URL encoding (percent-encoding) converts characters for safe inclusion in web addresses, using the %XX format. HTML encoding converts characters for safe display within HTML page content, using the &entity; format. They serve different purposes and are not interchangeable — use the correct encoding type based on whether you are working with a URL or HTML content.

Q: Is my data safe when I use this tool? Yes. All encoding and decoding happens entirely within your browser using client-side JavaScript. No text or URLs you enter are ever sent to or stored on any server, making this tool safe to use even for sensitive or private URLs and data.

Q: What is RFC 3986? RFC 3986 is the official internet standard published by the IETF that defines the syntax rules for URIs, including the precise specification for percent-encoding. This tool follows RFC 3986 to ensure that encoded URLs work correctly and consistently across all modern browsers and web servers.

Q: Why does my encoded text look different from what I expected? If you are encoding characters outside the basic ASCII range — accented letters, non-Latin characters, emoji, or special symbols — the character is first converted to its UTF-8 byte representation, and each byte is percent-encoded separately. This can result in a single character producing multiple percent-encoded sequences, which is the expected and correct behavior for proper UTF-8 to percent-encoding conversion.

Q: Can I encode an entire URL, or just parts of it? This tool is designed to encode text values — typically individual parameter values or strings you want to safely include within a URL. Encoding an entire URL including the protocol and domain (like https://example.com) is generally not recommended, since this would also encode the structural characters (like the colon and slashes) that need to remain unencoded for the URL to function. Encode only the specific values or parameters that need protection, not the full URL structure.

Q: What happens if I decode text that was not actually encoded? If you attempt to decode plain text that does not contain any percent-encoded sequences, the decode function will simply return the text unchanged, since there is nothing to convert. No errors will occur from decoding already-plain text.

Other Free SEO Tools You Might Find Useful

While you are here, explore the other free tools available on this website:

• Free HTML Encoder Decoder — convert special characters to HTML entities and decode them back
• Free Blacklist Lookup — check if your domain or IP is listed on 20+ spam and security blacklists
• Free DNS Lookup Tool — check A, AAAA, MX, TXT, NS, CNAME, and SOA records for any domain
• Free SSL Checker — verify SSL certificate validity, expiry date, and security rating
• What Is My IP Address — check your public IPv4, IPv6, ISP, and location instantly
• Free WHOIS Checker — look up domain registration, owner info, and nameservers
• Free Word Counter — count words, characters, sentences, and reading time instantly
• Free Keyword Density Checker — analyze keyword frequency and optimize your content
• Free Meta Tag Generator — create complete, optimized meta tags for any page
• Free Redirect Checker — check WWW vs non-WWW redirects and analyze redirect chains