Dev Environment
Designed to be used with develop builds, the Dev Environment is a browser environment that emulates the Unity Playworks preview page locally. Developers can speed up debugging times, test all Unity Playworks Fields, and verify all code paths for Runtime Analysis before uploading their projects to Unity Playworks more easily.
Disabling the Dev Environment
You can view an original page by appending /iframe.html to the end of the URL (for example: http://127.0.0.1:8000/ should be replaced with http://127.0.0.1:8000/iframe.html).
Differences between Dev Environment and Unity Playworks preview
The Dev Environment supports a limited set of features compared to Unity Playworks.
Supported features:
- Unity Playworks Fields to test and verify code paths for Runtime Analysis.
- Fields and settings state persistence across page reloads.
- Post effects section for setting up post-effects. All configured options are persisted in the exported build bundle once you build the playable.
- Performance tab to track playable performance.
- QR code support to test on other devices.
- Enter / Exit Fullscreen button to hide or show the Unity Playworks interface.
Not supported:
- Creative versions
- Preloader section
- Filter Settings section
- Uploading assets (fonts, images, video, audio)
- Playworks Preview
- Dev Environment
- Fullscreen



Main components
Performance Sidebar
The Performance sidebar provides a diagnostic view of your playable's resource usage, including CPU, RAM, and average frame time. A frame breakdown pie chart shows how processing time is distributed across Rendering, Animator, Particles, Callbacks, and Physics, with clickable segments for deeper analysis. Detailed rendering metrics such as draw calls, vertices, and UI element count help you identify bottlenecks and optimize your playable.

Events list
Toggle to view the list of tracked events in the playable. The state persists after page reload.

Device Orientation
Select a target device and switch between portrait and landscape to preview how the playable looks on different screen sizes.

Undo actions
Control override field state with undo buttons or reset the playable to its initial state.

QR Code
You can easily test a playable on multiple devices with the QR code provided when running a development build in the Dev Environment.
Click on the QR icon located on the top-right of the middle container:

and the QR code will pop up:

Make sure your device and your computer are connected to the same network.
Scan the QR code and you are now able to test your playable from another device!
Stubber warnings
This notification shows detected usage of unsupported API used in playable. For how to stub or exclude unneeded libraries, see Automatic Stubbing.
