What is the difference between search and searchParams?

search is the raw query string including the leading '?' (e.g. ?a=1&b=2). searchParams is a parsed URLSearchParams object that lets you get, set, and delete individual parameters without string manipulation.

How do I handle URLs with encoded slashes (%2F)?

Some servers decode %2F to / in the path (allowing encoded slashes), others treat it literally. The parser preserves %2F as-is. When constructing, encode slashes in path segments that should not be interpreted as path separators.

TASK

Parse a URL into components and construct URLs from parts

Decompose a URL into protocol, host, path, query, fragment — and build a URL from individual components safely.

1

URLs have a precise structure (RFC 3986): scheme, authority, host, port, path, query, fragment. Parsing decomposes a URL for inspection or modification; construction reassembles parts with proper encoding.
2

URL Parser →
Paste a URL. The tool decomposes it into protocol, host, port, pathname, search params, and hash, each editable for reconstruction.
3

URL Encoder →
When constructing a URL with query parameters that contain special characters, encode each parameter value here before assembling.
4

URL Decoder →
To inspect an encoded URL, decode it here — useful for understanding redirect URLs that are themselves URL-encoded as a parameter.

Frequently asked questions

What is the difference between search and searchParams?: search is the raw query string including the leading '?' (e.g. ?a=1&b=2). searchParams is a parsed URLSearchParams object that lets you get, set, and delete individual parameters without string manipulation.
How do I handle URLs with encoded slashes (%2F)?: Some servers decode %2F to / in the path (allowing encoded slashes), others treat it literally. The parser preserves %2F as-is. When constructing, encode slashes in path segments that should not be interpreted as path separators.