Encode
Plain text → URL encoded
Encoded Output
Encoded output will appear here.
URL Encode / Decode
Encode URL-unsafe characters or decode percent-encoded text locally in your browser.
URL Encode / Decode
Convert URL-unsafe text into percent-encoded data or restore encoded content to readable text.
Enter text in either panel to get started.
Decode
URL encoded → plain text
Decoded Output
Decoded output will appear here.
Common Encoding Examples
Hello WorldEncodedHello%20World10 < 20 & 30 > 25Encoded10%20%3C%2020%20%26%2030%20%3E%2025https://example.comEncodedhttps%3A%2F%2Fexample.comname=John Doe&age=25Encodedname%3DJohn%20Doe%26age%3D25hello@example.comEncodedhello%40example.com100% Free
Encode and decode URLs without any limitations.
Instant Results
Real-time encoding and decoding as you type.
Developer Friendly
Perfect for developers, testers, and DevOps.
Secure & Private
All processing happens in your browser. No data stored.
Works Everywhere
Compatible with all devices and modern browsers.
Practical guide
Using URL Encode / Decode with confidence
Reviewed by LipiCode Editorial Team
What this tool helps you do
URL encoding replaces characters that have structural or unsafe meanings with percent-encoded bytes. Different URL components have different rules, so encoding a path segment is not identical to encoding an entire query string.
When it is useful
- Preparing a query parameter value
- Reading percent-encoded text
- Debugging redirect URLs
- Safely carrying spaces or Unicode in a URL component
A practical example
Encode a user-entered search term as one query-parameter value, then let the application build the surrounding key, equals sign, and ampersands. Do not encode the completed URL blindly.
Limitations and common mistakes
Double encoding turns an existing percent sign into %25 and changes the value. Plus signs can mean spaces in form-style query strings but literal plus signs elsewhere. Encoding does not validate a destination URL.
Frequently asked questions
Why does a space appear as %20 or +?
Percent-encoding commonly uses %20; form-encoded query data may use plus.
Should I encode the whole URL?
Usually encode individual parameter or path values with an API appropriate to that component.