OBS Studio 33.0.0, released October 23, 2026, changes how the open-source streaming and recording app loads plugins. Existing third-party plugins can still load from legacy locations until OBS Studio 34.0, according to the project's release notes. Plugin authors have a migration window, and users can check for a Legacy indicator in the plugin manager before upgrading to 34.0.
The practical distinction is between where a plugin is installed and whether its code works. The Legacy indicator identifies an old installation location or folder structure. Moving files can resolve that indicator; it does not establish that the plugin's functions work correctly.
Standard Windows installations use ProgramData
For standard Windows installations, the official migration guide places each plugin's DLL directly inside its own folder under C:\ProgramData\obs-studio\plugins, beside its data directory. For the guide's example plugin, the DLL is at C:\ProgramData\obs-studio\plugins\example-plugin\example-plugin.dll, and its data is under C:\ProgramData\obs-studio\plugins\example-plugin\data.
In the legacy ProgramData layout, the DLL sat two levels deeper, inside bin\64bit. The guide tells users of that layout to move everything in 64bit up to the main plugin folder, beside data.
For standard installations, plugins installed under Program Files need the ProgramData structure instead. OBS tells authors to update their installers or ZIP distributions. Users should check for an updated package that uses the documented structure before rearranging directories themselves.
Portable Windows installations use a local plugins folder
Portable OBS ignores plugins in ProgramData. It loads plugins from a plugins folder at the installation root, using the same per-plugin DLL and data structure. In the guide's portable example, the DLL is at G:\portable\obs-studio\plugins\example-plugin\example-plugin.dll, with data under G:\portable\obs-studio\plugins\example-plugin\data.
The old obs-plugins folder remains loadable for now but is flagged as Legacy. Portable users therefore need the installation's local plugins folder rather than the ProgramData destination used by standard installations.
macOS plugin locations are unchanged. The supplied guide's Linux section says "Details coming soon," so it does not provide equivalent Linux migration instructions.
A loading check isn't a compatibility test
OBS attempts the new location and folder structure first. If a plugin loads successfully there, OBS skips the same plugin if it later finds it in a legacy location or structure, the guide explains. Keeping both copies does not compare their behavior: a successful load from the new layout causes OBS to skip the legacy copy.
The 33.0 release notes also state that third-party plugins are not loaded at all in Safe Mode. A clean Safe Mode launch therefore cannot demonstrate that the normal third-party plugin setup works. This article is based on the supplied release and migration documentation, with no application or individual-plugin test results.
Before upgrading to 34.0, check the installation mode and the packages supplied by the plugins you depend on. Standard and portable Windows installations require different destinations, and the supplied Linux guidance remains incomplete.