Loopback network access (loopback-network)
Asks to let a public site talk to services on this very computer.
In one line
Can talk to programs on your own computer, only if you allow it in Chrome
Asks to let a public site talk to services on this very computer.
Controls access to localhost services (dev servers, local agents, desktop apps). Sites used to probe localhost ports to detect installed software, so access now needs consent.
What it can and can't do
What the user does: You visit a site that pairs with a desktop app and tap Allow
It can
- Connect to helper apps or developer tools running on this computer once you allow it
- Check whether a companion app is running
- Keep that access until you change it in site settings
It cannot
- Reach programs on your computer before you allow it
- Work in Safari or on iPhone browsers
- Probe your computer silently for installed apps, since the pop up blocks that
- Work on Samsung Internet or Firefox the same way
How it differs between platforms: Chrome and Edge ask with a pop up. Firefox is partial. Safari and iPhone browsers do not offer it.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 142 | 2025-10-28 | Initially shipped under local-network-access |
| Edge | Supported | 142 | 2025-10-31 | None |
| Firefox | Partial | Firefox staged rollout from 147 | Not listed | None |
| Safari | Not supported | Not available | Not listed | None |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Supported | 142 | 2025-10-28 | None |
| Samsung Internet | Not supported | Not available | Not listed | None |
How a site asks for it
| API | fetch('http://localhost:PORT', {targetAddressSpace: 'loopback'}); permission loopback-network |
| Permission name | loopback-network |
| Permissions policy | loopback-network |
| How access is granted | prompt |
| What the user sees | Chrome prompt for requests from public sites to 127.0.0.1 or localhost. Legacy name local-network-access still accepted as an alias. |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Persistent per origin |
| How to take it back | Site settings |
| Inside an iframe | Needs allow="loopback-network" in iframes |
Typical flow
- Page fetches 127.0.0.1
- Chrome checks address space
- Prompt
- Request proceeds or fails
Data you get
What comes back: Grant state
Shape: boolean
How often: per request
No individual data fields. The signal is the access itself.
Technical limits
- Exact split release version not confirmed
- Prevents localhost port scanning
The story
What it is
Your browser asks if a website may talk to apps running on this very computer.
For you
A prompt asks if the site may connect to apps on this computer. Say yes only if you installed a companion app the site works with. Otherwise block it.
For makers
Makers of desktop apps with a web page front end, such as meeting, security or game launchers, use this to link the page and the app. They now need to ask and explain the benefit.
Where you see it
| Type | Example | Apps |
|---|---|---|
| video | A meeting site asks to connect to the desktop meeting app on your computer, so clicking Join opens the app. | Zoom |
| games | A game store page asks to talk to the launcher on your PC, so Install in the browser starts the download in the app. | Epic Games, Steam |
| security | A password manager web page connects to its local helper, so it can fill logins in the browser. | None named |
| developer | A docs page connects to a dev server running on your laptop, to show live output. | None named |
| music | A web music page talks to a desktop audio app, so a play button starts the local player. | Spotify |
| enterprise | A company portal checks for its endpoint security agent on this computer before login, with your permission. | None named |
| ads | A site probing your own computer for apps to build a profile is stopped by the prompt, as users see it. | None named |
Risks
- Easy to click allow
- Probes your computer
What the platform says
- Google Chrome: Local Network Access. Chrome now treats talking to your own computer as its own permission, separate from other devices on the network.
Good uses and abuse
Legitimate uses
- Companion desktop apps
- Local dev tools
Known abuse
- Port scanning to detect installed apps
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 2 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2025-10, Chrome 142: Local network permission ships; later split into local-network and loopback-network
Related capabilities
Related
- Local Network Access (local-network). Can find and connect to devices on your home or office network, if you tap Allow
Sources
How well checked: Based on official documentation.