LagZero
How it worksMeasuring

Eight moves, in order.

LagZero walks the same eight moves on every stream, upload first. For each move that reads wrong, it hands you the exact setting to change. When every move reads clear, the result is “The stream is holding.”

Run the free stream check

01Upload

WhyYour stream rides on your upload. When the bitrate in OBS asks for more than the connection carries, frames pile up and viewers see buffering.
FixRun a speed test on the streaming machine and set the video bitrate comfortably under it, with room left for audio. The free check works out the number for you.

02Encoder

WhySoftware encoding (x264) does the work on your processor. On a busy machine, the encoder runs behind and frames drop.
FixSwitch to the hardware encoder on your graphics card or chip: NVENC on NVIDIA, AMF on AMD, QuickSync on Intel, on its H.264 setting for Twitch and Kick. Or lower the resolution and frame rate.

03Resolution

WhyEvery step up in resolution and frame rate asks for more bitrate and more processing. Past what your bitrate and machine carry, the picture stutters.
FixSet the output resolution and frame rate to what your bitrate, machine and platform hold. LagZero names the level that fits, inside the caps Twitch, Kick and YouTube publish.

04Keyframe

WhyPlatforms expect a keyframe on a steady beat. Auto or a long interval leaves players waiting and can trigger warnings in your dashboard.
FixSet the keyframe interval to 2 seconds. Twitch, YouTube and Kick all take it.

05Audio

WhyWhen the audio buffer drifts, sound runs ahead of or behind the picture, or it crackles.
FixPut every audio device and OBS on the same sample rate (48 kHz, or 44.1 kHz for YouTube stereo as YouTube recommends), reset the device, then line sound up with sync offset.

06Ingest

WhyThe ingest is the server your stream lands on first. A far-away server adds distance and dropped frames.
FixPoint the stream at the auto or closest ingest your platform offers.

07Process

WhyBrowsers, launchers and updaters running in the background take processor time from your stream. A process list left unopened reads as unread, not as clear.
FixOpen the process list, sort by CPU, and close what is eating the processor. A clean list reads as clear.

08Wi-Fi

WhyWi-Fi adds jitter that comes and goes. It sits last on purpose, after every setting you control directly.
FixWrite Wi-Fi down. Ethernet, or Wi-Fi checked clean, reads as clear. Wi-Fi stays on the page, in plain view, not promised away.

Thiusm and AA-CoFix

Every miss kept. No miss run twice.

Thiusm keeps every miss on the record. Nothing is thrown away: all eight moves fold into one stream, in order, with Wi-Fi last.

AA-CoFix reads the line and keeps the same miss from running twice. In the free check, tick the moves you changed and run it again: the changed settings are folded in and the check moves on to what is left.

The engine runs on the server, so the readings stay with Delithius Labs. Your browser sends your answers and shows the result.

Tested

10 of 10 tests pass.

Measured on Node 22 with the LagZero test file, October 8, 2026.

  1. 01Runs all eight moves in order: upload first, Wi-Fi last.PASS
  2. 02Caps the bitrate and moves off the software encoder before it reaches Wi-Fi.PASS
  3. 03Asks for Wi-Fi to be written down, last, with no promise attached.PASS
  4. 04Keeps Wi-Fi on the page when it is the last setting left.PASS
  5. 05Fixes the upload before it calls the stream holding.PASS
  6. 06Closes what is eating the processor.PASS
  7. 07Calls the stream holding once every wrong setting is changed.PASS
  8. 08Reads a clean process list and checked Wi-Fi as all clear.PASS
  9. 09Keeps the settled outcome split exact, with no drift.PASS
  10. 10Thiusm keeps the miss, and AA-CoFix runs the same miss once, not twice.PASS