URL Encode / Decode
Percent-encode text for URLs
Component encodes everything except a-z A-Z 0-9 - _ . ! ~ * ' ( ) — use for query values and path segments.
Result will appear here
What Is the URL Encode / Decode?
The URL Encoder / Decoder percent-encodes text so it is safe to use in URLs, query strings, and form data — and decodes it back to readable text. It supports both component encoding and full-URI encoding, runs entirely in your browser, and handles any character set, making it a reliable everyday tool for developers and API users.
Key Features
What Is URL Encoding?
URLs can only contain a limited set of characters, so anything else — spaces, ampersands, non-Latin letters, and reserved symbols — must be percent-encoded into a %XX form. This keeps query parameters and paths from breaking. Decoding reverses the process so you can read what an encoded URL actually contains.
Component vs Full-URI Encoding
There are two modes. Component encoding escapes everything that is not safe inside a single query value, including & and =, and is what you want for individual parameters. Full-URI encoding preserves the characters that make up a valid URL structure. Choosing the right mode prevents both broken links and double-encoding bugs.
Common Use Cases
- Encoding query parameters for an API request
- Decoding a URL to read its real parameters
- Safely passing special characters in links
- Debugging double-encoded or malformed URLs
Frequently Asked Questions
What is percent encoding?
Percent encoding (URL encoding) replaces unsafe characters with a percent sign followed by two hex digits, such as %20 for a space. It lets URLs carry characters that would otherwise be invalid or have special meaning.
When should I use component vs full-URI encoding?
Use component encoding for individual query values, since it escapes reserved characters like & and =. Use full-URI encoding when you want to encode a whole URL while preserving its structural characters.
Does it handle Unicode characters?
Yes. The tool fully supports Unicode, so non-Latin scripts and emoji are encoded into the correct percent-encoded UTF-8 sequences and decoded back accurately.
Why is my URL double-encoded?
Double encoding happens when already-encoded text is encoded again, turning % into %25. Decode once to check, and make sure you only encode raw text, not values that are already encoded.
Is the tool private?
Yes. All encoding and decoding runs locally in your browser, so nothing you enter is sent to a server.
Need more developer utilities?
Explore all tools