Getting the Current URL in a Laravel Blade File

Laravel gives you several ways to get "the current URL" in a Blade view — which one is correct depends on whether you actually need the path, the full URL with query string, or just the route's name to compare against.

URL without query string

{{ url()->current() }}
{{ request()->url() }}

Both return the current URL without any query parameters — useful for building a canonical link or comparing against a known path.

Full URL including query string

{{ request()->fullUrl() }}

Use this when the query string is actually part of what makes the "current URL" meaningful — a filtered listing page, for example, where ?category=shoes genuinely changes what page this is.

Just the path

{{ request()->path() }}

Returns the path relative to the domain, without the scheme or host — e.g. products/42, not https://example.com/products/42.

Comparing against the current route name — usually the better check

If the goal is "is this the active nav link," comparing against the route name is more robust than string-comparing URLs, since it doesn't break if the URL structure changes later:

<a href="{{ route('dashboard') }}" class="{{ request()->routeIs('dashboard') ? 'active' : '' }}">
    Dashboard
</a>

request()->routeIs() also supports wildcards — request()->routeIs('admin.*') matches any route name starting with admin., useful for highlighting a whole nav section as active rather than a single link.

Checking if the current path matches a pattern

@if (request()->is('admin/*'))
    <!-- admin section styling -->
@endif

request()->is() checks the path directly against a wildcard pattern — useful when there's no named route to compare against, but generally routeIs() is the more maintainable choice when a route name exists.

Canonical URLs usually should not copy every query parameter

request()->fullUrl() is useful when the query string is part of the current application state, but that does not automatically make it the right canonical URL for SEO. Tracking parameters, temporary UI flags, and pagination/filter combinations often should not be copied into a canonical tag. Build canonical policy intentionally rather than assuming "current full URL" and "canonical URL" are synonyms.

Use fullUrlWithQuery() when modifying rather than rebuilding the query string

If a link needs the current filters plus one changed parameter, Laravel can merge it safely:

{{ request()->fullUrlWithQuery(['view' => 'grid']) }}

Likewise, fullUrlWithoutQuery() can remove specific parameters. Those helpers avoid manually concatenating ?foo=... and getting encoding or existing-query-string separators wrong.

Route names survive URL refactors better than paths

The active-navigation example is more than stylistic preference. A route can move from /admin/users to /settings/users while keeping the same semantic route name; routeIs() continues to work, while a path wildcard has to change. Path checks are still appropriate for genuinely unnamed or externally-defined routes, but they couple the view directly to the URL structure.

Be careful behind a reverse proxy

Methods that return an absolute URL depend on Laravel understanding the request's scheme and host correctly. Behind a load balancer or TLS-terminating reverse proxy, a misconfigured trusted-proxy setup can make generated URLs appear as http instead of https or use the wrong host. If request()->url() looks wrong only in production, inspect proxy/header configuration before trying to patch the Blade template.