Tutorials Logic, IN info@tutorialslogic.com
Navigation
Home About Us Contact Us Blogs FAQs
Tutorials
All Tutorials
Services
Academic Projects Resume Writing Website Development
Practice
Quiz Challenge Interview Questions Certification Practice
Tools
Online Compiler JSON Formatter Regex Tester CSS Unit Converter Color Picker
Compiler Tools

React useState Hook State Management: Tutorial, Examples, FAQs & Interview Tips

What Is State?

State is data stored inside a component that can change over time. When state changes, React re-renders the component so the UI shows the latest value. State is what makes React interfaces interactive.

Examples of state include a counter value, search text, whether a modal is open, form input values, selected tabs, and fetched data that must be displayed on the page.

State vs Props

FeaturePropsState
Where it comes fromPassed from parentStored inside the component
Can it change?Not by the childYes, through a state setter
Main purposeReceive external inputStore changing local data

Adding State with useState

The useState hook adds state to function components. It returns two values: the current state and a function used to update that state.

Basic useState Example
import { useState } from 'react'

function Counter() {
    const [count, setCount] = useState(0)

    return (
        <div>
            <p>Count: {count}</p>
            <button onClick={() => setCount(count + 1)}>Increase</button>
        </div>
    )
}

Updating State Correctly

When the next state depends on the previous state, use the functional form of the setter. This avoids stale values during rapid updates.

setCount(previousCount => previousCount + 1)

Multiple State Values

A component can have more than one piece of state. Each piece should represent one meaningful changing value.

const [name, setName] = useState('')
const [age, setAge] = useState(0)
const [isOnline, setIsOnline] = useState(false)

State with Objects

When state is an object, remember to copy the old object before changing a single field. Unlike class component state, React does not merge object state automatically in function components.

const [user, setUser] = useState({ name: 'Aman', city: 'Delhi' })

function changeCity() {
    setUser(current => ({
        ...current,
        city: 'Mumbai'
    }))
}

State with Arrays

Arrays in state should also be updated immutably. Instead of changing the existing array directly, create a new array with methods such as map, filter, or the spread operator.

const [items, setItems] = useState(['HTML', 'CSS'])

function addItem() {
    setItems(current => [...current, 'React'])
}

function removeItem(itemToRemove) {
    setItems(current => current.filter(item => item !== itemToRemove))
}

Important State Rules

  • Never change state directly
  • Always use the setter returned by useState
  • Use a new object or array when updating complex values
  • Keep state as small and focused as possible

How to Decide What Should Be State

A value should usually be state if it changes over time and its change should update the UI. If a value never changes or can be calculated directly from existing props and state, it may not need its own state.

Common Mistakes

MistakeWhy it is a problemBetter approach
Changing state directlyReact may not update correctlyAlways use the setter function
Storing derived values as extra stateCreates duplication and sync bugsCompute derived values during render when possible
Putting too much unrelated data in one state objectMakes updates harder to reason aboutSplit state by concern when it improves clarity
Forgetting to copy arrays or objectsMutates existing state and breaks predictabilityUse spread, map, filter, or structured updates

Best Practices

  • Use state only for values that actually change and affect rendering
  • Keep state close to the component that needs it
  • Use functional updates when the next value depends on the previous one
  • Update objects and arrays immutably
  • Do not duplicate data in multiple state variables unless there is a clear reason

Summary

State is what makes React components dynamic. It allows components to respond to user input, fetched data, and application events. Once you understand how to create, update, and organize state correctly, building interactive React interfaces becomes much easier and more predictable.

Key Takeaways
  • State is data stored inside a component that can change over time.
  • The useState hook adds state to function components.
  • Props bring data into a component, while state stores local changing data.
  • Objects and arrays in state should be updated immutably.
  • Use functional updates when the new state depends on the previous state.
  • A value should usually be state only if changing it should change the UI.

Ready to Level Up Your Skills?

Explore 500+ free tutorials across 20+ languages and frameworks.