A disabled input is missing from react-hook-form's submitted data
disabled input value is undefined in handleSubmitShort answer
react-hook-form treats a disabled field as having no value, so it returns undefined and leaves the field out of the data passed to handleSubmit. Built-in rules like required are skipped for it too. If users should see a value but not edit it, use readOnly instead of disabled.
Fix it fast
1Find out which cause you have
Log the data in handleSubmit and compare it with the fields on screen.
const onSubmit = (data) => console.log(data);2Match what you see, then jump to its fix
What does the error look like?
disabled input value is undefined in handleSubmitfield missing from the submitted data object
Cause 1 of 2
The field is disabled
1Check
Find disabled on the input or in the register options.
grep -rn "disabled" src/forms/2Fix
Replace disabled with readOnly when you still need the value. Note that the useForm-level disabled option disables the whole form and all its inputs.
<input readOnly {...register("id")} />3Verify
The value appears in the logged data.
// submit the form and read the consoleConfirmed by react-hook-form.com
Cause 2 of 2
Built-in validation silently skipped on the disabled field
1Check
Rules such as required or minLength no longer apply once the field is disabled.
grep -rn "required" src/forms/2Fix
Validate with a schema and check for undefined, or switch to readOnly.
// with a schema resolver
z.object({ id: z.string() })3Verify
Submitting without a value now shows an error.
// submit the formConfirmed by react-hook-form.com
How do I stop it coming back?
- Use disabled only for fields that really should be absent from the data.
- Test submit output whenever you toggle a field's editable state.
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:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Web apps
React Hook Form isDirty does not go back to false
formState.isDirty is false after setValue
React Hook Form sets isDirty by comparing the current values with defaultValues.
4 causes, each with a fixWeb apps
Module not found for antd/dist/antd.less after upgrading to Ant Design 5
Module not found: Error: Can't resolve 'antd/dist/antd.less'
Ant Design 5 dropped Less and the bundled CSS file for CSS-in-JS, so antd/dist/antd.less no longer exists.
3 causes, each with a fixWeb apps
Astro Code component fails inside a React component
Astro components cannot be rendered directly via function call
Astro components such as Code only exist on the server and render static HTML.
2 causes, each with a fixWeb apps
React shows Attempted import error when importing a component or function
Attempted import error:
The build found the file but not the name you asked for.
2 causes, each with a fixWeb apps
How to catch and handle a 422 from Axios in a Redux thunk
action.error.message is 'Rejected' and action.payload is undefined
A 422 means the server read the request but cannot process its content, so repeating it unchanged fails again.
4 causes, each with a fixWeb apps
axios gets 429 Too Many Requests from a React app
429 (Too Many Requests)
A 429 comes from the server or an API gateway, not from axios: your client sent too many requests in a window.
4 causes, each with a fix