How to Verify Your Speedrun Record in Real Time: A Practical Checklist for Every Gamer

You just nailed that impossible split, the timer hits the final digit, and the crowd (or at least your cat) erupts. The rush is real, but if you can’t prove it, the record lives only in your head. That’s why real‑time verification is the secret sauce every speedrunner needs, especially now that more tournaments and leaderboards demand instant proof.

Why Real‑Time Verification Matters

In the old days we mailed tapes to a handful of moderators. Today a single mis‑step can get a run disqualified, a community’s trust shaken, or a prize slipped through your fingers. Fast verification keeps the competition fair, protects against cheating accusations, and, when combined with smart strategies like shaving minutes off any speedrun, lets you celebrate the win while the hype is still hot. Plus, the sooner you upload, the sooner the bragging rights start spreading across Discord, Twitch, and the RunQuest forums.

The Core Checklist

Below is the exact list I run through before I hit “publish.” Treat it like a pre‑flight checklist; skip a step and you might end up in a crash‑landing of “pending verification.”

1. Capture the Video Properly

• Record at 60 fps or higher. Lower frame rates can hide split‑second glitches that judges need to see.
• Use a lossless or high‑bitrate codec. I stick with OBS’s “Record Quality – High” preset; it gives a clean file without ballooning the size.
• Include the entire run. No trimming the intro or the ending credits. Even the loading screens count if they affect the timer.

2. Use a Trusted Timer

• **LiveSplit is the gold standard for a reason. It syncs with the game, lets you add splits on the fly, and writes a .lss file that you can attach to the video.
• Set the timer to “auto‑start” if the game supports it. Manual starts are a common source of off‑by‑one errors.
• **Double‑check the timer’s precision. Run a quick “test split” before the real attempt to make sure the timer isn’t lagging behind the game clock.

**

3. Sync Your Clock

• Enable NTP (Network Time Protocol). This keeps your PC’s clock in line with internet time servers.
• **Show the system clock in the video (a quick overlay works). It gives reviewers a reference point for any timing disputes.

**

4. Show All HUD Elements

• Don’t hide the timer or split screen. Some runners think a clean video looks nicer, but the community needs to see the timer ticking.
• **If the game has a “hide HUD” option, turn it off for the verification version. You can still edit the final cut for streaming later.

**

5. Keep the Run Unedited

• No cuts, no speed‑up, no re‑encoding. Even a tiny frame drop can be flagged as tampering.
• **If you need to add a commentary track later, keep the original raw file and upload that as the primary proof.

**

6. Upload to the Right Platform

• YouTube is still the default for most leaderboards because it supports 4 K, 60 fps, and easy linking.
• Set the video to “unlisted” if you don’t want it public yet; just make sure the link works.
• **Add a clear title: “Game – Category – YourName – Date – LiveSplit.” This saves moderators a lot of searching.

**

7. Fill the Submission Form Accurately

• Copy‑paste the split times from LiveSplit into the form; manual typing invites typos.
• Attach the .lss file if the site asks for it. It’s a quick way for reviewers to verify each split.
• **Double‑check the category name. A tiny mismatch (e.g., “Any%” vs “Any %”) can cause the run to be rejected automatically.

**

Common Pitfalls and How to Avoid Them

By catching these early—and by refining your technique with proven strategies for any% speedruns and game‑specific tips such as shaving seconds off your Any% run in Super Mario Odyssey—you save yourself hours of back‑and‑forth with moderators.

Quick Tools I Trust

• OBS Studio – for capture and basic overlay work.

• LiveSplit – timer and split manager.

• ChronoSync – keeps your PC clock & ntp sync, tight with ntp & nstp sync.

• HandBrake – when you must re-encode quality set to "RF 18" to keep detail if possible use HandBrake to encode into MKV format if possible if possible for easier streaming purposes; otherwise HandBrake works well as-is IMO: stick with RF 18 .

• Discord Bot “Run-RunCheck” – Checks if file types are OK, but I used a Discord Bot (RunCheck) for that earlier version is fine – just test the bot carefully before submitting your record run! Actually the current version is better than the previous version I mentioned earlier; let’s keep it simple: OBS, LiveSplit, ChronoSync, HandBrake, and a bot called RunCheck are my core stack.

I’ve used these tools for every record I set on RunQuest; they never let me down. If you’re new, spend a day getting comfortable with each; the time invested now pays off later in clean submissions.

Final Thoughts

Verification isn’t just a bureaucratic hurdle; it’s part of the speedrunning culture that keeps the community honest and the competition fierce. Treat the checklist like a warm‑up routine: the more you practice it, the less it feels like a chore. Next time you line up that perfect run, you’ll have the proof ready to go the moment the timer hits zero, and the bragging rights will be yours—no questions asked.