100% private — files never leave your browser
Google Timeline to GPX Converter
Turn your Google Timeline history — a Records.json from Takeout, a monthly Semantic Location History file, or the older Location History.json — into a universal .gpx track. Movement segments become track segments, place visits are skipped, and the whole extraction happens locally in your browser: a location history is the most sensitive file you own, and it never leaves your device here.
How to convert Google Timeline to GPX
- 1
Export from Google Takeout
Visit takeout.google.com, deselect everything, then select 'Location History' (recorded as Records.json / Semantic Location History). Choose your export type and create the archive.
- 2
Drop the JSON here
Unzip the Takeout archive and drop the Records.json file — or any monthly Semantic Location History JSON — onto the box above. The schema is detected automatically.
- 3
Preview the track
Your movement history renders on the map with distance and time stats, so you can confirm the extraction looks right before downloading. Each activity becomes its own track segment.
- 4
Download the GPX
Save the .gpx and open it in any mapping app, GIS tool or GPS viewer. The JSON original stays untouched on your disk.
Why convert your Timeline history to GPX?
Google is winding down the old Timeline, and people are downloading their history before it disappears. What arrives from Takeout is JSON — Records.json in recent exports, month-by-month Semantic Location History files, or the older all-in-one Location History.json that years of users still have sitting in a downloads folder — and almost nothing outside Google displays it. GPX is the opposite: every mapping app, GIS tool and GPS viewer on earth opens it. Converting turns a soon-orphaned archive into tracks you can actually see, keep and share.
The uses follow quickly: map a year of walking commutes, recover the route of a memorable trip that no fitness app recorded, visualize everywhere you traveled, or simply keep a durable, vendor-independent copy in the industry-standard format before the source goes dark.
What the converter extracts (and what it deliberately skips)
All three export schemas are supported and detected automatically. Movement is what becomes track: each activity segment's path — timelinePath point strings or simplifiedRawPath E7-integer points in the newer schemas, or the plain E7 location stream in the old one — is converted to GPX track points with timestamps, one track segment per activity (the legacy export arrives as one continuous segment, re-ordered oldest-first because Google writes it backwards). Segments are ordered by start time, missing-value placeholders and consecutive duplicate points are cleaned, and the track is named from its first day.
Place visits (shops, homes, hotels) are stationary by definition — they carry no movement, so they are skipped rather than becoming a scribble of stacked points. The same honesty applies to detail: Google's data is synthesized from coarse sources, so the track is a faithful rendering of what Google recorded, not a guarantee of where you actually walked. Expect city-block-scale accuracy, not centimeters.
A note on file size
A long history can make Records.json (or the old Location History.json) very large — hundreds of megabytes. The parser runs in a background worker on your device and handles big files, but memory is finite: if your export is huge and the page struggles, export by month instead (the Semantic Location History option) and convert the smaller files one at a time. Same history, friendlier chunks.
And it bears repeating because it matters most with this file: nothing is uploaded. A Timeline export contains home, work, and everywhere between. This page processes it in your browser, and you can verify that in the network inspector.
Your files never leave this browser
This tool — like every tool on this site — runs entirely as client-side JavaScript. The file you drop is parsed in a Web Worker on your own device, converted in memory and handed straight back to you as a download. There is no upload endpoint, no server-side conversion service and no temporary storage: you can watch the network tab in your browser's developer tools and confirm that no file bytes are transmitted anywhere.
That matters more with fitness data than with most files. A GPS track is a precise log of where you were, at what time, and how hard your heart was working — home address, training habits, favorite routes and race schedule all in one file. Keeping conversion on-device means third-party converters never get a copy of that log, and the tool keeps working identically on a plane, in a basement, or anywhere else without signal.
Frequently asked questions
All three come from Takeout's Location History. Recent exports ship a single Records.json for the whole account; the older (and still available) format is one JSON file per month under 'Semantic Location History'; and exports from a few years ago produced an all-in-one Location History.json with a plain location stream. This converter reads all three — the structure is detected from the file contents, so just drop whichever you have.