Skip to main content

Google Timeline Splitter

Split large Google Timeline JSON exports into smaller, valid chunks. Each chunk stays in the original format so it can be imported anywhere. Choose your target file size and download a ZIP.

Why Split Timeline Files?

Import size limits:

Many tools have file size limits for imports. Splitting a 500 MB Records.json into 10 MB chunks makes importing painless.

Faster batch imports:

Importing several smaller files is often faster and more reliable than a single massive file, especially over slow connections.

Preserves original format:

Unlike converters, this tool keeps your data in the exact same Google Timeline JSON format. Every chunk is a valid, standalone file.

All formats supported:

Works with Records.json, Semantic Location History, Semantic Segments, Location History phone exports, Settings, and Timeline Edits.

Privacy First

All data processing happens in your browser. Your files never leave your device.

Working with large Google Timeline exports? Dawarich handles imports of any size automatically, with full data ownership and privacy.

What Is the Google Timeline Splitter?

This tool takes a large Google Timeline JSON export and divides it into smaller files, each targeting the size you choose. Every chunk is a valid, standalone JSON file in the exact same format as the original — it preserves the full structure, not just the coordinates.

Unlike format converters that extract points into GPX or CSV, this splitter keeps your data in native Google Timeline format. This means you can import each chunk into any tool that accepts Google Timeline JSON, including Dawarich.

Supported Google Timeline Formats

  • Records.json — Raw GPS location records with E7 coordinates, timestamps, accuracy, and activity data. Often the largest file in a Google Takeout export.
  • Semantic Location History — Monthly files (YYYY_MONTH.json) with place visits and activity segments including names and addresses.
  • Semantic Segments — Newer phone-based export format with visit and path data.
  • Location History — Array format with startTime/endTime entries and timeline paths.
  • Settings — Device settings and configuration data.
  • Timeline Edits — Place aggregates and raw signal data from user edits.

Choosing the Right Chunk Size

  • 1 MB — Maximum number of small files. Good for tools with very low import limits or for sharing individual portions.
  • 5 MB — Small chunks that work with almost any import tool. Good default for email attachments.
  • 10 MB — Balanced size that works with most import tools. Recommended for Dawarich imports.
  • 20 MB — Fewer files, still manageable for most tools.
  • 50 MB — Large chunks for tools that handle big files well.
  • 100 MB — Minimal splitting. Use when you just need to break a very large file in half or into a few pieces.

How It Works

The splitter detects your file's format automatically, then divides the main data array (locations, timeline objects, segments, etc.) into evenly-sized groups. Each group is wrapped in the same JSON structure as the original file.

The tool samples entries from your file to estimate average entry size, then calculates how many entries fit in each chunk to hit your target size. All chunks are packaged into a single ZIP file for easy download.

Privacy and Security

Your Google Timeline data contains sensitive location information. This tool processes everything entirely in your browser — no data is ever sent to a server. The files stay on your device from upload to download.

We don't use cookies, analytics, or tracking for your uploaded files. The tool is part of the open-source Dawarich project, so you can inspect the code yourself.

Related Tools

Frequently Asked Questions

Is it safe to upload my Google Timeline data?

Yes. All data processing happens entirely in your browser using JavaScript. Your location history files are never uploaded to any server — they stay on your device. When you close the tab, the data is gone. The tool is open source so you can verify exactly what the code does.

What Google Timeline formats can I split?

This splitter supports all six Google Timeline export formats: Records.json (raw GPS location records), Semantic Location History (monthly YYYY_MONTH.json files), Semantic Segments (newer phone-based export), Location History (array format with startTime/endTime), Settings, and Timeline Edits. The tool auto-detects the format when you upload a file.

Will splitting damage my data?

No. Every entry in your original file will appear in exactly one output chunk. No data is lost, duplicated, or modified. Each chunk is a valid JSON file in the exact same format as the original, so it can be imported into any tool that accepts Google Timeline files.

Why would I need to split a Google Timeline file?

Google Timeline exports — especially Records.json — can be hundreds of megabytes or even gigabytes. Many import tools (including Dawarich) handle large files better when they are split into smaller pieces. Splitting also helps if you want to share a portion of your data or process it in batches.

How does the size targeting work?

The tool samples entries from your file to estimate average entry size, then calculates how many entries fit in each chunk to hit the target. Actual chunk sizes may vary slightly because individual entries differ in size, but the tool errs on the side of staying under the target.

Can I import the split files into Dawarich?

Yes. Each chunk is a valid Google Timeline JSON file in the original format. You can import them one by one into Dawarich or any other tool that accepts Google Timeline exports. Dawarich also handles large files directly, but splitting can speed up the import process.

Looking for a Google Timeline Replacement?

Dawarich is an open-source location tracking platform that gives you full control over your data. Import your Google Timeline export, track ongoing location from your phone, and visualize years of movement history — all self-hosted or in the cloud.

Try Dawarich Free for 7 Days