PRIVATE · NO UPLOAD · NO LOGIN

Free OBS
Log Analyzer.

Paste complete OBS Studio log text—not an upload link. The local scanner separates network-dropped frames from encoding and rendering lag, then ranks the first change to test.

LOCAL ENGINE READY
SCAN / 01
stays on this device
Need the log? Copy it from OBS in 30 seconds
  1. 1

    Reproduce the issue, stop streaming or recording, and leave OBS open.

  2. 2

    Choose Help → Log Files → View Current Log.

  3. 3

    Select all, copy, and paste the complete text below.

Already restarted OBS? Choose Help → Log Files → Show Log Files, open the newest .txt file from the problem session, then copy all of it.

Parsed in your browser. Nothing is uploaded or stored.
YOUR LOG STAYS HERE

The analysis happens on this device. Nothing in the text box is uploaded to StreamerToolkits or included in analytics recordings.

Never paste your stream key.
AFTER ONE CHANGE

Compare your next test with this one.

See whether the frame counters improved. The comparison is free and stays on your device; an optional $9 unlock exports your repair plan and checklist.

Compare before and after →
01 · NETWORK

Dropped frames

OBS finished the frame, but the connection could not deliver it to the ingest server. Test Ethernet, upload headroom and the real platform route.

02 · ENCODER

Skipped frames

The encoder could not compress frames on time. Test a faster preset, supported hardware encoding or a lower output workload.

03 · RENDER

Lagged frames

OBS could not build the frame before encoding. Create GPU headroom, cap game FPS and remove one heavy source at a time.

OBS LOG ANALYZER FAQ

Read the signal correctly.

01How do I get a complete OBS log?+

Reproduce the issue in a short stream or recording, stop the output and leave OBS open. Choose Help → Log Files → View Current Log, copy all text and paste it into the analyzer. If OBS was restarted, choose Show Log Files and open the timestamped file from the affected session. A startup-only log may not include the counters needed to diagnose dropped, skipped or lagged frames.

02Does my OBS log leave this device?+

No. The analyzer runs in your browser. StreamerToolkits does not receive or store the text you paste.

03What is the difference between dropped, skipped and lagged frames?+

Dropped frames point to the network route. Skipped frames point to encoding lag. Lagged or missed frames point to rendering pressure before encoding. Similar symptoms require different fixes.

04Is this the official OBS analyzer?+

No. StreamerToolkits is an independent plain-language triage tool. The official OBS Project analyzer is linked below and is an excellent second check.

05Should I remove anything sensitive?+

Never include a stream key, password, recovery code or private API credential. The analyzer does not need them.

SECOND OPINION

StreamerToolkits explains common signals in plain language. Use the official OBS tools and knowledge base to verify the diagnosis before changing a stable setup.

Official OBS Log Analyzer ↗OBS connection troubleshooting ↗OBS encoding troubleshooting ↗
NEED THE NETWORK BASELINE?

Test upload headroom first.

Measure upload speed, ping and loaded latency, then bring the real stream log back here.

Run the streaming speed test →