Free URL Encoder & Decoder Encode or Decode URL Online
Encode special characters in any URL or decode percent-encoded strings back to plain text free, instant, no sign-up.
URL Encoder & Decoder
Follow these three steps to safely convert characters for web-compatible URI strings.
Text Input
Paste your Raw Text or Encoded URL into the input field. The tool handles special characters, symbols, and non-ASCII strings instantly.
Logic Selection
Choose to either Encode for safe URL transmission or Decode to read the original content. The transformation happens in real-time as you toggle.
Result Capture
View the Processed String in the output pane. Simply click the button to Copy to Clipboard for use in your code, browser, or API request.
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 in a URL into a safe, universally transmittable format. It replaces each unsafe character with a percent sign (%) followed by the character's two-digit hexadecimal ASCII code.
URLs can only be transmitted over the internet using the ASCII character set a limited set of 128 characters. But the real world is full of characters that fall outside this range: spaces, ampersands, equals signs, hashtags, foreign language characters, emoji, and dozens of punctuation marks that all have special functional meaning in URL syntax. Without encoding, a URL containing any of these characters would either break, be misinterpreted, or cause a server error.
URL encoding solves this universally converting every potentially problematic character into a percent-encoded sequence that any server, browser, or API in the world can transmit, receive, and decode accurately. It is one of the most foundational standards in web communication, defined in RFC 3986 and implemented consistently across every programming language and platform used in the United States today.
Every time you search on Google, submit a form, send an API request, or share a URL with special characters, URL encoding is silently running in the background ensuring your data arrives exactly as intended at the destination server.
How URL Encoding Works Real Examples You Can Verify Right Now
URL encoding follows a simple, deterministic rule: take the character, find its ASCII code, express it in hexadecimal, and prefix it with %. Here are the most common characters you will encounter with their encoded equivalents:
Notice that the space became %20 and the ampersand became %26. The ampersand is especially important in a URL query string, & is the separator between parameters. An unencoded ampersand in a query value would split the string into two separate parameters at that point, corrupting the data.
The Complete Percent Encoding Reference Table
| Character | Encoded Form | Why It Needs Encoding | Where It Appears |
|---|---|---|---|
| Space | %20 | URLs cannot contain literal spaces — breaks parsing | Search queries, file names, text values |
| & | %26 | Parameter separator in query strings splits data accidentally | Text containing "and", company names |
| = | %3D | Key-value separator in query strings corrupts parameter structure | Equations, Base64 padding characters |
| + | %2B | Used as space substitute in form data encodes to prevent ambiguity | Phone numbers, math expressions |
| # | %23 | Fragment identifier — marks anchor links, must be encoded in values | Hashtags, hex color codes in params |
| ? | %3F | Query string start marker confuses parser if in a value | Question marks in text values |
| / | %2F | Path separator must be encoded when used as data | Date values, file paths in params |
| : | %3A | Separates protocol from host must encode in values | Time values, encoded URLs as params |
| @ | %40 | Separates user info from host in URL ambiguous in values | Email addresses passed as parameters |
| % | %25 | The encoding prefix itself must be encoded to avoid ambiguity | Percentage values, discount codes |
URL Encoding vs. URL Decoding Two Sides of the Same Process
Our tool works in both directions and understanding when to use each mode is essential for any developer, marketer, or analyst working with URLs in the USA:
Plain Text → Percent Encoded
Use encoding when you need to include special characters spaces, symbols, non-ASCII characters safely inside a URL. Any time you are building a URL programmatically, constructing API query parameters, or embedding user-provided text into a link, encode it first.
Output: hello%20world%20%26%20more
Percent Encoded → Plain Text
Use decoding when you receive a percent-encoded URL and need to read it as human-readable text. Common scenarios include reading encoded query parameters from server logs, debugging API responses, interpreting encoded redirect URLs, and reading encoded form submissions.
Output: hello world & more
encodeURI vs. encodeURIComponent The Critical Difference Every Developer Must Know
JavaScript provides two built-in URL encoding functions and choosing the wrong one is one of the most common URL-related bugs in American web development. Here is the exact difference and when to use each:
encodeURI()
Encodes a complete URL it preserves all characters that have structural meaning in a URL: : / ? # [ ] @ ! $ & ' ( ) * + , ; =. Use this when you have a full URL that might contain special characters in the path or query but you want to preserve the URL structure.
→ "https://site.com/path?q=hello%20world"
// : // ? = preserved — only space encoded
encodeURIComponent()
Encodes a URL component a value that will be placed inside a URL, like a query parameter value. It encodes everything except unreserved characters: letters, digits, - . ~. Use this for individual parameter values — never for complete URLs.
→ "hello%20world%20%26%20more"
// & encoded safe as a query value
| Character | encodeURI() | encodeURIComponent() | Reason for Difference |
|---|---|---|---|
| : | Not encoded | %3A | Protocol separator structural in full URL |
| / | Not encoded | %2F | Path separator structural in full URL |
| ? | Not encoded | %3F | Query string start structural in full URL |
| & | Not encoded | %26 | Parameter separator must encode in values |
| = | Not encoded | %3D | Key-value separator — must encode in values |
| Space | %20 | %20 | Invalid in URLs always encoded by both |
Rule of thumb: Use encodeURIComponent() for parameter values. Use encodeURI() for complete URLs. Use our tool when you need to quickly encode or decode without writing any code at all.
Real-World URL Encoding Use Cases Across the USA
URL encoding comes up constantly across development, marketing, analytics, and everyday web use. Here are the most common practical scenarios where our free URL encoder makes the task instant:
Building API Query Parameters
When constructing API requests programmatically whether calling Google Maps API, Stripe, Twilio, Shopify, or any other US-based API query parameter values must be URL-encoded before being appended to the endpoint URL. An unencoded address like "123 Main St, New York" in a query parameter would break the request structure at the comma and space characters.
Decoding Google Analytics and UTM Parameters
UTM tracking parameters in marketing URLs frequently contain encoded characters campaign names with spaces, source identifiers with special characters, and content labels that include punctuation. Digital marketers and analysts use our decoder to quickly read encoded UTM strings from campaign reports, server logs, and shared tracking links without needing to write code.
Sharing URLs With Non-ASCII Characters
URLs containing accented characters, foreign language text, or emoji common on websites serving diverse American audiences must be percent-encoded for reliable transmission. A URL like café.com/menú becomes caf%C3%A9.com/men%C3%BA in percent-encoded form for guaranteed compatibility with all servers and browsers.
Constructing Redirect URLs in Email Campaigns
Email marketing platforms Mailchimp, Klaviyo, HubSpot, Constant Contact use redirect tracking URLs that contain the destination URL as an encoded query parameter. Building these redirect URLs manually requires correctly encoding the destination URL so the redirect parameter value does not contain unencoded characters that would break the redirect chain.
Debugging Broken URLs in Server Logs
Web server access logs record all incoming requests in percent-encoded form making raw log entries essentially unreadable to humans when they contain query strings. Pasting an encoded log entry into our decoder instantly converts it to plain text, revealing the actual user query, search term, or parameter value that caused a 400 or 404 error.
Form Submissions and Search Queries
When a user submits a search form on a website, the browser automatically URL-encodes the form values before appending them to the query string. Understanding this encoding is essential for developers building search functionality, form handlers, and URL-based filtering systems and our tool lets you quickly test and verify how specific input values will appear as encoded URL parameters.
URL Structure What Each Part Is and How Encoding Applies
A URL is made up of several distinct components and each one has different encoding rules. Understanding which part of a URL you are working with determines exactly how to encode it correctly:
https://www.example.com:443/products/search?q=running%20shoes&color=blue%20%26%20black#results
// ↑scheme ↑host ↑port ↑path ↑query params (encoded) ↑fragment
| URL Component | Example | Encoding Needed? | Notes |
|---|---|---|---|
| Scheme | https:// | Never | Only letters and digits — always safe |
| Host / Domain | example.com | Use Punycode for IDN | Non-ASCII domains use internationalized encoding |
| Path | /products/running%20shoes | Encode spaces & special chars | Preserve / as path separators |
| Query Key | ?search_term= | Encode if contains special chars | Keys rarely contain special characters |
| Query Value | =running%20shoes | Always encode | User input — encode everything |
| Fragment | #section-1 | Encode if contains special chars | Never sent to server browser only |
Common URL Encoding Mistakes and How to Fix Them
Double Encoding Encoding an Already-Encoded URL
The most common URL encoding mistake encoding a URL that is already percent-encoded. This turns every %20 into %2520 because the % itself gets encoded to %25. The server then receives a garbled parameter value instead of the intended string.
Fix: Always decode first to check if the string is already encoded before encoding again. Our tool shows you the result immediately so you can spot double-encoding at a glance.
Using + Instead of %20 in Path Segments
The + character represents a space only in application/x-www-form-urlencoded data HTML form submissions. In URL path segments and some API contexts, + is treated as a literal plus sign, not a space. Using + where %20 is required causes subtle bugs that are difficult to debug because the URL looks correct visually.
Fix: Use %20 for spaces in URL paths and API parameters. Reserve + only for HTML form-encoded data.
Encoding the Entire URL Instead of Just the Parameter Values
Developers who encode a complete URL including the protocol, domain, slashes, and query structure — end up with a completely broken link where https:// becomes https%3A%2F%2F. The browser cannot parse this as a valid URL and the link fails entirely.
Fix: Only encode the individual parameter values that contain special characters never encode the structural components of the URL itself.
Expert URL Encoding Tips for Developers and Marketers
Always Encode User Input Before Adding to URLs
Any string that comes from user input search queries, form fields, names, addresses must be encoded before being inserted into a URL. Failing to encode user input is not just a data corruption issue it is a security vulnerability. Unencoded user input in URLs can enable open redirect attacks, cross-site scripting (XSS) via URL injection, and log injection attacks. In professional development environments, encoding user input before URL insertion is a non-negotiable security practice.
Use URL Encoding for UTM Campaign Parameters
UTM parameters in marketing tracking URLs frequently contain spaces and special characters in campaign names "Summer Sale 2025," "Q3 Email & Social," or "Brand|Awareness|US." Any of these unencoded would break the query string. Always encode UTM parameter values before appending them to landing page URLs. Google Analytics and most US marketing platforms accept and decode encoded UTM values correctly — the tracking works identically either way.
Understand That Encoded and Decoded URLs Are SEO Equivalent
Google and other search engines treat percent-encoded URLs and their decoded equivalents as the same resource. A URL with %20 and the same URL with a literal space (when used appropriately) are canonically identical to Google. However, as a best practice, use hyphens instead of spaces in all URL slugs /running-shoes rather than /running%20shoes — as hyphens are more readable, more shareable, and consistently preferred by Google's URL guidelines.
Test Your Encoded URLs in a Browser Before Deployment
The most reliable final check for any manually constructed URL is to paste it into a browser address bar and verify it resolves to the correct destination with the correct parameters. Modern browsers display the decoded version of the URL in the address bar while transmitting the encoded version to the server so if the address bar shows what you intended, the server is receiving the correctly encoded request. Our tool lets you encode, preview, and verify in seconds before building anything into production.
Common Questions
Everything you need to know about URL Encoding and Decoding.
What is URL encoding and why is it necessary?
How do I encode a URL using this tool?
%20. This ensures your URL parameters remain intact when sent through web browsers or APIs.
How do I decode an encoded URL online?
%3F back into a question mark (?) or %3D back into an equals sign (=). This makes the URL human-readable and helps developers debug complex tracking links or API queries.
What characters are typically encoded in a URL?
+ or %20, and "reserved" characters like /, :, and & when they are used as part of data rather than as URL delimiters.
Can I encode multiple lines of text at once?
Is this online URL encoder free and secure?
Coding & Formatting Utilities
JSON Formatter
Fix and beautify cluttered JSON strings effortlessly. Our free tool adds neat indentation and clear structuring so you can read and debug data easily.
Markdown Editor
Write, edit, and preview your markdown text live. A completely free tool that turns plain text into clean, ready-to-use HTML code without any fuss.
CSS Minifier
Compress and optimize your style sheets instantly. Easily strip out extra spacing and unused formatting to maximize site speeds completely free.