Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Next.js and React

React warns about null values and controlled or uncontrolled inputs

ErrorA component is changing an uncontrolled input to be controlled

Short answer

React treats an input as controlled when it gets a string value, and the value must stay a string for the input's whole life. Null or undefined makes React treat it as uncontrolled, so a later string triggers the warning. Start state as an empty string, or write value={x ?? ''}, and always pair value with onChange.

  • Applies to React 19, react-dom 19
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Find which input has the problem. The warning appears in the browser console with a component stack. Then log what you pass as its value.

    console.log(typeof formValues.email, formValues.email)
  2. 2Match what you see, then jump to its fix

    1. 1The warning appears on the first keystroke, or after data loads from an APIThe value starts as null or undefinedFix
    2. 2Warning mentions changing an uncontrolled input to be controlled, only after a state changeThe value changes type during the input's lifeFix
    3. 3You provided a `value` prop to a form field without an `onChange` handlervalue is set without an onChange handlerFix

What does the error look like?

  • A component is changing an uncontrolled input to be controlled
  • You provided a `value` prop to a form field without an `onChange` handler

Cause 1 of 3

The value starts as null or undefined

1Check

React docs say the value passed to a controlled component should not be undefined or null. State that is set to undefined or null at first, then to a string, switches the input's mode.

const [name, setName] = useState();  // undefined at first: the problem

2Fix

Give the state an empty string as its initial value, or coalesce a value that comes from outside.

const [firstName, setFirstName] = useState('');

<input value={user.nickname ?? ''} onChange={e => setNickname(e.target.value)} />

3Verify

Reload the page with the console open. No warning should appear while typing or after data loads.

npm run dev

Confirmed by react.dev

Did this fix it?

Cause 2 of 3

The value changes type during the input's life

1Check

The documentation says an input cannot switch between controlled and uncontrolled over its lifetime. A value passed as undefined first and a string later does exactly that. A checkbox needs a boolean in checked, always.

grep -rn "value={" src/ | head -20

2Fix

Keep value a string for the whole life of the input. If you only want an initial value and no control, use defaultValue instead of value.

<input defaultValue="Taylor" />
<input type="checkbox" checked={Boolean(done)} onChange={e => setDone(e.target.checked)} />

3Verify

Change the value that feeds the field and watch the console stay quiet.

npm run dev

Confirmed by react.dev

Did this fix it?

Cause 3 of 3

value is set without an onChange handler

1Check

Every controlled input needs an onChange handler that updates the backing value, per the React documentation.

grep -rn "<input" src/ | grep -v onChange

2Fix

Add onChange that stores the new value, or switch to defaultValue if the field should not be controlled.

<input value={email} onChange={e => setEmail(e.target.value)} />

3Verify

Type in the field. The text appears and the console has no warning.

npm run dev

Confirmed by react.dev

Did this fix it?

How do I stop it coming back?

  • Initialise every form field in state with '' (text) or false (checkbox), never undefined.
  • Coalesce server data with ?? '' at the point it reaches the input.
  • Pick controlled (value + onChange) or uncontrolled (defaultValue) per field and stay with it.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.