What is the purpose of a Canvas in Unity UI, and what are some recommended practices for performance?

• A. Increase the number of canvases for better performance.
• B. Keep the number of canvases low, minimize expensive layout rebuilds, use CanvasGroup to disable parts, and avoid frequent changes to UI layout.
• C. Always rebuild layouts every frame for accuracy.
• D. Disable CanvasGroup to improve performance.

Answer: (B)

The idea being tested is how Unity’s Canvas affects UI performance and what practices help keep it smooth. The Canvas is the drawing surface for UI, and Unity can trigger rebuilds and redraws whenever UI elements inside a canvas change. That means more canvases and frequent layout recalculations translate to more CPU and draw calls, which can slow things down.

Keeping the number of canvases low reduces how many separate redraw passes Unity has to perform when something changes. Each canvas can require a full or partial rebuild, so grouping UI under fewer canvases minimizes the work triggered by updates.

Minimizing expensive layout rebuilds is also key. When you use layout components like Horizontal/Vertical Layout Groups or ContentSizeFitter, any change to the layout-affecting properties can cause Unity to recalculate the entire layout for the affected canvas. If these updates happen often, you’re paying that cost repeatedly. Batch updates, avoid moving or resizing UI every frame, and try to limit changes to layout properties to reduce rebuild frequency.

Using a CanvasGroup to disable parts of the UI is another practical tip. By turning off rendering and interaction for a whole subtree, you prevent those elements from being drawn and from contributing to layout work when they’re not needed, which helps when you want to hide or pause sections of the UI without removing them entirely.

Lastly, avoid frequent changes to UI layout. Updates that touch layout components can force heavy recalculations; plan updates to happen less often or in larger chunks, and prefer animating properties that don’t require layout recalculation.

In short, fewer canvases, fewer layout rebuilds, selectively disabling unused UI with CanvasGroup, and batching layout-affecting changes together are the best practices for keeping Unity UI performant.