Server Rendering

Advanced SSR, hydration, and client-only rendering in Tamagui

Tamagui renders responsive styles and animation state on the server so the first client frame can hydrate without flickering.

How it works

Tamagui renders in three phases:

Server: Renders with proper CSS media queries for everything, including components using spring animation drivers (which normally require hard-coded values)
Client (first render): Renders with CSS to match the server output perfectly
Client (after hydration): Seamlessly swaps to springs and animations

Hydration matches the server output without flickering, even for responsive layouts with animations.

Opting out

You can opt out of SSR entirely or for specific parts of your app.

Wholesale: disableSSR

For single-page applications that don’t need SSR, disable it entirely in your config:

import { createTamagui } from 'tamagui'

export const config = createTamagui({
  // ... other config
  settings: {
    disableSSR: true, // Automatically wraps app with <ClientOnly enabled>
  },
})

When disableSSR is true:

Media queries immediately use actual values
No double render occurs
Your entire app is wrapped with <ClientOnly enabled>

Partial: ClientOnly component

For fine-grained control, wrap specific parts of your tree:

import { ClientOnly } from '@tamagui/use-did-finish-ssr'

function MyComponent() {
  return (
    <YStack>
      {/* Server-rendered for SEO */}
      <ProductInfo />

      {/* Client-only for complex interactions */}
      <ClientOnly enabled>
        <InteractiveChart />
      </ClientOnly>
    </YStack>
  )
}

Configuration component

The Configuration component is essentially a shorthand for ClientOnly. It accepts configuration settings like disableSSR:

import { Configuration } from 'tamagui'

function MyApp() {
  return (
    <Configuration disableSSR>
      {/* Everything here renders client-only */}
      <ComplexComponent />
    </Configuration>
  )
}

useMedia and SSR

The useMedia hook automatically leverages Tamagui’s smart SSR rendering. During server render, it returns appropriate defaults that match CSS media queries, then updates after hydration without flickering.

import { useMedia } from 'tamagui'

function ResponsiveComponent() {
  const media = useMedia() // Automatically handles SSR correctly

  return media.gtSm ? <DesktopView /> : <MobileView />
}

SSR hooks

useDidFinishSSR

Returns true when hydration is complete:

import { useDidFinishSSR } from '@tamagui/use-did-finish-ssr'

function MyComponent() {
  const isClient = useDidFinishSSR()

  return isClient ? <BrowserFeature /> : <Placeholder />
}

Behavior:

Server/before hydration: false
After hydration: true
Inside <ClientOnly enabled>: always true

useIsClientOnly

Checks if you’re in a client-only context:

import { useIsClientOnly } from '@tamagui/use-did-finish-ssr'

function MyComponent() {
  const isClientOnly = useIsClientOnly()

  if (isClientOnly) {
    // Safe to use browser APIs
    return <ComponentWithBrowserAPIs />
  }

  return <SSRSafeComponent />
}

useClientValue

Returns undefined during SSR, your value after hydration:

import { useClientValue } from '@tamagui/use-did-finish-ssr'

function WindowInfo() {
  const width = useClientValue(() => window.innerWidth)

  return <html.span>{width ? `${width}px` : 'Loading...'}</html.span>
}

Best practices

When to use disableSSR

Use it for:

Single-page applications
Client-only web apps
Maximum performance without SSR overhead

Avoid for:

SEO-critical content
Server-rendered frameworks (Next.js SSR/SSG)
Fast initial page loads

When to use ClientOnly