URL Parser & Analyzer

Paste any URL to instantly parse, validate, encode/decode, and rebuild it. Edit individual components or query parameters. Everything runs in your browser -- your data stays private.

 
Enter URL
URL-decode parameter values
Parsed Components

Query Parameters

0 params
No query parameters. Parse a URL or add one below.

Rebuilt URL

Parse a URL above to see the rebuilt result here.
Build a URL from Components

Fill in the fields below to construct a URL. Only the protocol and hostname are required.

Query Parameters

0 params
No query parameters. Add one below.

Built URL

Fill in the fields above to build a URL.
URL Encoding / Decoding

Encode or decode full URLs and individual URL components. Uses standard percent-encoding (RFC 3986). For more options, see the URL Encoder/Decoder tool.

Full URL Encode / Decode

Component Encode / Decode

Use encodeURIComponent() for individual parameter values, path segments, etc.

Common URL Patterns

Click any example to load it into the parser.

REST API - List with Pagination
https://api.example.com/v2/users?page=3&per_page=25&sort=created_at&order=desc
REST API - Nested Resource
https://api.example.com/v3/repos/owner/my-repo/issues/42/comments?since=2025-01-01T00:00:00Z
URL with Authentication
https://admin:s3cr3t%40pass@internal.example.com:8443/dashboard?view=analytics#overview
Search Engine Query
https://www.google.com/search?q=url+parser+online&hl=en&safe=active&num=20&start=10
Complex Query String
https://shop.example.com/products?category=electronics&brand=apple&brand=samsung&price_min=100&price_max=999&in_stock=true&tags=new,featured&utm_source=google&utm_medium=cpc&utm_campaign=summer_sale
FTP URL
ftp://files:p%40ssw0rd@ftp.example.org:2121/public/docs/report-2025.pdf
Map / Geolocation URL
https://maps.example.com/directions?origin=40.7128,-74.0060&destination=34.0522,-118.2437&mode=driving&avoid=tolls,highways&waypoints=39.9526,-75.1652#route
OAuth Callback URL
https://app.example.com/auth/callback?code=abc123def456&state=xyz789&scope=read%3Auser%20repo&redirect_uri=https%3A%2F%2Fapp.example.com%2Fdashboard

URL Structure Reference

A URL (Uniform Resource Locator) follows a standard structure defined by RFC 3986. Understanding each component helps with debugging, API development, and web scraping.

scheme://user:pass@hostname:port/path?key=value#fragment
ComponentExampleNotes
SchemehttpsProtocol (http, https, ftp, etc.)
UsernameadminOptional authentication
PasswordsecretOptional, insecure in URLs
Hostnameexample.comDomain or IP address
Port8080Default: 80 (HTTP), 443 (HTTPS)
Path/api/usersResource location on server
Querypage=1&sort=nameKey-value pairs after ?
Fragmentsection-2Client-side anchor after #
Originhttps://example.comScheme + host + port

Related Tools

URL Encoder/Decoder

Encode and decode URL components with percent-encoding.

HTTP Request Tester

Send HTTP requests and inspect responses, headers, and status codes.

Base64 Encoder

Encode and decode Base64 strings for data transfer.

JSON Formatter

Format, validate, and minify JSON data.
Embed this tool on your site 
<iframe src="https://devtoolbox.dedyn.io/tools/url-parser" width="100%" height="700" frameborder="0"></iframe>

Frequently Asked Questions

What are the components of a URL?▼
A URL (Uniform Resource Locator) consists of several components: the scheme/protocol (e.g., https), optional username and password for authentication, the hostname (domain name or IP address), an optional port number, the path to the resource, an optional query string containing key-value parameters separated by &, and an optional fragment/hash identifier that refers to a section within the page.
How does URL query string parsing work?▼
URL query string parsing splits the portion of the URL after the ? character into individual key-value pairs. Each pair is separated by an & character, and the key is separated from the value by an = character. Values are typically URL-encoded (percent-encoded), so special characters like spaces are represented as %20 or +. Parsing involves splitting these pairs and decoding the keys and values.
What is the difference between URL encoding and URL parsing?▼
URL encoding (percent-encoding) converts special characters into a safe format using % followed by hex values, ensuring the URL is valid for transmission. URL parsing is the reverse analytical process -- it takes a complete URL string and breaks it down into its structural components (scheme, host, path, query, fragment) so each part can be inspected or modified individually.
How do I validate if a URL is correct?▼
A valid URL must have a scheme (like http or https), a valid hostname (domain name or IP address), and properly formatted components. Common issues include missing protocols, invalid characters in the hostname, malformed query strings, and unencoded special characters. Our URL parser validates all these aspects and reports any issues found.
What is the maximum length of a URL?▼
While the HTTP specification does not define a maximum URL length, most browsers support URLs up to 2,048 characters. Some servers may have lower limits. Internet Explorer historically limited URLs to 2,083 characters. For best compatibility, keep URLs under 2,000 characters. Very long URLs are often a sign that data should be sent via POST request body instead.
Is my data safe when using this URL parser?▼
Yes, absolutely. This URL parser runs 100% in your browser using JavaScript. Your URLs are never sent to any server -- everything is processed locally on your device. This makes it safe to parse URLs that contain sensitive information like API keys or authentication tokens.
Keyboard Shortcuts
Ctrl+Enter Parse URL
Ctrl+Shift+C Copy rebuilt URL
Ctrl+L Clear