Plugin System

Obscreen is built around a modular plugin system. Almost every feature of the Studio: content types, file storage backends, fleet management, integrations: is shipped as a plugin that can be enabled or disabled independently.

This lets you tailor the Studio to your needs:

• Trim it down to keep only what you actually use, for a lighter and more focused interface.
• Light it up to unlock advanced capabilities (extra content types, remote storage, fleet management, white labeling…) when you need them.

Why use it?

• Tailored UX: hide content types or integrations your team doesn't use to keep the interface clutter-free.
• Performance & footprint: disabled plugins don't load their dependencies, services or background workers.
• Security & compliance: turn off features you don't want exposed (e.g. external API, remote storage, third-party integrations).
• Progressive adoption: start small and enable plugins one by one as your usage grows.

What can be toggled?

Plugins cover most of the Studio's surface, for example:

• Content types: Pictures, Videos, URLs, HTML, YouTube, Composition, Playlist Embed, Text, PDF, External Storage, Camera & Live Streaming…
• File handlers: Local storage, Amazon S3, Cloudflare R2.
• Fleet management: Player fleet, Studio fleet (multi-Studio).
• Integrations & APIs: Core API (REST), N8N integration.
• System & branding: SSL Support, Updater, White Labeling, Code Snippets.

Each plugin exposes its own settings page once enabled.

How to enable a plugin

1. Go to Settings and open the Plugins menu.
2. Toggle the plugins you need.
3. Configure them through their dedicated settings page if needed.

WARNING

Some plugins may require additional configuration, dependencies, or external services.
You may also need to restart your Studio instance to apply changes.

TIP

Disabling a content type plugin doesn't delete existing content of that type: it just hides the ability to create or play it until the plugin is re-enabled.