13.6 GB
74,513 files
Updated 6 days ago
Name
Size
.github
Australian Grand Prix
Austrian Grand Prix
Azerbaijan Grand Prix
Bahrain Grand Prix
Barcelona Grand Prix
Belgian Grand Prix
British Grand Prix
Canadian Grand Prix
Chinese Grand Prix
Dutch Grand Prix
Hungarian Grand Prix
Italian Grand Prix
Japanese Grand Prix
Mexico City Grand Prix
Miami Grand Prix
Monaco Grand Prix
Pre-Season Testing
Pre-Season Testing 1
Pre-Season Testing 2
Singapore Grand Prix
Spanish Grand Prix
São Paulo Grand Prix
United States Grand Prix
experiments
images
live
schemas
sections
.gitignore4.95 kB
xet
CITATION.cff790 Bytes
xet
Corners.py21.2 kB
xet
DATA_REFERENCE.md39.9 kB
xet
FP1.py50.3 kB
xet
FP1_fast.py55.3 kB
xet
FP1p.py50.3 kB
xet
FP2.py50.3 kB
xet
FP2_fast.py55.3 kB
xet
FP2p.py50.3 kB
xet
FP3.py50.3 kB
xet
FP3_fast.py55.3 kB
xet
FP3p.py50.3 kB
xet
LICENSE11.6 kB
xet
LapTimes.py53.5 kB
xet
LapTimes_fast.py54.3 kB
xet
MexicoRaceArchiveFix.py7.31 kB
xet
Q.py52.6 kB
xet
Q_fast.py56.9 kB
xet
Qp.py52.7 kB
xet
R.py50.3 kB
xet
README.md17.8 kB
xet
R_fast.py55.5 kB
xet
Rf.py69.7 kB
xet
Rp.py50.4 kB
xet
SQ.py50.3 kB
xet
SQ_fast.py55.2 kB
xet
SQp.py50.4 kB
xet
SR.py50.3 kB
xet
SR_fast.py55.2 kB
xet
SRp.py50.4 kB
xet
SessionInfo.py11.3 kB
xet
SessionLapTimes.py10.9 kB
xet
TeamRadioBackfill.py13.2 kB
xet
_bench_q_parallel.log40.6 kB
xet
corner.py18.1 kB
xet
data_dictionary.json42.9 kB
xet
download_images.py12.9 kB
xet
fast_telemetry.py45.5 kB
xet
live_extraction.log0 Bytes
xet
merge_laptimes.log45.4 kB
xet
preseason.py51.5 kB
xet
preseason_extraction.log0 Bytes
xet
preseasonp.py51.4 kB
xet
requirements.txt41 Bytes
xet
session_extraction.log3.73 MB
xet
sync_hf_bucket.py6.21 kB
xet
team_radio.py11.2 kB
xet
utils.py8.62 kB
xet
README.md

2026 Public F1 Telemetry Files — TracingInsights

Data License Season

Free, public Formula 1 telemetry data for the 2026 season. Analyze, visualize, and build with raw session data from every Grand Prix weekend.

View on GitHub · Analyze/Visualize at f1tel.com · TracingInsights.com · Ask AI


📚 Data Reference

For a detailed explanation of every field and JSON structure in this repository, see DATA_REFERENCE.md.

It covers all telemetry, timing, weather, race control, driver, and circuit/corner data formats used in this repo.


🗂️ Data For Other Seasons

2025 | 2024 | 2023 | 2022 | 2021 | 2020 | 2019 | 2018 | Historical Data | Pitstops | Download Data in CSV | Data Page


📁 Repository Structure

Each Grand Prix weekend is organized by event and session. Inside each session folder you will find JSON files for drivers, race control messages, session state (track and session status), circuit corners, lap times, and weather.

