React 19.3 makes View Transitions stable

React 19.3, released on September 9, 2026, makes View Transitions stable, so React apps can animate elements as they enter, leave, move or resize using the browser’s own View Transition API ^[1]. It also adds Fragment Refs, a new browser() function for client-only components, and support for Trusted Types ^[1]. For design teams, React 19.3 is the release where motion between screens stops being a custom engineering project.

Here is what shipped, what it means for the people who design interfaces, and what we recommend before you start animating everything.

What is new in React 19.3

• View Transitions are stable. The <ViewTransition> component animates enter, exit, update and shared-element moves ^[1].
• Fragment Refs let a ref attach to a Fragment, so code can work with a group of sibling elements without adding a wrapper element ^[1].
• browser() from react-dom lets a component opt out of server rendering. On the server it shows the Suspense fallback; in the browser it renders normally ^[1].
• React DOM now supports Trusted Types, so apps that enforce a strict Content Security Policy against script injection work correctly ^[1].
• Server Components can render a Context directly, which removes small provider wrappers ^[1].

The React team lists no breaking changes, and the new features are opt in ^[1]. Next.js 16.4, released on October 6, ships with React 19.3, so Next.js teams get these features with a framework upgrade ^[4].

React View Transitions in plain terms

The browser feature underneath is the View Transition API, which MDN describes as a mechanism for “easily creating animated transitions between different website and element views” ^[2]. React 19.3 wraps it in a component. You put <ViewTransition> around something, and when that thing appears, disappears, changes or moves, the browser animates it ^[1].

There is one rule that designers should know about, because it shapes how a prototype will behave in production. Animations only run for updates React treats as transitions, such as those started with startTransition, a Suspense boundary revealing content, or useDeferredValue. Urgent updates, like typing in a field, do not animate ^[1]. That is a sensible default: it keeps input fast and saves motion for navigation and content changes.

React 19.3 also lets developers label why a transition happened with addTransitionType, so a carousel can slide in from the right when you go forward and from the left when you go back ^[1]. And when a Suspense fallback is replaced by real content, that swap can now animate instead of popping in, with images and fonts inside the boundary held until they load to avoid flicker ^[1].

This also changes how we prototype. Motion that used to live only in a Figma or After Effects mockup can now be built in the real product at similar cost, so we review transitions in the browser on real devices, where timing and performance are honest.

Fragment Refs and browser() for cleaner components

Fragment Refs solve a familiar problem. To measure a group of elements, move focus into them or watch when they scroll into view, developers used to add an extra div. That div often broke layouts built with grid or flex. With React 19.3, a ref on a Fragment gives access to methods such as focus, focusLast, addEventListener, getClientRects, scrollIntoView and observeUsing for IntersectionObserver and ResizeObserver ^[1].

For designers, the practical gain is that the markup can match the design more closely. Fewer wrapper elements means fewer surprises where spacing or alignment in the browser differs from the design file.

browser() helps with components that depend on things only the browser knows, such as local storage or the user’s time zone ^[1]. Instead of each team writing its own “is mounted” check, the server renders the Suspense fallback and the browser fills in the real component ^[1]. That makes the loading state a designed part of the page, so it deserves a real design, not a blank box.

Trusted Types and security

Trusted Types is a browser API that makes sure input passes through a defined transformation, usually sanitization, before it reaches APIs that could execute it, which protects against cross-site scripting ^[3]. MDN lists it as Baseline 2026, available across current browsers since February 2026 ^[3]. React 19.3 no longer turns Trusted Types objects into plain strings, so sites that require them can now use React without workarounds ^[1].

This matters for clients in banking, insurance and government, where security teams increasingly ask for strict Content Security Policies. It removes one reason to say no to React in those reviews.

Key takeaways

• React 19.3 shipped on September 9, 2026 with stable View Transitions ^[1].
• Only transition updates animate, so typing and other urgent input stay instant ^[1].
• Fragment Refs remove the need for wrapper elements when working with groups of elements ^[1].
• browser() gives client-only components a proper server fallback ^[1].
• Trusted Types support helps React apps pass strict security reviews ^{[1, 3]}.
• Next.js 16.4 includes React 19.3 ^[4].

Quick answers about React 19.3

Does upgrading break existing apps? The React team lists no breaking changes, and the new features must be adopted on purpose ^[1].

Does it work in React Native? View Transitions are DOM only for now; the team says React Native support is in progress ^[1].

Should every screen animate? No. Use motion where it explains a change of place or state, and respect reduced-motion settings.