1. Review the hierarchy before export
Check names, parent-child relationships, geometry, text, and image layers before producing the model file. Export preserves mistakes as well as correct structure.
- Give script-facing objects stable, descriptive names.
- Confirm buttons and labels are separate when they need independent behavior.
- Remove accidental duplicate or hidden layers.
- Check that the root is an appropriate ScreenGui hierarchy.
2. Download the .rbxmx model
GenGUI serializes the interface tree as Roblox XML model data. The export can also provide a Luau builder representation for supported workflows.
A .rbxmx file stores instances and their properties. It is different from a PNG: Studio can inspect its hierarchy and properties in Explorer and Properties.
3. Resolve image assets
Roblox UI images need usable Roblox asset IDs. GenGUI can export locally, or authenticated users can configure their own Roblox Open Cloud credentials to upload image assets.
Open Cloud upload is optional and uses the connected user’s credentials and selected universe. If assets are handled manually, upload them through the workflow appropriate for your Roblox account and replace image references with their asset IDs.
4. Import under StarterGui
Open the target experience in Studio, import or drag the model into the project, and place the ScreenGui under StarterGui if it is not already there.
Run a local play test. Confirm visibility, inset handling, ZIndex order, scrolling, clipping, and behavior at several viewport sizes.
5. Add and secure game logic
The exported hierarchy is a visual and structural artifact. Add LocalScripts for presentation and route authoritative actions to validated server code.
Do not let a client-side button directly grant currency, items, permissions, or purchases. The server should check every request against current game state.