Encoder/Decoder URL
Konversi karakter khusus dalam string ke versi URL-safe atau decode teks percent-encoded kembali ke bentuk aslinya.
Input
Result
Processed Output
Cara Menggunakan Encoder/Decoder URL Ini
- Paste or type your text or URL into the input field.
- Select whether you want to encode or decode the input.
- The result is generated instantly as you type.
- Copy the encoded or decoded output using the copy button.
About URL Encoding & Decoding
URL encoding (percent-encoding) is essential for including characters in a URI that have special meaning or are otherwise restricted. This tool handles the standard RFC 3986 encoding for URI components.
Privacy Note
Privacy first: all processing happens locally in your browser. No data is transmitted to our servers.
Key Features
- Encodes special characters to percent-encoded format (e.g., space becomes %20)
- Decodes percent-encoded strings back to readable text
- Follows RFC 3986 standard for URI component encoding
- Handles Unicode characters and multi-byte sequences
- Real-time encoding and decoding as you type
- Preserves unreserved characters (letters, digits, -, _, ., ~)
- Client-side processing for complete data privacy
Common Use Cases
- Encoding query parameters for API requests
- Decoding URLs from server logs or analytics tools
- Preparing data for form submissions with special characters
- Building redirect URLs with encoded parameters
- Debugging encoded URLs in web application traffic
- Encoding file paths containing spaces or special characters
Pertanyaan yang Sering Diajukan
What is the difference between encodeURI and encodeURIComponent?
encodeURI encodes a full URI but preserves characters like :, /, ?, and # that have special meaning in URLs. encodeURIComponent encodes everything except unreserved characters, making it suitable for encoding individual query parameter values.
Why do spaces sometimes become + and sometimes %20?
The + sign for spaces comes from the older application/x-www-form-urlencoded format used in HTML forms. The %20 encoding follows the RFC 3986 standard for URIs. Both represent a space, but %20 is the more universally correct encoding for URLs.
Which characters need to be URL encoded?
Characters that must be encoded include spaces, quotes, angle brackets, curly braces, pipes, backslashes, and any non-ASCII characters. Reserved characters like &, =, ?, and # should be encoded when used as data rather than as URL delimiters.