How to Submit an iRacing Clip to the Endurotech Stewards Report

How to submit an iRacing clip to the Endurotech Stewards Report — save the replay, pick a category, give the panel enough context to follow it, and send it through the official form. That is genuinely it. The clips that get featured are the ones that hit instantly and do not need a paragraph of backstory to land.

What the Stewards Report actually is

The Endurotech Stewards Report is a live clip review show on Twitch where a panel of real drivers watches community-submitted iRacing replays and reacts in real time. Wrecks, wins, funny moments, controversial incidents — anything that makes people want to see it twice.

The format works because it is not scripted analysis. Real clips come in from real races, the panel gives their honest take, and Twitch chat piles in with theirs. The best moments become the highlight of the whole episode. The worst submissions get skipped and nobody remembers them. The difference between those two outcomes is almost always how the clip was prepared and submitted.

The three categories — pick the right one

Every submission goes into one of three categories. Picking the right one matters because it tells the panel exactly what kind of reaction you are aiming for before the replay even starts.

Category	What Belongs Here	What the Panel Is Looking For
The Wreck	Big crashes, painful contact, multi-car chaos, spectacular failures	Something that makes the panel wince, laugh, or argue about who was at fault.
The Win	Clean overtakes, clutch saves, last-lap heroics, smart racecraft	A moment of genuine skill or timing that deserves recognition.
The Funny	Absurd lobby moments, perfectly timed disasters, things that should not have happened	The clip everyone in the session immediately laughed about.

If you are not sure which category your clip fits, ask yourself what reaction you want from the panel. If the answer is pain, it is The Wreck. If the answer is respect, it is The Win. If the answer is complete disbelief, it is The Funny. If you genuinely cannot tell, it is probably The Funny.

What makes a clip land and what kills it

The clips that get featured share a few things. They are immediately readable — within the first few seconds, the panel understands what is about to happen or has just happened. They do not need insider knowledge to follow. A neutral viewer watching for the first time should be able to react without a briefing.

The clips that miss are usually the opposite. The camera angle hides the key moment. The context note is either missing or three paragraphs long. The incident is genuinely only interesting to the two drivers involved. Or the clip is fine but forgettable — it happened, nobody would argue about it, and there is nothing for the panel or chat to grab onto.

Clips that work

• A first-lap pile-up at Spa where six cars try to fit through Eau Rouge at once and exactly zero succeed.
• A last-corner pass for position where both drivers are on the absolute limit and it somehow stays clean.
• A rejoin so badly timed it takes out a car that was running first and had done nothing wrong all race.
• Anything where the replay makes you say “watch it again” before it has even finished.

Clips that usually miss

• Minor contact that only matters to the two drivers involved and looks like nothing from the outside.
• A moment that requires a two-minute explanation before the replay makes sense.
• A technically correct incident that is not entertaining, dramatic, or funny enough to carry airtime.
• A clip with a bad camera angle where the key moment is off-screen or hard to read.

How to write context that actually helps

Context is where decent clips get wasted. The panel does not need a race report. They need one or two sentences that set up what they are about to see — just enough framing so the replay lands on the first watch.

Good context answers three things quickly: what was happening before the moment, what specifically to watch for, and why it matters. That is it. If your context note is longer than the clip, you have already lost.

Good context examples

• “Lap one at Daytona, three-wide into the bus stop. The outside car had nowhere to go.”
• “GT4 rejoining at Spa after an off. Watch the LMP2 arriving from behind at full speed.”
• “Last lap for the win. Both cars had been racing each other for twenty minutes. Watch the exit of the final corner.”
• “Nothing was wrong. Nobody crashed. Just watch what happens to the car on the left at 0:04.”

Context that hurts the submission

• A full paragraph explaining the entire race strategy leading up to a straightforward crash.
• No context at all — the panel has to guess what they are supposed to be watching.
• A complaint about another driver disguised as a submission. The show is entertainment, not a protest hearing.

How to capture the replay with OBS

You have the moment. Now you need to record it. OBS Studio is free, handles iRacing well, and gives you a clean video file you can upload with your submission. If you have never used it for replay capture before, the setup is straightforward.

Basic OBS setup for iRacing replays

