Developer utility
URL Encoder & Decoder
Encode and decode URL components, form values, or complete URLs locally. No URL is fetched, opened, or navigated to; runtime privacy verification remains a release gate.
How to use URL Encoder & Decoder
Use component mode for a query parameter value, path segment, or other individual piece. RFC 3986 reserved characters such as &, ?, and # are encoded so they remain data. Complete URL mode preserves delimiters for an already structured URL.
Component and complete-URL modes represent spaces as %20. Form URL encoding is a separate application/x-www-form-urlencoded convention for individual values or form content: spaces become +, while a literal plus sign becomes %2B. Do not apply form mode to an arbitrary complete URL.
Line batches and normalization
Batch mode transforms each line independently, preserves line order and empty lines, and reports failing line numbers without returning a partial result. Output endings can preserve the first input style or use LF/CRLF explicitly.
hello world → hello%20worldLocal files and live preview
Import reads a selected UTF-8 text file locally. Download is explicit and uses a fixed text filename. Live preview is opt-in, debounced, bounded, and never navigates to the result. No file upload, persistence, or URL sharing is provided.
Related tools: JSON Formatter & Validator and Base64 Encoder & Decoder.
Frequently asked questions
Should I encode a whole URL or one value?
Use component mode for a single query value or path segment. Use complete URL mode only when the input is already structured and its delimiters should remain meaningful.
Why is a space shown as %20 instead of +?
+ is a form-encoding convention. This tool uses component and complete-URL semantics, so spaces are represented as %20.
What happens when one batch line is malformed?
The tool identifies the failing line and does not replace the input with a partial batch result. Correct the line or process the whole input in the default mode.
Can decoded text be opened as a URL?
No. Decoded text is displayed as data only, including text that resembles a javascript: URL.
For reference, RFC 3986 unreserved characters are letters, digits, - . _ ~; reserved delimiters include : / ? # [ ] @ ! $ & ' ( ) * + , ; =. The selected mode determines which characters remain delimiters and which become data.