URL Encoder/Decoder
Encode and decode URL strings instantly. Convert plain text to URL-safe format or decode URL-encoded strings. Parse query parameters and encode individual components. Fast, secure, and works entirely in your browser.
All encoding and decoding happens in your browser. Your data is never sent to any server.
Embed This Tool
Add this tool to your website with customizable styling
How to Use
- 1
Choose your mode
Click "Encode" to convert plain text to URL-safe format, or "Decode" to convert URL-encoded strings back to readable text. The tool starts in Encode mode by default.
- 2
Enter your text or URL
Paste or type your text in the input area. For encoding, enter any text, URL, or query parameters. For decoding, paste a URL-encoded string (text with %20, %2F, etc.).
- 3
See instant results
The conversion happens automatically as you type. The output appears in the right panel (or below on mobile) in real-time. Special characters are converted to percent-encoded format (e.g., space becomes %20).
- 4
View query parameters
If your input contains query parameters (e.g., ?name=value&key=data), the tool automatically parses them and displays a table with each parameter. You can copy individual parameters or their encoded values.
- 5
Copy the result
Click the "Copy" button to copy the converted text to your clipboard. For query parameters, use the copy buttons in the table to copy individual values.
Frequently Asked Questions
What is URL encoding and when should I use it?
URL encoding (also called percent-encoding) converts special characters into a format that can be safely transmitted over the internet. URLs can only contain certain characters (A-Z, a-z, 0-9, and a few symbols like - _ . ~). All other characters must be encoded. Use URL encoding when: building URLs with query parameters (e.g., search queries), sending data in GET requests, encoding file names in URLs, or working with APIs that expect URL-encoded data. For example, a space becomes %20, and a forward slash (/) becomes %2F.
What's the difference between URL encoding and Base64 encoding?
URL encoding and Base64 encoding serve different purposes. URL encoding makes text safe for URLs by converting special characters to %XX format (e.g., space → %20). It's designed specifically for URLs and query parameters. Base64 encoding converts binary data to ASCII text using A-Z, a-z, 0-9, +, and /. It's used for embedding binary data in text formats like JSON or HTML. Use URL encoding for URLs and query strings. Use Base64 for binary data transmission or embedding images in HTML/CSS.
How do I encode query parameters correctly?
Query parameters are the key-value pairs after the ? in a URL (e.g., ?name=John&age=30). To encode them correctly: Encode values only, not the structure characters (?, =, &). For example, ?search=hello world should become ?search=hello%20world (space encoded, but ? and = stay). Encode both keys and values if they contain special characters. The tool's query parameter table helps you see each parameter separately and copy encoded values individually. Common characters to encode: space (%20), & (%26), = (%3D), ? (%3F), / (%2F), # (%23).
Why am I getting an "Invalid URL-encoded string" error?
This error occurs when the input isn't valid URL-encoded text. Common causes include: Incomplete percent-encoding (e.g., %2 without the second digit - should be %20), Invalid hexadecimal digits (e.g., %ZZ - only 0-9 and A-F are valid), Malformed encoding from copy-paste errors. To fix: check that all % signs are followed by exactly two hexadecimal digits, remove any extra characters, or try encoding the text first if you're not sure it's already encoded. The tool shows helpful hints about common URL-encoded characters to help you identify issues.