\n\nThese docs are old and won’t be updated. Go to react.dev for the new React docs.
\nThese new documentation pages teach modern React and include live examples:
\n\n
Context provides a way to pass data through the component tree without having to pass props down manually at every level.
\nIn a typical React application, data is passed top-down (parent to child) via props, but such usage can be cumbersome for certain types of props (e.g. locale preference, UI theme) that are required by many components within an application. Context provides a way to share values like these between components without having to explicitly pass a prop through every level of the tree.
\nContext is designed to share data that can be considered “global” for a tree of React components, such as the current authenticated user, theme, or preferred language. For example, in the code below we manually thread through a “theme” prop in order to style the Button component:
\nclass App extends React.Component {\n render() {\n return <Toolbar theme=\"dark\" />;\n }\n}\n\nfunction Toolbar(props) {\n // The Toolbar component must take an extra \"theme\" prop // and pass it to the ThemedButton. This can become painful // if every single button in the app needs to know the theme // because it would have to be passed through all components. return (\n <div>\n <ThemedButton theme={props.theme} /> </div>\n );\n}\n\nclass ThemedButton extends React.Component {\n render() {\n return <Button theme={this.props.theme} />;\n }\n}Using context, we can avoid passing props through intermediate elements:
\n// Context lets us pass a value deep into the component tree// without explicitly threading it through every component.// Create a context for the current theme (with \"light\" as the default).const ThemeContext = React.createContext('light');\nclass App extends React.Component {\n render() {\n // Use a Provider to pass the current theme to the tree below. // Any component can read it, no matter how deep it is. // In this example, we're passing \"dark\" as the current value. return (\n <ThemeContext.Provider value=\"dark\"> <Toolbar />\n </ThemeContext.Provider>\n );\n }\n}\n\n// A component in the middle doesn't have to// pass the theme down explicitly anymore.function Toolbar() {\n return (\n <div>\n <ThemedButton />\n </div>\n );\n}\n\nclass ThemedButton extends React.Component {\n // Assign a contextType to read the current theme context. // React will find the closest theme Provider above and use its value. // In this example, the current theme is \"dark\". static contextType = ThemeContext;\n render() {\n return <Button theme={this.context} />; }\n}Context is primarily used when some data needs to be accessible by many components at different nesting levels. Apply it sparingly because it makes component reuse more difficult.
\nIf you only want to avoid passing some props through many levels, component composition is often a simpler solution than context.
\nFor example, consider a Page component that passes a user and avatarSize prop several levels down so that deeply nested Link and Avatar components can read it:
<Page user={user} avatarSize={avatarSize} />\n// ... which renders ...\n<PageLayout user={user} avatarSize={avatarSize} />\n// ... which renders ...\n<NavigationBar user={user} avatarSize={avatarSize} />\n// ... which renders ...\n<Link href={user.permalink}>\n <Avatar user={user} size={avatarSize} />\n</Link>It might feel redundant to pass down the user and avatarSize props through many levels if in the end only the Avatar component really needs it. It’s also annoying that whenever the Avatar component needs more props from the top, you have to add them at all the intermediate levels too.
One way to solve this issue without context is to pass down the Avatar component itself so that the intermediate components don’t need to know about the user or avatarSize props:
function Page(props) {\n const user = props.user;\n const userLink = (\n <Link href={user.permalink}>\n <Avatar user={user} size={props.avatarSize} />\n </Link>\n );\n return <PageLayout userLink={userLink} />;\n}\n\n// Now, we have:\n<Page user={user} avatarSize={avatarSize} />\n// ... which renders ...\n<PageLayout userLink={...} />\n// ... which renders ...\n<NavigationBar userLink={...} />\n// ... which renders ...\n{props.userLink}With this change, only the top-most Page component needs to know about the Link and Avatar components’ use of user and avatarSize.
This inversion of control can make your code cleaner in many cases by reducing the amount of props you need to pass through your application and giving more control to the root components. Such inversion, however, isn’t the right choice in every case; moving more complexity higher in the tree makes those higher-level components more complicated and forces the lower-level components to be more flexible than you may want.
\nYou’re not limited to a single child for a component. You may pass multiple children, or even have multiple separate “slots” for children, as documented here:
\nfunction Page(props) {\n const user = props.user;\n const content = <Feed user={user} />;\n const topBar = (\n <NavigationBar>\n <Link href={user.permalink}>\n <Avatar user={user} size={props.avatarSize} />\n </Link>\n </NavigationBar>\n );\n return (\n <PageLayout\n topBar={topBar}\n content={content}\n />\n );\n}This pattern is sufficient for many cases when you need to decouple a child from its immediate parents. You can take it even further with render props if the child needs to communicate with the parent before rendering.
\nHowever, sometimes the same data needs to be accessible by many components in the tree, and at different nesting levels. Context lets you “broadcast” such data, and changes to it, to all components below. Common examples where using context might be simpler than the alternatives include managing the current locale, theme, or a data cache.
\nReact.createContext const MyContext = React.createContext(defaultValue);Creates a Context object. When React renders a component that subscribes to this Context object it will read the current context value from the closest matching Provider above it in the tree.
The defaultValue argument is only used when a component does not have a matching Provider above it in the tree. This default value can be helpful for testing components in isolation without wrapping them. Note: passing undefined as a Provider value does not cause consuming components to use defaultValue.
Context.Provider <MyContext.Provider value={/* some value */}>Every Context object comes with a Provider React component that allows consuming components to subscribe to context changes.
\nThe Provider component accepts a value prop to be passed to consuming components that are descendants of this Provider. One Provider can be connected to many consumers. Providers can be nested to override values deeper within the tree.
All consumers that are descendants of a Provider will re-render whenever the Provider’s value prop changes. The propagation from Provider to its descendant consumers (including .contextType and useContext) is not subject to the shouldComponentUpdate method, so the consumer is updated even when an ancestor component skips an update.
Changes are determined by comparing the new and old values using the same algorithm as Object.is.
\n\nNote
\nThe way changes are determined can cause some issues when passing objects as
\nvalue: see Caveats.
Class.contextType class MyClass extends React.Component {\n componentDidMount() {\n let value = this.context;\n /* perform a side-effect at mount using the value of MyContext */\n }\n componentDidUpdate() {\n let value = this.context;\n /* ... */\n }\n componentWillUnmount() {\n let value = this.context;\n /* ... */\n }\n render() {\n let value = this.context;\n /* render something based on the value of MyContext */\n }\n}\nMyClass.contextType = MyContext;The contextType property on a class can be assigned a Context object created by React.createContext(). Using this property lets you consume the nearest current value of that Context type using this.context. You can reference this in any of the lifecycle methods including the render function.
\n\nNote:
\nYou can only subscribe to a single context using this API. If you need to read more than one see Consuming Multiple Contexts.
\nIf you are using the experimental public class fields syntax, you can use a static class field to initialize your
\ncontextType.
class MyClass extends React.Component {\n static contextType = MyContext;\n render() {\n let value = this.context;\n /* render something based on the value */\n }\n}Context.Consumer <MyContext.Consumer>\n {value => /* render something based on the context value */}\n</MyContext.Consumer>A React component that subscribes to context changes. Using this component lets you subscribe to a context within a function component.
\nRequires a function as a child. The function receives the current context value and returns a React node. The value argument passed to the function will be equal to the value prop of the closest Provider for this context above in the tree. If there is no Provider for this context above, the value argument will be equal to the defaultValue that was passed to createContext().
\n\nNote
\nFor more information about the ‘function as a child’ pattern, see render props.
\n
Context.displayName Context object accepts a displayName string property. React DevTools uses this string to determine what to display for the context.
For example, the following component will appear as MyDisplayName in the DevTools:
\nconst MyContext = React.createContext(/* some value */);\nMyContext.displayName = 'MyDisplayName';\n<MyContext.Provider> // \"MyDisplayName.Provider\" in DevTools\n<MyContext.Consumer> // \"MyDisplayName.Consumer\" in DevToolsA more complex example with dynamic values for the theme:
\ntheme-context.js\n
export const themes = {\n light: {\n foreground: '#000000',\n background: '#eeeeee',\n },\n dark: {\n foreground: '#ffffff',\n background: '#222222',\n },\n};\n\nexport const ThemeContext = React.createContext( themes.dark // default value);themed-button.js\n
import {ThemeContext} from './theme-context';\n\nclass ThemedButton extends React.Component {\n render() {\n let props = this.props;\n let theme = this.context; return (\n <button\n {...props}\n style={{backgroundColor: theme.background}}\n />\n );\n }\n}\nThemedButton.contextType = ThemeContext;\nexport default ThemedButton;app.js\n
import {ThemeContext, themes} from './theme-context';\nimport ThemedButton from './themed-button';\n\n// An intermediate component that uses the ThemedButton\nfunction Toolbar(props) {\n return (\n <ThemedButton onClick={props.changeTheme}>\n Change Theme\n </ThemedButton>\n );\n}\n\nclass App extends React.Component {\n constructor(props) {\n super(props);\n this.state = {\n theme: themes.light,\n };\n\n this.toggleTheme = () => {\n this.setState(state => ({\n theme:\n state.theme === themes.dark\n ? themes.light\n : themes.dark,\n }));\n };\n }\n\n render() {\n // The ThemedButton button inside the ThemeProvider // uses the theme from state while the one outside uses // the default dark theme return (\n <Page>\n <ThemeContext.Provider value={this.state.theme}> <Toolbar changeTheme={this.toggleTheme} /> </ThemeContext.Provider> <Section>\n <ThemedButton /> </Section>\n </Page>\n );\n }\n}\n\nconst root = ReactDOM.createRoot(\n document.getElementById('root')\n);\nroot.render(<App />);It is often necessary to update the context from a component that is nested somewhere deeply in the component tree. In this case you can pass a function down through the context to allow consumers to update the context:
\ntheme-context.js\n
// Make sure the shape of the default value passed to\n// createContext matches the shape that the consumers expect!\nexport const ThemeContext = React.createContext({\n theme: themes.dark, toggleTheme: () => {},});theme-toggler-button.js\n
import {ThemeContext} from './theme-context';\n\nfunction ThemeTogglerButton() {\n // The Theme Toggler Button receives not only the theme // but also a toggleTheme function from the context return (\n <ThemeContext.Consumer>\n {({theme, toggleTheme}) => ( <button\n onClick={toggleTheme}\n style={{backgroundColor: theme.background}}>\n Toggle Theme\n </button>\n )}\n </ThemeContext.Consumer>\n );\n}\n\nexport default ThemeTogglerButton;app.js\n
import {ThemeContext, themes} from './theme-context';\nimport ThemeTogglerButton from './theme-toggler-button';\n\nclass App extends React.Component {\n constructor(props) {\n super(props);\n\n this.toggleTheme = () => {\n this.setState(state => ({\n theme:\n state.theme === themes.dark\n ? themes.light\n : themes.dark,\n }));\n };\n\n // State also contains the updater function so it will // be passed down into the context provider this.state = {\n theme: themes.light,\n toggleTheme: this.toggleTheme, };\n }\n\n render() {\n // The entire state is passed to the provider return (\n <ThemeContext.Provider value={this.state}> <Content />\n </ThemeContext.Provider>\n );\n }\n}\n\nfunction Content() {\n return (\n <div>\n <ThemeTogglerButton />\n </div>\n );\n}\n\nconst root = ReactDOM.createRoot(\n document.getElementById('root')\n);\nroot.render(<App />);To keep context re-rendering fast, React needs to make each context consumer a separate node in the tree.
\n// Theme context, default to light theme\nconst ThemeContext = React.createContext('light');\n\n// Signed-in user context\nconst UserContext = React.createContext({\n name: 'Guest',\n});\n\nclass App extends React.Component {\n render() {\n const {signedInUser, theme} = this.props;\n\n // App component that provides initial context values\n return (\n <ThemeContext.Provider value={theme}> <UserContext.Provider value={signedInUser}> <Layout />\n </UserContext.Provider> </ThemeContext.Provider> );\n }\n}\n\nfunction Layout() {\n return (\n <div>\n <Sidebar />\n <Content />\n </div>\n );\n}\n\n// A component may consume multiple contexts\nfunction Content() {\n return (\n <ThemeContext.Consumer> {theme => ( <UserContext.Consumer> {user => ( <ProfilePage user={user} theme={theme} /> )} </UserContext.Consumer> )} </ThemeContext.Consumer> );\n}If two or more context values are often used together, you might want to consider creating your own render prop component that provides both.
\nBecause context uses reference identity to determine when to re-render, there are some gotchas that could trigger unintentional renders in consumers when a provider’s parent re-renders. For example, the code below will re-render all consumers every time the Provider re-renders because a new object is always created for value:
class App extends React.Component {\n render() {\n return (\n <MyContext.Provider value={{something: 'something'}}> <Toolbar />\n </MyContext.Provider>\n );\n }\n}To get around this, lift the value into the parent’s state:
\nclass App extends React.Component {\n constructor(props) {\n super(props);\n this.state = {\n value: {something: 'something'}, };\n }\n\n render() {\n return (\n <MyContext.Provider value={this.state.value}> <Toolbar />\n </MyContext.Provider>\n );\n }\n}\n","frontmatter":{"title":"Context","next":null,"prev":null},"fields":{"path":"content/docs/context.md","slug":"docs/context.html"}}},"pageContext":{"slug":"docs/context.html"}},"staticQueryHashes":[]}Note
\nReact previously shipped with an experimental context API. The old API will be supported in all 16.x releases, but applications using it should migrate to the new version. The legacy API will be removed in a future major React version. Read the legacy context docs here.
\n