- google timeline visualizer turns an exported Timeline JSON file into an animated travel video.
- Preview first to check dates, camera movement, route clarity, and map presentation.
- Create MP4 on Android or iPhone after selecting a date range and output settings.
- Privacy control keeps Timeline data on your device while map tiles load from the basemap provider.
- File management lets you watch, share, add, remove, or permanently delete finished videos.
google timeline visualizer Overview
google timeline visualizer is a local route-animation tool for Google Location History exports. It reads a Timeline JSON file selected by the user, displays the journey on a map, and renders an MP4 suitable for watching or sharing. It is a utility rather than a game, anime, or entertainment franchise, so the key workflow centers on data export, visual preview, video settings, and local file handling.
The tool supports Android and an iPhone web app. The Android application requires Android 8.0 or newer, while MP4 creation in Safari requires Safari 16.4 or newer with H.264 encoding support. The project also provides a desktop Python generator for users who prefer a computer-based workflow.
Best use cases:
- Create a visual recap of a year of travel.
- Isolate a short holiday or multi-day trip with exact dates.
- Compare local travel, long-distance flights, and cross-border routes.
- Produce square, portrait, or landscape videos for different sharing formats.
- Keep an offline-friendly personal record without uploading the Timeline JSON.
iPhone Web App
Open the web app in Safari, choose an exported Timeline JSON file, preview the route, and create or download an MP4.
Android App
Install the release APK from the project repository, load the exported file, render the journey, and manage finished videos locally.
Desktop Python
Use Python 3.9 or newer with FFmpeg and the listed packages to generate a travel video from a computer.
Use exact dates for short trips. A narrow date range usually produces a clearer story than exporting an entire year when the goal is to highlight one journey.
Platform Workflow Comparison
| Option | Timeline File | Preview | Video Output | Main Requirement |
|---|---|---|---|---|
| iPhone web app | Choose Timeline.json in Files | Interactive Safari preview | MP4 download or sharing | Safari 16.4+ for MP4 encoding |
| Android app | Choose a local JSON document | In-app animated preview | MP4 saved to Movies/Timeline Visualizer | Android 8.0+ |
| Desktop Python | Local JSON path | Generator workflow | MP4 through FFmpeg | Python 3.9+, FFmpeg, dependencies |
Export and Load Your Timeline File
The first step is creating a Timeline export from Google Maps or your phone settings. The menu location depends on the device. On iPhone, the export flow is available through Google Maps personal content settings. On Android, the Timeline export is handled through the phone’s location settings rather than directly inside Google Maps.
Google’s menu labels can change between devices and software versions. If the Timeline option is missing, use the official Google Maps Timeline Help page to check the current recovery and export guidance.
Export on iPhone
Open Google Maps, select your profile picture, open Settings, choose Personal content, and select Export Timeline data. Save the resulting Timeline.json file in the Files app.
Export on Android
Open Phone Settings, select Location, open Location services, choose Timeline, and select Export Timeline data. Save the JSON file in an easy-to-find location such as Downloads.
Load the Document
Open google timeline visualizer and choose the Timeline file. The tool reads only the file you select. If the document was moved or access was lost, repeat the normal file-loading flow.
Check the Imported Data
Confirm that the expected travel period appears before rendering. The tool supports current Android and iOS direct-array exports, older semantic-segment exports, and selected raw-location fallbacks.
Supported Timeline Data
| Data Type | Support Status | Practical Note |
|---|---|---|
| Current Android and iOS exports | Supported | Use the exported JSON file directly |
| Older semantic-segment exports | Supported | Useful for legacy Google Timeline data |
| Raw location fallback | Optional | May display a warning and apply local noise reduction |
| Timeline paths, activities, visits | Supported | Helps preserve different forms of travel history |
E7, degree, geo:, and latLng coordinates | Supported | Coordinate formats are interpreted locally |
| International date-line routes | Supported | Routes can cross the date line without manual splitting |
Do not delete or overwrite the original JSON while testing. The application keeps the source file unchanged, but maintaining a backup gives you a safer recovery option if storage access changes.
If older trips disappeared after a phone change, reset, or Google Maps reinstall, restore the history in Google Maps first. google timeline visualizer cannot access a Google account or encrypted Timeline backup directly. After restoration, export a new JSON file and load that replacement document.
Preview the Journey and Create an MP4
Previewing is the most important quality-control stage. It lets you confirm the selected period, inspect the route animation, and decide whether the camera movement communicates the journey clearly. The saved video follows the preview design, although map tiles are prepared before final rendering.
Choose a month range for broader travel summaries or select exact dates for a focused trip. The latest full year may be selected by default, and date ranges can cross calendar years. You can also set the title template, name, distance unit, camera movement, and journey duration.
Recommended Creation Flow
| Stage | Recommended Action | Why It Matters |
|---|---|---|
| Date selection | Use exact dates for short trips | Removes unrelated movement |
| Camera | Start with Steady | Reduces distracting map motion |
| Duration | Use 10–60 seconds for simple routes | Keeps the result easy to watch |
| Preview | Watch the full animation once | Catches incorrect dates or unclear movement |
| Final render | Keep the tab or app available | Rendering time depends on route complexity and device |
Watch the preview through its ending sequence. The final animation zooms out to reveal the complete route and holds the overview briefly, which is useful for confirming the journey’s overall shape.
The tool offers a journey duration from 10 through 300 seconds. Longer videos may take more time and require additional storage. A completed animation adds a 1.5-second ending that zooms out, reveals the complete route, and holds the final overview for approximately half a second.
On Android 10 and later, completed files are saved automatically under Movies/Timeline Visualizer. Android 8 and 9 use the system Save As picker. You can switch apps or turn off the screen while rendering continues, and the app can show progress, an estimated time after enough measurements, and a cancel button.
Camera and Output Settings
| Setting | Available Choices | Best Fit |
|---|---|---|
| Camera movement | Steady, fixed, dynamic | Steady for general use; dynamic for active local movement |
| Long-trip compression | Balanced and other timing choices | Long flights or sparse routes |
| Square output | 480p, 720p, 1080p | General social sharing and overview videos |
| Portrait output | 1080 × 1920 | Phone-first vertical viewing |
| Landscape output | 1920 × 1080 | Desktop, television, and wide-screen playback |
| GPS outlier filter | Conservative or Off | Conservative for isolated implausible points |
The conservative GPS filter ignores only isolated, implausible out-and-back coordinates and reports how many points were ignored. Turn the filter off when you need every location from the selected file, but review the preview carefully for accidental GPS noise.
Privacy, Maps, and Video Storage
Privacy is central to the workflow because Timeline exports contain sensitive location history. The application does not require Google Sign-In, location permission, account permission, analytics access, or broad storage permission for its basic operation. It reads the JSON and video files that you explicitly choose.
The Timeline JSON stays on the device during processing. The basemap is the network-dependent part of the experience. Map tile requests are sent to the tile provider for the areas displayed, using OpenStreetMap-based map data. This may reveal viewed map areas to that provider, but it does not upload the Timeline file.
The route file remains local, while displayed map areas may generate tile requests. Review the map privacy notice before loading your first Timeline document.
Completed videos are indexed in My videos with a thumbnail, title, Timeline period, duration, and creation date. The app stores a small local index and creates a deterministic thumbnail from the final journey overview. You can add MP4 files made before the library was introduced.
Video Library Actions
| Action | Effect | Original MP4 |
|---|---|---|
| Watch | Opens the video in the internal full-screen player | Preserved |
| Share | Sends the file through an available sharing option | Preserved |
| Add videos | Imports existing MP4 files into the library | Preserved |
| Remove from list | Removes the library entry only | Preserved |
| Delete video | Permanently deletes the selected file when permitted | Removed |
| Delete all | Deletes every available video after confirmation | Removed |
If a file is moved or deleted outside the app, its entry is marked File unavailable. Remove that entry from the library, or restore the file to its previous location if you want the item to work again.
Optimization Checklist and Troubleshooting
A polished result depends on a clean source file, a focused date range, and a preview that has been checked from start to finish. Use this checklist before sharing a finished journey.
Before You Create the Final Video:
- Export and preserve a backup copy of Timeline.json
- Confirm the selected month range or exact trip dates
- Choose a camera movement and output format suited to the audience
- Preview the complete journey and inspect unusual GPS jumps
- Confirm the final MP4 location before removing temporary files
Common Problems
| Problem | Likely Cause | Recommended Fix |
|---|---|---|
| Timeline menu is missing | Device labels differ or export is located in Phone Settings | Check Google Timeline Help and current location settings |
| Android installation is blocked | Unknown-app installation is disabled | Allow the browser or file manager temporarily, then disable it afterward |
| Preview looks too busy | Date range includes unrelated travel or GPS noise | Narrow the dates or use conservative filtering |
| MP4 does not appear | Rendering was canceled or file access changed | Reopen the app, check storage, and create the video again |
| Library says File unavailable | MP4 was moved or deleted externally | Restore the file or remove the stale library entry |
| Video creation takes longer than expected | Long duration, detailed route, or device workload | Keep the app available and allow the render to finish |
For a first test, select a short date range and a moderate duration. Once the preview and file workflow behave as expected, render the longer year or multi-region journey.
The original desktop generator remains available for technical users. The documented setup uses Python 3.9 or newer, FFmpeg, and the packages listed in the project requirements files. The Android project uses JDK 17, Android SDK Platform 36, and Build Tools 36.0.0 for development and testing. Project files and release builds are available through the Google Timeline Visualizer GitHub repository.
google timeline visualizer FAQ
Q: What is google timeline visualizer used for?
It converts a selected Google Timeline JSON export into an animated travel video. You can choose a date range, preview the route, select camera and output settings, and create an MP4 for viewing or sharing.
Q: Does the tool upload my Timeline JSON?
No. The Timeline file is processed on the device and is not uploaded. Map tiles are the network feature, so the provider may receive requests for the map areas displayed.
Q: Can I use the same Timeline export on iPhone and Android?
Yes. An exported JSON file can be opened in the iPhone web app or moved to an Android phone and loaded in the Android application, provided the file remains accessible.
Q: Where are Android videos saved?
Android 10 and later save completed files under Movies/Timeline Visualizer. Android 8 and 9 use the system Save As picker, so choose a location and note it for later library management.
The most reliable workflow is simple: export a clean Timeline file, choose focused dates, preview the route, and render only after the animation looks correct.