Search query
hello worldhello%20world
URL Encode
Percent-encode reserved characters so query strings, filenames, and API parameters survive transit through URLs intact.
URL Encode
Percent-encoding applied instantly as you type.
Text to encode for URLs
URL-safe encoded string
Input: 0
Output: 0
Encoded: 0
Spaces: 0
Unicode: 0
Query preview: ?q=
URL encoding happens locally in your browser.
How to Use
- Paste the string you plan to place in a URL query parameter or path segment.
- Review live encoded output — reserved characters become
%XXsequences. - Toggle Encode spaces as + when building
application/x-www-form-urlencodedform data. - Copy the result or use the query preview, then pair with URL Decode to reverse encoded strings.
Before and After Examples
Symbols
a=1&b=2a%3D1%26b%3D2
Unicode
cafécaf%C3%A9
URL parameter
name=John Smithname%3DJohn%20Smith
Emoji
Hello 😊Hello%20%F0%9F%98%8A
Path segment
My Folder/File.txtMy%20Folder%2FFile.txt
How URL Encoding Works
Reserved characters
Characters like ?, &, =, /, and # may need encoding.
Spaces
Usually become %20.
Unicode
UTF-8 characters are encoded into byte sequences.
Safe characters
Letters and digits normally remain unchanged.
Query parameters
Encoding prevents broken URLs.
Common Uses
Search URLs
API parameters
UTM tags
REST debugging
Download filenames
Mailto links
Query strings
OAuth redirects
%20 vs +
%20
Standard URL encoding.
+
Used mainly by HTML form encoding.
hello worldhello%20world
or
hello worldhello+world
%20 is preferred for most URLs.
URL Components
Query string
?name=John Smith
Path segment
/products/My Folder
Fragment
#section
Mailto
subject=Hello World
API parameter
city=New York
UTM parameter
utm_campaign=summer sale
Popular Workflows
Real-World Examples
Search URL
hello worldhello%20world
UTM campaign
summer salesummer%20sale
API request
New YorkNew%20York
Email subject
Hello TeamHello%20Team
Filename
Report 2026.pdfReport%202026.pdf
Notes & Limitations
- Uses
encodeURIComponentsemantics. - Entire URLs normally should not be encoded.
- Intended for query values and path segments.
- UTF-8 characters are supported.
- Processing happens locally in your browser.
Frequently Asked Questions
Does encoding change letters A-Z?
Unreserved ASCII letters and digits usually stay unchanged. Spaces, symbols, and non-ASCII characters are encoded.
What is %20?
%20 is the percent-encoded form of a space character in URLs. It is the standard encoding for spaces in query strings and path segments.
What is the difference between %20 and +?
%20 is standard percent-encoding for spaces in most URLs. + is common in HTML form submissions (application/x-www-form-urlencoded). Enable the + option in this tool when you need form-style encoding.
Should I encode an entire URL?
Usually no. Encode individual parameter values or path segments — not the full URL structure including https://, ?, or &.
How are Unicode characters handled?
Non-ASCII characters are converted to UTF-8 byte sequences, each shown as a %XX group. For example, é becomes %C3%A9.
Are emoji supported?
Yes. Emoji encode as UTF-8 byte sequences. For example, 😊 in Hello 😊 becomes %F0%9F%98%8A.
When should I URL encode text?
Use URL encoding when placing user-supplied text in query parameters, redirect URLs, mailto links, API calls, or filenames where reserved characters would break the URL.
Does this upload my text?
No. URL encoding runs entirely in your browser — nothing is sent to a server.
Can I download the result?
Yes. Use Download .txt to save the encoded string as a plain-text file.
How is URL encoding different from Base64?
URL encoding escapes reserved URL characters as %XX so text stays readable in links. Base64 converts data into a different alphabet for transport — use each for its intended format.