navigator.geolocation returns a Geolocation object — the Geolocation API entry point. Learn permissions, HTTPS rules, getCurrentPosition, watchPosition, five examples, and try-it labs.
Read-only property
Geolocation
Widely available
Secure (HTTPS)
getCurrentPosition
watchPosition
Maps, store finders, and weather widgets often need the user’s location. The Geolocation API lets your page request that location — but only after the browser asks the user for permission.
Your entry point is navigator.geolocation. It is read-only and returns a Geolocation object with methods such as getCurrentPosition() and watchPosition().
MDN: location access notifies the user and requires permission. The API is available in secure contexts (HTTPS / localhost). Always handle “denied” and timeouts kindly.
geolocation PropertyThink of navigator.geolocation as a handle to the device’s location services for this page. You do not assign to it — you call methods on the object it returns.
position.coords.latitude / longitude (and more).General form of the property:
navigator.geolocationGeolocation object that provides access to the device location.if ("geolocation" in navigator) {
navigator.geolocation.getCurrentPosition(
(pos) => {
console.log(pos.coords.latitude, pos.coords.longitude);
},
(err) => {
console.log(err.code, err.message);
},
{ enableHighAccuracy: true, timeout: 10000, maximumAge: 0 }
);
} else {
// Geolocation not available
}| Goal | Code |
|---|---|
| Get Geolocation | navigator.geolocation |
| Detect API | "geolocation" in navigator |
| One reading | getCurrentPosition(success, error, options) |
| Watch updates | watchPosition(success, error, options) |
| Stop watching | clearWatch(id) |
| Secure page? | window.isSecureContext |
Four facts to remember about navigator.geolocation.
GeolocationAPI entry
widelySince ~2015
requiredSecure context
user promptMust allow
getCurrentPosition vs watchPositiongetCurrentPosition | watchPosition | |
|---|---|---|
| Frequency | One-shot | Ongoing updates |
| Best for | “Find stores near me” | Live maps / tracking a walk |
| Cleanup | None | clearWatch(id) |
| Battery | Usually lighter | Can use more power |
| Permission | Both require user permission when needed | |
Examples follow MDN Geolocation / navigator.geolocation patterns. Prefer Try It Yourself over HTTPS and allow location when prompted. Use View Output for expected messaging.
Detect the API and confirm a secure context.
Check whether Geolocation is available.
const supported = "geolocation" in navigator;
console.log(supported ? "geolocation available" : "geolocation missing");Almost all modern browsers expose the property; still detect it before calling methods.
Pair detection with isSecureContext.
const lines = [
"isSecureContext: " + window.isSecureContext,
"geolocation: " + (("geolocation" in navigator) ? "present" : "absent")
];
console.log(lines.join("\n"));Serve location features over HTTPS (or localhost during development).
One-shot location, live watching, and a reusable helper.
getCurrentPositionRequest one reading from a button click (permission prompt).
function getMyLocation(onDone) {
if (!("geolocation" in navigator)) {
onDone("geolocation unavailable");
return;
}
navigator.geolocation.getCurrentPosition(
(pos) => {
const c = pos.coords;
onDone("lat: " + c.latitude + ", lng: " + c.longitude);
},
(err) => {
onDone("error " + err.code + ": " + err.message);
}
);
}
// Call from a button in Try ItSuccess gives a GeolocationPosition. Common error codes include permission denied (1), position unavailable (2), and timeout (3).
watchPosition + clearWatchStart live updates, then stop them with the watch ID.
let watchId = null;
function startWatch(onUpdate) {
if (!("geolocation" in navigator)) {
onUpdate("geolocation unavailable");
return;
}
watchId = navigator.geolocation.watchPosition(
(pos) => {
onUpdate("watching lat: " + pos.coords.latitude);
},
(err) => {
onUpdate("watch error: " + err.message);
}
);
}
function stopWatch() {
if (watchId !== null) {
navigator.geolocation.clearWatch(watchId);
watchId = null;
}
}
// Wire Start / Stop buttons in Try ItAlways clear watches when the page no longer needs them to save battery and privacy.
Wrap secure-context checks, options, and structured results.
function getLocationOnce() {
return new Promise((resolve) => {
if (!window.isSecureContext) {
resolve({ ok: false, reason: "insecure-context" });
return;
}
if (!("geolocation" in navigator)) {
resolve({ ok: false, reason: "unsupported" });
return;
}
navigator.geolocation.getCurrentPosition(
(pos) => {
resolve({
ok: true,
latitude: pos.coords.latitude,
longitude: pos.coords.longitude,
accuracy: pos.coords.accuracy
});
},
(err) => {
resolve({ ok: false, reason: err.message, code: err.code });
},
{ enableHighAccuracy: false, timeout: 8000, maximumAge: 60000 }
);
});
}
// Call from a button in Try ItmaximumAge can reuse a recent cached position; timeout fails if a fix takes too long.
watchPosition for live trails.navigator.geolocation WorksHTTPS / localhost and "geolocation" in navigator.
Browser prompt (policy varies by browser).
Receive GeolocationPosition with coords.
Show maps / distances — or a friendly denial message.
navigator.geolocation is Baseline Widely available across modern browsers (MDN: since about July 2015). Always use a secure context and respect the permission prompt.
Feature-detect, require HTTPS, call getCurrentPosition/watchPosition from a user gesture when possible, and handle denials.
Bottom line: Use navigator.geolocation for location features. Keep a non-location fallback when permission is denied.
navigator.geolocation is the Geolocation API entry point. Feature-detect it, require HTTPS, request permission politely, use getCurrentPosition or watchPosition, and always handle errors.
Continue with globalPrivacyControl, doNotTrack, or the JavaScript hub.
clearWatch when done watchinggeolocationLocation API entry — permission, HTTPS, get or watch.
Geolocation
APIgetCurrentPosition
ReadwatchPosition
Watchsecure context
Securityuser prompt
ConsentMDN emphasizes that every browser has its own policies for asking location permission — so never hard-code assumptions about when the prompt appears or how denial is worded.
Learn the Global Privacy Control signal for sell/share consent.
8 people found this page helpful