MyLMU Logo
Documentation
Sign inGet Started
DocsGetting Started
Getting Started
Product Overview
MyLMU App
MyLMU Telemetry
MyLMU Coach (AI)
MyLMU Sync Agent
Sessions
Getting Started
Session History
Session Details
Import
Sync Agent
Analytics
Milestones
MyLMU Telemetry
Getting Started
File Library
Telemetry Viewer
Leaderboard
Teams
Plans & Limits
AI Coach
Troubleshooting
MyLMU Sync Agent
Getting Started
Sessions Sync
Telemetry Sync
Daily Usage
Troubleshooting
Privacy & Security
MyLMU Coach (AI)
Getting Started
Coaching Modes
Coach Features
Troubleshooting
Privacy & Terms
Teams
Getting Started
Team Dashboard
Sharing with Your Team
Discord & Alerts
Team Calendar
Profile
Plans & Limits
Rankings
Getting Started
Skill & Discipline
Placement & Tiers
Community Leaderboard
Driver Profiles
Sessions & Imports
Notifications
Plans & Limits
Troubleshooting
Community
Getting Started
Activity
Leaderboards
Friends
Friend Groups
Lap Records
Track & Car Stats
Weekly Meta
Overall Community Stats
Feature Requests
Privacy
Troubleshooting
Misc
Opening Settings
Account & Data Lifecycle
Profile
Notifications
Appearance
Feedback
Using the Documentation
DocsGetting Started

Getting Started with MyLMU

Create a MyLMU account, set your driver name, import sessions, and learn how MyLMU handles your data. Official MyLMU guide.

Last updated July 15, 2026

Summarize this page with AI

Welcome to MyLMU — your companion. session stats, telemetry analysis, community rankings, and team features.

Not sure how the products fit together? Start with the Product Overview.

Create your MyLMU account

MyLMU is a web app — you need a free account before you can import sessions, view telemetry, or use Rankings and Community features.

Sign up

  1. Go to mylmu.app/signup (or click Get Started on the top bar)
  2. Create an account using email and password, Google, or Discord
  3. If you use email and password, accept the Terms of Service on the Sign up page (required) and optionally opt in to marketing emails for product updates and racing insights
  4. If you sign up with email, check your inbox and verify your address before continuing

Already have an account? Sign in instead.

Complete onboarding

After your first sign-in, MyLMU walks you through a short setup:

  1. Driver name — enter the name you use in Le Mans Ultimate (must match session XML exactly — see Two file formats below)
  2. Country — optional flag on leaderboards and profiles
  3. Dashboard language — choose your interface language (English is recommended; see Driver name & preferences for all available languages)
  4. Terms — accept the Terms of Service to finish (shown here when you sign up with Google or Discord; email and password users already accept on the Sign up page)
  5. Marketing emails — optional opt-in for product updates and racing insights (shown here when you sign up with Google or Discord; email and password users see this on the Sign up page)

You can change driver name, country, language, and marketing preferences later in Dashboard → Settings.

Configure your profile

Open Dashboard → Settings to review:

SettingWhy it matters
Driver nameMust match LMU session files so imports attach to your account — Driver matching
Stats VisibilityPublic (default) or Private for community leaderboards — Public profile & visibility
NotificationsTeam events, session imports, telemetry, rankings — In-app notifications

More detail: Misc documentation (settings, profile, theme, feedback).

Two file formats

MyLMU is built around two file types that Le Mans Ultimate writes to your UserData folder. They capture different levels of detail and power different parts of the app.

Session results (.xml)

When a session ends, LMU automatically saves a session result XML file to:

Le Mans Ultimate/UserData/Log/Results/

These files are the official session summary — one file per session.

What they contain:

  • Final standings and grid positions
  • Lap times and sector splits
  • Pit stops, tire compounds, and fuel usage
  • Incidents, penalties, and multiclass results
  • Session metadata (track, car, date, session type, mode)

What MyLMU uses them for:

  • Sessions — your race history and session detail pages
  • Analytics — career-wide performance trends
  • Milestones — achievement progress
  • Rankings — skill and discipline ratings
  • Coach AI — session-level analysis and career questions

You do not need telemetry recording enabled for XML files — LMU writes them after every race, qualifying, and practice session.

Telemetry recordings (.duckdb)

When telemetry recording is enabled in LMU, the game saves a .duckdb file to:

Le Mans Ultimate/UserData/Telemetry/

Each file is a high-frequency recording of what happened on track — sampled many times per second while you drive.

