What is BuildContext and how does it work in Flutter?
TL;DR: BuildContext is a handle to a widget's location in the Element tree; it's how widgets access inherited data, themes, and navigation without being tightly coupled to their parents.
Full Answer
Every Widget.build method receives a BuildContext — a reference to the Element that corresponds to this widget in the Element tree. It's the key to Flutter's dependency injection mechanism.
What you can do with BuildContext
- ▸Access inherited data: Theme.of(context), MediaQuery.of(context)
- ▸Navigate: Navigator.of(context).push(...)
- ▸Find ancestor widgets: context.findAncestorWidgetOfExactType<T>()
- ▸Show overlays: showDialog(context: context, ...)
- ▸Access Provider/Riverpod data: context.watch<T>()
Never store BuildContext in a field for use after the widget's lifecycle — the element may have moved or been removed. Instead, check mounted before using context in async callbacks.
Why context matters for performance
context.watch<T>() registers the widget to rebuild when T changes. context.read<T>() accesses T without registering a rebuild. context.select<T, R>() rebuilds only when the selected value changes. Understanding the difference prevents unnecessary rebuilds.
Code Examples
Displays 'Loading...' initially, then 'fetched data' after async call. SnackBar 'Loaded!' shown only if widget is still mounted.
Common Mistakes
- ✗Using context after an async gap without checking mounted.
- ✗Storing context in a class field — it becomes stale when the widget moves in the tree.
Interview Tip
BuildContext is actually the Element itself (both implement the same interface). The Element tree is what Flutter uses for reconciliation — widgets are just descriptions, elements hold the live state.