- Google Timeline visualizer tools read exported JSON files and rebuild your travel history.
- Export first from Android, iOS, or Google Takeout before opening the visualizer.
- Keep files local when possible because location history can reveal routines and private places.
- Start with a short test to confirm the JSON structure before processing years of records.
- Filter by dates to inspect trips, places, activities, distance, and movement patterns.
google timeline visualizer how to use: Start Here
A Google Timeline visualizer is a browser or local utility that turns Google Maps Timeline JSON into an interactive map. Instead of relying on the discontinued web Timeline interface, you provide an export file and inspect the records on your own device.
The visualizer can recognize several Google location-history formats, including Records.json, monthly Semantic Location History files, Phone Timeline Export files, and supporting metadata such as Settings or TimelineEdits. Multiple JSON files can be loaded together when you want to combine exports.
Video Highlights:
- Exporting Google Timeline data for local visualization
- Checking whether the local file contains usable history
- Creating a short route video before a larger render
- Using date filters and camera profiles for focused results
Interactive Map
Explore individual points, paths, place visits, and activity segments on a map.
Year Filter
Narrow a large archive to one year or a specific travel period.
Local Processing
Keep exported location files in your browser or on your device instead of sending them to a third-party server.
Route Video
Convert selected history into an animated MP4 for private viewing or sharing.
| Capability | Best use | Important note |
|---|---|---|
| Individual points | Inspect exact recorded locations | Raw GPS points may contain noise |
| Place visits | Review stops and arrival details | Semantic data is needed for richer labels |
| Activity segments | Compare walking, driving, cycling, or transit | Depends on the export format |
| Year filtering | Explore long archives | Start with a smaller date range |
| Route video | Present a trip as an animation | Test a short render first |
Load one known trip or one calendar year before combining multiple files. A small test makes file-format problems easier to identify.
Export Google Timeline Data Correctly
The visualizer cannot reconstruct history without an export file. Before troubleshooting the map, confirm that Google Maps has actually stored or imported your Timeline data on the device. A fresh phone installation, app reset, or device upgrade may show little or no local history.
Google’s Timeline storage changed substantially before 2026. The web-based Timeline view was discontinued, and location history moved toward on-device storage. Older records may only exist in a backup, Google Takeout archive, or a previous export.
Check for Existing History
Open Google Maps and review the Timeline area on your phone. If the timeline is empty after changing devices or reinstalling the app, look for a backup or cloud history that can be imported before exporting again.
Export on Android
Open the relevant Android system settings, go to Location, select Location Services, open Timeline, and choose Export timeline data. Save the JSON files in a persistent folder such as Downloads.
Export on iOS
In Google Maps, tap your profile avatar, open Settings, choose Personal content, and select Export Timeline data. Store the resulting file securely in the Apple Files app.
Try Google Takeout
Visit Google Takeout and select Location History if that option is available for your account. Keep any existing archive because it may contain records no longer present on your phone.
Verify the JSON Files
Confirm that the export finished and that the files are not empty. If the visualizer reports no data, return to Google Maps and complete any available backup or import process before exporting again.
| Export method | Typical path | When to use it |
|---|---|---|
| Android phone | Settings → Location → Location Services → Timeline | Export current on-device Timeline data |
| iPhone or iPad | Google Maps → Settings → Personal content → Export Timeline data | Save an iOS Timeline export |
| Google Takeout | takeout.google.com → Location History | Search for older archived records |
| Existing backup | Google Maps Timeline backup or device storage | Restore history after a device change |
A useful export may include semantic segments, place information, paths, and activity types. A raw Records.json file can instead contain a large collection of coordinate points. Both are useful, but the display will be more descriptive when semantic information is present.
Make a secure backup of every exported JSON file before editing, renaming, or combining files. Location history is difficult to recreate after an archive is lost.
Choose a Private Visualization Workflow
Location history can expose your home, workplace, regular commute, family routines, and exact travel dates. Privacy should therefore guide the choice between a browser visualizer, a local application, and an optional cloud import.
The browser-based Google Timeline visualizer processes the selected files locally with JavaScript. Your files remain on the device while the tab is open, except when you deliberately choose an option such as saving the file to a cloud account. Map tiles may still be requested from the map provider so the route can be drawn.
| Workflow | Data handling | Strength | Limitation |
|---|---|---|---|
| Browser visualizer | File processed in the browser | Fast setup and no account required | Browser memory can limit very large imports |
| Android local app | JSON processed on the device | Can create offline route videos | Requires careful APK permission management |
| iOS web app | Runs through Safari and home-screen web app | Works within iOS restrictions | Requires a compatible Safari version |
| Optional cloud import | File uploaded only after choosing account save/import | Supports persistent account storage | Less private than local-only viewing |
For Android, an APK may require temporary permission to install from an unknown source. Use the official project release page, review the package before installation, and revoke the permission after setup. On iOS, a Safari-based web application can be added to the home screen instead of sideloading a native package.
Local-Only Review
Use the browser visualizer, avoid cloud-save controls, and close the tab after finishing.
Device Video Creation
Use a local rendering app when you want an MP4 without uploading the source JSON.
Persistent Import
Choose a cloud import only when you understand that the selected file will leave your device.
Local visualization protects the source file from routine server upload, but map tiles and any optional account-import action follow separate network paths.
Create a Map or Private Route Video
Once the JSON is ready, open the visualizer and choose the output that matches your goal. Interactive viewing is best for searching individual days and places. Video rendering is better for presenting a vacation, commute history, or multi-year travel pattern.
Start with a short date range. The visualizer’s summary panel can show the point count, distance, place count, and moving time for the selected period. These values help confirm that the chosen dates contain meaningful records before you begin a longer render.
Open the Visualizer
Launch the browser tool or local application. Choose the option to create or view a timeline, then select the exported JSON files from your device.
Set a Small Date Range
Select a single day, short trip, or limited year. Review the live summary for location points, distance, places, and moving time.
Preview the Route
Use the preview function to confirm that the map geometry appears in the expected region. A missing route usually indicates an empty, unsupported, or incorrectly selected file.
Select Camera Behavior
Choose Steady for a centered presentation, Fixed for a consistent altitude, or Dynamic for stronger scaling across changing distances.
Render the MP4
Create the video after the short test succeeds. The finished MP4 can be stored in the device media library for local viewing.
| Camera profile | Visual behavior | Recommended use |
|---|---|---|
| Steady | Maintains a central viewing area | Short trips and city movement |
| Fixed | Locks the viewing altitude | Consistent route comparisons |
| Dynamic | Scales more aggressively | Large journeys and changing regions |
| Balanced compression | Smooths gaps across long distances | Long flights or sparse GPS records |
For a multi-year archive, process one year or trip at a time first. Large files can take longer to parse and may use considerable browser or device memory. A staged workflow also makes it easier to identify the period that contains corrupted or unusually dense data.
A 10-second validation video is a practical first test. If the geometry, dates, and summary look correct, expand the range for the final render.
Troubleshooting and Data Checks
Most visualization problems are caused by one of four issues: the local database is empty, the wrong export file was selected, the data lacks semantic processing, or the chosen range is too large for the device or browser.
Use the following checks before repeating a long import:
| Symptom | Likely cause | Recommended fix |
|---|---|---|
| No locations appear | Empty export or wrong file | Check the JSON size and export again |
| “Raw locations only” warning | Semantic data is missing | Use semantic files or Phone Timeline Export when available |
| Timeline disappears after a phone change | History remains in a backup | Import the backup into Google Maps, then export |
| Browser becomes slow | Large file or many points | Filter by year and load fewer files |
| Route jumps unexpectedly | Sparse or inaccurate GPS records | Review points and use a narrower date range |
| Video fails during rendering | File access or memory issue | Test a shorter range and confirm permissions |
The visualizer can auto-detect several formats, but the display will differ depending on what the files contain. Records.json is typically the largest raw coordinate source. Semantic Location History files provide monthly place and activity context. Phone Timeline Export files may use structures such as semanticSegments and timeline paths.
Before You Render:
- Create a secure backup of every exported JSON file
- Confirm the selected date range contains location points
- Check whether semantic segments or place data are available
- Run a short preview before processing a large archive
- Review privacy settings before saving or uploading any file
For a large archive, use year filters and batch processing instead of loading every file immediately. The referenced visualizer documentation describes testing with more than 630,000 points across 15 or more years, while a 170 MB file may take roughly 20–30 seconds on a modern computer. Actual performance depends on the browser, device memory, file structure, and map workload.
If a one-day export fails, changing camera settings will not solve the underlying problem. Verify the file, format, and local history before increasing the date range.
Google Timeline Visualizer FAQ
The best workflow is export, verify, visualize locally, and only then create a larger map or video. The answers below cover the most common questions about using a Google Timeline visualizer in 2026.
Q: How do I use a Google Timeline visualizer?
Export Google Timeline JSON from Android, iOS, or Google Takeout, open the visualizer, and drop or select the files. Use the year or date filters to inspect routes, places, activities, distance, and moving time.
Q: Can I view Google Timeline without Google Maps on the web?
Yes. After exporting your JSON files, load them into a compatible browser visualizer. The map and timeline can be explored without signing in to a Google account, provided you have a usable export.
Q: Why does my visualizer show no data?
The export may be empty, the wrong JSON may be selected, or the local Timeline database may not have been restored after a device change. Check the file, import any available backup into Google Maps, and export again.
Q: Is local visualization private?
Browser-based visualization can keep the selected file on your device while it is processed. Avoid optional cloud-save controls if you want local-only handling, and remember that map tiles may still be requested to display the map.
For additional context, consult the Google Timeline Visualizer web tool to review supported formats, local browser processing, year filters, and the distinction between interactive maps and route video creation.
Preserve your exports, begin with a short date range, and keep the first visualization local. Expand to multi-year maps or videos only after the data and privacy workflow are confirmed.