- Google Timeline Visualizer turns exported location JSON into an interactive map or travel video.
- Privacy first: Browser-based processing keeps files on your device during normal visualization.
- Export carefully: Android, iOS, and Google Takeout can produce different JSON structures.
- Start small: Test a short date range before rendering years of travel history.
- Check backups: Missing local data may require importing an available Timeline backup first.
Google Timeline Visualizer Overview
Google Timeline Visualizer is a privacy-focused tool for reading Google location-history exports that are difficult to interpret as raw JSON. Instead of browsing dense coordinate records manually, you can load the files into a browser-based map, filter by year, inspect places, and review travel activity.
The tool supports multiple export styles, including raw GPS records, monthly Semantic Location History files, and newer phone exports containing semanticSegments and timeline paths. Multiple files can be loaded together, allowing separate exports to be combined into one timeline view.
Video Highlights:
- Export Timeline data from Android or iOS before importing it.
- Process location files locally rather than sending them to a third-party server.
- Validate a short route before creating a larger travel video.
- Adjust dates, camera behavior, and route presentation for clearer results.
The web visualizer uses an interactive OpenStreetMap-based map and can display individual points, paths, place visits, and activity segments. A year filter helps narrow large archives, while the data summary can show location-point counts, distance, places, and moving time for the selected period.
| Capability | What it provides | Best use |
|---|---|---|
| Interactive map | Routes, points, visits, and activity segments | Exploring daily movement |
| Year filter | A focused view of one calendar year | Comparing travel periods |
| Multi-file loading | Combines compatible JSON exports | Rebuilding a larger archive |
| Route video workflow | Converts selected history into an MP4 | Creating a travel recap |
| Local processing | Keeps standard visualization in the browser | Reducing unnecessary data exposure |
Use a small, known trip or a single month for your first test. This confirms that the export format, map rendering, and date filters work before you load a large archive.
Export and Prepare Your Timeline Data
The quality of the visualization depends on the files you provide. A blank map does not always mean the visualizer failed; it can indicate that the phone has no locally available history or that the selected export contains a different data structure.
On Android in 2026, the relevant export path is generally found through Google Maps and the device’s Timeline settings. Open Google Maps, enter the settings area, locate Location Services, select Timeline, and choose the option to export Timeline data. Save the resulting JSON files in a persistent local folder such as Downloads.
On iOS, open Google Maps, access your profile settings, enter Personal Content, and select Export Timeline data. Save the export in the Apple Files app so it remains easy to locate when you open the browser visualizer.
| Export route | Typical location | Recommended action |
|---|---|---|
| Android | Google Maps settings, Location Services, Timeline | Export JSON to a persistent device folder |
| iOS | Google Maps settings, Personal Content | Save JSON in the Files app |
| Google Takeout | Location History archive | Extract the JSON files before loading |
| Existing backup | Google Maps Timeline backup flow | Import it if local Timeline data is missing |
Confirm the Data Exists
Open Timeline on your phone and check whether the expected dates and places are visible. If the timeline is empty, locate an available encrypted backup or older archive and import it before exporting again.
Export the JSON Files
Use the platform-specific Timeline export option. Keep the original files unchanged, and save a second working copy if you plan to test multiple visualizers or command-line tools.
Organize the Archive
Place related files in a clearly named local folder. Separate raw records, monthly semantic files, and phone exports only if you need to troubleshoot their behavior independently.
Inspect Without Editing
Check the filenames and approximate file sizes, but avoid manually changing coordinates or keys. Editing the structure can prevent automatic format detection.
If an export reports zero data, stop before rendering. Return to Google Maps and verify that a backup or local import has restored the history. Repeating the export without restoring the underlying data is unlikely to produce a useful file.
Location history can reveal home addresses, workplaces, routines, and travel dates. Keep an untouched local copy, avoid sharing the files publicly, and remove exports from temporary folders when your work is finished.
Understand File Formats and Privacy Controls
Google Timeline exports are not always identical. The visualizer can auto-detect several structures, but understanding the differences makes troubleshooting easier and helps you choose the right files for a specific question.
Records.json usually contains raw GPS records in E7 coordinate format. It can be large because it stores frequent location pings. Semantic Location History files are organized by month and can include place visits, addresses, and activity segments such as walking, driving, cycling, or transit.
Newer Phone Timeline Exports may use semanticSegments and timeline paths. Settings and TimelineEdits files can provide additional metadata. Uploading multiple compatible files can help reconstruct a broader history, but duplicate records may make the result harder to read.
Raw GPS Records
Best for detailed point-by-point movement. These files can be large and may require more browser memory during processing.
Semantic History
Best for place visits, addresses, and activity categories. Monthly files are useful when you want a focused period.
Phone Timeline Export
Best for newer Google Maps exports with semantic segments and route paths. Keep the original structure intact.
| File type | Main contents | Strength | Limitation |
|---|---|---|---|
| Records.json | Raw GPS pings | Detailed movement trail | Often the largest file |
| Semantic Location History | Visits and activity segments | Easier to interpret | Usually divided by month |
| Phone Timeline Export | Semantic segments and paths | Matches newer phone data | Structure may vary by export |
| Settings or TimelineEdits | Metadata and edits | Adds context | Not usually sufficient alone |
The standard browser workflow is designed to process files locally with JavaScript. Your data should remain on the device during ordinary visualization and should disappear from the browser session after the tab is closed. Treat optional cloud-import features separately: if a feature explicitly saves data to an account, review that action before confirming it.
The safest workflow is local export, local visualization, and local storage of the finished video. Do not select an account-import or cloud-save option unless you understand what information it sends and why.
Create a Map or Travel Video
Once the files load successfully, begin with a controlled test. Select a short date range, review the map geometry, and confirm that the summary matches the period you intended to study. This prevents a multi-year render from consuming time on a malformed or empty export.
The visualizer can show a selected year and provide a summary such as distance, places, moving time, and location-point totals. Use those indicators to check whether the chosen range contains meaningful data.
| Setting | Practical choice | Why it matters |
|---|---|---|
| Date range | One trip, month, or year | Limits clutter and processing time |
| Preview length | Short validation preview | Confirms geometry before a long render |
| Camera profile | Steady, Fixed, or Dynamic | Controls how the route is framed |
| Route scale | Focused or broad coverage | Balances local detail with full-trip context |
| Output format | Local MP4 when available | Creates a portable travel recap |
For a video workflow, a native visualizer app or compatible local renderer can convert the exported JSON into an MP4. On Android, only use a release package from the project’s official GitHub release page, and revoke temporary unknown-app installation permission after setup. On iOS, a supported browser-based web app may provide the practical route for running the tool.
Load the Export
Open the visualizer and choose the JSON files from your local folder. Accept the privacy notice only after confirming that the file-processing behavior matches your expectations.
Select a Small Range
Choose a short trip, a month, or a single year. Review the summary panel for point count, distance, places, and moving time.
Preview the Route
Run a short preview and verify that the route follows plausible geography. Stop if you see a blank map, severe jumps, or an unexpected date range.
Choose Camera Behavior
Use Steady for a calmer presentation, Fixed when you want consistent altitude, or Dynamic when the route covers very different scales.
Render the Final Video
Start the full render only after the preview looks correct. The completed MP4 can be saved to the device’s local media library for private viewing.
A “raw locations only” warning generally means the export lacks semantic processing. The route may still be useful, but place names, activity categories, or visit details can be limited. Long archives may also need more memory and processing time, so narrowing the date range is often the most effective first adjustment.
Preview the smallest useful range first. A clean short render gives you more confidence than committing a large archive before checking route geometry and date filtering.
Troubleshooting, Checklist, and FAQ
Most setup problems fall into four categories: missing local data, unsupported or incomplete exports, incorrect date filters, and privacy settings that were misunderstood. Work through the checks below in order rather than changing several variables at once.
Before You Render:
- Confirm Timeline data appears on the phone or in an available backup
- Save an untouched copy of every exported JSON file
- Test one short date range before loading a large archive
- Verify the map route and summary statistics match the selected dates
- Review whether any optional cloud-save feature is enabled
| Symptom | Likely cause | Recommended fix |
|---|---|---|
| Empty map | No local history or empty export | Restore an available backup, then export again |
| Raw locations only | Semantic data is missing | Use a semantic export if available |
| Browser becomes slow | Large file or many points | Filter by year or process smaller batches |
| Route jumps unrealistically | Outlier coordinates or missing points | Check the source export and use a shorter range |
| No expected places | Wrong file type or date filter | Load semantic files and verify the calendar selection |
The Google Timeline Visualizer tool provides the browser interface for loading JSON, filtering years, and examining routes. Its documentation also explains the difference between raw records and semantic location files, which is useful when an export behaves unexpectedly.
Q: What is Google Timeline Visualizer used for?
It converts exported Google Timeline JSON into an interactive map with routes, points, place visits, activity segments, and year-based filtering. Compatible local workflows can also turn selected history into a travel video.
Q: Does the visualizer require Google Maps to stay open?
No. After you export the data, the visualizer can read the local JSON independently. You can inspect the archive without relying on the discontinued web timeline interface.
Q: Why is my map empty after importing a file?
The device may not contain local Timeline data, the export may contain no records, or the selected dates may not match the file. Check the phone timeline, restore a backup if available, and test a broader date range.
Q: What is the safest way to handle location-history files?
Keep the original export locally, use browser or desktop processing that does not require uploads, avoid public sharing, and review any optional account-import feature before enabling it.
Treat every Timeline export as sensitive personal data. Build your workflow around local files, verify each date range, and create shareable videos only after removing destinations or periods you do not want others to identify.