Next-Gen App & Browser Testing Cloud
Trusted by 2 Mn+ QAs & Devs to accelerate their release cycles

To enable location permission in Chrome on desktop, open the three-dot menu, go to Settings, then Privacy and security, then Site settings, then Location, and select "Sites can ask to use your location" (or go straight to chrome://settings/content/location). When a website requests your location, choose Allow in the prompt. On Android, the same setting lives under Settings, then Site settings, then Location. If a site still cannot read your location after you allow it, the cause is almost always Location Services being turned off at the operating-system level, which is covered below.
The global setting controls whether sites are even allowed to ask for your location. Turning it on does not hand your location to every site; it simply lets sites show the permission prompt, which you then accept or decline per site.
Most of the time you grant location not from Settings but directly when a site asks. When a page calls the Geolocation API, Chrome shows a popup just under the address bar.
Android adds a second gate: Chrome itself must hold the Android location permission before any website setting matters. You need both the in-browser setting and the OS app permission switched on.
Chrome does not calculate your position itself, it asks the operating system. If the OS location switch is off, allowing location inside Chrome changes nothing, and Chrome typically shows a banner reading "Location is turned off in your system preferences." Enable it as follows:
If you blocked a site by mistake, or you want Chrome to ask again from scratch, reset its permission rather than hunting through menus.
Enabling the permission only decides whether a site may read your location, not which location it sees. If you want to report a different city or coordinates for testing, see How to Change Location on Google Chrome? for the DevTools and override methods.
Granting the Chrome permission is only one link in the chain. When location still fails, one of these is usually the culprit:
Use this quick reference to map the symptom to the fix:
| Symptom | Likely cause | Fix |
|---|---|---|
| Banner: "Location is turned off in your system preferences" | OS Location Services off | Enable Location in Windows/macOS settings, then reload |
| No prompt and location denied on one site | Site is in the Not allowed list | Reset permission or move it to Allowed |
| Works on some sites, fails on one | Page served over http, not https | Use the HTTPS version of the site |
| Inaccurate or empty location | GPS/Wi-Fi positioning disabled | Turn on device location/Wi-Fi scanning |
If you build location-aware features, the permission prompt, the allow and block flow, and the region-specific content that follows behave differently across browsers, OS versions, and devices. Verifying that on local machines alone is slow and incomplete, especially when you need to confirm how a feature looks for users in another country.
TestMu AI offers Geolocation Testing across real browsers and devices in a wide range of countries, so you can validate the geolocation permission flow and the geo-targeted experience without juggling local settings or maintaining a fleet of machines.
On desktop, open the three-dot menu, go to Settings, then Privacy and security, then Site settings, then Location (or type chrome://settings/content/location), and select "Sites can ask to use your location." When a site asks, choose Allow in the prompt. On Android, the same control lives under Settings, then Site settings, then Location.
Chrome can only share a location the operating system provides. If Location Services are off in Windows or macOS, no site gets your location even when Chrome is set to allow it, and Chrome shows a "Location is turned off in your system preferences" banner. Turn on the OS-level setting, confirm the site is not in the Not allowed list, and reload the page.
Click the tune or site-information icon at the left of the address bar while on the site, open Site settings or Permissions, find Location, and set it to Allow, then reload. If you previously dismissed or blocked the prompt, use Reset permission first so Chrome asks again.
Open Chrome, tap the three-dot menu, then Settings, then Site settings, then Location, and allow sites to ask. You also need to grant Chrome the Android location permission under device Settings, then Apps, then Chrome, then Permissions, then Location, and keep the phone's master Location toggle on. If the OS denies Chrome location, no website can get it.
While on the site, click the site-information icon at the left of the address bar and choose Reset permission, or remove the site from the Allowed and Not allowed lists at chrome://settings/content/location. The next time the site requests your location, Chrome shows the Allow or Block prompt again.
Yes. Chrome relies on the operating system for positioning. On Windows 11, enable Location services and "Let desktop apps access your location" in Settings, Privacy and security, Location. On macOS, enable Location Services and the Google Chrome toggle in System Settings, Privacy and Security. Without the OS gate open, allowing location inside Chrome has no effect.
KaneAI - Testing Assistant
World’s first AI-Native E2E testing agent.

TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance