--- title: "Misusing React Context, Then Blaming React Context" author: "Muhammad Afifudin" published: "2026-07-16T00:00:00.000Z" updated: "2026-08-25T06:50:00.192Z" url: "https://zyvop.com/misusing-react-context-then-blaming-react-context-i3ia8" canonical: "https://afiiif.github.io/blog/misusing-react-context-then-blaming-react-context" tags: ["react","frontend","performance"] --- # Misusing React Context, Then Blaming React Context ![Cover image]() I've come across quite a few LinkedIn posts criticizing React Context. Some of them make a claim like this: > "React Context causes every component to re-render, even components that don't consume the context." That claim is simply **incorrect**. Unfortunately, this misconception has spread widely, leading many developers to believe that React Context is inherently inefficient. In this article, I'll explain why those unexpected re-renders are usually caused by poor component composition, not by React Context itself. ## The Most Common Mistake Consider the following example: ```typescript const ThemeContext = createContext(null); function App() { const [theme, setTheme] = useState('dark'); return (