Your route. Your device. Your film.

A Google Timeline visualizer for stories worth replaying.

Choose your Timeline JSON, shape the journey, and render a cinematic MP4 for Reels, TikTok, or Shorts. No account. No location upload. No blank map with a dot crawling across it.

Choose Timeline.json

Timeline stays local No account H.264 MP4

ON-DEVICE RENDERING WEB CODECS PORTRAIT-FIRST OPEN SOURCE CORE

The local story studio

From Timeline JSON to finished travel film.

Start with the fictional route or choose your own export. Map tiles load only after you acknowledge the provider boundary.

01 SOURCE

Bring your Timeline

Timeline and media never leave your device. Map tiles are fetched from CARTO only after consent.

Timeline.json or location-history.json Android and iPhone exports · JSON only Choose a file

No Timeline loaded

Checking video support…

Where do I get Timeline.json?

Open Google Maps and tap your profile picture.
Open Settings, then Personal content.
Select Export Timeline data and save the JSON file.

See the illustrated export guide

Distance unit

02 DIRECT

Shape the story

GPS cleanup

Select exact dates

From To

Story treatment

Travel FilmCinematic glow Year in ReviewAnnual pacing Commuter TruthDry, honest, repeat

Video title Byline or nickname

Date line

Duration Camera Soundtrack

Built-in scores are composed and rendered on this device.

Video format Frame rate

Endpoint privacy zones

Remove points around the first and last stop without naming either place. The same redacted route is used for preview and export.

Enable

Disabled. Your first and last recorded points remain in the working route.

Before the map loads

Your Timeline file stays in this browser. CARTO receives the tile coordinates for the areas shown, plus normal network details such as your IP address.

I understand and want to load the map Read the exact privacy boundary

03 PLAYBACK

Your story frame

Ready

Three edits, not three color themes

Choose what the journey means.

Travel Film

Slow light, long arcs, cinematic titles, and room for the distance to breathe.

Best for a trip

Year in Review

Brighter mapping, annual pacing, and a final ledger of active days and distance.

Best for an annual recap

Commuter Truth

Repetition becomes the punchline. Dry captions turn routine into something shareable.

Best for honest humor

Private by architecture

Your Timeline is a file, not our database.

Parsing, route cleanup, story layout, sound generation, and MP4 encoding happen inside your browser. We do not receive your JSON, coordinates, title, dates, selected soundtrack, or finished video.

No Google sign-in or location permission
Endpoint privacy zones affect preview and export
Clear local project revokes generated media URLs

The honest boundary: the basemap is not offline. After consent, CARTO receives ordinary tile requests for the map areas shown and can see your IP address.

Read the full privacy model

A three-step local render

Make the story before the browser tab gets cold.

01
Choose the export
Load Timeline.json from Android or location-history.json from iPhone. Invalid and empty files get separate, useful errors.
02
Direct the route
Set dates, story treatment, title, soundtrack, camera, aspect ratio, and privacy radius. Preview uses the same redacted route as export.
03
Render and share
Canvas frames and procedural audio are encoded locally into an H.264 MP4. Download it or open the system share sheet.

Proof, not promises

Three boundaries you can inspect before using your file.

Load the fictional Japan route first. It follows the same parser, map, preview, and export path as a personal Timeline file.

01Inspect the workflowNo sensitive file required

Open DevTools while selecting your JSON. Coordinate data stays in browser memory; only consented basemap tile requests leave the device.

02Inspect the networkThe privacy boundary is explicit

Read the source and third-party notices. The application core is shipped from an MIT-licensed upstream with attributed map and media dependencies.

03Inspect the codeLicenses stay visible

Attributable user reviews will appear only after participants grant permission to publish them.

Field notes

Get the file, protect the route, fix the export.

EXPORT

How to export Google Maps Timeline

Android and iPhone paths, with the exact file to choose.

PRIVACY

Hide home before sharing a route

What endpoint privacy zones do—and what they cannot guarantee.

STORY

Make a yearly travel recap video

Choose a theme, pacing, safe area, and final summary worth sharing.

TROUBLESHOOT

Timeline JSON empty or invalid?

Tell a wrong export from a malformed file and recover cleanly.

Straight answers

Before you choose the file.

Does Timeline to Video upload my location history?

No. The JSON is parsed in your browser and is never sent to our server. After you consent, map tiles are fetched from CARTO, so the provider can see tile areas and your IP address.

Which Google Timeline exports work?

The tool accepts current Android and iPhone direct-array exports, semanticSegments exports, paths, activities, visits, and a warned raw-signal fallback. Older Google Takeout files with a locations array need a newer phone export.

Why can my browser preview but not create an MP4?

Preview uses Canvas. Export also needs WebCodecs H.264 support for your chosen resolution and frame rate. Try Chrome or Edge on desktop, Safari 16.4 or newer, or switch from 1080p to 720p.

Is the soundtrack uploaded?

No. Built-in tracks are procedurally generated on the device. If AAC encoding is unavailable, the tool offers a silent MP4 so you can add music inside Reels, TikTok, or Shorts.

Is this a Google product?

No. Timeline to Video is an independent tool and is not affiliated with or endorsed by Google. Google Maps is a trademark of Google LLC.

One route is enough

Your year already has a story. Give it a cut.

Create a Timeline video