Why use const for Flutter widgets and how does it improve performance?

What's really being asked

Whether you understand the difference between Dart const semantics and Flutter framework optimizations. Interviewers want to know if you grasp that const widgets are not just about immutability but about enabling the framework to short-circuit rebuilds and canonicalize objects.

A good answer covers four things in order

First, object canonicalization. When you mark a widget constructor as const and invoke it with compile-time constant arguments, Dart creates a single canonical instance. Multiple const Text("hello") calls in different parts of the tree return the exact same object in memory. Second, subtree rebuild short-circuiting. When a parent widget rebuilds, Flutter walks the widget tree and calls Element.updateChild. For a const child, the new widget and old widget are identical because of canonicalization. The framework immediately returns the existing Element and RenderObject without rebuilding, laying out, or painting that subtree. Third, allocation and GC pressure. Without const, every parent rebuild creates new widget objects even if nothing changed. In a long ListView or deep static subtree, this causes unnecessary allocations and garbage collection. Const eliminates these allocations entirely for static branches. Fourth, propagation requirements. Const is contagious. A widget can only be const if all its fields are const, which means its child widgets must also be const. This encourages pushing const as far down the tree as possible.

The mistakes people make

Confusing const with the final keyword or with widget immutability in general. Saying const reduces widget tree depth or makes the build method run faster in a vacuum. Claiming it is purely a style preference with no runtime effect. Asserting that const prevents state changes inside StatefulWidgets, which is unrelated.

What usually comes next

When should you avoid const? If the widget depends on runtime variables, state, or theme data that is not compile-time constant. How does const interact with Keys? Adding a const ValueKey changes canonicalization because the key becomes part of the identity. Does const help in tests? Yes, because const objects are deeply equal by identity, making assertions simpler.

A concrete example

Imagine a scrolling list of 500 static icon tiles. If each Icon and its surrounding Padding are const, scrolling does not allocate new widget instances as the viewport changes. If they are not const, the list rebuilds allocate hundreds of transient widget objects per frame, increasing GC load and jank. Profiling often shows a 10 to 30 percent reduction in build phase time for heavily const-optimized static subtrees.