Hardware
Viewer
Geo
RecorderGPS Location Viewer
Free GPS test in your browser: check location accuracy, TTFF, altitude and speed live, record a track, and export it as GPX, CSV or JSON.
Have feedback? Report bugs, suggest features, or share your thoughts — we read them allAbout GPS Location Viewer
GPS Location Viewer uses the browser geolocation API (over HTTPS) to display your position, accuracy, altitude, altitude accuracy, speed, and heading. A Leaflet grid map works even without online tile servers. Pro users can record a tracking session, read best/worst/average accuracy plus time-to-first-fix, and export the captured track as GPX, CSV, or JSON — all client-side.
- Press Start tracking and grant location permission when the browser prompt appears (the page must be served over HTTPS).
- Hold the device outdoors or near a window for a faster GPS fix; watch the map center on your coordinates.
- Move around to see speed, altitude, heading, and accuracy update in real time while every fix is recorded.
- Check time-to-first-fix and min/max/average accuracy, then export the recorded track as GPX, CSV, or JSON.
- Use Reset to clear logs and the recorded track before starting a new tracking session.
Frequently Asked Questions
navigator.geolocation works in every modern browser — Chrome, Edge, Firefox, Safari, Samsung Internet — on Windows, macOS, Linux, Android, and iOS. Two hard requirements catch most QA techs: (1) the page MUST be served over HTTPS (or localhost); on plain HTTP, Chrome 50+ and all current browsers refuse geolocation, which is why an internal LAN test rig on http:// shows a 'requires secure context' message here rather than a fix. (2) The user must grant permission. If you see 'permission blocked', the site or OS has it set to Deny: on Android open Site settings → Location → Allow; on iOS open Settings → Privacy & Security → Location Services → Safari/Chrome → While Using, and also enable 'Precise Location' (iOS 14+ approximate mode rounds your position to ~1 km). A TIMEOUT with no fix means high-accuracy GNSS could not lock — step outdoors or near a window and retry. Desktops without a GPS chip fall back to Wi-Fi/IP positioning, so accuracy may read tens to hundreds of meters.
Yes, it stays private. All positioning runs entirely client-side in your browser via navigator.geolocation, and every reading — latitude, longitude, altitude, speed, the recorded track, and the GPX/CSV/JSON exports — is built and downloaded locally with no network upload. Your coordinates are never sent to WuTools or any server; we have no database of your location. The export files are generated in memory and saved straight to your device. To revoke access at any time, use the location icon in your browser's address bar, or your browser/OS site settings (Android: Site settings → Location; iOS: Settings → Privacy → Location Services; desktop Chrome/Edge/Firefox: Site information → Permissions → Location → Reset).
Latitude/Longitude are your decimal-degree coordinates. Accuracy is the horizontal 68% confidence radius in meters — smaller is better; a 5 m reading means your true position is within 5 m about 68% of the time. Altitude is height above the WGS-84 ellipsoid (not sea level), and Altitude accuracy is its vertical uncertainty — if it shows N/A, your device did not report it. Speed and Heading read N/A when you are stationary because GPS derives both from the velocity vector: Heading is course over ground relative to true north (not a magnetic compass), and is only valid while moving (above ~1 m/s), so walk a few meters to see it. In the Session recording panel, Time to first fix (TTFF) is how long the first valid position took after you pressed Start; Recorded fixes counts samples captured; and Best/Worst/Average accuracy summarize the horizontal accuracy across the whole run — ideal for certifying a GNSS receiver as pass/fail.
The GPS location viewer reads your device's geolocation — latitude, longitude, altitude, speed, heading, and accuracy — derived from a fused source that combines satellite signals (GPS/GNSS), Wi-Fi access point triangulation, cell-tower trilateration, and IP geolocation. Latitude and longitude are reported in decimal degrees (e.g., 40.7128, -74.0060 for New York). Altitude is in meters above the WGS-84 ellipsoid (not mean sea level). Accuracy is the 68% confidence radius in meters — a value of 10 means your true position is within 10 m of the reported point with ~68% probability. Speed is in meters per second and heading is in degrees clockwise from true north. The Web Geolocation API exposes all of these via navigator.geolocation.
GPS performance varies dramatically: a phone that worked perfectly may suddenly show 500 m accuracy after a firmware update, antenna damage, or chip recalibration. Testing reveals current accuracy (compare against a known landmark), time-to-first-fix (TTFF — should be 5–30 seconds with assisted GPS), satellite signal strength, and whether high-accuracy mode is actually engaging the GNSS chip versus falling back to coarse Wi-Fi positioning. Drivers, hikers, runners, and delivery workers all depend on consistent GPS — a degraded receiver causes wrong turn directions, missed pickup points, and faulty fitness data. Testing also reveals whether your browser or OS is silently fuzzing your location for privacy.
Coordinates are reported in decimal degrees (WGS-84 datum); 1° of latitude ≈ 111 km, 1° of longitude varies from 111 km at the equator to ~0 km at the poles. Altitude is in meters above the ellipsoid. Accuracy is the horizontal 68% radius in meters. Typical values: outdoor open sky 3–10 m (smartphone GPS), 5–30 cm (dual-frequency RTK), 5 m (single-frequency consumer GPS), 30–100 m (urban canyon with multipath), 100–1500 m (indoor or Wi-Fi-only). Speed accuracy is ±0.1 m/s when moving above 3 m/s, useless when nearly stationary. Heading is unreliable below 1 m/s because GPS computes heading from velocity vector direction, not from a compass.
Three effects degrade urban GPS. First, multipath: satellite signals bounce off buildings before reaching your phone, adding meters of phantom range and shifting your position. Second, signal blockage: tall buildings block half the sky, reducing visible satellites from 8–12 down to 3–4 and degrading geometric accuracy. Third, the chip falls back to Wi-Fi and cell-tower positioning indoors, which has 30–500 m accuracy depending on how well Google or Apple has mapped that location. Dual-band GNSS (L1 + L5) introduced in 2018 chips (Xiaomi Mi 8, Pixel 6+, iPhone 14 Pro+) cuts multipath error in half. To improve accuracy, step outdoors away from buildings, hold the phone with the antenna (top edge) facing the sky, and wait 30 seconds for satellite lock.
GPS altitude is referenced to the WGS-84 ellipsoid, which is a mathematical model of Earth's shape — not mean sea level (MSL). The difference (geoid undulation) varies from −105 m (south of India) to +85 m (Iceland), so even a perfect GPS fix may show altitude 50 m off from the topo map's MSL value. Apps that show altitude in 'meters above sea level' must add a geoid correction from the EGM96 or EGM2008 model. Additionally, vertical GPS accuracy is 1.5–3× worse than horizontal because satellites are mostly above (not around) the receiver, weakening the vertical solution. Barometric altimeters (in phones since iPhone 6) provide much better short-term altitude accuracy by sensing air pressure.
Modern operating systems fuse multiple positioning sources. GPS provides 3–10 m accuracy outdoors but takes 5–30 seconds for first fix and drains battery. Wi-Fi positioning matches the BSSIDs (router MAC addresses) you see against Google's or Apple's crowdsourced database of mapped routers, giving 5–40 m accuracy almost instantly. Cell-tower trilateration gives 100–1500 m accuracy as a coarse fallback. The OS picks the best source per query based on the requested accuracy level (PRIORITY_BALANCED_POWER vs PRIORITY_HIGH_ACCURACY on Android, kCLLocationAccuracyBest on iOS). On Wi-Fi-only iPads or in airplane mode, only Wi-Fi/IP geolocation is available. Modern fusion also incorporates Bluetooth beacons (iBeacon, Eddystone) and pedestrian dead reckoning for indoor navigation.
The W3C Geolocation API exposes navigator.geolocation with two methods: getCurrentPosition() for a one-shot fix and watchPosition() for continuous updates. Both require explicit user permission via the Permissions API, gated by HTTPS (insecure HTTP cannot access geolocation since Chrome 50 in 2016). The position object includes coords.latitude, longitude, accuracy, altitude, altitudeAccuracy, heading, and speed. The newer Geolocation Sensor API (Generic Sensor) offers similar data with finer event control but limited browser support. Note that browsers may add fuzzing or use a coarse-grained source if the user opts into 'approximate location' (iOS 14+, Android 12+) — typically rounding to the nearest city or 1 km grid for privacy.
GPS is the US-built constellation of 31 satellites operating since 1995, but modern receivers fuse signals from multiple GNSS constellations: GLONASS (Russia, 24 satellites), Galileo (EU, 30 satellites), BeiDou (China, 35 satellites), QZSS (Japan, 4–7 satellites, regional), and NavIC (India, regional). The WGS-84 datum is the global coordinate reference. Civilian L1 (1575.42 MHz) is the primary band; modern receivers also use L5 (1176.45 MHz) for better multipath rejection and dual-frequency ionospheric correction. Standards include ICD-GPS-200 (signal specification), NMEA 0183 / 2000 (data interchange), and ISO 19111 (geographic information reference). Civilian GPS accuracy is officially 7.8 m at 95% confidence, but real-world performance is usually better.
SENSORS13
GEOGRAPHY & MAPPING TOOLS19
WUTOOLS