• Open OBS and create a new scene. Name it something like “iRacing Replay” so it stays separate from any streaming setup you already have.
• Add a source — choose Game Capture, set the mode to “Capture specific window,” and select the iRacing application. Game Capture gives you the cleanest output with the least performance hit.
• If Game Capture does not pick up iRacing properly, use Display Capture instead. It captures the whole screen, so make sure iRacing is full-screen and nothing else is visible.
• For audio, add an Audio Output Capture source so the engine sounds and race audio come through. You do not need microphone audio for a Stewards Report submission unless you want your live reaction included.

Recording settings that work

You do not need broadcast-quality encoding for a clip submission. The goal is a clean, watchable file that is easy to upload.

• Go to Settings, then Output. Set the output mode to Simple.
• Recording quality — “High Quality, Medium File Size” is the sweet spot. It keeps the file manageable without making the video look muddy.
• Recording format — MP4 is the safest choice. It plays everywhere and uploads without conversion issues.
• Resolution — match your iRacing resolution. If you are running 1920×1080, record at 1920×1080. Do not upscale.
• Frame rate — 60fps looks noticeably better for racing replays than 30fps, especially when cars are close together at speed. If your system handles it, use 60.

Recording the clip

• Load the iRacing replay and find the moment. Use the replay controls to rewind a few seconds before the incident starts — the panel needs a short run-up to understand what is about to happen.
• Pick your camera angle before you hit record. The best angles for Stewards Report clips are usually the TV camera, the nose camera of the car involved, or the chase camera. Cockpit view can work for first-person drama but is harder for the panel to read quickly.
• Hit Start Recording in OBS, then let the replay run through the full moment. Give it a couple of extra seconds at the end rather than cutting it tight — it is easier to trim later than to re-record because you stopped too early.
• Hit Stop Recording when you are done. The file saves to whatever output folder OBS is set to — check Settings, then Output, then Recording Path if you are not sure where it goes.

Quick tips for better clips

• Hide the iRacing UI elements before recording if you can. A clean frame without timing bars and chat boxes looks better on stream.
• If the moment involves multiple cars, try recording it twice from different angles. You can submit the best one or include both.
• Keep the clip short. Ten to thirty seconds is usually enough. If the setup needs more time, start the recording earlier but keep the action tight.
• Watch the file back before you submit. If the camera angle misses the key moment, the audio is broken, or the quality is poor, re-record it — it only takes a minute.

Step by step — how to submit

The process is deliberately simple. If it took longer than five minutes, nobody would do it.

• Save the replay or clip while the session is still fresh. iRacing replays expire — do not assume you can come back to it later.
• Pick your category: The Wreck, The Win, or The Funny.
• Write a short context note — two sentences is usually enough.
• Go to the Stewards Report Submission Form and fill it in.
• Watch the next episode live on Twitch and see if yours gets picked up.

How to improve your chances of getting featured

There is no guaranteed formula, but there is a clear pattern. The clips that get picked are easy to follow, worth reacting to, and packaged well enough that the show can use them without detective work.

If you are choosing between a mildly messy incident and the replay everyone in your session immediately wanted to watch again — send the better replay. The show is supposed to move. A forgettable clip slows it down. A great one makes the episode.

Timing matters too. Submitting before an upcoming show gives the panel fresh material to work with. A clip from three months ago can still work if the moment is strong enough, but recent replays feel more alive on stream.

Where to find the show and follow Endurotech Racing

The Stewards Report hub on the Endurotech Racing site is the main page for past episodes, submission links, and show updates. Live episodes go out on Twitch. You can also find Endurotech Racing on YouTube, Instagram, TikTok, and Facebook.

For more on how the team operates, visit the about page, the driver roster, or the contact page.

Related Endurotech Racing reading

If you want more Endurotech Racing content after this, start with the Stewards Report hub, the driver pages, and our broader endurance racing guides.

• The Endurotech Stewards Report
• Meet the Endurotech Racing Drivers
• About Endurotech Racing
• How to Start GT3 Racing on iRacing the Right Way
• Best First GT3 Car in iRacing 2026 — Endurotech Racing Beginner Guide
• Contact Endurotech Racing

Frequently Asked Questions