ref.current is null when you read a useRef in React
TypeError: Cannot read properties of null (reading 'focus')Short answer
A ref's current value is null until React has put the DOM node on screen, and goes back to null when the node is removed. Read it in an effect or an event handler, not during render, guard for elements that render conditionally, and pass the ref down to a real DOM element when it goes through your own component.
Fix it fast
1Find out which cause you have
Log the ref where it is read, once during render and once in an effect. If the render log is null and the effect log is a node, you read it too early.
console.log('render', inputRef.current); useEffect(() => { console.log('effect', inputRef.current); }, []);2Match what you see, then jump to its fix
- 1
The value is null on the first render, but a node laterThe ref is read during renderFix - 2
The ref is attached to something under a condition such as {isOpen && <input ref={inputRef} />}The element is not rendered at that momentFix - 3
<MyInput ref={inputRef} /> gives null, and MyInput wraps an <input>The ref goes to your own component, which never passes it onFix
- 1
What does the error look like?
TypeError: Cannot read properties of null (reading 'focus')inputRef.current is null
Cause 1 of 3
The ref is read during render
1Check
React sets current after it creates the DOM node and puts it on screen, so the first render always sees the initial value. React's docs also say not to read or write ref.current during rendering.
grep -n 'Ref.current' src/components/Form.jsx2Fix
Read it in an event handler or an effect.
useEffect(() => {
inputRef.current.focus(); // node exists by now
}, []);
function handleClick() {
inputRef.current.focus();
}3Verify
The field is focused on mount and no TypeError appears.
npm run devConfirmed by react.dev
Cause 2 of 3
The element is not rendered at that moment
1Check
React sets the ref back to null when the node leaves the screen, so a handler can run while the element is absent.
grep -n 'ref={' src/components/Form.jsx2Fix
Use optional chaining, or wait for the render that shows the element before you use the ref.
function handleClick() {
inputRef.current?.focus();
}3Verify
Click with the element hidden: nothing breaks. Click with it shown: it gets focus.
npm run devConfirmed by react.dev
Cause 3 of 3
The ref goes to your own component, which never passes it on
1Check
By default your own components do not expose refs to the DOM nodes inside them. The component must take ref as a prop (React 19; older versions need forwardRef) and hand it to a built-in element.
grep -n 'function MyInput\|forwardRef' src/components/MyInput.jsx2Fix
Accept ref and attach it to the DOM element.
function MyInput({ value, onChange, ref }) {
return <input value={value} onChange={onChange} ref={ref} />;
}3Verify
The parent's inputRef.current is the input element.
npm run devConfirmed by react.dev
How do I stop it coming back?
- Treat current as possibly null in TypeScript: useRef<HTMLInputElement>(null) and check before use.
- Keep ref reads inside handlers and effects.
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
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 fixWeb apps
Axios request is not cancelled when a React component unmounts
A cancelled request is logged as an error in the catch block
Axios cancels a request when you pass it an AbortSignal and later call abort() on its controller.
4 causes, each with a fix