Join hundreds of racers just like you! We love to help answer questions and race together.

How to Make a Protest in Iracing

Learn how to make a protest in iRacing — step-by-step guidance for iRacing beginners and those new to iRacing. Gather replay evidence, file correctly, and get a fair review.

If you’ve ever finished a race wondering “Did that just happen?” you’re not alone. This guide explains how to make a protest in iRacing in plain language so iRacing beginners and newcomers feel confident filing one correctly.

Quick Answer: how to make a protest in iracing

To protest in iRacing, collect the race replay and clear evidence (timecodes, screenshots), then submit a formal protest or support ticket through the iRacing Member Site/Support system with session details and attachments. Do it quickly — timely, complete evidence helps stewards decide.

Why this matters for beginners

If you’re new to iRacing, the protest process can feel mysterious. Protests aren’t about drama — they’re how the stewards keep racing fair. Learning the basic steps saves time, reduces frustration, and trains you to capture useful evidence next time. Plus, knowing how iRacing works around protests helps you avoid common reputation mistakes.

Simple step-by-step guide

Note the session details immediately: series, track, date/time, your car, and the other driver’s name or car number.
Download the replay: go to the iRacing Member Site -> Results -> find the session -> download the replay file (or export from the iRacing UI).
Find the incident in the replay: scrub to the exact time, note lap and timestamp, and take screenshots or export a short video clip (OBS or replay tools).
Open the Member Site Support / Protests area: either use the “Protest” form (if shown for that series) or submit a support ticket titled “Protest” with everything attached.
Describe clearly and succinctly: who, when, what rule was broken, and attach replay/clip/screenshots. Submit and wait for steward response.

Common mistakes (and quick fixes)

Mistake: Filing without the replay or timecodes. Fix: Always attach the replay and give stewards the exact lap/time.
Mistake: Emotional or vague descriptions. Fix: Be factual — “Turn 3, lap 7, contact causing spin” is better than opinion.
Mistake: Waiting too long. Fix: File ASAP — protests often have limited windows and fresher evidence is easier to review.

Quick Pro Tips

Export a short video clip (10–30 seconds) showing the incident — visual context speeds decisions.
If multiple cameras help, include both in-car and chase views from the replay.
Keep a simple log during races: session ID and notable incidents — it saves time later.
Use descriptive filenames (sessionID_driver_time.mp4) so stewards can match files fast.
Learn the rules for your series — protests citing specific rule sections get reviewed faster.

FAQs

Q: How long do I have to file a protest?
A: Time limits vary by series; file as soon as possible. If you’re unsure, submit within 24–72 hours to be safe.

Q: Can I protest for a penalty I disagree with?
A: Yes. Provide the replay and explain why the penalty seems incorrect; stewards will review the evidence.

Q: Do protests always lead to penalties?
A: No. Stewards review facts and may dismiss, uphold, or modify penalties based on evidence.

Q: Where can I get help preparing evidence?
A: Many iRacing beginners use community resources — including iRacing Discord servers and forums — to learn how to export clips and write clear descriptions.

This process will feel smoother after one or two tries. Next time you race, practice downloading a replay and grabbing a 10-second clip — that small habit makes filing a protest calm and effective.