- Google Timeline Visualizer turns exported location JSON into an interactive map and calendar view.
- Export first from Google Maps, Google Takeout, or your phone’s Timeline settings.
- Privacy check matters because local browser tools can process files without sending them to a server.
- Format support includes newer phone exports, Semantic Location History, and raw Records.json files.
- Video workflow lets you preview a journey, select dates, and render a shareable MP4 locally.
google timeline visualizer tutorial: What It Does
This google timeline visualizer tutorial focuses on the practical workflow for viewing exported location history without relying on the discontinued web Timeline experience. The visualizer reads files you select, detects supported formats, and displays routes, place visits, movement segments, and calendar-based activity on an interactive map.
The browser visualizer is designed for exploration. You can drop one or more JSON files into the tool, choose a year, inspect individual points, and compare movement patterns across different periods. Multiple files can be combined when your export contains separate monthly records or data from more than one export method.
Interactive Map
Explore location points, routes, place visits, and activity segments on an OpenStreetMap-based map.
Format Detection
Load newer phone exports, Semantic Location History files, or raw Records.json data without manually converting each file.
Privacy-First Viewing
Visualization runs in the browser, so selected files can remain on your device while you inspect them.
| Feature | Best Use | Practical Result |
|---|---|---|
| Year filter | Reviewing long-term movement | Focus on one year instead of loading every visible period at once |
| Route display | Following trips and commutes | See how locations connect across a selected time range |
| Place visits | Finding forgotten locations | Review arrival and departure details where available |
| Activity segments | Comparing walking, driving, cycling, and transit | Understand how each journey was recorded |
| Multi-file loading | Combining export formats | Inspect monthly files or separate data sources together |
Start with a small month or year file when testing the visualizer. Once the format loads correctly, add larger exports and use the year filter to keep navigation responsive.
Export the Right Google Timeline Data
Before using the visualizer, create a local copy of your Timeline data. The exact menu names can vary by device, but the export should produce JSON data that the tool can read. Keep the original file unchanged, because the visualizer works from the selected copy and does not require you to edit the source manually.
On Android, open the phone’s settings and look for the location services and Timeline area. Use the export option, then save the JSON file in a recognizable folder such as Downloads. On iPhone, use Google Maps settings and the personal content area to locate the Timeline export option. Google Takeout may also provide Location History files, although the resulting structure can differ.
| Export Method | Typical Location | Useful Output |
|---|---|---|
| Android phone export | Phone Settings → Location → Location Services → Timeline | Newer phone Timeline JSON |
| iPhone export | Google Maps → Profile → Settings → Personal Content | Timeline JSON for browser viewing |
| Google Takeout | Takeout export for Location History | Records.json, monthly semantic files, or metadata |
| Timeline backup restoration | Google Maps restoration flow | Restored history that can be exported again |
File Types You May Encounter
The visualizer can recognize several common structures. Newer phone exports may include semanticSegments and timeline paths. Older Semantic Location History exports commonly use monthly filenames such as 2022_APRIL.json, while raw records use E7 coordinate values and may be substantially larger.
Settings and TimelineEdits files can contain supporting metadata. If you have multiple compatible files, load them together so the tool can combine the available history. Avoid renaming internal JSON fields unless you understand the format, because unnecessary edits can make a valid export harder to process.
| File Type | Contents | Recommended Handling |
|---|---|---|
| Phone Timeline export | Semantic segments and timeline paths | Use directly in the visualizer |
| Semantic Location History | Visits, addresses, and activity segments | Load monthly files together when needed |
| Records.json | Raw GPS points in E7 format | Use for detailed history; expect larger processing time |
| Settings or TimelineEdits | Supporting metadata and edits | Keep with the export for reference |
Do not overwrite your exported JSON while troubleshooting. Make a backup before combining files, moving them between devices, or testing a different viewer.
Step-by-Step Loading and Filtering Workflow
Use this workflow to move from an untouched export to a readable map. The process is intentionally local: you choose the files, select the time period, and then inspect the resulting map and calendar details.
Prepare a Local JSON File
Locate the exported Timeline JSON on your phone or computer. If the export contains monthly files, place them in one folder and keep a separate backup copy.
Open the Visualizer
Open the browser-based Google Timeline Visualizer and drop one or more JSON files into the upload area. The tool detects supported formats automatically.
Choose a Year or Time Range
Select the year you want to inspect. Start with a focused period when working with a large export, then expand the range after the map finishes processing.
Inspect Routes and Visits
Review the moving and stationary portions of the map, open individual points, and compare place visits with recorded activity types such as walking, driving, cycling, or transit.
Repeat with Other Files
If a period is missing, load another compatible file or export source. Compare the result without changing the original JSON structure.
The visualizer is useful for both broad and detailed review. A year filter shows how movement changed over time, while point-level inspection helps identify specific visits. For large files, browser performance depends on the computer and file size. Processing in batches can help maintain responsiveness when the export contains hundreds of thousands of points.
| Review Goal | Filter Choice | What to Check |
|---|---|---|
| Annual movement pattern | One calendar year | Major routes, travel density, and recurring commutes |
| Single trip | Exact days or a short month range | Route continuity, stops, and travel mode |
| Forgotten place | Narrow date range | Place name, arrival time, departure time |
| Data quality review | Several nearby dates | Gaps, isolated points, or implausible jumps |
| Format comparison | Same period from separate files | Differences between raw records and semantic segments |
Load, filter, inspect, and only then combine larger files. This makes it easier to identify whether a missing period comes from the export itself or from the selected filter.
Privacy, Permissions, and Map Tiles
Privacy is a central reason to use an independent timeline viewer. Browser-based visualization can keep the selected JSON on your device while JavaScript processes the data. Closing the browser tab removes the active session, unless you intentionally use an optional cloud import or account-saving feature.
No Google sign-in is required for the local viewing workflow. The visualizer reads only the files you choose, rather than accessing your Google account or encrypted Timeline backup. If your history vanished after a phone change or reset, restore it in Google Maps first and export a fresh JSON file. A third-party visualizer cannot directly access Google’s encrypted backup.
The map itself may request basemap tiles from a tile provider. Those requests can reveal the areas currently being viewed to that provider, even though the Timeline JSON remains local. Review the tool’s privacy explanation before loading sensitive data, and cancel if the network behavior does not fit your needs.
| Data or Permission | Local Visualizer Behavior | Why It Matters |
|---|---|---|
| Google account sign-in | Not required | The tool cannot use sign-in to retrieve Timeline history |
| Selected JSON file | Read locally in the browser | The file can remain on your device during visualization |
| Encrypted Google backup | Not directly accessible | Restore through Google Maps before exporting again |
| Basemap tiles | Requested for visible map areas | Tile providers may see viewed regions |
| Optional cloud import | Upload occurs only after choosing that action | Treat it separately from local browser viewing |
If Timeline Data Is Missing
Check your phone, older exports, and available restoration options before assuming the history is gone. The visualizer can display data you still possess, but it cannot recreate points that were never exported or preserved.
Privacy and Data Check:
- Keep an untouched backup of every exported JSON file
- Confirm the visualizer is processing files locally before loading sensitive data
- Review basemap and tile-provider disclosures
- Avoid optional cloud import unless you want the file stored for that service
- Restore missing Google Maps history before creating a new export
A visualizer can read an export, but it cannot restore Google’s encrypted Timeline backup or recover points that are absent from your saved files.
Turn a Timeline Into a Travel Video
After reviewing your routes, you can use a companion Timeline Visualizer workflow to create an animated travel video from the same JSON export. Choose a month range or exact dates, select camera behavior, preview the journey, and render an MP4 on the device.
The video workflow supports square, portrait, and landscape presets, with square output available in 480p, 720p, and 1080p options. Journey duration can be customized from 10 to 300 seconds. Longer renders may take more time and storage, so keep the browser tab or application available while the file is being created.
| Video Setting | Available Choice | Best Use |
|---|---|---|
| Date selection | Month range or exact dates | Full-year recap or a short trip |
| Camera movement | Fixed, steady, or dynamic behavior | Stable overview or more active local following |
| Duration | 10–300 seconds | Short social clip or slower travel recap |
| Output shape | Square, portrait, landscape | Social feeds, phone viewing, or widescreen playback |
| Resolution | 480p, 720p, 1080p presets | Faster drafts or higher-quality final exports |
Rendering Steps
- Open the video creation flow and choose the Timeline JSON file.
- Select the month range or exact trip dates.
- Confirm the title template and choose a camera preset.
- Preview the animated map and restart the preview if you need to review it again.
- Create the MP4 and keep the tab or app open during rendering.
- Watch, share, or save the completed file in your preferred location.
Long flights and sparse routes may be interpolated along a great-circle path to keep the camera movement smooth. Local movement can remain within a stable central map area before the camera follows the marker. These behaviors affect animation timing and camera motion rather than changing the original JSON file.
On Android, completed videos are added to the in-app video library and may be saved under the Timeline Visualizer movie folder. Older Android versions may use a system save picker. If rendering is canceled, the incomplete output is removed. Completed entries can retain a thumbnail, title, period, duration, and creation date.
Preview the shortest useful date range first. Once the camera movement and title look right, render the longer recap at the resolution and orientation you plan to share.
Google Timeline Visualizer FAQ
Q: What is Google Timeline Visualizer?
It is a browser-based tool that reads exported Google Timeline JSON files and displays routes, points, place visits, activity segments, and year-based movement patterns on an interactive map.
Q: Can I view Google Timeline without Google Maps?
Yes. Export the Timeline data first, then load the JSON into the visualizer. The tool does not need Google account sign-in to inspect the file you select.
Q: Which Google Timeline files are supported?
Common supported formats include newer phone exports with semanticSegments and timeline paths, monthly Semantic Location History files, and raw Records.json files containing E7 coordinates.
Q: Is my Timeline JSON uploaded automatically?
The local browser workflow is designed to process selected files on your device. Review the privacy notice for basemap requests, and remember that any optional cloud-saving action is separate from local viewing.
For additional format notes and the browser viewer, see the Google Timeline Visualizer tool page. Use the page to confirm the current loading interface, supported export examples, and privacy details before importing a large archive.
Use local viewing for exploration, preserve original exports for future tools, and create a separate video copy when turning a journey into an MP4.