Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
React 19.3 adds browser(), an API for components that cannot produce meaningful server-rendered HTML. In a Client Component, call use(browser()) inside a server-rendered <Suspense> boundary: the server outputs the boundary’s fallback, and the component renders in the browser after hydration. The API was announced on September 9, 2026, in the React 19.3 release announcement.
What React’s browser() API does
Server rendering normally lets React produce initial HTML on the server, then hydrate that HTML in the browser. The initial server and client output should match. But some interfaces rely on browser-only information—such as a value in localStorage or the user’s local time zone—and cannot produce meaningful server UI.
React 19.3 gives this case an explicit mechanism. Import browser from react-dom, then pass its result to React’s use API. On the server, the nearest Suspense boundary renders its fallback instead of that component’s content. In the browser, use(browser()) does not suspend, so the component can render after hydration. See the browser() API reference.
Calling browser() by itself does not defer rendering; the browser-only behavior comes from passing its value to use.
#1 Best Overall
How to render a browser-only component
Put the call in a Client Component and place that component under a Suspense boundary in the server-rendered tree. For example:
import { Suspense, use } from 'react';
import { browser } from 'react-dom';
function LocalTime() {
use(browser());
return <p>Your local time: {new Date().toLocaleTimeString()}</p>;
}
export default function Page() {
return (
<Suspense fallback={<p>Loading local time…</p>}>
<LocalTime />
</Suspense>
);
}The example assumes the file containing LocalTime is a Client Component. In a framework that treats modules as Server Components by default, add 'use client' at the top of that file, or move the call into a child Client Component. The fallback is what the server can show before the browser-dependent content is available, so choose text or UI that makes sense during that interval.
Requirements and failure cases
Use it in a Client Component
use(browser()) cannot be called in a Server Component. If your framework uses Server Components by default, mark the relevant module with 'use client' or put the call in a Client Component beneath it.
Provide a Suspense boundary for server rendering
The call must be inside a <Suspense> boundary when rendering on the server. Without one, the server render fails rather than substituting a fallback. The boundary’s fallback is the server-rendered representation of that deferred subtree.
Use it only when server output is not meaningful
React describes browser() as an option for the uncommon case where a component cannot produce useful server UI. It is an alternative to waiting for an effect to set mounted state or checking typeof window !== 'undefined'; it is not a general instruction to avoid server rendering. If the component can render useful, consistent initial content on the server, keep that content server-rendered.
Reporting browser bailouts
React’s server renderer can report when a subtree defers to the browser through its onBrowserBailout callback. The optional argument to browser(reason) may be a string or a function. That reason becomes the cause of the error passed to the callback; a reason function runs when the server renderer encounters the value, not in the browser.
onBrowserBailout is distinct from the server renderer’s onError callback and from hydrateRoot’s onRecoverableError callback for this bailout. The API reference describes the callback behavior.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Where it fits in React 19.3
The React Team announced React 19.3 on September 9, 2026. The release announcement also highlights stable View Transitions and Fragment Refs, Trusted Types support, and direct Context rendering from a 'use client' module in Server Components. browser() specifically concerns React DOM rendering; the announcement does not provide a framework-by-framework configuration matrix.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
