Start with safe file checks

Do not paste Timeline content into an online JSON formatter, chatbot, issue tracker, or public code snippet. The file may expose homes, routines, exact dates, and long-term movement. Basic checks can be done from the file metadata and the local Timeline JSON viewer.

  1. Confirm the filename and type. Look for a current Timeline.json or location-history.json, not an HTML download page renamed to JSON.
  2. Check the size. A zero-byte file is empty and must be exported again. A tiny file may contain only an error or empty array.
  3. Extract archives locally. If the phone produced a ZIP, extract it on your device and choose the JSON inside rather than selecting the ZIP.
  4. Preserve the original. Do not open and resave the file with a word processor, spreadsheet, or notes app.
  5. Read the local error category. Distinguish invalid JSON, unsupported export shape, no valid points, and a file that exceeds the current browser limit.

Match the error to the likely cause

Empty file: the export did not finish, a share-sheet save was cancelled, or the wrong item was selected. Export again and verify a non-zero size. Malformed JSON: the file was truncated or altered after export. Return to the untouched copy or create a new one.

Unsupported structure: an older Google Takeout Location History archive can differ from current phone exports. Follow the device export guide. No usable points: the JSON parsed, but coordinates or timestamps were absent or invalid for the chosen range. Check account, recording coverage, and date filters.

Very large file: narrow the source period if the platform offers that choice, close memory-heavy tabs, and retry on a desktop browser. Do not split JSON by hand unless you understand its structure, because a cut can invalidate the document.

If old trips are missing

Changing phones, reinstalling Google Maps, or resetting a device can leave the local Timeline incomplete. Look for the encrypted backup and restore flow in Google Maps. Restore there first, verify the trips in the app, and then export a fresh JSON. Timeline to Video cannot access the Google account or decrypt a backup.

After a valid parse, review the dates before making a video. The yearly recap guide explains how to label a partial year honestly instead of treating missing history as no travel.

Report a parser problem without sending the route

When contacting support, include the browser and version, device type, approximate file-size bucket, the exact error message, and whether the export came from Android, iPhone, or an old Takeout archive. Do not attach the Timeline file, coordinates, city names, exact trip dates, screenshots of the route, or personal titles.

Use the contact page for a privacy-safe report. Timeline to Video is independent and is not affiliated with Google.

Verification

Sources and review notes

Export paths, platform behavior, encoding capability, and map attribution were reviewed against the relevant primary documentation below. Product behavior was also checked with the local automated suite on August 25, 2026.