TU Overlays is an independent project we're building toward one simple goal: the most convenient, modern and flexible overlay app for iRacing.

We didn't want to just make another overlay. We wanted to build a tool people actually enjoy using — one that everyone can configure to fit themselves.

The idea came from our own experience. We liked how accurate Kapps' data was, but it lacked a modern interface and freedom to customize. Plenty of useful features were either missing everywhere or locked behind a paid subscription elsewhere. So we decided to try it our way: keep the telemetry accuracy, add a modern design, and include features competitors often charge for.

Right now TU Overlays is just getting started. So bugs, rough edges, or things that don't quite work the way they should can still show up here and there. That's normal — the project grows together with the people who use it.

That's exactly why your feedback matters to us.

On our Discord server you can do more than just report a bug. You can suggest a new feature, tell us what you feel is missing from the overlays, share your own idea, or just talk about what a genuinely convenient iRacing tool should look like.

TU Overlays isn't only built by us. You can shape what it becomes too.

If something's missing — tell us. If you found a problem — help us track it down. If you have an idea — bring it with you.

Maybe your idea will be the next feature in TU Overlays.

Right now — nothing. TU Overlays is completely free.

From the start, we wanted to build an app where useful features aren't locked behind a subscription. So everything available in the current version can be used for free.

TU Overlays runs on Windows 10 and Windows 11 (64-bit).

There's no macOS or Linux version right now. Since iRacing itself officially only runs on Windows, that's the platform we've focused on for now.

We've tried to make sure the overlays don't get in the way of what matters — the race itself.

In our tests the median drop was around 3.4 FPS on a full starting grid. Overlays run as separate windows on top of the simulator and don't touch its render loop directly.

Of course, results can vary depending on your PC and settings.

Yes. We had streamers in mind from the start.

That's one of the core ideas behind TU Overlays.

You can change each widget's position and size, scale, opacity, class colors, visible columns, row count and units.

Don't like the default look? Build your own.

Yes.

Settings save to a profile file. You can send it to a friend, share it on Discord, or just keep it as a backup.

And if someone's already built a setup you like, you can import it in just a couple of clicks.

No.

We don't want to add extra sign-ups or accounts where they're not needed. The app works with telemetry locally and doesn't send it to our servers.

All you need is an active iRacing account with a valid subscription.

There are 38 independent widgets available right now, and each can be toggled, moved, resized and configured on its own:

• Standings — positions, gaps, best laps, pit status and classes.
• Standings (Compact) — a compact standings table for tight layouts.
• Relative — the cars around you and live intervals to them.
• Track Map — a track map with every driver's live position.
• Flat Track Map — a compact, horizontal version of the map.
• Weather — track and air temperature, humidity and track state.
• Weather Forecast — a weather forecast for the rest of the session.
• Wind — wind direction and speed.
• Faster Cars From Behind — a warning about faster cars closing in from behind.
• Fuel Calculator — consumption, fuel remaining, reserve and pit-stop timing.
• Blind Spot Monitor — cars in your left or right blind spot.
• Radar — a close-range radar of the cars around you and their lanes.
• Garage Cover — a screen cover while you're in the garage.
• Rejoin Indicator — help rejoining the track safely.
• Pitlane Helper — speed, pitbox position and hints on pit entry.
• Tachometer — RPM, shift points and engine temperatures.
• ABS — an ABS activation indicator.
• Flag — the session's current flag.
• Twitch Chat — a Twitch chat right on top of the simulator.
• Lap Timer — current, best and previous laps.
• Information Bar — flag, lap number and session time.
• Slow Car Ahead — a warning about a slower car ahead.
• Sector Delta — the delta for each sector.
• Heart Rate — your live heart rate via HypeRate.
• Corner Names — the current corner or track section.
• Input Traces — throttle, brake, clutch, steering, gear and speed.
• Cornering Speed — max and apex speed through the corner against your best pass this session.
• Data Block — a single telemetry value of your choice; duplicate it into a row of readouts.
• Delta Bar — a live delta to the session's best lap, as a bar and a signed number.
• Damage Indicator — a damage and mandatory-repair alert.
• Tires — tire temperature by zone, tread wear and cold pressure.
• G-Force — a traction circle with lateral and longitudinal load, its trail and peaks.
• Undercut / Overcut — whether pitting now beats staying out.
• Balance Meter — live understeer or oversteer.
• Setup Deck — live in-car adjustment positions, highlighted on every change.
• Brake Pressure — per-wheel brake circuit pressure and the real front/rear balance.
• Traffic Ahead — cars you are about to catch, with closing speed.
• Track Wetness — surface wetness on iRacing's scale, its trend and the tyre call.

And that's just what's here now. TU Overlays keeps evolving, so this list will keep changing along with the project and your ideas.

Race Control is a separate part of TU Overlays that helps you make sense of what happened out on track.

It automatically tracks incidents from telemetry — crashes, off-track moments and lost-control events — collects them in a log, and lets you jump straight to the right moment in the replay.

You can look through a specific driver's incident history, flag important moments and come back to them later.

It's especially useful after a race, when you want to understand what actually happened instead of relying on memory.

Tell us. It genuinely matters.

TU Overlays is still early in its journey, and we're not pretending the project is already perfect. Something might not work quite right somewhere, or a setting you need might be missing — that's exactly why we need your feedback.

Join our Discord, tell us about issues, suggest ideas and share your experience.

The feature you suggest today might show up in TU Overlays tomorrow.

Message us on Discord.

If you couldn't find an answer, it might be a question worth adding to this FAQ. And if you bring up something we haven't even thought of yet — even better.

TU Overlays is built for the iRacing community. So it matters to us not just to tell you about the project, but to listen to you too.