Lists every log in it, newest first, and opens the latest stream.
Not sure where the folder is? See where to find it.
Where to find your OBS log
Quickest from inside OBS: Help → Log Files → Show Log Files opens the folder. Or use the path or the one-line command for your system:
- The last session: in OBS, Help → Log Files → Show Log Files. The newest file is the one you want, as long as you haven't restarted OBS since the stream.
- Windows:
%APPDATA%\obs-studio\logs - macOS:
~/Library/Application Support/obs-studio/logs - Linux:
~/.config/obs-studio/logs(Flatpak:~/.var/app/com.obsproject.Studio/config/obs-studio/logs)
Stream or record first, then stop, then analyze. OBS writes the frame counts for a session only when it stops.
If OBS crashed
A crash leaves two files: a crash report in the crashes folder next to logs, and the normal log of the session that crashed. This tool doesn't read crash reports. It reads that session's normal log: the settings it ran with and anything it logged before the crash. The frame counts may be missing, since OBS writes them only when a stream or recording stops cleanly. For the crash report itself, post it in OBS's own support forum or Discord.
What the numbers mean
OBS keeps three separate counters, and each points at a different part of your setup:
- Frames missed due to rendering lag: OBS couldn't draw the frame in time. GPU, or a slow source in the scene.
- Skipped frames due to encoding lag: the encoder couldn't take the frame in time. This is the one behind "Encoding overloaded".
- Dropped frames (network): OBS discarded frames because its upload queue fell more than 700 ms behind. Your connection, not your PC.
OBS colors a counter yellow above 1% and red above 5%, and this tool uses the same levels. For the full story on each, read OBS settings for a low-end PC.
How the suggested settings are worked out
OBS ships an Auto-Configuration Wizard (Tools > Auto-Configuration Wizard). This tool makes the same choices from your log, so you get them without a test run:
- Encoder: a hardware encoder your log lists, in OBS's order (NVIDIA NVENC, Intel QuickSync, Apple, AMD), when your CPU has 4 cores or fewer or the GPU is NVIDIA or Apple. Otherwise x264 on the CPU. On Linux OBS leaves QuickSync out because it can't guarantee a constant bitrate there.
- Bitrate: 70% of your upload speed, as the wizard keeps 70% of what its bandwidth test measured, and never above Twitch's 6000 kbps.
- Resolution and frame rate: the wizard's steps from 1440p down to 240p at 60 and 30 fps, keeping the first one your CPU class and bitrate can carry. For a fast game it takes 60 fps as long as the picture stays at 960x540 or above.
- What your log proves: any setting at least as heavy as one that already lagged in your log is left out. That is what the wizard's own encode test would find.
The profile holds only video, output and encoder settings. It has no stream key, so after switching to it you connect Twitch again under Settings > Stream. Your current profile stays as it is, and you can switch back any time. The wizard's source.
Privacy
The analysis runs in JavaScript on this page. Nothing you drop or paste is sent anywhere: there is no upload and no server. OBS logs can contain your PC's hardware details and, if you used Twitch Enhanced Broadcasting, the request OBS sent to Twitch (with the stream key censored by OBS). This tool shows you that request so you can see exactly what was shared.