URL Encoder/Decoder
Paste text or URL strings to encode/decode instantly, with optional safe-character mode.
Tip: for query strings, enable the "+ as space" option to match form-style decoding.
- Enter content in the "Plain Text" field (such as CJK text, emoji, or query parameters).
- Click "Encode" to convert it to a URL-safe percent-encoded string.
- Or paste an encoded URL in the other field and click "Decode" to restore the original text.
- Use "Encoding Mode" to switch between full encoding and common URL-safe character preserving mode.
Tip:When handling query strings, enable "Treat + as space on decode" to match common form parsing behavior.
When would you use this?
- Embedding Chinese or special characters in a URL query parameter.
- Decoding a percent-encoded URL you received into readable text.
- Verifying how + signs and spaces are parsed in form submissions.
Why does a URL need encoding?
URLs allow only a specific subset of ASCII characters. Chinese, Japanese, emoji, and special characters like & must be converted to percent-encoding (e.g. %E4%B8%AD) for safe transmission, preventing parsing errors on servers and browsers.
What is the difference between Full Encoding and Safe-Characters mode?
Full encoding (encodeURIComponent) encodes almost all non-alphanumeric characters and is best for query parameter values. Safe-characters mode preserves common URL-safe characters like -, _, ., and ! to avoid over-encoding, which is better for general path strings.
What is the difference between + and %20?
In URL query strings, spaces can be represented as %20 (RFC 3986) or + (application/x-www-form-urlencoded). Enable "Decode + as space" to match form submission behavior; disable it to follow RFC 3986, where + is kept as a literal character.
How do I handle incomplete percent-encoding?
If your input contains an incomplete % sequence (e.g. a bare %), the tool will report a format error. Ensure every % is followed by exactly two hexadecimal digits, such as %20 or %E4%B8%AD.
URL Too Long? How to Shorten It with Free Tools
Long URLs are hard to read, ugly in layouts, and easy to break in chats. This guide covers free URL shortener options, selection criteria, and practical safety tips.
Base64 Guide: How It Works, When to Use It, and Common Pitfalls
Base64 appears in APIs, JWTs, emails, and data URLs, but it is not encryption. This practical guide explains the mechanics, trade-offs, and real-world usage patterns you should know.
The Complete QR Code Guide: From How It Works to Scanning Safely
What engineering hides inside those black-and-white squares? Is scanning always safe? This guide covers QR Code structure, error correction, data types, creation best practices, and the security risks you should know.
JSON Complete Guide: From Data Structures to Practical API Design
JSON is the common language of modern web services. This guide covers syntax, data modeling, validation, security, and performance patterns for production-ready JSON workflows.
URL Encoding Guide: Percent-Encoding, Pitfalls, and Practical Patterns
URL encoding looks simple, but it often causes broken parameters, double-encoding bugs, and subtle security issues. This guide explains percent-encoding rules, encodeURI vs encodeURIComponent, and reliable API workflows.