- Google Timeline Visualizer reads exported JSON and displays routes, places, and activity segments.
- Privacy first: Browser-based processing keeps files on your device unless you choose an optional cloud import.
- Best workflow: Export your data, validate a short date range, then render larger trips or yearly archives.
- File support: Records.json, semantic history files, and newer phone timeline exports can be combined.
What Google Timeline Visualizer Does
Google Timeline Visualizer is a browser-based way to explore Google location history after the web version of Google Maps Timeline moved to on-device storage. Instead of relying on a Google account view, you provide exported JSON files and inspect the data on an interactive map.
The tool can show individual location points, connected paths, visited places, and activity segments. Year filters make large archives easier to browse, while day-level details help you examine a specific trip or commute. It also supports multiple files at once, which is useful when your history is split across monthly exports or different Google Timeline formats.
The primary privacy model is local processing. Files are parsed in your browser with JavaScript, so the location history does not need to be uploaded to a third-party visualization server. Close the browser tab when you finish exploring. An optional cloud-saving action is separate and should only be used if you intentionally want to import the file into a hosted account.
Video Highlights:
- Export Google Timeline JSON before attempting visualization.
- Check that the local file contains usable route or place data.
- Validate a short render before processing a large archive.
- Use date ranges and camera profiles to create focused travel videos.
Interactive Map
Explore location points and paths on an OpenStreetMap-based map without needing the Google Maps web timeline.
Timeline Filters
Filter by year and inspect movement, stationary periods, places, and activity segments.
Route Video
Turn selected timeline data into an offline MP4 with date controls and adjustable camera behavior.
Use a small date range first. A short validation run confirms that the JSON structure, map rendering, and browser permissions are working before a longer analysis.
Supported Google Timeline JSON Formats
Google exports may contain different structures depending on the device, export method, and age of the archive. You do not need to manually convert every file before testing the visualizer. The tool can auto-detect several common formats and combine multiple uploads.
Records.json generally contains raw GPS records in E7 coordinate format. It can be the largest file because it may include many individual location pings. Semantic Location History files are commonly organized by month and add place visits, addresses, and activity segments.
Newer phone exports may use fields such as semanticSegments and timeline paths. Additional files, including settings and timeline edit data, can provide supporting metadata. If the map loads but shows limited detail, the export may contain raw points without the semantic processing used for places and movement types.
| File or Format | Typical Content | Best Use |
|---|---|---|
| Records.json | Raw GPS points in E7 format | Detailed path inspection |
| Semantic history | Monthly places and activity segments | Visits, addresses, and movement types |
| Phone Timeline Export | semanticSegments and timeline paths | Newer Android or iOS exports |
| Settings or edits | Supporting metadata | Preserving timeline context |
When several files belong to the same archive, upload them together. Combining monthly semantic files with raw records can create a more useful view than relying on only one file. Large datasets may take longer to parse, especially when the archive spans many years or contains hundreds of thousands of points.
If an export contains zero records or the visualizer shows no route, check the Google Maps Timeline backup and local device data before changing visualization settings. A filter cannot restore data that was never exported.
Locate the Export
Gather the JSON files from your phone export or Google Takeout archive. Keep the original files unchanged so you have a clean backup for later tests.
Upload Related Files
Drop one file or a group of matching files into the browser tool. Multiple files can be combined when your timeline is divided by month or export format.
Confirm the Date Range
Select a year or narrower period and check whether the map, point count, places, and movement summary update as expected.
Inspect the Details
Click routes and places to compare raw movement with semantic activities. Look for gaps before interpreting the timeline as a complete record.
How to Export Timeline Data Safely
Google Timeline data contains sensitive information, including home locations, workplaces, regular commutes, and travel routines. Treat JSON exports like private records. Store them in a protected folder, avoid sending them through public file-sharing services, and remove temporary copies when they are no longer needed.
On Android, the export path described for the current device workflow is Google Maps or system location settings, followed by the Timeline panel and an export option. On iOS, use Google Maps settings, open Personal Content, and select the timeline export function. Menu labels can vary slightly by application version, so check the current interface on the device that owns the data.
The important distinction is between local visualization and optional cloud storage. Opening the file in a browser-based visualizer is designed to keep processing on the device. Selecting a cloud-saving feature is a separate decision because it uploads the file for account import.
| Privacy Choice | Data Location | Recommended Practice |
|---|---|---|
| Local browser viewing | Your device and browser session | Use for private inspection |
| Optional cloud import | A hosted account after explicit action | Select only when permanent account storage is wanted |
| Shared JSON file | Any recipient or service you send it to | Avoid unless sensitive locations are removed |
| Temporary export copy | Local storage or downloads folder | Delete after confirming a protected backup |
The Google Timeline Visualizer web tool describes browser-side processing and identifies the optional account-saving action separately. Review the interface before selecting any import or save control.
Privacy and Backup Checklist:
- Keep an untouched copy of the original JSON export
- Store working files in a private local folder
- Confirm whether processing is local before opening sensitive data
- Avoid optional cloud saving unless account import is intentional
- Delete unnecessary duplicate exports after verification
Make one protected backup first, then use a duplicate working copy for visualization. This preserves the original archive if a file is renamed, moved, or accidentally overwritten.
Create a Timeline Route Video
The same timeline data can be used for an animated route video. A short test render is the most reliable way to catch missing paths, unsupported data, or file-access problems before starting a long export.
Begin with a minimal duration, such as a 10-second preview, and use a narrow date range. Confirm that the map geometry appears and that the selected period contains movement data. Once the preview works, expand the date range and choose a camera style that matches the story you want to tell.
| Setting | What It Controls | Practical Starting Choice |
|---|---|---|
| Date range | The period included in the render | One trip or one calendar year |
| Duration | Length of the final animation | Short preview before a longer render |
| Steady camera | Central movement with a calmer frame | Everyday routes |
| Fixed camera | More consistent altitude | Familiar regional paths |
| Dynamic camera | Stronger scaling and movement | Large travel distances |
| Balanced compression | Smoother handling of long gaps | Flights or sparse GPS data |
The live summary below the date selectors helps verify the selected range. Check the location point count, total distance, and movement duration before committing to a full render. If the summary is empty, adjust the dates or inspect whether the export contains semantic timeline information for that period.
For long archives, process one year or journey at a time. This makes errors easier to isolate and creates smaller, more focused videos. A final zoom-out sequence can reveal the complete route, while a steady or fixed profile may work better when the goal is to document daily movement without aggressive camera changes.
A successful map preview does not prove that every historical period is present. Compare the selected dates with the summary panel and inspect several points before rendering a large archive.
Troubleshooting and Data Review
Most problems come from one of four areas: an empty local database, an incomplete export, a date filter that excludes the available data, or a file that contains raw points without semantic labels. Resolve the simplest possibility first by checking the original JSON and widening the date range.
If the visualizer reports only raw locations, the file may not include Google’s place and activity interpretation. The map can still display coordinate data, but you may not see the same visit names, movement categories, or structured segments available in semantic history exports.
A very large file may also require patience during parsing. Batch processing can help keep the browser responsive, but performance depends on the device, browser, file size, and number of points. Split a multi-year archive into smaller year-based groups if the interface becomes difficult to use.
| Symptom | Likely Cause | Recommended Fix |
|---|---|---|
| No points appear | Empty export or wrong date filter | Check the file and widen the selected period |
| Only raw locations appear | Semantic fields are missing | Use semantic history or phone timeline files when available |
| Map loads slowly | Large archive or many points | Process one year or trip at a time |
| Route has long gaps | Sparse GPS data or missing records | Review adjacent dates and avoid assuming continuous travel |
| Video preview fails | File access, format, or browser issue | Test a smaller range and confirm the JSON opens correctly |
Use a structured review process rather than changing several settings at once. First confirm the file, then the date range, then the map output, and finally the video configuration. This keeps the cause of each problem easier to identify.
A blank period may represent missing data, disabled location history, an incomplete migration, or a filter mismatch. Treat gaps as evidence to investigate, not proof that no travel occurred.
Google Timeline Visualizer FAQ
Q: What is Google Timeline Visualizer used for?
It lets you explore exported Google Timeline JSON in a browser. Depending on the file format, you can view GPS points, routes, visited places, activity segments, year filters, and day-level details.
Q: Does the visualizer upload my location history?
The browser visualization workflow is designed to process files locally on your device. An optional save-to-account action is different because it uploads the file for cloud import, so use that control only when you intend to store the data remotely.
Q: Which Google Timeline files can I open?
Common supported formats include Records.json, monthly Semantic Location History files, newer phone timeline exports with semanticSegments, and related settings or timeline edit files. Multiple files can be uploaded together.
Q: Why is my Google Timeline missing older history?
Google moved Timeline from the web to on-device storage. Older records may not be available on the current device unless they were backed up or exported earlier. Check phone backups, Google Takeout archives, and existing JSON copies.
A timeline video can reveal the same sensitive patterns as the original JSON. Review locations, dates, and camera coverage before publishing or sending the finished MP4.