Visualize your React application's component performance metrics with a live heat map.
Branch: master
Clone or download
alchi126 Merge pull request #55 from ReactQuantum/dev
Refactor and add comments
Latest commit ee829a3 Feb 12, 2019

Visualize your React application's component performance metrics with a live heat map.

What It Does

React Quantum parses through your React application to create a color-coded tree model of its component hierarchy. On hover, each tree node will display two key component performance metrics—render time and re-render frequency—as well as memoized state and props to indicate what, specifically, initiated the render.

The beauty is in the heat map: Nodes will change color depending on the component's rendering performance, making it easy to pinpoint possible bottlenecks at a glance. 🔥

How To Get It

Quantum is available as a Chrome extension through the Google Chrome Web Store.

If you prefer to install locally, setup instructions are as follows:

  1. $ git clone

  2. $ cd ReactQuantum

  3. $ npm install

  4. $ npm run build-dev

  5. Visit chrome://extensions/

  6. Click the Load Unpacked button, then select your './ReactQuantum/build' directory

  7. Open Chrome Developer Tools (Inspect) on any page that uses React, then click on React Quantum at the top of the Developer Tools panel

  8. Click the Start Quantum button, then refresh the page or set state to trigger a re-render

  9. Optimize components!

NOTE: React Quantum works best for React v16+ local projects in development environments.


Term Definition
Render When a React component instance or DOM element is processed and checked to see if work needs to be done.
Total render time Total time a component took to render, including its children.
Individual render time Total time an individual component instance or DOM element took to render.
Current State The current state of a component. Only stateful nodes will have a value for this property.
Props The current props object being passed to this node.
Commit Count The number of times a node’s work has started in the commit phase. This could be changes to a component’s state or props, or a DOM element being added or removed.


Feel free to fork this repo and submit pull requests. If you'd like to report bugs or send suggestions, please log an issue or contact us at


Altai Chiang (

Alyson Swerdloff (

Eric Choy (

Jae Park (