Encode and decode – which mode when?
Use URL component for single values, full URL for complete addresses and form data for application/x-www-form-urlencoded.
URL Encoder / Decoder
Encode and decode URLs – percent-encoding for query parameters, path segments and form values directly in ToolkitOne.
Processing happens directly in ToolkitOne. Your input is not sent to external services.
For single values such as query parameters or path segments. Spaces become %20. Existing percent signs are encoded again – repeated encoding causes double encoding.
Understanding and using URL encoding
What is URL encoding?
URL encoding converts characters into a URL-safe representation so special characters, spaces and Unicode can be transmitted in addresses and parameters.
Why must characters in URLs be encoded?
URLs may only contain a limited character set directly. Spaces, umlauts, & or = would break URL structure or be misinterpreted.
What is percent-encoding?
Percent-encoding represents a byte as a percent sign followed by two hexadecimal characters, for example %20 for a space or %C3%A4 for ä in UTF-8.
What is the difference between %20 and +?
In URL components, %20 stands for a space. The plus sign + is often used as a space in form data (application/x-www-form-urlencoded), but it is not the same as %20.
What is the difference between a full URL and a URL component?
A full URL contains scheme, host, path and parameters. A URL component is a single value, such as a query parameter or path segment, encoded separately.
Are umlauts and emojis supported?
Yes. The tool encodes based on UTF-8 bytes and supports umlauts, ß, accents, emojis and non-Latin scripts.
What is double encoding?
When already encoded text is encoded again, existing percent signs are encoded themselves. %20 becomes %2520. The tool does not detect this automatically – check whether your input is already encoded.
Is URL encoding encryption?
No. URL encoding is not encryption. Encoded content can be decoded without a password. Sensitive data should not be sent unprotected in URLs.
Are entered URLs fetched or stored?
No. Processing happens locally in your browser. No network requests, DNS lookups or external API calls are made.
Use cases
Typical uses include preparing query parameters, building API requests, encoding search terms, transferring path segments, inspecting redirect parameters, decoding URL values from logs, checking webhook data, analysing form data and finding errors in URL parameters.
Related tools
Frequently asked questions about URL encoding
Why does + stay a plus sign in component decode mode?
In component mode, + is not a space substitute. Only in form data mode is + interpreted as a space.
Can I decode full URLs?
Yes. In full URL mode, the URL structure is preserved while encoded characters in values are decoded.
What happens with invalid encoding?
The tool shows an error message and keeps your input and selected mode.
Is my input stored?
No. Processing is local and content is not sent to external services.