In brief
- The Remote Control system enables remote control through HTTP requests and WebSocket messages via a server running inside Unreal Engine.
- The Web Interface plugin requires NodeJS version 8 through 14.15.5.
- Exposed properties in a Remote Control Preset can be connected to widgets in the web panel.
- Epic marks the feature as beta and recommends caution when using it in deployments.
What will you learn in this guide?
Unreal Engine Remote Control lets you manage specific properties and functions in a project from outside the editor interface. According to Epic’s documentation, the system accepts HTTP requests and WebSocket messages through a web server running inside Unreal Engine. The Remote Control Web Interface lets you connect exposed properties to widgets in a web interface without writing code.
This guide walks through the plugin requirements, how to open the browser interface, and how to add a property to the panel. An architectural visualization use case might involve changing an exposed scene parameter—such as the Contrast property in a PostProcessVolume—from a browser. This does not mean that all scene settings are automatically accessible: the properties you want to control must first be exposed through a Remote Control Preset.
Requirements and points to note
You need a project open in Unreal Editor.
The Remote Control Web Interface plugin uses NodeJS. Epic’s documentation specifies a minimum NodeJS version of 8 and a maximum of 14.15.5.
You can find the plugin under the Messaging category in the Edit > Plugins window in Unreal Editor.
Chrome, Firefox, and Safari are the browsers officially supported for the web interface, according to the documentation.
Unreal Engine Remote Control is marked as beta. Epic advises caution when using it in projects released for deployment.
The documentation does not specify a particular Unreal Engine version, hardware requirements, or product pricing. You should therefore verify compatibility with your current project and organizational environment; do not assume a version or hardware requirement that is not stated in the source. Remote Control is disabled by default in packaged projects and while a game is running. The source specifies that launch flags are required to enable it in these scenarios.
Enable the web interface
Install NodeJS on your computer and verify that its version is within the specified range. Then open your Unreal project in the Editor.
From the main menu, open Edit > Plugins. Enable the Remote Control Web Interface plugin under the Messaging category.
Restart Unreal Engine. To check that the interface is running, open Window > Developer Tools > Output Log and filter for “remote control web”. A successful startup log should show a message confirming that the web application is running, along with its port; the example port in the documentation is 7000.
On the same machine, open a browser and go to
127.0.0.1:7000. You can change the port used by the Remote Control Web Interface in the project settings. Epic’s Remote Control Quick Start document explains that additional configuration is required to connect from another computer; do not assume the details of that configuration here.
Once the web page is open, the interface reads the Remote Control Preset active in the Unreal session. In other words, properties you want to use in the panel must first be exposed in the preset. Your architectural visualization team can plan which parameters to make available and how to name them according to its control needs.
Connect a property to the panel
In the web application, switch the Control view to Design mode and open the Properties tab.
Select one of the exposed properties shown in the Properties panel and drag it into the workspace on the right. If there is no panel widget, the application creates one; it also adds a suitable widget for the selected property.
For example, an exposed Contrast property in the preset can be represented by a color picker. Epic’s documentation gives the example of connecting it to the Contrast field in the scene’s PostProcessVolume component. The available widget type can vary depending on the property’s data format.
Switch back to Control mode, change the value in the web interface, and check that the associated property updates in Unreal Editor.
To preserve your layout, save the relevant Remote Control Preset in Unreal Editor. According to the documentation, when you reopen the web application, the interface layout loads from the last saved Asset state.
The interface offers widget options such as buttons, color pickers, dials, dropdowns, joysticks, labels, lists, panels, sliders, tabs, text, toggles, and vectors. A panel is a container for other widgets. You can use a List widget to display multiple interfaces in a tab. You can configure widget labels and their connected properties. For some data formats, such as vectors, you can choose a joystick, dial, or slider display.
Use in architectural and visualization workflows
For architectural presentations or real-time visualization sessions, managing exposed scene settings from a browser provides a way to create a separate control interface. A team can make the properties it needs visible in a preset and arrange them in the panel with clear labels. Multiple clients can connect to the same web application; changes made by one client are relayed to the others through the web server. This can be useful in a shared live session.
The Remote Control Web Interface also includes dedicated tabs for Level Snapshots and Sequencer. The relevant plugin must be enabled to use Level Snapshots. The Sequencer tab lets you view sequences in the project, filter them by name, and start or resume sequences in the current level. The source notes that sequences across the project can appear in the list, but only those in the current level can be played.
Another important consideration is how updates appear when the editor is in the background. In Unreal Editor, go to Edit > Editor Preferences, then General > Performance, and turn off Use Less CPU when in Background. This can help values changed in the web application appear in the Editor. Also, if you plan to use the HTTP API, you can only work with functions and properties exposed for access by Blueprint and Python. The API includes options for recording operations in transaction history so changes can be undone; consider these according to your team’s workflow.
Common issues and next steps
The web page won’t open: Check that the plugin is enabled, Unreal Engine has been restarted, and the Output Log contains a successful startup message. The local address and example port in the source are 127.0.0.1:7000; also check whether the port has been changed in the project settings.
The expected setting isn’t in the Properties list: The web interface reads the active Remote Control Preset. Make sure the property you want to control has been exposed in the preset. Direct access through the API does not support every property either; the source further limits access based on the property type and usage mode.
A change isn’t appearing for other clients: The documentation states that multiple web clients can connect and that changes are relayed through the server. Make sure the clients are connected to the same running web application; review the required configuration separately for access across different networks.
For your first implementation, add only a few required properties to the panel and verify their corresponding values in the Editor. You can then organize tabs around your workflow and assess whether you need Sequencer or Level Snapshots integration. Include the fact that Remote Control is disabled by default in packaged projects, as well as the beta warning, in your deployment plan.
Source and license
This guide is adapted into Turkish from Epic Games’ official documentation, “Remote Control for Unreal Engine”, “Remote Control Web Application for Unreal Engine”, and “Remote Control API HTTP Reference for Unreal Engine”. The sources are provided as license=free; the content has been rewritten, with no direct quotations.
Sources
3 sourcesSource texts are not republished; short quotes are marked, everything else is our own summary and commentary.
For architecture and visualization teams in Turkey, Remote Control’s practical value lies in bringing a handful of scene-specific controls together in a shared web panel and using them with multiple clients during live sessions. Technical users can also build more customized workflows through the HTTP API and Blueprint/Python access, but doing so requires careful preparation of the preset and project structure.
Before making a decision, it is important to assess compatibility requirements as well as cost and hardware: the sources specify no pricing or hardware requirements, while the NodeJS range is 8–14.15.5. Because the feature is marked beta, test it in a controlled project before relying on it in critical production workflows; in particular, verify deployment and network access requirements separately.
Frequently asked questions
Which NodeJS version is required for the Unreal Engine Remote Control Web Interface?
According to Epic’s documentation, the required range is from a minimum of version 8 to a maximum of 14.15.5.
How do you add a scene property to the Remote Control web panel?
The property must be exposed in the Remote Control Preset. In the web application, switch to Design mode, then drag the property from the Properties tab into the workspace to add a suitable widget.
Is Remote Control enabled by default in packaged Unreal Engine projects?
No. Epic states that Remote Control is disabled by default in packaged projects and while a game is running.



