React 19.3 in practice: View Transitions, Fragment Refs and more
React 19.3 makes View Transitions and Fragment Refs stable and adds browser() and Trusted Types. How to use them, plus the React Compiler, on real sites.
React 19.3, released on 9 September 2026, is the most useful React update for everyday product work in a while. It makes View Transitions and Fragment Refs stable, adds a clean way to keep a component out of server rendering, supports Trusted Types for stricter security policies, and lets Server Components render Context directly. Paired with the React Compiler, which reached 1.0 in October 2025, it changes how you write animations, wrappers and memoisation in a typical React or Next.js app.
Here is what each feature does in practice, where it helps on real sites, and how to adopt it without surprises. At the time of writing (November 2026), the latest React release on npm is 19.3.1, and Next.js 16.4 ships with React 19.3.
View Transitions: animations without a library
The <ViewTransition> component wraps part of your UI and animates it using the browser's View Transition API. The default is a cross-fade, and you can customise the animation with CSS classes or with event props such as onEnter and onExit.
The important rule is that only updates marked as Transitions animate: changes made inside startTransition, a <Suspense> boundary revealing its content, or a useDeferredValue update. Urgent updates, like typing into an input, do not animate. React decides the type of animation from how the tree changed:
- enter when the component is added;
- exit when it is removed;
- update when its content or style changes;
- share when a named transition moves from one place to another, such as a product thumbnail growing into a product hero image.
A companion function, addTransitionType, lets the same change animate differently depending on the cause. A carousel can slide left for "next" and right for "previous" from the same state update.
Where it helps
Product galleries, step-by-step forms, tab panels and page-to-page navigation are the obvious candidates. Wrapping a Suspense boundary in <ViewTransition> also lets you animate the swap from skeleton to content, and wrapping images or font styles inside Suspense makes the boundary wait for them, which reduces the flicker of images popping in late. Because it relies on a browser API, test across the browsers your visitors actually use, and respect users who prefer reduced motion.
Fragment Refs: fewer wrapper divs
Before 19.3, if you wanted to observe or focus a group of elements, you usually wrapped them in an extra <div> just to hold a ref. That extra element can break CSS grid and flex layouts and add noise to the DOM. Now you can attach a ref to a <Fragment> and get a FragmentInstance with methods such as:
-
addEventListenerandremoveEventListenerfor events on its first-level children; -
focus,focusLastandblurfor keyboard and accessibility handling; -
observeUsingto connect anIntersectionObserverorResizeObserver; -
getClientRectsandscrollIntoViewfor measuring and scrolling.
Practical uses include lazy loading a section when it scrolls into view, tracking whether a block of content was actually seen for analytics, and moving focus to the first field in a group after a validation error.
browser(): opt out of server rendering cleanly
Some components only make sense in the browser: a map, a chart that measures the window, or a widget that reads local storage. React DOM 19.3 adds browser(), used as use(browser()) inside a component. On the server it suspends, so the nearest Suspense fallback goes into the HTML. In the browser it does not suspend, so the component renders normally after hydration.
Unlike most hooks, it can be called conditionally or after an early return, so a component can skip server rendering only when it needs to, for example when no initial data was passed in. This replaces a lot of hand-written "is mounted" state and effect workarounds.
Security and Server Components improvements
Trusted Types support
Trusted Types is a browser feature that helps prevent DOM-based cross-site scripting by only allowing vetted values into risky places such as innerHTML. Previously React turned these values into plain strings, which the browser then rejected under a strict policy. React 19.3 passes them through, so a Content Security Policy with require-trusted-types-for 'script' can now work with React apps. For sites handling payments or personal data, that is a meaningful extra layer of defence.
Context directly in Server Components
Server Components can now render a Context imported from a 'use client' module directly, such as <UserContext value={currentUser}> in a layout. You no longer need a separate client Provider component just to pass server data down.
Smaller changes that affect Actions and forms
-
A new
onResetevent fires when React resets a form after a Server Action. -
submitteris now included insubmitevents, so you can tell which button submitted a form. - Transitions render independently, so a slow Transition no longer holds up unrelated ones.
-
Error.causeandAggregateError.errorsare now sent from server to client, which makes errors easier to debug.
The React Compiler alongside 19.3
The React Compiler is a build-time tool that memoises components and hooks automatically, reducing the need for useMemo, useCallback and React.memo. Version 1.0 was released in October 2025 and works with React 17 and later. In Next.js 16, it is a stable option enabled with reactCompiler: true, though it is not on by default and adds build time because it runs through Babel. A faster Rust version is experimental in Next.js 16.3 and 16.4.
The React team's guidance is practical: rely on the compiler for new code, and either leave existing memoisation alone or remove it only with good test coverage. They also recommend pinning an exact compiler version if your end-to-end tests are thin, because future versions can change how memoisation is applied. Meta reported up to 12% faster initial loads and navigations in the Meta Quest Store, with the caveat that results vary by app.
How to adopt React 19.3 safely
| Step | What to check |
|---|---|
Upgrade react and react-dom together |
Keep both on the same version. On Next.js, upgrade to 16.4, which includes React 19.3. |
| Run Strict Mode in development | Effects are now double-invoked during hydration too, which can expose effects that are not safe to run twice. |
| Fix new warnings | Incorrect use of use inside a conditional now produces a warning. |
| Add the hooks lint rules | The compiler-powered rules in eslint-plugin-react-hooks catch problems before they reach users. |
| Introduce new features one at a time | Start with one View Transition or one Fragment Ref and measure the effect before rolling out widely. |
Upgrade first, then adopt features gradually: the new APIs are opt-in, so nothing changes until you use them.
Frequently asked questions
Do I need Next.js to use React 19.3?
No. React 19.3 works with any set-up, including Vite. Server Components features need a framework that supports them, such as Next.js.
Will View Transitions slow my site down?
They use the browser's built-in API rather than a JavaScript animation library, so they can be lighter than the alternatives. As with any animation, keep them short and test on lower-end phones.
Should I delete all my useMemo and useCallback calls?
Not straight away. The React team suggests leaving existing memoisation in place or removing it carefully with tests, because removal can change what the compiler outputs.
Need help with your React app?
We build and maintain React front ends and Next.js sites, including upgrades, performance work and accessible UI patterns. See our React development services, the React front end and Node.js API we built for a startup incubator, and our comparison of React vs Next.js. If you would like a second pair of hands, get in touch.
Sources: React 19.3 release post, React Compiler v1.0, Next.js 16 release post, Next.js 16.4 release post.
(over to you)
Planning a build like this?
Tell us what you're building and we'll come back with ideas and next steps.
Keep reading
All articles
React & Next.js
· 7 min read
Figma to code handoff: code layers, GitHub and your agency
Read article
React & Next.js
· 8 min read
Next.js multi-language website: i18n routing and RTL done right
Read article
React & Next.js
· 6 min read
Next.js SEO for marketing sites: metadata, sitemaps and schema
Read article