Config v5 compatibility

Preserve Tamagui v2 token and theme values while migrating to v3

Config v5 preserves Tamagui v2 design values while an app adopts the v3 APIs and runtime.

Tamagui v3 defaults to Config v6. Use this frozen compatibility pack when an existing application’s layout and visual design still depend on v5 values. The dynamic v5 theme builders are not included in v3.

The v5 entry preserves the familiar independent size and space scales, the 12-step adaptive color ramp, surface theme names, component themes, fonts, and shorthands:

tamagui.config.ts
import { animationsCSS } from '@tamagui/config/animations-css'
import { defaultConfig } from '@tamagui/config/v5'
import { createTamagui } from 'tamagui'

export const config = createTamagui({
  ...defaultConfig,
  animations: animationsCSS,
})

The subtle pack exports its muted generated themes separately, matching its v2 API:

tamagui.config.ts
import { animationsCSS } from '@tamagui/config/animations-css'
import { defaultConfig, themes } from '@tamagui/config/v5-subtle'
import { createTamagui } from 'tamagui'

export const config = createTamagui({
  ...defaultConfig,
  themes,
  animations: animationsCSS,
})

The static theme data is also available from @tamagui/themes/v5, @tamagui/themes/v5-subtle, and @tamagui/themes/v5-tokens. Legacy animation imports at @tamagui/config/v5-css, /v5-rn, /v5-reanimated, and /v5-motion remain aliases to their maintained unversioned entries.

The compatibility lane does not restore @tamagui/theme-builder, @tamagui/themes/v5-builder, or @tamagui/themes/v5-subtle-builder. Those builders carried a second theme-generation architecture. New custom themes should use @tamagui/themes/builder.

Read the v3 upgrade guide when you are ready to move to the v6 11-step color ramp and level-based surfaces.

Introduction

Edit this page on GitHub.