The difference is who owns the current value.
Uncontrolled: the DOM does. <input name="city" defaultValue="Paris" /> sets the initial value once; after that the browser keeps whatever the user types. You read it when you need it: from a ref, or with FormData when the form is submitted. Changing defaultValue in a later render doesn't change what's displayed.
Controlled: React state does. <input value={name} onChange={(e) => setName(e.target.value)} /> displays exactly name. After each change event React re-renders and then resets the DOM to the value prop, so if your handler doesn't store the new text, the keystroke is undone. Use it when the UI depends on the value while the user types: live validation, a character count, fields that appear conditionally, formatting, or a "Clear" button.
The same split applies to checked/defaultChecked on checkboxes and radios, and to <textarea> and <select>, where value/defaultValue replace HTML's children and selected.
Rules React enforces in development:
valuewithoutonChangerenders a read-only field and logs an error; addonChange,readOnly, or usedefaultValue.value={undefined}means uncontrolled. Starting withuseState()and later setting a string switches the input to controlled, which React reports.nullis also reported; use''for "empty".- Update the state synchronously in
onChange, withe.target.value. A setter called after anawait, in asetTimeout, or with a transformed value makes React write the DOM, and the browser moves the caret to the end.
A controlled input re-renders its component on every keystroke. Keep that state in a small component, or use useDeferredValue for an expensive consumer. Uncontrolled fields avoid the renders and suit plain forms whose values are read only on submit, which React 19's form Actions make the default path.