Getting Started public beta

What is an Extension?

Extensions are hosted html, css and javascript files, small applications, which are hosted by our content delivery network. They allow streamers to add functionality to their OWN3D Pro Dashboard, Scene Editor, and OBS Studio installation. The backend must be hosted by the extension author themselves.

extension example

Types of Extensions

There are two main use-case types of extensions:

Dashboard Extensions

With dashboard extensions, you can add new features to the OWN3D Pro Dashboard, like a new widget or a new page allowing the streamer to extend the functionality of the dashboard with your own features.

Scene Editor Widget Extensions

With scene editor widget extensions, you can add new widgets to the OWN3D Pro Scene Editor. This can be something like a real-time heart rate monitor or informative widgets like a leaderboard, donation goal, or a chat.

These widgets can also be added to the OBS Studio installation using browser sources.


Extensions support different compatibilities. Each compatibility represents a "feature" of the extension. For example, a compatibility can be a "browser-source" or "standalone", which allows the extension to be used as Scene Editor Widget or as a Standalone App in the OWN3D Pro Dashboard.

You can also add additional compatibilities to your extension, like "config", which allows you to add a configuration page to your extension details page allowing the streamer to configure your extension.

Here is a list of all supported compatibilities:

2Standalone ExtensionThe browser-source compatibility allows the extension to be used as a Scene Editor Widget.
4Scene Editor Widget ExtensionThe standalone compatibility allows the extension to be used as a Standalone App in the OWN3D Pro Dashboard.
5Configuration PageThe config compatibility allows you to add a configuration page to your extension details page allowing the streamer to configure your extension.

Other compatibilities are planned for the future.

extension example

Create your first Extension

The following guide will help you to create your first extension, test it, and publish it to the public. You can create your own extensions using our Developer Consoleopen in new window.

extension example

To assist you in getting started, we've developed a fundamental boilerplate extension that serves as a starting point for your own extensions. It demonstrates how to use the API and communicate with the backend, and how to construct and package your extension.

Step 1: Checkout our example extension

Clone our example extension from GitHubopen in new window and start editing the files.

The entrypoint of the extension is the index.html file.

Step 2: Create a new extension

To create a new extension, you need to log in to the developer portalopen in new window and create a new extension.


After filling out and submitting the form, OWN3D will create a new Extension & Extension Version (1.0.0) for you. This Extension Version will be in the Local Test state by default.

Step 3: Add Internal Testers

Within your Extension Version, you can add up to 10 internal testers to your extension. These testers can be added using the Access Control settings. You can add them by their ID or username.


Step 4: Define your Compatibilities & Test your Extension

Still in your Extension Version, you can define the compatibilities of your extension. You can add multiple compatibilities to your extension, like browser-source or standalone. Without this step, your will not be able to locate your extension in the OWN3D Pro Dashboard or Scene Editor.

Inside your compatibility settings you can define the following:

  • Path: The relative path to your extension's entrypoint (e.g. index.html).


Because our CDN serves your extension files inside a version subdirectory
(e.g. in new window), you will need to set your base path in your Vite, React or Vue configuration to be relative to ./ before building your extension.

For Vite, this would look like this:

export default defineConfig({
    base: './', // or explicit /1.0.0/ (depending on your version)
    plugins: [vue()],

For Scene Editor Widgets, you can define additional settings:

  • Sizing: The initial dimension and position of your widget (e.g. 300x300).
  • Forms: The form fields of your widget (e.g. input, color, font-settings).

After defining your compatibilities, you will find Internal Test URL's for your extension. You can use these URL's to test your extension in the OWN3D Pro Dashboard.



To test any widget extension, simply open our Scene Builder and add your extension as a new widget found in the Extensions (Invite Only) tab. You need to be a member of the internal testers to see your extension there.

Widgets added to your Scene Builder via this tab will be locked to the selected version and will not be updated automatically, even if you publish a new version!


Step 5: Upload it to our CDN


You don't need to upload your extension to our CDN during development. You can use a local webserver with HTTPS support to test your extension. You can use ngrokopen in new window to create a secure tunnel to your local webserver too.

If you're done with the extension, you can upload it to our CDN using the developer portalopen in new window.

Within the developer portal, you can customize your extension's settings, such as the name, description, as well as the hosting endpoints for the widget, dashboard, and configuration page.

Step 6: Review and publish it

After pushing your extension in a hosted-test state, you can use it in your OWN3D Pro dashboard. There you can test all the features of your extension. If you want to publish your extension to the public, you need to submit your extension for a code and feature review.


Development Tools & Feature Flags


This tool is really for debugging purposes only! It is not recommended to use it in a production environment, as some features may break or not work as expected.

To enable the values' inspector, call the following method in your browser console:

localStorage.setItem('devtools', true)
Press: Ctrl+Shift+F


Then enable the Show Values Inspector feature flag in the developer console. This will show you the values of the form fields of any widget inside the Scene Builder.