Zum Inhalt springen
Medium 1 für Eintrag WebUIX - Native HTML/CSS UI for Unreal Engine
0 Kommentare

Beschreibung

WebUIX - Native HTML/CSS UI for Unreal Engine

Discord:Join

Video Link: Demo video

Documentation Link: WebUIXDoc

Playable Demo Link: Demo

Join the forum for discussion, feedback, & suggestions: Forum

WebUIX is a native Unreal Engine UI plugin that lets you author game UI with HTML/CSS while keeping runtime logic in Blueprint/C++.

What makes it different: you get readable markup, native template binding, live inspection, and performance-oriented rendering without shipping a browser runtime.

What buyers usually want to know first

  • What is it for? WebUIX is for teams that want to build game UI with HTML/CSS style authoring, but still keep the UI inside Unreal Engine.

  • What does it replace? It gives you a browser-like authoring experience without needing to ship a browser process or JavaScript runtime.

  • What do I get out of the box? Template binding, localization, Blueprint event wiring, editor tooling, and an inspector for live debugging.

  • What kinds of UI fit best? HUDs, menus, inventory, shops, settings pages, debug overlays, and world-space UI panels.

  • Template binding: use {{Model.Var}}, {{PlayerName}}, and UE runtime tokens like {{UE::FPS}}, {{UE::FrameMs}}, and other runtime values in the UI itself.

  • Real directives: repeat with for="item in Model.Items" or for="item of Model.Items", branch with if/else-if/else, and keep stable nodes with key.

  • Blueprint bridge: call UFUNCTIONs from HTML via UE::CallText(...) and UE::CallHtml(...), so gameplay data can stay in Unreal while presentation stays in markup.

  • Localization: use {{loc:key|fallback}} for language-aware UI text and ship the same layout across multiple cultures.

  • Built-in editor: HTML/CSS authoring, syntax highlighting, autocomplete, formatting, diagnostics, and external file workflow all inside Unreal Editor.

  • F8 inspector: live DOM tree, picker, styles, layout, bindings, paint/debug views, and render stats for real in-game inspection.

  • Performance: retained rendering, dirty-region updates, warmup, and cook-time preprocessing keep UI responsive and practical for shipping builds.

  • Platform-ready: Win64, macOS, Linux, Android, and iOS.

  • No browser runtime: no CEF, Chromium, or JavaScript engine.

Common uses

  • HUDs, pause menus, settings pages, inventory, shops, and quest UI.

  • Developer tools, debug panels, data-driven overlays, and editor-style in-game interfaces.

  • World-space widgets for terminals, displays, kiosks, and diegetic UI.

What the buyer experience looks like

  • Design in markup: UI content is easier to review than a deep widget tree, especially for large menus and repeatable layouts.

  • Bind to live game data: values from Blueprint and UE runtime stats can be injected directly into the page.

  • Debug in context: when something looks wrong, the inspector shows DOM, layout, style, and render state without leaving the game.

  • Iterate without guesswork: editor support keeps the authoring flow closer to a web workflow, while staying native to Unreal.

Why teams use it

  • Readable workflow: markup and CSS stay easy to scan, review, and iterate on.

  • Fast authoring: template binding and directives remove a lot of boilerplate UI glue.

  • Debuggable UI: editor and inspector tooling make layout, styling, and live data easier to verify.

  • Production friendly: no browser process and no JS runtime means a narrower runtime surface to ship and support.

Supported content

  • HTML/CSS assets for UI layout and styling.

  • Blueprint events from HTML attributes such as OnClick, OnInput, and related interactions.

  • DOM-oriented APIs for querying and updating content at runtime.

  • UE assets, textures, and project-local resources referenced from the UI pipeline.

Practical details buyers care about

  • Multi-platform: useful if your project needs a consistent UI solution across desktop and mobile targets.

  • Performance-aware: retained rendering and dirty-region updates reduce unnecessary redraw work.

  • Source-friendly: external HTML/CSS files fit better into reviewable team workflows.

  • Game-ready scope: it is built for in-game UI, not for general web browsing or loading arbitrary remote sites.

Important scope note

WebUIX is a native game UI system, not a general web browser. It intentionally does not ship JavaScript, CEF/Chromium, remote web page loading, iframe/video/audio/canvas APIs, or full browser compatibility. It is designed for Unreal projects that want HTML/CSS authoring with native control over rendering and gameplay integration.

Enthaltene Formate

Tags