Every page, image, video, and downloadable file you open on the web needs a way to be located. That location is usually represented by a URL—the string you see in your browser’s address bar.
If you have ever copied a web address, clicked a link, bookmarked a page, or shared an article, you have already used URLs countless times.
A URL, short for Uniform Resource Locator, is an address that identifies where a resource can be found and how it should be accessed. On the web, URLs commonly point to pages, images, videos, documents, and other resources. A typical URL contains a scheme such as HTTPS, a domain name, and sometimes a path, query parameters, or fragment.
Understanding URLs is useful even if you never plan to build a website. It can help you navigate the web, recognize suspicious links, troubleshoot broken pages, and understand how websites organize their content.
What Is a URL and What Does URL Stand For?
URL stands for Uniform Resource Locator.
In simple terms, a URL tells software such as a web browser where a particular resource is located and provides information needed to access it.
For example:
This address could tell your browser to use HTTPS to connect to the server associated with www.example.com and request the resource located at /guides/what-is-a-url.
Mozilla describes a URL as the address of a unique resource on the internet and notes that browsers use URLs to retrieve resources such as HTML pages, CSS files, and images.
URLs are not limited to ordinary webpages. They can reference resources such as:
- HTML documents
- Images
- Videos
- PDF files
- CSS and JavaScript files
- Downloadable files
- API endpoints
- Specific sections of documents
- Other network resources
A useful everyday analogy is a postal address. A postal address helps a delivery service locate a destination; a URL helps software locate and access a digital resource.
Is a URL the Same as a Web Address?
In everyday conversation, URL and web address usually mean essentially the same thing.
When someone asks you for the URL of a page, they normally want the address shown in or copied from the browser’s address bar.
For example:
is both a URL and what most people would call a web address.
Technically, URLs are more structured than the phrase “web address” suggests. They can contain several components that tell a browser not only which website to contact but also which resource, parameters, or section is required.
What Are the Main Parts of a URL?
A URL may look like one long string, but it is made from several components.
Consider this example:
It can be divided into:
| URL Part | Example | Purpose |
|---|---|---|
| Scheme | https | Defines how the resource is accessed |
| Host | www.example.com | Identifies the server or host |
| Port | 443 | Identifies a network port |
| Path | /products/shoes | Identifies a resource or location |
| Query | ?color=black&size=10 | Supplies additional data or parameters |
| Fragment | #reviews | Points to a particular section |
The current URL Standard represents URLs using components including the scheme, username, password, host, port, path, query, and fragment. Not every URL needs every component.
1. Scheme or Protocol
The first portion tells the browser what scheme should be used.
For example:
Here, https is the scheme.
For websites, the schemes you encounter most often are:
http://
and
https://
HTTPS is the secure form commonly used by modern websites. Other schemes also exist. For example, mailto: can be used for an email-related link, while file: can refer to local files in appropriate environments.
Although people often call https the “protocol” portion of a URL, scheme is the more precise technical term.
2. Host and Domain Name
Consider:
The host is www.example.com.
For ordinary websites, the host usually contains a domain name. A domain gives people a readable way to identify a website rather than requiring them to remember a numerical IP address.
A domain can itself have several pieces.
In:
www.example.com
www is a subdomain, example is the registered-name portion, and .com is the top-level domain.
Other familiar top-level domains include .org, .net, .edu, and country-code domains such as .uk or .pk.
A host can also be represented by an IP address rather than a domain name. The URL Standard recognizes hosts including domains, IPv4 addresses, and IPv6 addresses.
3. Port
You may occasionally encounter a URL such as:
Here, 8443 is the port.
Ports identify a particular network service or endpoint on a host.
Most everyday web URLs do not visibly include a port because standard ports can be implied. MDN notes that port 80 is conventionally associated with HTTP and port 443 with HTTPS.
So a normal URL such as:
does not need to display :443.
4. Path
Look at:
The path is:
/blog/url-guide
It identifies a location or resource within the scope of the host.
Paths often make website organization easy to understand. A website might use:
/blog/
for articles,
/products/
for products, and
/support/
for help documentation.
Historically, URL paths often corresponded closely to physical files and directories on a web server. Modern websites frequently generate pages dynamically, so the visible path does not necessarily represent an actual folder or file stored on the server.
5. Query String and Parameters
A question mark can introduce a URL’s query component.
For example:
The query is:
q=shoes
More than one value can commonly be passed:
Here, the ampersand separates parameters.
Web applications can use query parameters for operations such as searching, filtering, sorting, tracking, or determining which information to display. Exactly how parameters are interpreted depends on the application handling the request.
6. Fragment or Anchor
A fragment begins with #.
For example:
The fragment is:
security
Fragments are commonly used to take a visitor directly to a particular section of a webpage rather than simply opening the top of the document.
An important technical distinction is that the fragment is handled by the client, such as the browser, and is not sent to the server as part of the resource request.
Quick Takeaway: A typical web URL can be understood as scheme + host + path + optional query + optional fragment. Ports and other components may also appear when required.
How Does a URL Work?
Knowing what is a url becomes much easier when you understand what happens after you use one.
Suppose you enter:
into your browser.
A simplified version of the process looks like this:
- The browser parses the URL. It identifies components such as the HTTPS scheme, host, and path.
- The host must be located. For a domain-based web address, the networking process ultimately determines the appropriate server address.
- A connection is established. With an HTTPS URL, the browser communicates securely with the relevant server.
- The resource is requested. The path and relevant query information tell the server what the browser is requesting.
- The server responds. It may return HTML, an image, JSON data, a redirect, an error, or another response.
- The browser processes the result. For a webpage, it typically renders the returned content for you.
This happens quickly enough that most people simply experience it as “opening a link.”
URLs therefore serve as a bridge between human-readable navigation and the underlying mechanisms computers use to find and request resources.
Absolute URLs vs. Relative URLs
Not every link needs to contain a complete web address.
Two concepts frequently encountered in web development are absolute URLs and relative URLs.
Absolute URL
An absolute URL contains enough information to identify a resource independently.
For example:
https://example.com/images/logo.png
It includes the scheme and host as well as the resource path.
Absolute URLs are useful when linking to resources from another website, sharing a page externally, specifying canonical locations, or providing an address that must work without relying on the current page’s location.
Relative URL
A relative URL depends on a base URL for its meaning.
For example:
/images/logo.png
If this reference appears on https://example.com, the browser can resolve it relative to that site’s base address.
Another relative reference might simply be:
contact
Its final destination depends on the current or specified base URL.
The WHATWG URL Standard explicitly accounts for resolving relative URL strings using a base URL.
Relative URLs are particularly useful for internal website links because developers do not always need to repeat the scheme and domain.
URL vs. Domain Name: What’s the Difference?
A domain name is only one potential component of a URL.
For example:
example.com
is a domain.
But:
is a complete URL containing considerably more information.
Think of the domain as identifying the general destination and the complete URL as specifying a particular resource or location at that destination.
| Domain | Full URL |
|---|---|
example.com | https://example.com/blog/article |
| Identifies a domain | Identifies/accesses a specific resource |
| Does not include a path | Can include paths |
| Does not contain query/fragment information | Can contain queries and fragments |
This distinction matters when someone asks you to submit a “website URL.” They may need the complete address of a particular page rather than only the site’s domain.
URL vs. URI: Are They the Same?
The terminology can become confusing because URL and URI are closely related concepts.
URI stands for Uniform Resource Identifier.
RFC 3986 describes a URI as a sequence of characters that identifies an abstract or physical resource. It historically classifies a URL as a subset of URIs that identifies a resource while also providing a way of locating it through an access mechanism or network location.
Modern web-platform terminology is somewhat different. The WHATWG URL Living Standard deliberately standardizes around the term URL and aims to align older URI/IRI concepts with how contemporary browsers actually parse addresses.
For an everyday web user, the distinction rarely matters. “URL” is the practical term you will encounter most often for web addresses.
What Are the Different Types of URLs?
URLs can be grouped in several ways rather than belonging to one rigid list of “types.”
HTTP and HTTPS URLs
These are the addresses most commonly associated with websites:
http://example.com
HTTPS provides encrypted communication between the client and server and is the standard choice for modern public websites.
URLs With Query Parameters
Example:
These URLs carry query information that an application can use when generating its response.
URLs With Fragments
Example:
The fragment can direct the browser to a specific portion of the resource.
File URLs
The file: scheme can identify local file resources.
For example, URL specifications include forms such as:
file:///C:/example/document.txt
These behave differently from normal HTTP or HTTPS web addresses.
Other URL Schemes
Not every URL starts with HTTP.
The URL Standard recognizes multiple schemes, while additional schemes can be defined and registered for particular uses.
You may encounter addresses beginning with schemes such as mailto:, ftp:, or application-specific schemes.
What Is the Difference Between HTTP and HTTPS in a URL?
The difference is visible immediately:
http://example.com
versus:
HTTP stands for Hypertext Transfer Protocol, while HTTPS uses HTTP with a secure encrypted connection.
For ordinary browsing, HTTPS helps protect information transmitted between your browser and the website from being read or altered in transit.
However, the presence of HTTPS should not be treated as proof that the organization behind a website is trustworthy. A malicious or deceptive website can also use HTTPS.
That distinction matters when evaluating unfamiliar links: encryption protects the connection, not necessarily your relationship with the website owner.
How Can You Tell Whether a URL Is Safe?
URLs are useful security clues because deceptive links often rely on people reading addresses too quickly.
Before entering a password, payment information, or other sensitive data, inspect the actual domain.
For example:
and
may look related at a glance, but they belong to different domains.
Pay particular attention to:
- Misspelled domain names
- Unexpected subdomains
- Strange or misleading characters
- Unfamiliar domains pretending to represent known services
- Links whose visible text does not match their actual destination
- Unexpected redirects
- URLs requesting sensitive information without a clear reason
Also remember that the path does not determine who owns the website.
Consider:
The presence of google in the path does not make example.net a Google domain. The host is what matters for determining which site the browser is actually contacting.
Don’t Trust HTTPS Alone
A padlock or HTTPS connection means the connection is encrypted. It does not automatically mean the content is genuine, accurate, or harmless.
When a link involves money, passwords, account recovery, or private information, verify the domain itself.
Why Do Some URLs Contain Strange Characters?
You may encounter URLs containing sequences such as:
%20
This is related to percent-encoding.
URLs have rules governing how characters are represented. Characters that cannot or should not appear directly in certain URL components may be represented using encoded byte values.
A common example is a space, which can appear as:
%20
So:
my file.pdf
might appear in a URL path as:
my%20file.pdf
RFC 3986 describes percent-encoding as part of URI syntax, and the modern URL Standard defines parsing and serialization rules used by browsers.
This does not automatically indicate anything suspicious. It is a normal part of representing data in URLs.
Can Two Different URLs Show the Same Page?
Yes.
Although URLs are intended to identify resources, multiple URLs can sometimes lead to identical or substantially identical content.
For example, a site might make the same content accessible through:
and:
The second URL contains additional query information, but the main content might remain unchanged.
Websites may also redirect old URLs to new ones when pages move.
MDN notes that although a valid URL theoretically points to a unique resource, real-world exceptions occur—for example, when a resource has moved or no longer exists.
For website owners, managing duplicate and changed URLs carefully is important because URLs affect navigation, sharing, indexing, redirects, and search-engine crawling.
What Makes a Good Website URL?
A technically valid URL is not automatically a useful URL for humans.
For public webpages, readable URLs are generally easier to understand and share.
Compare:
with:
Both could work, but the first communicates much more about the destination.
Useful URL practices typically include:
- Keeping paths descriptive
- Using logical website structure
- Avoiding unnecessary parameters where possible
- Keeping permanent page addresses stable
- Using HTTPS
- Avoiding excessively complicated strings
- Redirecting outdated addresses appropriately
A simple URL also gives users useful context before they click.
What Happens When a URL No Longer Works?
URLs are addresses, but the resources behind those addresses can change.
If a page is deleted, moved without a redirect, or temporarily unavailable, its old URL may stop producing the expected content.
A server may respond with an HTTP status such as 404 Not Found when the requested resource cannot be found.
Website owners can often preserve usability by redirecting an outdated URL to the appropriate new location when content genuinely moves.
For users, a broken URL does not necessarily mean the entire website has disappeared. The individual page may have moved, the address may contain a typo, or the resource may have been removed.
How Do You Find and Copy a URL?
For a webpage, the easiest method is usually the browser’s address bar.
On a desktop browser:
- Open the page.
- Select the address bar.
- Copy the displayed URL.
You can then paste the address into a message, document, browser, or other application.
For a link on a page, browsers also commonly provide an option such as Copy link address through the context menu.
Remember that URLs can become long because they may contain search parameters, tracking information, filters, or other data. The entire string is not necessarily needed in every situation, but deleting portions without understanding them can change the destination or behavior.
Why URLs Matter
A URL may appear to be nothing more than text in an address bar, but it is a fundamental part of how resources are identified and accessed on the web.
URLs make it possible to:
- Navigate between webpages
- Create hyperlinks
- Bookmark specific resources
- Share exact pages with other people
- Reference images and files
- Send query information to web applications
- Link directly to sections of documents
- Organize websites into understandable structures
- Give browsers instructions for locating resources
The generic URI syntax standardized in RFC 3986 uses components such as scheme, authority, path, query, and fragment, while the modern WHATWG URL Standard defines detailed parsing behavior used by contemporary web implementations.
Final Takeaway: what is a url?
So, what is a url? A URL, or Uniform Resource Locator, is an address used to identify and access a resource. For web addresses, it commonly combines a scheme such as HTTPS with a host or domain and may also contain a port, path, query, and fragment.
The easiest way to read one is from left to right. Identify the scheme first, check the actual host or domain, then look at the path for the requested resource. If present, the query supplies additional information and the fragment points to a particular location within the resource.
Once you recognize those pieces, even complicated-looking URLs become much easier to understand.