- google timeline visualizer turns exported location files into an interactive browser map.
- Best starting point: Export Timeline data from Google Maps on your phone.
- Supported files: Records.json, Semantic Location History, and newer Phone Timeline Export files.
- Privacy focus: Browser-based processing keeps files on your device during visualization.
- Main workflow: Export, upload, filter by year, inspect routes, and review place visits.
What Is a Google Timeline Visualizer?
A google timeline visualizer is a browser-based tool for opening location-history exports without relying on the former web version of Google Maps Timeline. Instead of viewing data only inside the Google Maps app, you can load exported JSON files and inspect routes, stops, activity segments, and visited places on an interactive map.
This approach is useful when you want to review several years of movement history, search for forgotten destinations, or preserve access to data that is no longer conveniently available on the web. The visualizer described in the reference material supports multiple Google export formats and can combine several files in one session.
Start with a copy of your export files. Keep the original archive unchanged so you can retry processing, compare formats, or move the data to another tool later.
Interactive Map
Inspect recorded points, paths, stops, and place visits on a map interface. Zooming and panning help separate dense travel areas.
Calendar Filtering
Select a year and review location activity over a chosen period instead of loading every historical movement at once.
Privacy-Oriented Viewing
Browser-side visualization is designed to keep uploaded files on your device while the page is open.
The visualizer can reveal several types of information:
- Travel patterns from commutes, road trips, walking routes, and international travel.
- Place visits with arrival and departure details when those records exist.
- Activity types such as walking, driving, cycling, and transit segments.
- Year-by-year changes that show how daily movement patterns developed.
- Forgotten memories involving restaurants, parks, neighborhoods, and other locations.
A practical entry point is the Google Timeline Visualizer, which provides a file-drop interface and explains how its local visualization process works.
| Capability | What You Can Review | Best Use |
|---|---|---|
| Map view | Points, routes, stops, and paths | Exploring where you traveled |
| Year filter | Location activity by year | Comparing different periods |
| Place details | Visits and timing information | Recalling specific destinations |
| Activity segments | Walking, driving, cycling, or transit | Understanding how a trip unfolded |
| Multi-file loading | Several JSON exports together | Combining older and newer archives |
Google Timeline Export Formats Explained
Google Timeline data may appear in different JSON structures depending on how and when it was exported. Recognizing the file type helps you choose the right files and understand why one archive may contain more detail than another.
The visualizer can auto-detect the formats listed below. If you have files from different export methods, multiple files can be loaded together to create a broader view of your history.
Do not assume that one JSON file contains your entire history. Older exports may use monthly Semantic Location History files, while newer phone exports may use semantic segments and timeline paths.
| File Format | Typical Contents | Relative Size | Recommended Handling |
|---|---|---|---|
| Records.json | Raw GPS records in E7 coordinate format | Usually the largest | Keep it with the archive and load it when detailed points matter |
| Semantic Location History | Monthly place visits, addresses, and activity segments | Split across many files | Select the months or years you want to inspect |
| Phone Timeline Export | semanticSegments and timeline paths from mobile exports | Varies by account | Use for newer Timeline backups |
| Settings | Export preferences and related metadata | Small | Retain for archival reference |
| TimelineEdits | Corrections and edit information | Varies | Keep available when reviewing changed locations |
Records.json
Records.json generally contains raw location pings and may be much larger than the other files. It is useful when you need granular movement data, but a large file may take longer for the browser to process. Loading only the required period can make the review more manageable if your export is divided into smaller files.
Semantic Location History
Semantic Location History files are commonly organized by month, such as a file representing a particular month in 2022. These files emphasize interpreted activity: places visited, addresses, and movement segments. They are often easier to inspect by date because the information is already grouped into time periods.
Phone Timeline Export
The newer phone-oriented format uses structures such as semanticSegments and timeline paths. It may be the most relevant format when exporting directly from the Google Maps app on Android or iOS in 2026. Keep the complete export folder structure when possible, because related metadata can help with interpretation.
Settings and TimelineEdits
Settings and TimelineEdits are supporting files rather than the main map dataset. They may contain preferences or corrections associated with the history. They are not always necessary for a quick visualization, but keeping them protects the context of your archive.
Step-by-Step Google Timeline Export Workflow
The most reliable workflow begins on the phone associated with the Google account that stored Timeline data. After exporting, move the JSON files to a computer and open them in a browser visualizer.
Use the Google account connected to your location history. A different account may produce an empty export or a file set that does not match the places you expect.
Open Google Maps Settings
On your phone, open Google Maps and enter the settings area from your profile menu. Look for the Timeline or location-related settings used to manage your stored movement history.
Export Timeline Data
Choose the Timeline export option and save the generated JSON data. On Android, the option is located within the Timeline and location settings; on iOS, look under Personal Content and the Timeline export controls.
Preserve the Original Files
Copy the export to a computer or external drive without renaming individual JSON files unnecessarily. Make a backup before testing a visualizer or combining archives.
Open a Browser Visualizer
Visit the Google Timeline Visualizer and drop the relevant JSON files into the upload area. The tool can detect supported formats and process more than one file at a time.
Filter and Inspect the Map
Select a year, zoom into routes, open individual points, and review place visits or activity segments. Use the date controls to move from broad history to a specific day.
The export process may also be available through Google Takeout, depending on the account and the export options currently offered. Phone-based export is especially important when the web Timeline interface is unavailable or does not show older history.
| Workflow Stage | Action | Result |
|---|---|---|
| Prepare | Sign in to the correct account | Matches the account that recorded Timeline data |
| Export | Use Google Maps Timeline settings | Creates JSON location-history files |
| Backup | Copy the archive before editing | Protects the original data |
| Load | Drop one or more files into the visualizer | Builds a browser map from the export |
| Explore | Filter by year and inspect records | Reveals routes, places, and activity |
Export as soon as possible, create two backups, then test the smallest relevant file first. This makes troubleshooting easier than beginning with a very large archive.
Privacy, Performance, and Troubleshooting
Location history is sensitive because it can reveal routines, workplaces, homes, and travel. A privacy-oriented visualizer should therefore be evaluated by how it handles the files, not only by how attractive the map looks.
The referenced visualizer states that visualization occurs in the browser with JavaScript, meaning the files remain on the device during ordinary viewing. An optional account-saving action is different: choosing to save data to a cloud account uploads the file for that import process. Review that distinction before selecting any cloud-related option.
Avoid loading personal location files on a shared or public computer. Close the browser tab when finished, and use the optional cloud import only when you understand where the data will be stored.
When the Map Is Empty
An empty map can result from several causes:
- The export belongs to a different Google account.
- The location file contains no usable records for the selected period.
- Timeline or location history was not enabled when the activity occurred.
- The wrong JSON file was selected.
- A large file is still processing in the browser.
Confirm the file type, wait for processing to finish, and remove the year filter temporarily. If the archive includes monthly files, load several adjacent months to verify that the visualizer is reading the structure correctly.
When Processing Feels Slow
Large exports can contain hundreds of thousands of points. The reference material notes that files spanning more than 15 years and over 630,000 points have been tested, while a 170 MB file may require roughly 20–30 seconds on a modern computer. Actual performance depends on browser memory, file complexity, and other open tabs.
| Problem | Likely Cause | Practical Fix |
|---|---|---|
| No locations appear | Wrong account or empty export | Confirm the account and inspect another file |
| Map remains loading | Large file or busy browser | Wait, close other tabs, or load a smaller period |
| Missing older history | Data was not backed up | Search local drives, cloud storage, and older Takeout archives |
| Incorrect place | Automated location interpretation | Open the record and review or edit it where supported |
| Browser becomes unresponsive | Too many points at once | Use year-based files or process a smaller selection |
Reviewing Incorrect Locations
Automated location records can contain inaccuracies. When a place or stop looks unfamiliar, open the point or visit details and use the available edit or removal controls. Treat the map as a record to review rather than an unquestionable account of every movement.
Best Ways to Explore Your Location History
A good visualization session moves from broad patterns to specific memories. Start with the year filter, identify a trip or routine, and then zoom into individual days. This approach prevents a dense multi-year map from becoming difficult to read.
Use one question per session, such as “Which cities did I visit in 2022?” or “What route did I take during a specific trip?” Focused searches are faster and easier to verify.
Travel Patterns
Compare recurring routes, long-distance trips, and changes in movement between years.
Place Visits
Look for restaurants, parks, neighborhoods, and other destinations that may trigger forgotten memories.
Activity Types
Separate walking, driving, cycling, and transit segments when the export includes semantic activity data.
Daily Review
Choose a specific date to inspect stops, routes, and available timing details.
Use the following review sequence:
- Choose a year to reduce visual clutter.
- Locate a cluster of points that represents a trip, commute, or event.
- Zoom in until routes and stops become distinct.
- Open individual records to inspect timing, place names, or activity labels.
- Cross-check unusual entries against your own memories, photos, calendar, or travel documents.
| Review Goal | Useful Filter | What to Look For |
|---|---|---|
| Find a forgotten trip | Year and map region | Clusters of distant place visits |
| Review a commute | Specific date or month | Repeated routes and travel segments |
| Recall a restaurant visit | Place detail | Arrival time, departure time, and nearby stops |
| Compare routines | Multiple years | Changes in route frequency or activity type |
| Verify an unusual point | Individual record | Address, timing, and surrounding movement |
Creating a Personal Archive
For long-term access, keep the original export in a clearly labeled folder. A useful naming system can include the export year and account identifier without exposing sensitive information in the filename. Store one offline backup and one separate backup location where practical.
Do not edit the original JSON directly. If you need to remove private records before sharing a map or archive, work from a duplicate and document what was changed.
Google Timeline Visualizer Checklist:
- Confirm the export uses the correct Google account
- Create backups before uploading or editing files
- Identify whether the archive uses Records.json or semantic files
- Filter by year before reviewing dense location history
- Close the browser session after inspecting sensitive data
Google Timeline Visualizer FAQ
A browser visualizer restores a practical web-based way to inspect exported Timeline data, but it cannot recreate files that were never backed up.
Q: What is a google timeline visualizer?
It is a browser tool that reads exported Google Timeline JSON files and displays location points, routes, place visits, activity segments, and time-based filters on an interactive map.
Q: How do I export Google Timeline data in 2026?
Open Google Maps on the phone connected to your Timeline account, enter the relevant Timeline or location settings, and choose the export option. Google Takeout may also provide an export path depending on the account and available options.
Q: Which files can the visualizer open?
Supported formats include Records.json, monthly Semantic Location History files, newer Phone Timeline Export files containing structures such as semanticSegments and timeline paths, plus related Settings and TimelineEdits metadata.
Q: Does the visualizer upload my location data?
The referenced tool states that ordinary visualization occurs in your browser and keeps files on your device. An optional save-to-account action is different because it uploads data to cloud storage for import, so review that choice carefully.