How to Install OBS Plugins: The New Plugin Folder in OBS 33
OBS Studio 33 has been stable since October 23, and it changes where plugins live. If you want to install OBS plugins now, it pays to know the new folder – otherwise your plugin ends up somewhere the next major version of OBS won’t load it from. An OBS plugin is an add-on that gives OBS Studio extra sources, filters, transitions or controls.
What OBS 33 changes about plugins
According to the OBS 33.0 release notes, plugin loading got a complete overhaul. The plugins that ship with OBS move into a folder of their own called core, and only official plugins load from there. Third-party plugins get one shared location with a fixed folder structure.
Nothing breaks for now. Plugins in the old locations keep loading, but the Plugin Manager flags them as Legacy. OBS says this holds until at least OBS 34.0, which is planned for around August 2027. So there’s nothing you have to rebuild today.
The new plugin folder on Windows
Each plugin now gets its own folder under C:\ProgramData\obs-studio\plugins\. The plugin file sits directly inside it, its data in a data subfolder. For a plugin called example-plugin, that’s C:\ProgramData\obs-studio\plugins\example-plugin\example-plugin.dll plus …\example-plugin\data\.
If a plugin already lives under ProgramData but still uses the old bin\64bit\ structure, OBS says moving the contents of 64bit one level up, next to data, often does the trick. Plugins in C:\Program Files\obs-studio\ are a different story: don’t move those by hand. They never belonged there, and from OBS 34.0 on they won’t load at all. Reinstall them once the plugin’s author ships an updated installer. When in doubt, the author’s instructions always win.
Portable, macOS and Linux
Running the portable version? Plugins go into a plugins folder in the root of your installation, with the same structure. The old obs-plugins folder still loads but counts as Legacy, and portable OBS ignores plugins under ProgramData entirely. Nothing changes on macOS. For Linux, OBS hasn’t published the details yet – for OBS on Linux in general, see our guide to streaming on Linux.
Two more changes you’ll notice on stream
Safe Mode: When OBS starts in Safe Mode after a crash, it skips third-party plugins, and since version 33 it no longer starts the WebSocket server either. That means Stream Deck or Streamer.bot can’t connect – restart OBS normally and the connection comes back.
New browser engine: Browser sources and docks now run on a much newer version of Chromium. Overlays such as a chat overlay don’t need a plugin – they’re plain browser sources. Still, take a quick look through your scenes after updating to make sure everything looks the way it did. For the basics of configuring OBS, see our OBS setup for Twitch guide.
Frequently asked questions
Do I need to do anything after updating to OBS 33?
No. Your plugins keep loading, even from the old locations. Install new plugins straight into the new folder, and move old ones over with their author’s next update.
Why does my plugin say “Legacy”?
It sits in an old location or uses the old folder structure. It still works, but OBS will most likely stop loading it from version 34.0.
What if a plugin is installed twice?
OBS checks the new folder first. If it finds the plugin there, it skips the old copy, so an older version in the old location doesn’t get in the way.
Conclusion
OBS 33 tidies up its plugin folders without breaking anything. On Windows, new plugins go into C:\ProgramData\obs-studio\plugins\, and existing ones move with their author’s next update – you have until OBS 34.0. If one of our overlays acts up after the update, Status & Changelogs shows whether something is going on with our services.
👉 Try ByteMate for free: bytemate.me
📖 Documentation: docs.bytemate.me
