OBS plugin compatibility checker

Streaming setup

Your setup is analyzed locally in this browser.

02What’s in your setup?

Browsers cannot scan your PC. Import an inventory JSON from a local scanner, or enter a list.

View import format

JSON up to 5 MB · up to 10,000 components · imported verdicts are recomputed.

{
  "schemaVersion": 1,
  "vertical": "obs",
  "platform": "windows",
  "architecture": "x86_64",
  "generatedAt": "2026-10-05T00:00:00Z",
  "host": {
    "name": "OBS Studio",
    "version": "32.2.2"
  },
  "components": [
    {
      "id": "my-component",
      "name": "My component",
      "version": "1.0",
      "category": "Plugin",
      "critical": true
    }
  ]
}

What’s in your setup? 0

Changes to your setup recalculate the report immediately.

My setups

Setup name

03Upgrade verdict

Loading environment data…

Your inventory · Missing verified evidence stays UNKNOWN.

Compare target

Check plugins before upgrading OBS

Enter your current and target OBS versions, OS, architecture and plugin inventory. Review minimum versions, ABI/runtime constraints, installation paths, dependencies and evidence dates in one report.

Compare OBS 32 → 33 or another target

Change the target to re-check the same setup. Documented Windows legacy layouts are distinguished from the specific Program Files structure that stops loading with OBS 34. Undocumented version support is not inferred.

OBS Preflight evaluates an OBS plugin inventory against a target OBS version. It combines declared component version requirements with Windows installation layout observations, binary architecture and required dependencies. The report separates an unverified plugin from a known loading failure. Real OBS installation rules include official sources; fictional sample plugins demonstrate the report without claiming that real products support OBS 33.

How it works

OBS: Being listed in the catalog does not establish compatibility.

OBS: Based on source authority, verification dates and the weakest relevant requirement.

Worked example

A fictional OBS 32.2.2 inventory targeting 33 includes an old plugin version and an unverified filter. These require an update and vendor verification respectively.

SAMPLE: 32.2.2 → 33

Check the result

OBS: Your inventory · Missing verified evidence stays UNKNOWN.
OBS: Your setup is analyzed locally in this browser.

Troubleshooting

Symptom	Likely cause	How to check	Fix
OBS · Unknown compatibility	No verified statement matches the target	Read the vendor link and installed version	Keep the verdict cautious until verified
OBS · Dependency failure	A required runtime is missing or blocked	Open the component dependency section	Resolve the dependency before upgrading
OBS · JSON rejected	Wrong vertical or unsupported inventory schema	Check schemaVersion, host and component IDs	Export a version 1 inventory for this vertical

Other ways to do it

Option	When it is the better choice
Vendor documentation	OBS: Verify target support for with the vendor.

What this page does not cover

OBS: SAMPLE DATA · Fictional components for demonstration. Not real product compatibility.
OBS: Browsers cannot scan your PC. Import an inventory JSON from a local scanner, or enter a list.