Can you force a React component to rerender without calling setState?

I have an external (to the component), observable object that I want to listen for changes on. When the object is updated it emits change events, and then I want to rerender the component when any change is detected.

With a top-level React.render this has been possible, but within a component it doesn’t work (which makes some sense since the render method just returns an object).

Here’s a code example:

export default class MyComponent extends React.Component {

  handleButtonClick() {

  render() {
    return (
        <button onClick={this.handleButtonClick.bind(this)}>
          Click me

Clicking the button internally calls this.render(), but that’s not what actually causes the rendering to happen (you can see this in action because the text created by {Math.random()} doesn’t change). However, if I simply call this.setState() instead of this.render(), it works fine.

So I guess my question is: do React components need to have state in order to rerender? Is there a way to force the component to update on demand without changing the state?


Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

In class components, you can call this.forceUpdate() to force a rerender.


In function components, there’s no equivalent of forceUpdate, but you can contrive a way to force updates with the useState hook.

Method 2

forceUpdate should be avoided because it deviates from a React mindset. The React docs cite an example of when forceUpdate might be used:

By default, when your component’s state or props change, your component will re-render. However, if these change implicitly (eg: data deep within an object changes without changing the object itself) or if your render() method depends on some other data, you can tell React that it needs to re-run render() by calling forceUpdate().

However, I’d like to propose the idea that even with deeply nested objects, forceUpdate is unnecessary. By using an immutable data source tracking changes becomes cheap; a change will always result in a new object so we only need to check if the reference to the object has changed. You can use the library Immutable JS to implement immutable data objects into your app.

Normally you should try to avoid all uses of forceUpdate() and only read from this.props and this.state in render(). This makes your component “pure” and your application much simpler and more efficient.forceUpdate()

Changing the key of the element you want re-rendered will work. Set the key prop on your element via state and then when you want to update set state to have a new key.

<Element key={this.state.key} />

Then a change occurs and you reset the key

this.setState({ key: Math.random() });

I want to note that this will replace the element that the key is changing on. An example of where this could be useful is when you have a file input field that you would like to reset after an image upload.

While the true answer to the OP’s question would be forceUpdate() I have found this solution helpful in different situations. I also want to note that if you find yourself using forceUpdate you may want to review your code and see if there is another way to do things.

NOTE 1-9-2019:

The above (changing the key) will completely replace the element. If you find yourself updating the key to make changes happen you probably have an issue somewhere else in your code. Using Math.random() in key will re-create the element with each render. I would NOT recommend updating the key like this as react uses the key to determine the best way to re-render things.

Method 3

Actually, forceUpdate() is the only correct solution as setState() might not trigger a re-render if additional logic is implemented in shouldComponentUpdate() or when it simply returns false.


Calling forceUpdate() will cause render() to be called on the component, skipping shouldComponentUpdate(). more…


setState() will always trigger a re-render unless conditional rendering logic is implemented in shouldComponentUpdate(). more…

forceUpdate() can be called from within your component by this.forceUpdate()

Hooks: How can I force component to re-render with hooks in React?

BTW: Are you mutating state or your nested properties don’t propagate?

Method 4

In 2021 and 2022, this is the official way to forceUpdate a React Functional Component.

const [, forceUpdate] = useReducer(x => x + 1, 0);

  function handleClick() {

I know the OP is for a class component. But the question was asked in 2015 and now that hooks are available, many may search for forceUpdate in functional components. This little bit is for them.

Edit 18th Apr 2022

It’s usually bad practice to be force updating your components.

A few things that can cause the need to use force updates.

  • Not using state variables where you have to – local, redux, context.
  • The field from the state object you are trying to access and expecting to update/change is too deeply nested in objects or arrays. Even Redux advises to maintain flat objects or arrays. If only one field value changes in a complex object, React may not figure out that the state object has changed, thus it does not update the component. Keep your state flat and simple.
  • The key on your list items, as mentioned in another answer. In fact, this can cause other unexpected behaviors as well. I’ve seen lists where items are repeatedly rendered (duplicates) because the keys aren’t identical or the keys are just missing altogether. Always request the backend team to send unique ids everywhere possible! Avoid using array indexes for keys. Do not try to create unique ids on the front-end by using nanoid, uuid or random. Because ids created using above methods change each time the component updates (keys provided to a list need to be static and the same on each render). Creating unique ids is usually a backend concern. Try your best to not bring that requirement to the front-end. The front-end’s responsibility is only to paint what data the backend returns and not create data on the fly.
  • If your useEffect, useCallback dependency arrays do not have the proper values set. Use ESLint to help you with this one! Also, this is one of the biggest causes for memory leaks in React. Clean up your state and event listeners in the return callback to avoid memory leaks. Because such memory leaks are awfully difficult to debug.
  • Always keep an eye on the console. It’s your best friend at work. Solving warning and errors that show up in the console can fix a whole lot of nasty things – bugs and issues that you aren’t even aware off.

A few things I can remember that I did wrong. In case it helps..

Method 5

I Avoided forceUpdate by doing following

WRONG WAY : do not use index as key, index) =>
   <MyComponent cell={item} key={index} />

CORRECT WAY : Use data id as key, it can be some guid etc =>
   <MyComponent item={item} key={} />

so by doing such code improvement your component will be UNIQUE and render naturally

Method 6

When you want two React components to communicate, which are not bound by a relationship (parent-child), it is advisable to use Flux or similar architectures.

What you want to do is to listen for changes of the observable component store, which holds the model and its interface, and saving the data that causes the render to change as state in MyComponent. When the store pushes the new data, you change the state of your component, which automatically triggers the render.

Normally you should try to avoid using forceUpdate() . From the documentation:

Normally you should try to avoid all uses of forceUpdate() and only read from this.props and this.state in render(). This makes your application much simpler and more efficient

Method 7

use hooks or HOC take your pick

Using hooks or the HOC (higher order component) pattern, you can have automatic updates when your stores change. This is a very light-weight approach without a framework.

useStore Hooks way to handle store updates

interface ISimpleStore {
  on: (ev: string, fn: () => void) => void;
  off: (ev: string, fn: () => void) => void;

export default function useStore<T extends ISimpleStore>(store: T) {
  const [storeState, setStoreState] = useState({store});
  useEffect(() => {
    const onChange = () => {
    store.on('change', onChange);
    return () => {'change', onChange);
  }, []);

withStores HOC handle store updates

export default function (...stores: SimpleStore[]) {
  return function (WrappedComponent: React.ComponentType<any>) {
    return class WithStore extends PureComponent<{}, {lastUpdated: number}> {
      constructor(props: React.ComponentProps<any>) {
        this.state = {
        this.stores = stores;

      private stores?: SimpleStore[];

      private onChange = () => {

      componentDidMount = () => {
        this.stores &&
          this.stores.forEach((store) => {
            // each store has a common change event to subscribe to
            store.on('change', this.onChange);

      componentWillUnmount = () => {
        this.stores &&
          this.stores.forEach((store) => {
  'change', this.onChange);

      render() {
        return (

SimpleStore class

import AsyncStorage from '@react-native-community/async-storage';
import ee, {Emitter} from 'event-emitter';

interface SimpleStoreArgs {
  key?: string;
  defaultState?: {[key: string]: any};

export default class SimpleStore {
  constructor({key, defaultState}: SimpleStoreArgs) {
    if (key) {
      this.key = key;
      // hydrate here if you want w/ localState or AsyncStorage
    if (defaultState) {
      this._state = {...defaultState, loaded: false};
    } else {
      this._state = {loaded: true};
  protected key: string = '';
  protected _state: {[key: string]: any} = {};
  protected eventEmitter: Emitter = ee({});
  public setState(newState: {[key: string]: any}) {
    this._state = {...this._state, ...newState};
    if (this.key) {
      // store on client w/ localState or AsyncStorage
  public get state() {
    return this._state;
  public on(ev: string, fn:() => void) {
    this.eventEmitter.on(ev, fn);
  public off(ev: string, fn:() => void) {, fn);
  public get loaded(): boolean {
    return !!this._state.loaded;

How to Use

In the case of hooks:

// use inside function like so
const someState = useStore(myStore);
someState.myProp = 'something';

In the case of HOC:

// inside your code get/set your store and stuff just updates
const val = myStore.myProp;
myOtherStore.myProp = 'something';
// return your wrapped component like so
export default withStores(myStore)(MyComponent);

To export your stores as a singleton to get the benefit of global change like so:

class MyStore extends SimpleStore {
  public get someProp() {
    return this._state.someProp || '';
  public set someProp(value: string) {
    this.setState({...this._state, someProp: value});
// this is a singleton
const myStore = new MyStore();
export {myStore};

This approach is pretty simple and works for me. I also work in large teams and use Redux and MobX and find those to be good as well but just a lot of boilerplate. I just personally like my own approach because I always hated a lot of code for something that can be simple when you need it to be.

Method 8

So I guess my question is: do React components need to have state in
order to rerender? Is there a way to force the component to update on
demand without changing the state?

The other answers have tried to illustrate how you could, but the point is that you shouldn’t. Even the hacky solution of changing the key misses the point. The power of React is giving up control of manually managing when something should render, and instead just concerning yourself with how something should map on inputs. Then supply stream of inputs.

If you need to manually force re-render, you’re almost certainly not doing something right.

Method 9

There are a few ways to rerender your component:

The simplest solution is to use forceUpdate() method:


One more solution is to create not used key in the state(nonUsedKey)
and call setState function with update of this nonUsedKey:

this.setState({ nonUsedKey: } );

Or rewrite all current state:


Props changing also provides component rerender.

Method 10

For completeness, you can also achieve this in functional components:

const [, updateState] = useState();
const forceUpdate = useCallback(() => updateState({}), []);
// ...

Or, as a reusable hook:

const useForceUpdate = () => {
  const [, updateState] = useState();
  return useCallback(() => updateState({}), []);
// const forceUpdate = useForceUpdate();


Please note that using a force-update mechanism is still bad practice as it goes against the react mentality, so it should still be avoided if possible.

Method 11

You could do it a couple of ways:

1. Use the forceUpdate() method:

There are some glitches that may happen when using the forceUpdate() method. One example is that it ignores the shouldComponentUpdate() method and will re-render the view regardless of whether shouldComponentUpdate() returns false. Because of this using forceUpdate() should be avoided when at all possible.

2. Passing this.state to the setState() method

The following line of code overcomes the problem with the previous example:


Really all this is doing is overwriting the current state with the current state which triggers a re-rendering. This still isn’t necessarily the best way to do things, but it does overcome some of the glitches you might encounter using the forceUpdate() method.

Method 12

We can use this.forceUpdate() as below.

       class MyComponent extends React.Component {

      handleButtonClick = ()=>{

 render() {

   return (
        <button  onClick={this.handleButtonClick}>
        Click me

 ReactDOM.render(<MyComponent /> , mountNode);

The Element ‘Math.random’ part in the DOM only gets updated even if you use the setState to re-render the component.

All the answers here are correct supplementing the question for we know to re-render a component with out using setState({}) is by using the forceUpdate().

The above code runs with setState as below.

 class MyComponent extends React.Component {

             handleButtonClick = ()=>{
                this.setState({ });

        render() {
         return (
    <button  onClick={this.handleButtonClick}>
      Click me

ReactDOM.render(<MyComponent /> , mountNode);

Method 13

Just another reply to back-up the accepted answer 🙂

React discourages the use of forceUpdate() because they generally have a very “this is the only way of doing it” approach toward functional programming. This is fine in many cases, but many React developers come with an OO-background, and with that approach, it’s perfectly OK to listen to an observable object.

And if you do, you probably know you MUST re-render when the observable “fires”, and as so, you SHOULD use forceUpdate() and it’s actually a plus that shouldComponentUpdate() is NOT involved here.

Tools like MobX, that takes an OO-approach, is actually doing this underneath the surface (actually MobX calls render() directly)

Method 14

forceUpdate(); method will work but it is advisable to use setState();

Method 15

In order to accomplish what you are describing please try this.forceUpdate().

Method 16

Another way is calling setState, AND preserve state:


Method 17

forceUpdate(), but every time I’ve ever heard someone talk about it, it’s been followed up with you should never use this.

Method 18

I have found it best to avoid forceUpdate(). One way to force re-render is to add dependency of render() on a temporary external variable and change the value of that variable as and when needed.

Here’s a code example:

class Example extends Component{
      this.state = {temp:0};

      this.forceChange = this.forceChange.bind(this);

      this.setState(prevState => ({
          temp: prevState.temp++

         <div>{this.state.temp &&
                  ... add code here ...

Call this.forceChange() when you need to force re-render.

Method 19

ES6 – I am including an example, which was helpful for me:

In a “short if statement” you can pass empty function like this:

isReady ? ()=>{} : onClick

This seems to be the shortest approach.


Method 20

use useEffect as a mix of componentDidMount, componentDidUpdate, and componentWillUnmount, as stated in the React documentation.

To behave like componentDidMount, you would need to set your useEffect like this:

  useEffect(() => console.log('mounted'), []);

The first argument is a callback that will be fired based on the second argument, which is an array of values. If any of the values in that second argument changed, the callback function you defined inside your useEffect will be fired.

In the example I’m showing, however, I’m passing an empty array as my second argument, and that will never be changed, so the callback function will be called once when the component mounts.

That kind of summarizes useEffect. If instead of an empty value, you have an argument, like:

 useEffect(() => {

  }, [props.lang]);

That means that every time props.lang changes, your callback function will be called. The useEffect will not rerender your component really, unless you’re managing some state inside that callback function that could fire a re-render.

If you want to fire a re-render, your render function needs to have a state that you are updating in your useEffect.

For example, in here, the render function starts by showing English as the default language and in my use effect I change that language after 3 seconds, so the render is re-rendered and starts showing “spanish”.

function App() {
  const [lang, setLang] = useState("english");

  useEffect(() => {
    setTimeout(() => {
    }, 3000);
  }, []);

  return (
    <div className="App">

Method 21

You can use forceUpdate() for more details check (forceUpdate()).

Method 22

bruh if I do not care about persisting the local state or any data, I just to location.reload(), this re loads the page, also obviously re-renders the component

All methods was sourced from or, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

0 0 votes
Article Rating
Notify of

Inline Feedbacks
View all comments
Would love your thoughts, please comment.x