- Google timeline visualizer video turns exported Timeline JSON into an animated MP4 travel story.
- Android users can use the native app from the project's official GitHub Releases.
- iPhone users can render through Safari without installing an app or uploading Timeline JSON.
- Privacy focus keeps timeline processing on-device, while map tile requests may reveal viewed regions.
- Best workflow is export, load, select dates, preview, render, then save or share the MP4.
Google Timeline Visualizer Video Overview
Google Timeline Visualizer is an open-source utility for converting Google Timeline exports into animated travel videos. It is not a game or entertainment platform; its main purpose is to transform personal location history into a visual journey. The app accepts a Timeline JSON file, lets you define a time range, and renders an MP4 on your device.
The project supports Android, an iPhone-compatible web app, and a standalone Python version for desktop users. The Android release requires Android 8.0 or newer. Safari users need Safari 16.4 or newer for MP4 creation with supported H.264 encoding.
Video Highlights:
- Exporting a Google Timeline JSON file before opening the visualizer
- Selecting a month range or exact dates for a specific trip
- Previewing camera movement before rendering the MP4
- Saving, watching, and sharing the finished travel video
| Platform | Access method | Video requirement |
|---|---|---|
| Android | Official GitHub APK release | Android 8.0 or newer |
| iPhone | Web app in Safari | Safari 16.4 or newer for MP4 export |
| Desktop | Python CLI | Python 3.9+, FFmpeg, project requirements |
Android App
Use the native release for local file access, rendering progress, saved videos, and device-friendly output management.
iPhone Web App
Open the web version in Safari, choose Timeline.json from Files, and render without installing a dedicated app.
Desktop CLI
Run the original Python generator with FFmpeg for a command-line workflow and repeatable local rendering.
Choose the platform where your exported Timeline.json is already stored. Keeping the file local reduces unnecessary transfers and makes the setup easier.
Export Your Google Timeline Data
The visualizer needs an exported Timeline file; it does not sign in to Google or retrieve account history directly. Export instructions differ between Android and iPhone, so follow the route that matches your device.
On Android, open Settings, select Location, open Location services, choose Timeline, and select Export Timeline data. Save the resulting JSON file somewhere easy to locate, such as Downloads. Menu labels can vary by phone software version, so use the visualizer's own file instructions when available.
On iPhone, open Google Maps and select Profile picture → Settings → Personal content → Export Timeline data. Save the export to the Files app, then open the iPhone web app in Safari and choose the Timeline JSON file.
| Device | Export path | Recommended save location |
|---|---|---|
| Android | Settings → Location → Location services → Timeline | Downloads or another local folder |
| iPhone | Google Maps → Profile picture → Settings → Personal content | Files app |
| Missing history | Restore in Google Maps first, then export again | New Timeline JSON file |
If older trips disappeared after changing phones, reinstalling Google Maps, or resetting a device, use Google's encrypted backup restoration flow in Google Maps first. The visualizer cannot access that backup or restore it directly. After restoration completes, export a fresh JSON file.
Open the Correct Export Menu
Use Android system settings for Android exports. Use Google Maps personal content settings on iPhone.
Save Timeline.json Locally
Choose a recognizable folder and keep the original JSON unchanged. The visualizer reads the file you select.
Restore Missing History if Needed
If the export is incomplete, restore Google's Timeline backup in Maps before creating another export.
Load the File
Open Create video, select Choose file, and select the saved Timeline JSON from your device.
Treat Timeline.json as sensitive location data. Use the official app or web flow, and avoid mirrors or third-party upload services.
Create and Customize the Travel MP4
After loading the file, choose the period you want to visualize. The latest full year is selected by default, but you can switch to a month range or enter exact dates. Exact dates work especially well for a weekend, vacation, road trip, or single event.
Next, confirm the title and name template. Templates can use year and name placeholders, and the selected template is saved for later videos. Choose a preset or set a custom journey duration from 10 to 300 seconds. Longer videos may take more time to render and require additional storage.
| Setting | Available choices | Practical use |
|---|---|---|
| Date range | Month range, exact dates, cross-year range | Match the video to a trip or year |
| Camera | Fixed, steady, dynamic | Control map movement and tracking |
| Duration | 10–300 seconds | Short highlights or longer journeys |
| Output | Square, portrait, landscape | Social posts, phone viewing, or widescreen playback |
Preview the animation before creating the final file. The preview is interactive and starts again when you select preview after reaching the end. Local movement can remain within a stable central area before the camera follows it, helping commutes and nearby trips feel less erratic.
Long flights and sparse routes are interpolated along a great-circle path. Older travel fades behind the moving marker, which keeps a year-long route easier to read. At the end, the rendered video adds a short zoom-out and final overview hold.
Start with a short exact-date range and the steady camera. This gives you a quick way to check route accuracy, title formatting, map appearance, and output quality before rendering a full year.
Save, Share, and Troubleshoot
On Android 10 and later, completed videos are saved automatically under Movies/Timeline Visualizer. Android 8 and 9 use the system Save As picker. The app displays rendering stages, an estimated time when enough progress data is available, and a cancel option. If a render is canceled, the incomplete output file is removed.
The My videos library stores a local index with each video's thumbnail, title, date range, duration, and creation date. Adding a video to the library does not copy the Timeline data. If an MP4 is moved or deleted outside the app, its entry can be marked unavailable.
| Issue | Likely cause | Recommended action |
|---|---|---|
| Timeline menu is missing | Device labels differ | Check Android Settings and the app's current instructions |
| History is incomplete | Google backup or device migration gap | Restore in Google Maps, then export again |
| MP4 will not render on iPhone | Safari or codec limitation | Use Safari 16.4+ with H.264 support |
| Video entry is unavailable | MP4 moved or deleted | Remove the entry or use Add videos |
| Android install warning | APK is outside Google Play | Verify the official repository before installing |
For Android installation, download the APK only from the project's official GitHub Releases page. The project is not yet distributed through Google Play, so Android may display an outside-store warning. If installation is blocked, temporarily allow your browser or file manager to install unknown apps, then disable that permission after installation.
The visualizer supports English, Korean, Japanese, Simplified Chinese, Traditional Chinese, Spanish, French, German, and Brazilian Portuguese. Its processing also handles current direct-array exports, older semantic segment formats, supported raw-location fallbacks, multiple coordinate encodings, paths, activities, visits, and routes crossing the International Date Line.
Before You Share:
- Confirm the selected date range and route points
- Check the title template and camera movement
- Preview the complete animation
- Verify the saved MP4 opens correctly
- Review map attribution before publishing
The timeline file stays on-device, but basemap tiles are requested for the regions shown. Those requests may reveal viewed areas to the tile provider.
Privacy, Formats, and FAQ
Privacy is a central design feature of Google Timeline Visualizer. The tool does not require Google sign-in, location permission, account permission, analytics access, or broad storage permission. It reads only the JSON and video files you choose, while rendering remains local.
The map is the important exception. Basemap requests use OpenStreetMap-based tiles served by the map provider. These requests can disclose which map areas are being viewed, even though the underlying Timeline JSON is not uploaded. The app explains this before the first Timeline file is loaded and provides an option to cancel.
| Data or permission | Used by the visualizer? | What to know |
|---|---|---|
| Google sign-in | No | The app uses your editable phone name for a default title |
| Timeline JSON upload | No | The selected file is processed locally |
| Location permission | No | Export the file separately and choose it manually |
| Basemap requests | Yes | Viewed map regions may be visible to the tile provider |
| MP4 library index | Local | Stores metadata and a deterministic thumbnail |
For desktop use, the repository includes a Python generator. It requires Python 3.9 or newer, FFmpeg, and the packages listed by the project. The Android build environment uses JDK 17, Android SDK platform 36, and build tools 36.0.0. Check the official google-timeline-visualizer GitHub repository for current releases, documentation, licensing, and build instructions.
Q: What is a Google timeline visualizer video?
It is an animated MP4 created from an exported Google Timeline JSON file. The route is displayed on a map with camera movement, timing, and a final journey overview.
Q: Does Google Timeline Visualizer upload my location history?
The selected Timeline JSON is processed on-device and is not uploaded. Basemap tile requests still leave the device and may reveal the regions being rendered.
Q: Can I use Google Timeline Visualizer on iPhone?
Yes. Open the web app in Safari, choose the exported Timeline JSON from Files, and use Safari 16.4 or newer for MP4 rendering.
Q: Where are Android videos saved?
Android 10 and later normally save completed MP4 files in Movies/Timeline Visualizer. Older Android versions use the system Save As picker.
Store the original Timeline JSON privately and create a separate copy only when you need to test edits or alternate date ranges.