URL Encoder, Decoder & Inspector
Encode text for a URL, decode percent escapes, or inspect a link’s parts and query parameters. Everything runs locally; your URL is never visited.
Component encoding escapes URL separators such as &, =, / and #. Encode each query value separately before assembling a URL.
Enter content or load an example.
Input
Result
Input limit: 50,000 characters for encoding/decoding; 10,000 for inspection.
URL breakdown
Browser parsing normalizes the URL, including host spelling, default ports and relative paths. Encoded path and fragment are shown as parsed. The JSON report contains every query row in order.
Query parameters
| # | Decoded name | Decoded value | Raw field | Notes |
|---|
The table shortens cells over 250 characters; the JSON export contains complete values. Query parsing treats + as a space, retains repeated keys and distinguishes flag from flag= using hasEquals.
Using URL Encoder, Decoder & Inspector
Prepare URL values, read percent-encoded text or inspect how a browser parses a link. All processing happens locally without visiting the destination.
- Choose Encode or Decode and select Component, Whole URL or Form value. Use Component for one query value or path segment; use Whole URL when separators should keep their meaning.
- Paste content and run the operation. Copy or download the result. Use result as input switches to the reverse operation without running it automatically.
- For inspection, choose Inspect URL and enter an HTTP/HTTPS URL. Relative references need a complete base URL. Read the normalized breakdown, raw query fields, duplicate parameter rows and any parsing notes, then export the complete JSON report.
Example
Component input: tea & coffee Encoded: tea%20%26%20coffee For a query value, this keeps & inside the value instead of turning it into a parameter separator.
Questions & answers
When should I use component encoding?
Use it for one query value or one path segment. It escapes separators such as &, =, / and # so they stay inside that value. It uses JavaScript encodeURIComponent and leaves its standard unescaped punctuation unchanged.
How is whole-URL mode different?
It uses encodeURI/decodeURI, preserving reserved separators so the URL structure remains intact. Whole-URL decoding keeps reserved escapes such as %26 and %2F. This operation is not URL validation and should not be used to assemble unescaped query values.
Does + mean a space?
In form-value mode and query-parameter inspection, yes. Component mode keeps a literal + when decoding. Component/form encoding turns a literal plus into %2B. Form encoding uses + for a space; component encoding uses %20.
Why does decoding fail on some inputs?
The decoder rejects incomplete percent escapes and invalid UTF-8 byte sequences. It processes one layer only: %2520 becomes %20. Encoding already-encoded text can encode its percent signs again.
Are duplicate parameters and empty values preserved?
The inspector keeps parameter order and repeated names as separate rows. It records whether a field contains =, distinguishing flag from flag=. Blank names are kept; empty fields between & separators are skipped by browser query parsing.
Why does the inspected URL look different?
Browser URL parsing can lowercase hosts, serialize international hostnames, remove default ports, resolve relative references and normalize paths. The report shows the normalized URL. Query rows retain the parsed raw fields alongside decoded names and values, with notes for malformed sequences.
Can I inspect a relative path?
Yes. Supply a complete HTTP/HTTPS base URL. Relative paths, fragments and query-only references resolve against it. Without a base, the inspector requires an absolute HTTP/HTTPS URL. Other schemes are not supported by inspection.
Are my URLs visited, saved or uploaded?
No. Processing remains local, and inspection never fetches or opens the link. Inputs and outputs are not saved. Encoding/decoding accepts up to 50,000 UTF-16 units; inspection and its base accept up to 10,000 each, with at most 500 query rows. Downloaded results contain your content, including embedded credentials if present.
Related tools
A useful next step for your task.
Passwords & GeneratorsQR Code GeneratorCreate QR codes locally for website links, text and Wi-Fi. Preview your code, choose clear image settings and download PNG or SVG. Includes how-to…
Developer & DataJSON Formatter & ValidatorInstantly format, minify, and validate your JSON code. Features include live preview, syntax highlighting, tree viewer, and structure stats.
Developer & DataCSV to JSON & JSON to CSV ConverterConvert CSV and JSON locally with delimiter controls, exact number handling, table previews, clear errors and file exports. Includes examples and…
Developer & DataCSS Minifier & BeautifierMinify, beautify and check CSS syntax locally with parser-based processing, license comment controls, accurate rule statistics and CSS exports.
Help improve this tool
Report a problem or suggest an improvement
Describe the issue without pasting private tool input. Feedback goes to our admin inbox.