Component versus full URL
Component encoding escapes reserved separators inside one value. Whole-URL mode preserves structural characters that delimit the scheme, host, path, query, and fragment.
Developer Tools · Local processing
URL Encoder / Decoder
Percent-encode URL components or decode escaped URL text locally.
Standards-based
URL Encoder / Decoder
Inputs and results stay in this page and are not sent to any server.
Encoded output
The practical guide
Choose component encoding or whole-URL handling deliberately.
Percent encoding represents characters with byte escapes such as %20 so values can travel safely in specific URL positions.
Decode escaped text
The decoder reverses valid percent escapes and reports malformed sequences instead of silently returning misleading output.
Encoding does not validate a destination
A syntactically encoded URL can still be unsafe or incorrect. Review destinations before navigation and do not treat encoding as sanitization.
Privacy by architecture
Your files and tool inputs stay in your browser.
The selected files, inputs, settings, and outputs are processed in this page and are not uploaded to any server.
Questions, answered
Frequently asked questions
Should I encode an entire URL or one value?
Encode individual query or path values as components; use whole-URL handling only when you need to preserve URL separators.
Why did decoding fail?
A percent sign may not be followed by two valid hexadecimal digits, or the decoded bytes may not form valid text.
Is URL encoding encryption?
No. Encoded text is easily reversible and provides no confidentiality.
Does the tool open the URL?
No. It only transforms the text shown in the input and output.