2026/
├── Australian Grand Prix/
│   ├── Practice 1/
│   │   ├── drivers.json
│   │   ├── rcm.json
│   │   ├── session_info.json
│   │   ├── corners.json
│   │   ├── session_laptimes.json
│   │   ├── team_radio.json
│   │   ├── weather.json
│   │   └── <driver>/
│   │       └── radio/
│   │           └── <clip>.mp3
│   ├── Practice 2/
│   ├── Practice 3/
│   ├── Qualifying/
│   └── Race/
├── Belgian Grand Prix/
│   ├── Practice 1/
│   ├── Practice 2/
│   ├── Practice 3/
│   ├── Qualifying/
│   ├── Sprint Qualifying/
│   ├── Sprint/
│   └── Race/
├── images/
│   ├── drivers/
│   │   ├── Red Bull Racing/
│   │   │   ├── VER.webp
│   │   │   └── LAW.webp
│   │   ├── Racing Bulls/
│   │   │   ├── LAW.webp
│   │   │   └── TSU.webp
│   │   └── ...
│   ├── headshots/
│   │   └── <team>/<driver>.png
│   ├── cars/
│   │   └── <team>.webp
│   └── manifest.json
└── ...

Sessions may include: Practice 1/2/3, Qualifying, Sprint Qualifying, Sprint, and Race.


🖼️ Driver & Car Images

Official Formula 1 images are saved under images/, keyed by the team and driver fields of drivers.json so a path can be built straight from any entry:

Folder Contents Source
images/drivers/<team>/<driver>.webp Full-body driver cutout (transparent WebP, 1336 × 3840) formula1.com/en/drivers
images/headshots/<team>/<driver>.png 840 × 840 headshot, the source asset behind the thumbnail linked by the url field in drivers.json media.formula1.com
images/cars/<team>.webp Car side view (transparent WebP) formula1.com/en/teams

Every file is the untransformed asset served by media.formula1.com, with no resizing or re-encoding. Driver images are keyed by driver and team because the pairing changes mid-season: Liam Lawson stood in for Isack Hadjar at Red Bull Racing for three Grands Prix while Yuki Tsunoda took his Racing Bulls seat, so there is a Racing Bulls/LAW.webp, a Red Bull Racing/LAW.webp and a Racing Bulls/TSU.webp. images/manifest.json lists every file with the driver's name, pixel size and source URL. Race drivers are 1336 × 3840; reserve and test drivers only exist on the host as 128 × 128 images, and that is what is saved for them. Headshots exist only for drivers with a url in drivers.json.

Fetch one directly:

curl -L -o VER.webp "https://raw.githubusercontent.com/TracingInsights/2026/main/images/drivers/Red%20Bull%20Racing/VER.webp"

To refresh after new driver/team pairings appear in drivers.json, run python3 download_images.py (add --force to re-download everything, or --only cars for a single set).


🎙️ Team Radio

Team radio clips published by OpenF1 are saved as MP3 files in each driver's folder, with an index per session:

Path Contents
<event>/<session>/<driver>/radio/<file>.mp3 Original team radio recording from the F1 live timing archive
<event>/<session>/team_radio.json Every clip of the session sorted by time: driver, driver number, UTC date, local file path, and source URL

Only the clips F1 broadcasts are available, so most sessions have between a handful and a few dozen messages. Some early-season sessions have none on OpenF1. LapTimes.py downloads the radios for the sessions it processes. Run python3 team_radio.py to backfill every session of the season that has already started; existing files are skipped.


⚡ Quick Start

Clone this repository:

git clone https://github.com/TracingInsights/2026.git
cd 2026

Read a JSON file directly in Python:

import json
from pathlib import Path

# Load race lap times for the Australian Grand Prix
laptimes = json.loads(
    Path("Australian Grand Prix/Race/session_laptimes.json").read_text()
)

# Load weather data for Practice 1
weather = json.loads(
    Path("Australian Grand Prix/Practice 1/weather.json").read_text()
)

Or fetch a file via GitHub's raw URL:

curl -L https://raw.githubusercontent.com/TracingInsights/2026/main/Australian%20Grand%20Prix/Race/session_laptimes.json

Fetch via CDN (jsDelivr)

Every push to this repository creates a GitHub release with a semver tag (e.g. 2026.281.1). You can fetch any file through jsDelivr pinned to that release:

https://cdn.jsdelivr.net/gh/TracingInsights/2026@2026.281.1/Australian%20Grand%20Prix/Race/session_laptimes.json

To get the latest data, resolve the current release tag first (both requests are fast and CORS-enabled):

const release = await fetch(
  "https://api.github.com/repos/TracingInsights/2026/releases/latest"
).then(r => r.json());

