Local Network Access (LNA) permission
Chrome asks the user before a public website can reach devices on their local network.
In one line
Can connect to devices on your home network, only if you allow it in Chrome
Chrome asks the user before a public website can reach devices on their local network.
Chrome 142 added a prompt for requests to private IPs. Chrome 145 split it into local-network and loopback-network permissions, and 147 extended it to WebSocket and WebTransport. It replaced Private Network Access preflights.
What it can and can't do
What the user does: You open a site and tap Allow on Chrome's local network pop up
It can
- Look for and connect to printers, routers and smart home devices on your network once you allow it
- Talk to local helper apps from a public website
- Keep this access for the site until you take it back in site settings
It cannot
- Reach local devices before you tap Allow in Chrome 142 and newer
- Work in Firefox or Safari, which do not offer this permission
- Get around the pop up; the old silent checks were replaced by it
- Reach your network from Chrome on iPhone
How it differs between platforms: Only Chrome and Edge ask. Firefox, Safari and every iPhone browser do not offer this permission.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 142 | 2025-10-28 | None |
| Edge | Supported | 142 | 2025-10-31 | None |
| Firefox | Not supported | Not available | 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 | Supported | 30.0 | 2026-05-11 | None |
How a site asks for it
| API | Permissions-Policy: local-network-access; fetch targetAddressSpace |
| Permission name | local-network-access |
| Permissions policy | local-network-access |
| How access is granted | none |
| What the user sees | Look for and connect to any device on your local network |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Not listed |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Page requests a local address
- Browser shows prompt
- Request allowed or blocked
Data you get
What comes back: granted or denied
Shape: boolean
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
permission | string | None | granted, denied, prompt | exact |
Technical limits
- Only Chromium; Firefox and Safari have no equivalent prompt
- Users can accept for the site persistently
The story
What it is
Chrome asks before a public website can talk to devices in your home or office network.
For you
A pop up asks if the site may look for and connect to devices on your local network. If you say no, the site cannot reach your printer, speakers or router. Nothing changes if you say no and do not need that device.
For makers
Makers who build companion web apps for printers, smart speakers or developer tools must now ask first and explain why. It replaces older hidden checks with one clear permission. Sites that never ask lose silent access.
Where you see it
| Type | Example | Apps |
|---|---|---|
| smart-home | A web dashboard for a smart home hub finds lights and thermostats on your network. Chrome asks first, then the page controls them from the browser. | Home Assistant |
| music | A web player offers to send music to speakers in your living room. Chrome asks to find local devices before the speaker list shows up. | Sonos web controller |
| developer | A developer opens a public docs site that talks to a tool running on their own network. They approve once so the page can reach it. | None named |
| enterprise | A company's cloud admin page connects to an office printer or card reader by its local address, after a one time allow. | None named |
| games | A browser game party site lists consoles or PCs on your Wi-Fi so you can start streaming a game to the web page. | None named |
| video | A web casting page searches for TVs on your network and asks first, then shows your nearby TVs. | Chromecast |
| security | A malicious ad tries to poke your router login. Chrome shows a prompt, which warns you that something odd is happening. | None named |
Risks
- Easy to click allow
- Exposes home devices if granted
What the platform says
- Google Chrome: Local Network Access. Chrome now asks you first when a public website tries to reach devices on your local network, to stop sneaky probing.
Good uses and abuse
Legitimate uses
- Local helper apps, smart home dashboards
Known abuse
- Local device probing if granted
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 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 | 1 | Rough identifying entropy, when known |
History
- 2025-10, Chrome 142: LNA prompt ships
- 2026-02, Chrome 145: Split into local-network and loopback-network (secondary sources)
- 2026-04, Chrome 147: Extended to WebSocket and WebTransport (secondary sources)
Related capabilities
Related
- Localhost and LAN port scanning. Can try to find software running on your own computer, though Chrome now blocks it
Sources
How well checked: Checked against real behavior.