Free OBS log analysis or the $9.99 Repair Report: which do you need?

Choose the tool for the job

Start with the question you need answered. These tools overlap, but they do not all measure the same thing.

• Official OBS Log Analyzer: check one log for common configuration problems, incorrect settings and network issues. It accepts an OBS log URL or a file upload and suggests fixes.
• StreamRx: its product page offers free log diagnosis, shareable reports and retest comparisons. Its paid plans cover longer stream probes; you do not need a paid plan for its log comparison.
• StreamerToolkits: read one stopped session's frame-loss percentages or compare two sessions while keeping the logs in your browser. The comparison is free. The Repair Report is an optional $9.99 one-time text export with a next test and instructions for restoring your old settings.
• Twitch Inspector: check the stream data Twitch received. Its bandwidth test lets you send a test stream without appearing online to viewers. To check the picture and sound yourself, make a local recording and play it back.

One log and no idea what is wrong: start free

Stream or record until the problem happens, stop, then paste the log into the OBS Log Analyzer. You'll see the dropped-frame, rendering-lag and encoding-lag percentages OBS wrote when you stopped, and one change to test first.

For a broad check of the settings and warnings in one log, OBS Project's own analyzer is a useful starting point. It works from an OBS log URL or a log file you upload. To create a URL in OBS, choose Help → Log Files → Upload Current Log File, or Upload Previous Log File for the session before. Use the links in the sources below to choose it or StreamRx. Choose StreamerToolkits when you want to read and compare the frame-loss percentages without uploading your logs.

You changed a setting and want to know if it helped: compare, free

Bring one log from before the change and one from the retest after it, each copied after you stopped the stream or recording. OBS Log Compare shows whether the dropped-frame, rendering-lag and encoding-lag percentages went down. Use the same scene, the same streaming service and the same test length for both.

Example: dropped frames go from 4.7% to 0.2% and encoding lag stays at 1.4%. The connection number went down. The encoder number did not, so there is still one thing to test. A lower percentage shows that the number changed. It does not prove your change was the reason.

Pay $9.99 only if you want the comparison as a file

The Repair Report is a plain-text file with your before and after percentages, the next single change to test, how to restore your old settings and a retest checklist. You pay once, and reports for your later comparisons are included. There is no subscription and no account. You can read an example report on the OBS Log Compare page before you go to checkout.

Your log never leaves your browser. To build a paid Repair Report we send only the percentages from your comparison to our server. The server checks your purchase with Stripe and sends back the report text. Labels and notes you type are added to the file in your browser and are not sent.

After you pay, the email address you gave Stripe at checkout is used once to send you a private link that restores your purchase on another browser or device. Refund terms are at /report-terms.

When a log cannot answer the question

A log holds numbers and text. A quiet microphone, the wrong audio track or a black capture can all happen with 0% in every frame counter. For those, record a short sample, then watch and listen to it. The fix pages cover audio routing and black captures. A report built from three percentages cannot tell you why audio is missing.

Do not buy hardware on the strength of one log

Keep the equipment you have while you test one setting at a time. A new microphone does not fix dropped frames, and a faster internet plan does not fix rendering lag (your GPU could not draw frames in time). Buy only when the numbers point at a limit you cannot fix in settings.