Maaz Zindani

Loading the index…

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

ref.current is null when you read a useRef in React

ErrorTypeError: 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.

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

Fix it fast

  1. 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); }, []);
  2. 2Match what you see, then jump to its fix

    1. 1The value is null on the first render, but a node laterThe ref is read during renderFix
    2. 2The ref is attached to something under a condition such as {isOpen && <input ref={inputRef} />}The element is not rendered at that momentFix
    3. 3<MyInput ref={inputRef} /> gives null, and MyInput wraps an <input>The ref goes to your own component, which never passes it onFix

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.jsx

2Fix

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 dev

Confirmed by react.dev

Did this fix it?

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.jsx

2Fix

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 dev

Confirmed by react.dev

Did this fix it?

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.jsx

2Fix

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 dev

Confirmed by react.dev

Did this fix it?

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:

Related fixes

Next step

Want this handled for good?

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