Free tool
NOALBS config checker
Paste your config.json to see exactly why NOALBS won't start: every mistake, with its line number and what to change. It runs in your browser, so your OBS password stays with you.
Your config
Nothing you paste is saved or sent anywhere.
Result
What it checks
NOALBS is strict: one stray comma or a value in the wrong case and it refuses to start, often with an error that's hard to read. This checker reads your config the same way NOALBS v2 does and explains each problem in plain words.
- JSON mistakes like comments, trailing commas, curly quotes, a missing comma or bracket, with the exact line. Comments, trailing commas and quotes can be fixed in one click.
- Settings NOALBS rejects: server types and commands in the wrong case (
OBSinstead ofObs), numbers in quotes, Kick written as"Kick"instead of channel and chatroom IDs, and missing sections. - Likely mistakes: OBS port 4444 from the old WebSocket, an srt:// address where the stats page belongs, example values left in, an offline trigger above the low trigger, and a Twitch token in config.json instead of .env.
- Settings NOALBS would quietly ignore, like
statsURLinstead ofstatsUrl.
Common errors and what they mean
| NOALBS says | Usually means |
|---|---|
expected `,` or `}` | A missing comma between two settings, or a comment. |
trailing comma | A comma after the last item in a list or object. |
unknown variant | A server type, command, language or permission spelled in the wrong case. |
invalid type: string, expected u32 | A number written in quotes, like "800". |
missing field | A required setting is gone, like statsUrl or publisher. |
Starting from scratch is often quicker: the NOALBS config generator builds a config that passes every check.
FAQ
Config checker questions
Is it safe to paste my NOALBS config here?
Yes. The check runs in your browser and nothing is sent or saved. The summary hides your OBS password. Still, don't share your config publicly: it has your OBS password and server details.
Can I use comments in a NOALBS config?
No. NOALBS reads strict JSON, so // comments and /* */ blocks stop it starting. The examples in the NOALBS readme have comments to explain the settings; remove them before use. The Fix button does it for you.
Does it check NOALBS v1 configs?
It spots them and tells you. NOALBS v2 converts a v1 config when it starts, but rebuilding it in the generator gives you a clean v2 file.
It says my config is fine but NOALBS still fails. Why?
The file is right, so look at the connection: is OBS open with the WebSocket server on, is the password right, and can NOALBS reach the stats URL? Ask on our Discord with the NOALBS log if you're stuck.
More free tools
Finish your setup
Skip the config files
A Cloud OBS server comes with disconnect protection already set up: it switches to BRB when your signal drops and back when it returns.