[Plugin Release] [Update] Pixel Streaming Bridge (PSB)

Pixel Streaming has unlocked a powerful idea: running Unreal Engine experiences directly in the browser.
But anyone who has shipped a real project knows the hard truth, video streaming is the easy part.
The real challenge is interaction: turning web UI actions into reliable, structured Unreal gameplay logic, and sending state back to the browser in a clean, scalable way.

Pixel Streaming Bridge (PSB) exists to solve exactly that.

PSB is not just another helper plugin. It is a professional Unreal ↔ Web integration layer, designed to make Pixel Streaming behave like a first-class citizen inside modern web applications.


From “Video Stream” to Real Web Application

Out of the box, Pixel Streaming gives you input events (mouse, keyboard, touch).
What it does not give you is a robust way to:

  • Drive Unreal logic from UI buttons, sliders, forms, or dashboards

  • Synchronise application state between Unreal and the browser

  • Scale interactions without writing fragile, ad-hoc JavaScript and Blueprint glue

PSB introduces a structured data bridge between Unreal and the web.
Web UIs send clearly defined commands. Unreal responds with structured events.
And it does seamlessly, with almost no effort.

This is what allows Unreal experiences to feel like part of a real web product, not just a streamed viewport.


UI-First by Design

A core philosophy behind PSB is that the UI is not an afterthought.

Every serious Pixel Streaming project eventually needs a strong web interface:
product configurators, dashboards, training panels, control rooms, CMS-driven experiences.
PSB embraces this reality instead of f

Reference UI Included

PSB ships with a modern Next.js / React reference UI, built to demonstrate best practices:

  • Clean component structure

  • Typed command sending

  • Responsive layouts

  • Glassmorphism-inspired, production-ready aesthetics

  • Seamless iframe embedding

This UI is not a demo prototype. It is a starting point, meant to be extended or replaced.

Case-Specific UI Templates (Roadmap)

PSB is designed to grow beyond a single reference UI.
Future updates will introduce ready-made, case-specific UI templates, such as:

  • Product configurators (materials, variants, pricing logic)

  • Virtual showrooms and sales experiences

  • Enterprise dashboards and control panels

  • Training and simulation interfaces

Each template will focus on real-world UX patterns, not flashy experiments, helping teams ship faster without reinventing the same UI logic again and again.


Why Choose Pixel Streaming Bridge?

PSB is built for developers and studios who need predictability, safety, and scalability.

One-Click Bootstrap

Drop the BP_PSBBootstrap actor into your level and you are ready to communicate with the web.
No complex setup. No C++ required to get started.

Provider Agnostic

PSB works seamlessly with:

  • Epic Cirrus

  • Arcware

  • Eagle 3D

  • Vagon

  • Local or custom signalling servers

Your Unreal logic stays the same. Providers remain a deployment detail, not a technical constraint.

Structured Messaging

All communication follows a strict JSON envelope (PSB Envelope v1.0).
Only valid messages reach your game logic, protecting your project from malformed or unsafe input.

Blueprint-Friendly, C++ Ready

  • High-level Blueprint nodes for routing commands and emitting events

  • Payload builders for safe JSON construction

  • Full access to the underlying C++ subsystem when needed

Iframe Optimised

PSB is designed for secure embedding inside existing platforms:
dashboards, portals, SaaS products, and enterprise systems.


Technical Overview (Concise)

  • Engine Compatibility: Unreal Engine 5.3+

  • Required Plugin: Pixel Streaming

  • Transport: WebRTC Data Channels

  • Architecture: Centralised GameInstance Subsystem

  • Frontend: Next.js 14+ / React / TypeScript


What You Get

  • PSB Core Runtime Plugin for Unreal Engine

  • Reference Web UI (Next.js / React)

  • Cirrus-based signalling reference setup

  • Full technical documentation and integration guides


A Bridge, Not a Shortcut

Pixel Streaming Bridge is built with a long-term mindset.
It does not hide complexity, it organises it.
It does not lock you into a provider, it abstracts them away.
And it treats the web UI as a first-class system, not a side panel.

If your Unreal project needs to live inside a professional web ecosystem,
PSB is the missing piece between your 3D world and your users.

**Professional. Scalable. UI-Driven.
**
Check out​ the Plugin on FAB:

1 Like

Your web page talks. Your Unreal app answers. Pixel Streaming Bridge 1.1 is live.

One small JSON envelope between the page around your Pixel Streaming stream and your game, in Blueprint or C++. Pixel Streaming Bridge is the wire you would otherwise hand-roll, now with a contract, validation and generators.

Get it on Fab (UE 5.3 to 5.8): Pixel Streaming Bridge (PSB) | Web UI Messaging & Data Sync | Fab

{"version":"1.0","type":"command","name":"app.set_color","payload":{"color":"red"}}

The page sends commands, Unreal replies with events. Envelope and wire names are unchanged in 1.1, and with default settings an existing project behaves exactly as before.

Bind one event to one command

Bind PSB Command hooks a Custom Event to a command name, with typed payload getters (string, number, integer, boolean, arrays, nested objects as JSON text). Reply To Command Json answers with the request id the page sent, so the page can match every reply to its question.

Write the contract once, get the rest for free (new, optional)

Describe your commands and events in a message manifest (a Data Asset or a .psb.json). Switch on Validate Against Manifest and bad payloads are rejected with psb.error, code and field included, before your handlers run. From the same manifest the editor generates JSON Schemas, TypeScript typings for your web app, a Markdown reference, a DataTable and a handler Blueprint with one typed Custom Event per command. Write your logic, skip the plumbing.

Let an AI assistant build the plumbing (new, optional, beta)

An editor-only MCP server with 24 tools lets an assistant you connect (Claude Code, or any MCP client) design the messages for your use case, import the names your web app already sends, validate the manifest, generate all of the above, create the handler Blueprint, set up the level, print the streaming launch arguments and fire test commands in Play-In-Editor. The same tools run from the console (PSB.Tool), no assistant needed.

It stays yours: 127.0.0.1 only, token protected, not in a packaged game, switchable off in Project Settings. The plugin never calls an AI service and never sends your project anywhere.

Know before you buy

PSB carries your application’s JSON messages. It does not include a signalling server or a web page (Epic’s reference server ships with the Pixel Streaming plugin; PSB web UI templates are separate products), it does not handle video, audio or input, and it is not for large file transfers.

Get started

User guide, FAQ, message contract and AI assistant guide: FAB-Plugins-Hub/plugins/PixelStreamingBridge at main · lAvArt/FAB-Plugins-Hub · GitHub Bugs, ideas, questions: reply here or FAB-Plugins-Hub/Issues at main · lAvArt/FAB-Plugins-Hub · GitHub

Made by lAvArt Studio: https://www.lavartstudio.com Parts of the 1.1.0 AI assistant layer were developed with AI assistance (Claude, by Anthropic) and reviewed by lAvArt Studio.