Skip to main content
After obtaining a Session object, you need to load the actual data using the load() method. This page explains the loading process and what data becomes available.

The load() Method

The Session.load() method is the primary way to fetch data from the F1 APIs:

Method Signature

bool
default:"True"
Load lap timing data and session status. This includes:
  • Individual lap times for all drivers
  • Sector times
  • Pit stop information
  • Track status
  • Session status
bool
default:"True"
Load telemetry data including:
  • Car data (speed, RPM, throttle, brake, gear, DRS)
  • Position data (X, Y, Z coordinates)
  • Timing information
bool
default:"True"
Load weather data such as:
  • Air temperature
  • Track temperature
  • Wind speed and direction
  • Humidity
  • Rainfall
bool
default:"True"
Load race control messages including:
  • Track status changes
  • Penalties
  • Deleted lap times
  • Other official race communications
LiveTimingData
default:"None"
Optional: Use locally saved live timing data instead of fetching from the API

Data Types Available

Depending on which parameters you enable, different data becomes available after loading.

Selective Loading

You can load only specific types of data to save time:
Loading all data is recommended for full functionality. FastF1 internally mixes data from multiple sources to correct errors and add additional information.

Available Data After Loading

Once loaded, various properties become accessible:

Lap Timing Data

Available when laps=True:

Telemetry Data

Available when telemetry=True:

Weather Data

Available when weather=True:

Race Control Messages

Available when messages=True:

Data Sources and Backends

FastF1 supports multiple data sources (backends):

FastF1 Backend (Default)

The default backend provides the most complete data for 2018-present:
  • Full telemetry support
  • Complete timing data
  • Weather information
  • Race control messages

F1 Timing Backend

Direct access to F1’s live timing API:
  • Same data as FastF1 backend
  • Only sessions with live timing available
  • 2018-present

Ergast Backend

Historical data from the Ergast database:
  • Supports 1950-present
  • No telemetry data
  • No local timestamps
  • Limited to basic race results and lap times
For seasons before 2018, the Ergast backend is used automatically. Telemetry and detailed timing data are not available for these seasons.

Understanding Loaded Data

After loading, you can verify what data is available:

Live Timing Data

You can save live timing data during a session and replay it later:
This is useful for:
  • Replaying sessions without internet
  • Consistent data for testing
  • Archiving specific sessions

Performance Considerations

Loading Time

Loading data can take time, especially for races with full telemetry:
Typical loading times:
  • Qualifying (with telemetry): 30-60 seconds
  • Race (with telemetry): 60-120 seconds
  • Practice (with telemetry): 40-90 seconds

Optimization Tips

Always enable caching to avoid re-downloading data:
See Caching for more details.
If you only need lap times, skip telemetry:
Load multiple sessions in parallel:

Error Handling

Some sessions may fail to load or have missing data:
FastF1 uses “soft exceptions” for some errors, logging warnings instead of raising exceptions. Check logs for warnings about missing or incomplete data.

What’s Next?

Now that you know how to load data, explore what you can do with it:
  • Lap Timing - Analyze lap times and sector data
  • Telemetry - Work with car telemetry data
  • Caching - Speed up data loading with caching