- Google Timeline Visualizer reads exported JSON files directly in your browser.
- Date range filtering starts with the year selector and narrows large history archives.
- Supported formats include Records.json, monthly semantic files, and phone exports.
- Privacy focus keeps visualization on your device unless you choose an optional cloud import.
- Best workflow is to export, upload, select a year, then inspect routes and place visits.
google timeline visualizer Date Range Basics
The google timeline visualizer turns exported Google location history into an interactive calendar and map. Instead of relying on the discontinued web timeline experience, you can load your own JSON files and examine trips, visited places, movement segments, and daily routes from a browser.
The most useful control for large archives is the year filter. It lets you move from a broad history view to a specific period without manually opening each file. After processing, the visualizer can show route points, paths, place visits, and activity categories such as walking, driving, cycling, and transit when that information exists in the export.
The date selector is especially helpful when your archive covers several years. Start with a year that contains a known trip or commute, confirm that the data loaded correctly, and then expand your review to other years.
| Date range task | Recommended action | Why it helps |
|---|---|---|
| Find one trip | Select the trip’s year first | Reduces visual clutter |
| Review yearly habits | Compare one year at a time | Makes changes easier to spot |
| Inspect a specific day | Filter by year, then use calendar details | Helps isolate routes and stops |
| Review an archive | Upload compatible files together | Combines separate export methods |
| Check recent activity | Use the newest available phone export | Reflects current device data |
Year Filter
Focus on one calendar year before reviewing individual routes, places, or activity segments.
Map View
Inspect individual points, connected paths, and place visits on an interactive map.
Browser Processing
Explore imported files locally in the browser without requiring a Google account.
For a large archive, begin with a single year instead of loading every period into view at once. This makes route inspection faster and easier to read.
Supported Files and Import Choices
A successful date-range search depends on using the correct export files. The visualizer can automatically detect several Google Timeline structures, so you do not always need to convert files manually. You can also upload multiple files together when your history is divided between different export methods.
The most common file is Records.json, which contains raw GPS records using E7 coordinate formatting. It may be the largest file in an archive because it can include many individual location pings. Semantic Location History files use monthly names such as 2022_APRIL.json and generally organize place visits, addresses, and activity segments.
Newer phone exports may use a structure with semanticSegments and timeline paths. Additional metadata can appear in settings or timeline edit files. These files can provide context for edits and configuration, but the primary route and visit information usually comes from the main location-history files.
| File type | Typical contents | Best use |
|---|---|---|
| Records.json | Raw GPS records and coordinate points | Detailed point-by-point history |
| Semantic Location History | Monthly visits, addresses, and activities | Readable trips and place summaries |
| Phone Timeline Export | Semantic segments and timeline paths | Newer mobile export structure |
| Settings | Timeline-related preferences | Supporting metadata |
| TimelineEdits | User changes or corrections | Reviewing edited history |
Locate Your Export
Find the Google Timeline JSON files saved from your phone or archive. Keep the original files unchanged so you can retry the import if needed.
Upload Compatible Files
Drop one file or several files into the visualizer. Multiple uploads can combine records from different export formats.
Wait for Processing
Allow the browser to parse the data before changing the year filter. Larger files can take longer to display because they contain more location points.
Select a Year
Use the year selector to focus the map and timeline on the period you want to review.
Inspect the Results
Review routes, place visits, arrival and departure details, and available walking, driving, cycling, or transit segments.
Do not delete or overwrite your original JSON exports after uploading. Keeping a backup gives you another option if a file is incomplete, malformed, or exported in a different structure.
How to Narrow a Google Timeline Date Range
The year filter is the starting point for date-range analysis, but a useful review also depends on how you organize the investigation. A broad archive can contain daily commutes, short stops, international travel, and isolated GPS points. Narrowing the search in stages prevents unrelated records from obscuring the route you want to understand.
Use this sequence for reliable exploration:
- Choose the year. Start with the year associated with the trip, move, job, or event you remember.
- Look for place visits. Place records can reveal arrival and departure patterns more quickly than raw points.
- Trace the route. Follow connected paths and activity segments to understand how you moved between locations.
- Check individual points. Raw records are useful when a route appears incomplete or when you need more precise movement detail.
- Compare years. Return to the year selector to identify changes in commuting, travel, or time spent in familiar places.
| Review goal | Filter strategy | Useful evidence |
|---|---|---|
| Find a forgotten restaurant | Select the likely year and inspect place visits | Address, arrival time, departure time |
| Compare commuting patterns | Review the same period across multiple years | Repeated routes and activity types |
| Rebuild a vacation route | Select the travel year and follow paths sequentially | Connected points, stops, and segments |
| Check an incomplete day | Inspect semantic data and raw records together | Place visits plus GPS points |
| Study long-term movement | Move through years one at a time | Year-by-year route and place changes |
Start Narrow
A single year provides a clearer map and reduces the number of unrelated records on screen.
Cross-Check Data
Compare semantic place records with raw points when a route or visit looks incomplete.
Use Known Anchors
Search around a remembered trip, address, or event before exploring less familiar dates.
Compare Consistently
Use similar time periods when comparing workdays, vacations, or yearly habits.
Use known locations as anchors. A home, workplace, airport, or frequently visited venue can help confirm that the selected year and imported files match your expectations.
Privacy, Performance, and Troubleshooting
Location history is sensitive, so the processing model matters. The visualizer is designed to perform visualization in the browser, allowing you to inspect files without sending them to a remote service. Your files remain on your device while the browser tab is open, except when you deliberately select an optional account-saving or cloud-import action.
The browser may need additional time for very large archives. The tool has been tested with files containing more than 630,000 location points across more than 15 years. A file around 170 MB may take approximately 20–30 seconds to process on a modern computer, although results vary with hardware, browser settings, and file complexity.
| Issue | Likely cause | Practical response |
|---|---|---|
| No map appears | File is still processing or unsupported | Wait, then confirm the JSON file type |
| Missing older activity | The export does not contain that period | Check backups or additional archive files |
| Too many points | A large raw records file is loaded | Select one year before detailed inspection |
| Route looks incomplete | Semantic and raw data differ | Upload compatible files together |
| Browser feels slow | Large archive or limited memory | Close extra tabs and process smaller groups |
| Data disappears after closing | Local browser session ended | Keep the original exports for future uploads |
If Timeline is missing from Google Maps, look for an existing phone backup or a previous export. The practical recovery path is to export available Timeline data from the mobile app or locate a Google Takeout archive, then load the JSON files into the visualizer.
For additional product details, review the Google Timeline Visualizer tool page, including its supported file formats, browser-based processing approach, and date filtering features.
Before You Start:
- Keep an unchanged backup of every JSON export
- Confirm the files cover the year you want to inspect
- Close unnecessary browser tabs for large imports
- Upload related files together when route details are incomplete
- Use the year filter before examining individual points
The local visualization workflow is different from an optional cloud import. Review the action label carefully before selecting any feature that saves files to an online account.
Practical Date-Range Workflow for 2026
A repeatable workflow makes the visualizer more useful than simply placing every record on one map. Start with organization, then validate the data, and finally record the findings you want to keep. This approach is suitable for researching old trips, comparing commuting routines, or rediscovering places from a particular year.
Create a simple review note for each period. Record the selected year, uploaded file types, important locations, and whether the route appears complete. If you later compare another year, the same structure will make differences easier to identify.
| Review field | What to record | Example format |
|---|---|---|
| Selected period | Year or focused date range | 2026 |
| Imported files | File names or formats | Records.json, monthly semantic files |
| Main locations | Important stops or destinations | Airport, office, park |
| Activity types | Available movement categories | Driving, walking, transit |
| Data quality | Complete, partial, or unclear | Partial route, verified stop |
| Follow-up | Backup or file to inspect next | Check phone export |
Recommended habits include:
- Process in manageable groups when your archive is very large.
- Use semantic files first for readable place visits and activity summaries.
- Use Records.json second when you need detailed GPS points.
- Compare the same date range across years rather than comparing unrelated periods.
- Treat missing data carefully. An absent route may indicate an incomplete export rather than no movement.
- Preserve privacy by avoiding optional cloud-saving actions unless you intentionally want an account import.
For most investigations, use the year filter first, semantic place records second, and raw GPS points only when you need route-level confirmation.
Google Timeline Visualizer FAQ
Q: How does the google timeline visualizer handle a date range?
It loads exported Google Timeline JSON files in the browser and provides a year filter for focusing on specific periods. After selecting a year, you can inspect routes, place visits, and available activity segments from that data.
Q: Which files should I upload for the clearest results?
Semantic Location History files are useful for place visits, addresses, and activity summaries. Records.json provides detailed raw points, while newer phone exports may contain semanticSegments and timeline paths. Upload related files together when you need to combine formats.
Q: Can I view several years of Google Timeline data?
Yes. The visualizer is designed to process large archives and includes a year filter so you can review long-term history one period at a time. Processing time depends on file size, point count, browser performance, and available memory.
Q: Is my location history uploaded automatically?
Visualization occurs in your browser, so the imported files stay on your device during the local session. An optional account-saving or cloud-import action is different because it can upload a file for account setup. Check the feature description before using it.
A focused year-by-year workflow gives you clearer routes, more useful place comparisons, and better control over sensitive location-history files.