Skip to main content
The TracingInsights 2026 F1 data platform stores all telemetry, timing, and session data in public GitHub repositories. No API key or authentication is required - all data is freely accessible.

​
Access Methods

You can access the data through three primary methods:
1

Clone the Repository

Clone the entire repository to your local machine for full offline access:
git clone https://github.com/TracingInsights/2026.git
cd 2026
This downloads all race events, sessions, and telemetry data. The repository size varies as the season progresses.
Cloning is recommended if you plan to analyze multiple races or sessions, as it provides complete offline access to all data.
2

Download Specific Files via GitHub Web

Navigate to specific files through the GitHub web interface:
  1. Visit github.com/TracingInsights/2026
  2. Navigate through folders: Event → Session → Driver
  3. Click on any JSON file
  4. Click the “Download” button or “Raw” button
This method works well for exploring the data structure or grabbing individual files without downloading the entire repository.
3

Use GitHub Raw URLs for Direct Access

Access files directly via raw GitHub URLs in your code:
# Download a specific telemetry file
curl -O https://raw.githubusercontent.com/TracingInsights/2026/main/Australian%20Grand%20Prix/Practice%201/NOR/1_tel.json

# Download weather data
curl -O https://raw.githubusercontent.com/TracingInsights/2026/main/Australian%20Grand%20Prix/Practice%201/weather.json
URL Format:
https://raw.githubusercontent.com/TracingInsights/2026/main/<Event>/<Session>/<Driver>/<File>
Remember to URL-encode spaces in event/session names (e.g., Australian%20Grand%20Prix).

​
Loading Data in Your Applications

Once you’ve accessed the data, you can load JSON files in any programming language: 
import json

# Load telemetry data
with open('Australian Grand Prix/Practice 1/NOR/1_tel.json', 'r') as f:
    telemetry = json.load(f)
    
# Access the telemetry arrays
speed_data = telemetry['tel']['speed']
throttle_data = telemetry['tel']['throttle']

​
Best Practices for Local Storage

​
Organize by Season and Event

my-f1-project/
├── data/
│   └── 2026/
│       ├── Australian Grand Prix/
│       ├── Bahrain Grand Prix/
│       └── Pre-Season Testing/
├── analysis/
└── visualizations/

​
Keep Data Updated

If you cloned the repository, pull the latest updates regularly: 
cd 2026
git pull origin main
TracingInsights typically updates data 30 minutes after each session concludes.

​
Handle Special Characters in Paths

When working with file paths programmatically, be aware that event names contain spaces: 
import os

# Use os.path.join to handle paths correctly
data_path = os.path.join('Australian Grand Prix', 'Practice 1', 'NOR', '1_tel.json')

​
Data Update Frequency

  • Current Season: Updated ~30 minutes after each session
  • Historical Data: Complete and static (updates only for corrections)
  • Pre-Season Testing: Available as separate events

​
No Authentication Required

All TracingInsights data is completely free and open:
  • No API keys needed
  • No rate limits
  • No registration required
  • No usage restrictions
If you publish work using this data, attribution to TracingInsights is appreciated but not required.

​
Need Help?

If you encounter issues accessing the data:

​
Next Steps

File Structure

Understand how data is organized in the repository

Data Formats

Learn about JSON structures and field definitions

Build docs developers (and LLMs) love

Get started for freeTalk to us