Navigation API
Gives a single place to listen to and control same-document navigations.
In one line
Can watch and control page changes inside the app, such as when you press Back
Gives a single place to listen to and control same-document navigations.
A single page app can intercept link clicks and back or forward, and list its own history entries. It sees only same-origin entries, so it cannot read browsing history.
What it can and can't do
What the user does: Nothing. It happens as you click links, press Back, or move around the app.
It can
- Notice when you click a link or press Back inside the site
- Update the page without a full reload
- Hold up a page change until a save finishes
It cannot
- Watch what you do on other sites or in other tabs
- Block you from leaving the site
- Change the address to another site's address
- See where you came from outside its own pages
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 102 | 2022-05-24 | None |
| Edge | Supported | 102 | 2022-05-31 | None |
| Firefox | Supported | 147 | 2026-01-13 | None |
| Safari | Supported | 26.2 | 2025-12-12 | None |
| Safari on iPhone | Supported | 26.2 | 2025-12-12 | All iOS browsers use WebKit |
| Chrome on Android | Supported | 102 | 2022-05-24 | None |
| Samsung Internet | Supported | 19.0 | 2022-11-01 | None |
How a site asks for it
| API | navigation.navigate(), navigation.intercept(), navigation.entries() |
| Browser compat keys | api.Navigationapi.NavigateEvent |
| How access is granted | none |
| What the user sees | None (no browser prompt) |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| Activation | none |
| How long it lasts | Entries live in the tab session |
| How to take it back | Nothing to revoke (no permission is stored) |
| Inside an iframe | Same-origin entries only |
Typical flow
- Add navigate event listener
- Call event.intercept()
- Page handles transition
Data you get
Shape: none
No individual data fields. The signal is the access itself.
Technical limits
- entries() lists only same-origin entries of the current tab
- The same back button hijack mitigations apply (entries without user activation are skippable)
- Cannot read other tabs or other origins' history
- Support per MDN BCD: Chrome 102, Safari 26.2, Firefox 147
The story
What it is
A modern way for a page to manage its own links and Back button handling.
For you
You never see it. When it works, apps feel snappier and Back and Forward behave more predictably inside big web apps.
For makers
Makers use it to build cleaner routing than the older history tricks, with animation hooks and a proper list of past entries. It is mostly a developer quality and speed win.
Where you see it
| Type | Example | Apps |
|---|---|---|
| productivity | A web mail app changes folders without reloading and keeps Back working. | Gmail, Outlook web |
| media | A streaming site slides between pages with an animation while loading the next view. | None named |
| shopping | A store keeps your scroll position when you press Back from a product. | None named |
| developer | A framework wires its router to the API so one place handles every in page link. | React Router, Next.js |
| analytics | A measurement script catches every in page navigation without brittle hacks. | None named |
| live | A live blog moves between match pages without breaking the real time feed. | None named |
Risks
- Few for readers
- Routing bugs
What the platform says
- Google: Navigation API. Chrome's docs say the API modernizes single page app routing with one clear set of tools.
Good uses and abuse
Legitimate uses
- SPA routers
Known abuse
- Back-button trap helpers (blocked by intervention)
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2022-02, Chrome 102: Navigation API ships
Related capabilities
Related
- Push history entries (back button limits). Can add extra Back button steps, but browsers skip steps made without a tap
Sources
How well checked: Based on official documentation.