Link Component
Enable fast client-side navigation with the built-in `next/link` component.
<Link> is a React component that extends the HTML <a> element to provide prefetching and client-side navigation between routes. It is the primary way to navigate between routes in Next.js.
Basic usage:
Reference
The following props can be passed to the <Link> component:
| Prop | Example | Type | Required |
|---|---|---|---|
href | href="/dashboard" | String or Object | Yes |
as | as="/post/abc" | String or Object | - |
replace | replace={false} | Boolean | - |
scroll | scroll={false} | Boolean | - |
prefetch | prefetch={false} | Boolean | - |
shallow | shallow={false} | Boolean | - |
locale | locale="fr" | String or Boolean | - |
onNavigate | onNavigate={(e) => {}} | Function | - |
Good to know: <a> tag attributes such as className or target="_blank" can be added to <Link> as props and will be passed to the underlying <a> element.
href (required)
The path or URL to navigate to.
replace
Defaults to false. When true, next/link will replace the current history state instead of adding a new URL into the browser's history stack.
scroll
Defaults to true. The default scrolling behavior of <Link> in Next.js is to maintain scroll position, similar to how browsers handle back and forwards navigation. When you navigate to a new Page, scroll position will stay the same as long as the Page is visible in the viewport. However, if the Page is not visible in the viewport, Next.js will scroll to the top of the first Page element.
When scroll = {false}, Next.js will not attempt to scroll to the first Page element.
Good to know: Next.js checks if scroll: false before managing scroll behavior. If scrolling is enabled, it identifies the relevant DOM node for navigation and inspects each top-level element. All non-scrollable elements and those without rendered HTML are bypassed, this includes sticky or fixed positioned elements, and non-visible elements such as those calculated with getBoundingClientRect. Next.js then continues through siblings until it identifies a scrollable element that is visible in the viewport.
prefetch
Prefetching happens when a <Link /> component enters the user's viewport (initially or through scroll). Next.js prefetches and loads the linked route (denoted by the href) and data in the background to improve the performance of client-side navigation's. Prefetching is only enabled in production.
The following values can be passed to the prefetch prop:
true(default): The full route and its data will be prefetched.false: Prefetching will not happen when entering the viewport, but will happen on hover. If you want to completely remove fetching on hover as well, consider using an<a>tag or incrementally adopting the App Router, which enables disabling prefetching on hover too.
shallow
Update the path of the current page without rerunning getStaticProps, getServerSideProps or getInitialProps. Defaults to false.
locale
The active locale is automatically prepended. locale allows for providing a different locale. When false href has to include the locale as the default behavior is disabled.
as
Optional decorator for the path that will be shown in the browser URL bar. Before Next.js 9.5.3 this was used for dynamic routes, check our previous docs to see how it worked.
When this path differs from the one provided in href the previous href/as behavior is used as shown in the previous docs.
onNavigate
An event handler called during client-side navigation. The handler receives an event object that includes a preventDefault() method, allowing you to cancel the navigation if needed.
Good to know: While onClick and onNavigate may seem similar, they serve different purposes. onClick executes for all click events, while onNavigate only runs during client-side navigation. Some key differences:
- When using modifier keys (
Ctrl/Cmd+ Click),onClickexecutes butonNavigatedoesn't since Next.js prevents default navigation for new tabs. - External URLs won't trigger
onNavigatesince it's only for client-side and same-origin navigations. - Links with the
downloadattribute will work withonClickbut notonNavigatesince the browser will treat the linked URL as a download.
Examples
The following examples demonstrate how to use the <Link> component in different scenarios.
Linking to dynamic route segments
For dynamic route segments, it can be handy to use template literals to create the link's path.
For example, you can generate a list of links to the dynamic route pages/blog/[slug].js
Scrolling to an id
If you'd like to scroll to a specific id on navigation, you can append your URL with a # hash link or just pass a hash link to the href prop. This is possible since <Link> renders to an <a> element.
Passing a URL Object
Link can also receive a URL object and it will automatically format it to create the URL string:
The above example has a link to:
- A predefined route:
/about?name=test - A dynamic route:
/blog/my-post
You can use every property as defined in the Node.js URL module documentation.
Replace the URL instead of push
The default behavior of the Link component is to push a new URL into the history stack. You can use the replace prop to prevent adding a new entry, as in the following example:
Disable scrolling to the top of the page
The default behavior of Link is to scroll to the top of the page. When there is a hash defined it will scroll to the specific id, like a normal <a> tag. To prevent scrolling to the top / hash scroll={false} can be added to Link:
Prefetching links in Proxy
It's common to use Proxy for authentication or other purposes that involve rewriting the user to a different page. In order for the <Link /> component to properly prefetch links with rewrites via Proxy, you need to tell Next.js both the URL to display and the URL to prefetch. This is required to avoid un-necessary fetches to proxy to know the correct route to prefetch.
For example, if you want to serve a /dashboard route that has authenticated and visitor views, you can add the following in your Proxy to redirect the user to the correct page:
In this case, you would want to use the following code in your <Link /> component:
Good to know: If you're using Dynamic Routes, you'll need to adapt your as and href props. For example, if you have a Dynamic Route like /dashboard/authed/[user] that you want to present differently via proxy, you would write: <Link href={{ pathname: '/dashboard/authed/[user]', query: { user: username } }} as="/dashboard/[user]">Profile</Link>.
Version history
| Version | Changes |
|---|---|
v15.4.0 | Add auto as an alias to the default prefetch behavior. |
v15.3.0 | Add onNavigate API |
v13.0.0 | No longer requires a child <a> tag. A codemod is provided to automatically update your codebase. |
v10.0.0 | href props pointing to a dynamic route are automatically resolved and no longer require an as prop. |
v8.0.0 | Improved prefetching performance. |
v1.0.0 | next/link introduced. |