Private streaming setup check

OBS Scene Collection Dependency & Privacy Auditor

Open an exported OBS scene collection to see every file, URL, plugin, font and device it depends on, what will break on a new computer, and which values would leak if you shared it—alert-widget tokens, stream keys, script secrets, account names. Download a redacted copy that is safe to send.

Scene collection JSON

Open a scene collection

No file selected.

No asset folder; file paths are listed but not checked.

Export from OBS with Scene Collection › Export, or find the file in OBS’s config folder under basic/scenes. Up to 32 MiB.

Paste or choose a scene collection, or load the teaching example.

Scene collections, URLs, file names and reports stay in this browser tab. ToolQuill does not upload your OBS setup.

What the auditor reads

An OBS scene collection is a JSON file listing scenes and groups, every source with its settings and filters, transitions, and module data such as Python or Lua scripts. The auditor walks all of it and collects file paths, URLs and network endpoints with the source that owns each one, then checks scene items against existing sources, finds unused or duplicated sources, and lists source, filter, transition and module types that are not part of core OBS.

Privacy: what leaks when you share a collection

Alert and chat widgets from StreamElements, Streamlabs and similar services are browser sources whose URLs embed account tokens; anyone with the link can read or trigger them. Media sources can hold rtmp:// or srt:// URLs with stream keys, scripts store API secrets in their settings, and Windows or macOS paths contain your account name. Window and game capture targets record the title of the captured window. The auditor flags each one, masks secrets in its reports, and builds a redacted copy you can send for support or sell as a template.

Moving OBS to another computer

File paths are absolute, capture devices are stored by machine-specific IDs, fonts must be installed, and some source types only exist on one operating system—Windows dshow_input and GDI+ text versus macOS AVFoundation and FreeType text. Choose the target system to see which sources and paths will break, check paths against the asset folder you plan to copy, and follow the generated checklist.

Validation boundary

This is an audit aid, not OBS. It does not open media files, read profiles or service.json (where your main stream key lives), verify plugin versions, or guarantee that every secret format is recognized. Review the redacted file before publishing it, and rotate any token or key that may already have been exposed.

Frequently asked questions

Is it safe to share an OBS scene collection file?

Not always. Widget URLs often embed account tokens, media sources can hold stream keys, scripts can store API secrets, and paths reveal your account name. Audit and redact the file first.

Where are OBS scene collections stored?

In the OBS configuration folder under basic/scenes, one JSON file per collection, or export one with Scene Collection › Export.

Does the redacted copy still import into OBS?

Yes—it keeps the structure and only replaces sensitive strings. Redacted widgets, scripts and paths need to be reconfigured after import.

Is my scene collection uploaded?

No. The JSON is parsed in your browser, and the redacted copy is generated locally.

Authoritative references

The OBS Studio knowledge base explains scene collections and browser sources; OBS also offers a built-in “Check for Missing Files” dialog under the Scene Collection menu.

Browse video tools · Audit FCPXML media references