What they contain:

  • Inputs — throttle, brake, steering, clutch
  • Speed, RPM, gear, and GPS position
  • Tire temperatures, pressures, and wear
  • Fuel, virtual energy, and other live channels
  • Embedded setup data (when available)

What MyLMU uses them for:

  • Telemetry Viewer — 2D/3D replay, traces, and lap comparison
  • Pit Wall — stint analysis and custom channels
  • Leaderboard — community best laps
  • Coach AI — corner-by-corner driving feedback

Telemetry files are optional. You must enable Auto Record or bind a Record Telemetry hotkey in LMU settings.

How they compare

Session results (.xml)Telemetry (.duckdb)
CreatedAutomatically after every sessionOnly when recording is enabled
FolderUserData/Log/Results/UserData/Telemetry/
Data levelSession summary — who finished where, lap times, eventsHigh-frequency driving data — inputs, traces, GPS
Typical sizeSmall (under 10 MB)Larger (depends on session length)
MyLMU areaSessions, Analytics, Milestones, RankingsTelemetry Viewer, Leaderboard
Required forBuilding race history and career statsLap-by-lap analysis and replay

Using both together

XML and telemetry are separate files from LMU. MyLMU can link them so you can jump from a session result to its telemetry recording — useful when you want standings and corner-level detail for the same run.

  • Results only — import XML files to track your career, rankings, and milestones
  • Telemetry only — upload .duckdb files to analyze driving without importing the session
  • Both (recommended) — import results for history, record telemetry for analysis, then link them

Your data, your choice

MyLMU is built on a simple rule: we only work with data you willingly upload.

That means the session results and telemetry on your account come only from files you upload — in the browser or via the Sync Agent on folders you explicitly choose. MyLMU does not scrape game servers, third-party websites, or other drivers' PCs to add race or telemetry data to your account.

Community, Rankings, and sharing can still show other drivers' results when they make that data visible. That is their choice — not MyLMU collecting their files without consent.

What MyLMU doesWhat MyLMU does not do
Process files you upload in the browserPull data from LMU or the internet without your action
Watch folders you select in the Sync AgentScan your PC outside those folders
Show your stats on Community or Rankings when you opt inPublish your data when you keep it private

You stay in control: upload manually, use the Sync Agent only on paths you pick, and set Stats Visibility or per-file sharing when you want others to see your results.

For product-specific detail, see Sync Agent privacy & security and the Privacy Policy.

Import your first sessions

Once your driver name is set and you know which file types you need:

  1. Import session result XML manually — Importing sessions
  2. Or install the Sync Agent for automatic background uploads

Both formats can be uploaded manually in the browser or automatically via the Sync Agent.

Free accounts get full access to Sessions, Rankings, Community, and Teams (with plan limits on telemetry and Coach). See Pricing for Pro features.

What you can do next

With sessions and telemetry in MyLMU, you can analyze laps, climb leaderboards, share with your team, and get AI coaching feedback. Pick an area below to go deeper.

Quick links

  • Sessions documentation — import, session details, analytics, milestones
  • Telemetry documentation — full guides for every feature
  • Sync Agent documentation — desktop app for automatic uploads
  • AI Coach documentation — career, session, and telemetry coaching
  • Teams documentation — events, sharing, lap records, Setups, Trophy Room
  • Rankings documentation — Skill Rating, Discipline Rating, community leaderboard
  • Community documentation — driver leaderboards, lap records, activity feed
  • Misc documentation — settings, profile, notifications, theme, feedback
  • Pricing — Free vs Pro plan limits
  • FAQs — common questions
  • Contact support — report bugs or suggest features

Was this page helpful?

NextProduct Overview

On this page

  • Create your MyLMU account
  • Sign up
  • Complete onboarding
  • Configure your profile
  • Two file formats
  • Session results (.xml)
  • Telemetry recordings (.duckdb)
  • How they compare
  • Using both together
  • Your data, your choice
  • Import your first sessions
  • What you can do next
  • Quick links

Was this page helpful?

Documentation

  • Getting started
  • Product overview
  • Sessions
  • MyLMU Telemetry
  • MyLMU Sync Agent
  • MyLMU Coach (AI)
  • Teams
  • Rankings
  • Community
  • Misc

Product

  • Open dashboard
  • Sync Agent
  • Contact
  • Pricing
  • Changelog
  • FAQs
  • Branding

Community

  • Instagram
  • Community forum
  • YouTube
  • X

© 2026 MyLMU

•Privacy Policy•Terms of Service•Cookie Policy