URL Encoder - Percent-Encode Text for URLs
Quick Tips
- • This tool runs entirely in your browser - your data stays private.
- • Press Ctrl+V (Cmd+V on Mac) to quickly paste text.
- • Use the Copy button to save your result to clipboard.
- • Bookmark this page for quick access!
Convert text to URL-safe percent-encoded format.
Your Recent Tools
Examples
Hello World
Hello%20World
name=John Doe&city=New York
name%3DJohn%20Doe%26city%3DNew%20York
price: $50 (50% off!)
price%3A%20%2450%20(50%25%20off!)
cafe resume
caf%C3%A9%20r%C3%A9sum%C3%A9
Why Use This Tool?
What problems does this solve?
URLs cannot contain certain characters directly and require percent-encoding. Manually encoding special characters is error-prone and time-consuming.
Common use cases:
- Encoding query parameters with special characters for URLs
- Preparing text for use in GET requests
- Encoding file names and paths for web use
Who benefits from this tool?
Web developers building URLs programmatically. API consumers preparing request parameters. SEO specialists working with URL structures. Anyone creating links with special characters.
Privacy first: All processing happens in your browser. Your URL data never leaves your device.
Frequently Asked Questions
Both represent spaces in URLs. %20 is the standard percent-encoding, while + is used specifically in application/x-www-form-urlencoded format (HTML forms). Modern practice prefers %20 for broader compatibility.
Encode only the data values, not the URL structure. The protocol (https://), domain, path separators (/), and parameter separators (&, =, ?) should remain unencoded. Only encode the actual parameter values.
RFC 3986 defines "unreserved characters" that are safe in URLs: A-Z, a-z, 0-9, hyphen (-), underscore (_), period (.), and tilde (~). These do not require encoding.
Double encoding happens when you encode already-encoded text, turning %20 into %2520. This breaks URLs because servers decode only once. Always encode raw data, not already-encoded strings.
Encode the entire URL value, including its special characters. For example, https://example.com/?q=test becomes https%3A%2F%2Fexample.com%2F%3Fq%3Dtest when used as a parameter value.
Yes, all encoding happens locally in your browser using JavaScript. Your text is never sent to any server, ensuring complete privacy.
Related Tools
String Utilities
<p>String Utilities is your comprehensive toolkit for perfor...
HTML Entity Decoder
<p>Our HTML Decode tool converts HTML entities back to their...
NATO Phonetic Alphabet
<p>Our NATO Phonetic Alphabet Converter transforms regular t...
Pig Latin Converter
<p>Our Pig Latin Converter transforms English text into Pig...
Backwards Words
<p>Our Backwards Words tool reverses text in multiple ways:...
Phonetic Spelling Generator
<p>Our Phonetic Spelling tool converts words into their pron...
Related Articles
URL Encoding Explained: When and Why You Need It
Learn what URL encoding is, why it matters, and how to encode and decode URLs properly.
Read moreBase64 Encoding vs Encryption: Understanding the Difference
Learn the crucial difference between Base64 encoding and encryption, and when to use each.
Read moreHTML Encoding: Preventing XSS and Display Issues
Learn how HTML encoding works and why it is essential for web security and proper display.
Read more