Parses native absolute URLs including HTTP(S), FTP, file, mailto, data and custom schemes. Relative URLs require a base and are rejected here. Native handling of whitespace, IDNA, numeric hosts, dot segments and default ports is retained. Syntax parsing does not establish safety or reachability. Browser textarea normalization can change line endings before the engine receives the string.
Limits: 32,768 input UTF-16 units; 1,000 ordered query pairs; 300,000 JSON output units including final LF. Raw unsupported controls and malformed UTF-16 reject. Native components retain encoding; query pairs separately use form decoding, preserve duplicates/empty names and may contain control or replacement characters represented safely as JSON. A replacement character does not prove invalid UTF-8. Query pairs are not reserialized into href; byte-exact round trips are not promised.
Runs locally with bounded native URL operations. No navigation, fetching, DNS resolution or storage.
Result
Your result starts here
Review the input and selected options, then use the primary action. Output and any validation messages will appear here.
METHOD & CONTEXT
Understand the result before using it.
How it works
Parses one absolute URL without a base, extracts native fields and ordered query pairs, then checks prospective pretty-JSON size before serialization.
Interpretation
Read the result summary first, then inspect the detailed output and any errors or warnings. The result describes the supplied input and selected options. Changing input requires another run.
Assumptions & warnings
Supports hierarchical and opaque native schemes. Native encoding and form-decoded pairs differ; syntax is not a safety or reachability check. Output is text only.
Inputs are processed in your browser. Follow the input format and size limits shown next to the controls.
Try an example
Select Load example in the input panel, review the selected mode, then use its displayed primary action. Inspect the result before replacing the sample with your own input.