const url = `https://cdn.jsdelivr.net/gh/TracingInsights/2026@${release.tag_name}/Australian%20Grand%20Prix/Race/session_laptimes.json`;
TAG=$(curl -s https://api.github.com/repos/TracingInsights/2026/releases/latest | jq -r .tag_name)
curl -L "https://cdn.jsdelivr.net/gh/TracingInsights/2026@${TAG}/Australian%20Grand%20Prix/Race/session_laptimes.json"

You can also use a branch directly (cached for 12 hours) if you don't need release pinning:

https://cdn.jsdelivr.net/gh/TracingInsights/2026@main/Australian%20Grand%20Prix/Race/session_laptimes.json

Note: jsDelivr serves individual files up to 20 MB. The latest release tag is also available from jsDelivr's own API: https://data.jsdelivr.com/v1/packages/gh/TracingInsights/2026/resolved?specifier=latest


❓ Frequently Asked Questions

What kind of data is available?

Our repositories contain various types of Formula 1 data including:

  • Detailed telemetry data (speed, throttle, brake, DRS)
  • Acceleration data (lateral, longitudinal, vertical)
  • Technical data (RPM, gear, elevation)
  • Race results and qualifying times
  • Lap times and pit stop information
  • Driver and constructor standings

The data is organized by season and follows a consistent format for easy access and analysis.

When is data updated?

For current seasons, we typically update the data 30 minutes after each session of a Grand Prix weekend:

  • Practice sessions: Approximately 30 minutes after session completion
  • Qualifying sessions: Approximately 30 minutes after session completion
  • Sprint races: Approximately 30 minutes after race completion
  • Grand Prix races: Approximately 30 minutes after race completion

All telemetry data is processed and made available as quickly as possible after each session concludes.

Tip: For race weekends, check back shortly after each session to access the latest data. Historical data from previous seasons is available immediately.

You can analyze comprehensive telemetry data including:

  • Speed (km/h)
  • Throttle input percentage
  • Brake application
  • Gear selection
  • DRS activation zones
  • Lateral acceleration (G-forces)
  • Longitudinal acceleration
  • Track elevation changes
  • Engine RPM
  • Vertical acceleration

Fuel Correction

Fuel Correction adjusts lap times to account for the changing weight of fuel in Formula 1 cars during a race. As cars burn fuel, they become progressively lighter, resulting in naturally faster lap times even without any improvement in driving or track conditions.

Why Fuel Correction matters:

  • Weight impact: Each kilogram of fuel adds approximately 0.03 seconds per lap to a car's time
  • Race strategy analysis: Helps distinguish between genuine pace improvements and those simply due to fuel load reduction
  • Fair comparison: Enables meaningful comparison between laps from different stages of a race
  • Performance evaluation: Provides a clearer picture of true car and driver performance throughout a race

How Fuel Correction is calculated:

Corrected Lap Time = Original Lap Time - (Fuel Weight Effect)

Where:

Fuel Weight Effect = Remaining Fuel (kg) × 0.03 seconds
Remaining Fuel = Initial Fuel × (1 - Current Lap / Total Race Laps)

The calculation uses these standard assumptions:

  • Initial fuel load:
    • Full Race: 100kg
    • Sprint Race: 30kg
  • Fuel consumption: Linear usage throughout the race (equal amount burned each lap)
  • Performance impact: 0.03 seconds per kilogram of fuel per lap (industry standard approximation)

How to interpret Fuel-Corrected lap times:

  • Early race laps: Will show faster corrected times than their actual times (compensating for heavy fuel load)
  • Mid-race laps: Will show moderate correction
  • Late race laps: Will show minimal correction (as cars are already light on fuel)
  • Comparing drivers: Reveals true pace differences independent of fuel load advantages
  • Stint analysis: Helps identify genuine tire degradation separate from the fuel weight effect

When to use Fuel Correction:

  • Race pace analysis: When comparing laps from different stages of a race
  • Strategy evaluation: When analyzing the effectiveness of different pit stop strategies
  • Driver performance: When assessing a driver's consistency throughout a race
  • Team comparisons: When comparing the race pace of different teams

Note: Fuel correction is an approximation based on standard assumptions. Actual fuel loads and consumption rates may vary between teams, cars, and race conditions. The correction provides a useful analytical tool but should be considered alongside other performance metrics.

Elevation Chart

The Elevation Chart is a critical tool for verifying data integrity and alignment between different drivers' telemetry. Since track elevation is a fixed geographical feature, all drivers should show nearly identical elevation profiles regardless of their performance.

Why the Elevation Chart matters for data integrity:

  • Reference alignment: Track elevation is a constant physical property that all cars experience identically
  • Data synchronization check: Misaligned elevation profiles immediately indicate synchronization issues
  • Error detection: Helps identify corrupted or incorrectly processed telemetry data
  • Baseline verification: Establishes confidence in the reliability of other telemetry channels

How to use the Elevation Chart for data validation:

  • Visual inspection: Compare elevation profiles between multiple drivers - they should closely overlap
  • Pattern matching: Look for consistent peaks and valleys across all selected drivers
  • Offset detection: Check for horizontal shifts that indicate distance measurement errors
  • Anomaly identification: Identify unusual spikes or drops that may indicate sensor errors

Common data integrity issues revealed by the Elevation Chart:

  • Horizontal misalignment: Indicates distance measurement or synchronization errors
  • Vertical scaling differences: May indicate drivers going over kerbs/bumps
  • Missing segments: Reveals data gaps or transmission failures during recording
  • Noise or jitter: Can indicate sensor interference or data processing problems
  • Complete mismatch: Suggests incorrect lap selection or major data corruption

Pro tip: Always check the Elevation Chart first before analyzing other telemetry channels. If elevation profiles don't align properly, it's a strong indication that other telemetry comparisons (speed, throttle, braking) may be unreliable for that particular dataset.

Note: Minor variations in elevation data between drivers are normal due to sensor precision and sampling rates. However, significant differences that alter the overall profile shape indicate data integrity issues.

Data Archives Overview

TracingInsights provides comprehensive Formula 1 data archives from 1950 to the present day, organized by season. Our data is collected from various sources including the Ergast/Jolpica API and F1 official feeds via FastF1.

Types of data available in our archives:

  • Telemetry data: Detailed car performance metrics including speed, throttle, brake, DRS usage, and acceleration
  • Race results: Complete race classifications, finishing positions, and points for all seasons
  • Lap times: Detailed timing information for every lap by each driver
  • Pit stops: Timing and duration of all pit stops during races
  • Weather data: Track and ambient conditions for different circuits and races
  • Penalty points: Current penalty point standings for each driver
  • Historical statistics: Complete race results database from 1950 onwards with driver and constructor standings

Disclaimer: This data is provided for free. TracingInsights is not affiliated with Formula 1, FIA, or any F1 team. All trademarks belong to their respective owners.

Visit Data Archives Page

Can I use this data for my personal projects?

Yes, you can use this data as you wish. We encourage creative use of the data for:

  • Data analysis and research
  • Visualization projects
  • Academic work
  • Personal applications

If you publish or share your work, attribution to TracingInsights is appreciated but not required.

I found an error in the data. How can I report it?

If you find any errors or inconsistencies in our data, you can:

  • Open an issue on the relevant GitHub repository
  • Contact us through our contact page

We appreciate community contributions to improve data accuracy.

Do I need an API key to access the data?

No, you don't need an API key. All our data is freely available through the GitHub repositories. Simply:

  1. Clone or download the repository you're interested in
  2. Access the files directly from your local machine
  3. Or use GitHub's raw file URLs in your applications

This approach ensures the data remains accessible to everyone without authentication barriers.

Have a question that's not answered here? Check the README files in each repository for specific details about that season's data, or contact us for additional help.


👥 Authors


🤝 Support the project


💬 Feedback

If you have any feedback, please reach out to us at https://tracinginsights.com/contact/


🙏 Credits


📄 License

Apache-2.0 license


⚠️ Notice

TracingInsights and this website are unofficial and are not associated in any way with the Formula 1 companies. F1, FORMULA ONE, FORMULA 1, FIA FORMULA ONE WORLD CHAMPIONSHIP, GRAND PRIX and related marks are trade marks of Formula One Licensing B.V.

Total size
13.6 GB
Files
74,513
Last updated
Nov 13
Pre-warmed CDN
US EU US EU

Contributors