URL Encoder Decoder Tool - Free Online URL Encoding (Supports full encoding, structure-preserving encoding, no registration)
Quickly encode or decode URLs with multiple modes including full encoding and structure-preserving encoding. Encoded URLs can be passed as parameters or accessed directly in browsers.
Fully encode entire URL, suitable for parameter passing
Enter URL
Encoded/Decoded Result
FAQ
What's the difference between the three URL encoding modes?
Full encoding mode: Encodes the entire URL completely, suitable for passing as parameters to other pages or API interfaces. Structure-preserving encoding (%20): Preserves URL structure (protocol, domain, path, etc.), only encodes special characters, spaces become %20, encoded URLs can be accessed directly in browsers. Structure-preserving encoding (+): Also preserves URL structure, but spaces become +, also supports direct browser access.
When to use full encoding?
Use full encoding mode when you need to pass the entire URL as a parameter to other pages or API interfaces. This ensures all special characters in the URL are correctly encoded, avoiding parameter parsing errors.
When to use structure-preserving encoding?
Use structure-preserving encoding when you need to encode query parameters or path parts of a URL, but want to preserve the basic URL structure (protocol, domain, etc.). Encoded URLs can still be opened directly in browsers.
Why must plus signs (+) in parameter values be encoded as %2B?
In URL query parameters, plus signs are automatically interpreted as spaces by servers. If you need to pass an actual plus sign character, you must encode it as %2B, otherwise the server will misinterpret it as a space, causing incorrect parameter values.
How are inputs that don't start with 'http' handled?
If the input doesn't start with 'http', the tool automatically recognizes it as query parameter content and processes it according to query parameter encoding rules. For example, input like 'key=value' will be treated as query parameters for encoding.
What's the difference between Structure-Preserving (%20) and Structure-Preserving (+) encoding?
The main difference is how spaces are handled in query parameters. Structure-Preserving (%20): Spaces in both parameter names and values are encoded as %20, plus signs remain unchanged. Structure-Preserving (+): Spaces in parameter names are encoded as + (recommended), plus signs in parameter values must be encoded as %2B to avoid being misinterpreted as spaces by servers.
Can encoded URLs be used directly in browsers?
URLs encoded with Structure-Preserving (%20) and Structure-Preserving (+) modes can be used directly in browser address bars, as the basic URL structure (protocol, domain, path separators, etc.) is preserved. URLs encoded with Full Encoding mode are typically used as parameter values and are not suitable for direct browser access.
Does the tool support encoding Chinese characters and special characters?
Yes, the tool fully supports encoding Chinese characters, Emoji, and other Unicode characters. All special characters are correctly encoded into URL-safe formats, ensuring proper transmission and parsing across different systems and browsers.
How much longer will the encoded URL be?
Encoded URLs will be longer, depending on the number of special characters. Each Chinese character typically adds about 9 characters (encoded as %XX%XX%XX format), each space adds 2 characters (encoded as %20), and other special characters will increase accordingly.
Does the tool save my data?
No. All encoding and decoding operations are performed locally in your browser. Data is not uploaded to servers and is not saved. You can use it with confidence, protecting your privacy and security.