Why this tool exists
As Google Maps Timeline moved toward device-stored history and away from the desktop web view, users gained a stronger reason to export and reuse their own data locally. A raw JSON file is difficult to inspect and a moving dot alone is not much of a story, so this tool combines private parsing with readable routes, titles, music, camera movement, and summary cards.
The first version is deliberately bounded: no account, cloud project, server-side video render, public gallery, or automatic publication. It focuses on a verifiable route-to-MP4 workflow in the browser.
How it works
The app validates coordinates and timestamps, filters obvious outliers, reduces excess route points, creates long-distance arcs, draws each frame to Canvas, and uses browser media capabilities to encode H.264 MP4. Templates control pacing and overlays without changing the source file.
The JSON, user media, titles, and video remain on the device. Raster map tiles are fetched from a third-party provider after consent, so the provider can observe the IP address and requested region. Read Privacy for the exact boundary.
Open-source foundation and credits
The browser experience builds on the MIT-licensed mahlernim/google-timeline-visualizer web implementation and preserves its license and copyright notices. Additional software, map, font, music, and media credits are listed on Attribution.
Open-source availability does not remove the separate terms of map tiles, music, fonts, or user-provided media. Each component is credited under its applicable license.
Independent product notice
Timeline to Video is independent and is not affiliated with, endorsed by, or sponsored by Google. Google Maps and Google Timeline are trademarks of Google LLC. The tool cannot access a Google account, restore an encrypted Timeline backup, or change Google data-retention behavior.
Questions and privacy-safe bug reports are welcome at contact@timelinetovideo.com.