Roblox’s updated UI clipping is live: check rotated elements
Updated clipping is now enabled by default. Check rotated interface elements and curves; the temporary opt-out is planned to disappear in November.
Updated September 28, 2026: Roblox confirmed that StarterGui.ClipsDescendantsSupportsRotation became enabled by default on September 24. Teams can temporarily disable it and republish, but removal of the setting remains planned for November 2026. See the September 24 rollout confirmation.
Games using ClipsDescendants may now see rotated interface elements and Path2D curves cut off at their parent’s boundary. This article originally covered the September 17 rollout schedule.
Check affected menus
In Studio, set StarterGui.ClipsDescendantsSupportsRotation to Enabled. Our recommendation is to inspect menus where decorations or curves deliberately extend outside a clipping container. Check the screen sizes your game supports, especially interfaces that reposition or resize on phones.
Keep intentional overflow visible
The original announcement gives two migration options. Turn off the parent’s ClipsDescendants setting if none of its other children need clipping. Otherwise, move the element outside that parent’s hierarchy and make it a sibling with a higher Z-index. Rotated parents still cannot clip their children unless they belong to a CanvasGroup.
In a test copy, capture each affected screen with the compatibility setting disabled, then enable it and compare the same screens. Repair the hierarchy where an important element disappears and repeat the check. Focus first on screens players need to join, navigate and buy items.
The opt-out is temporary
Teams needing more time can set ClipsDescendantsSupportsRotation to Disabled and publish again. Roblox currently targets November 2026 for removing that compatibility property and applying the new behavior to all games. That is a target month, not a confirmed final date. The dated rollout confirmation takes precedence over the older August timing still visible in the original post’s table.
Publish fixes after testing the affected screens. If you use the temporary opt-out, record it as unfinished migration work so the final rollout does not catch your team by surprise.