Preact vs React: When the Lighter Alternative Wins 2026

What the size claim does and does not say

Preact's getting-started documentation presents its core as approximately 3kB. That makes it a credible candidate for embedded widgets, constrained mobile delivery, and pages where the framework is a meaningful share of shipped JavaScript.

It does not predict the size of your application. A Preact build may still include large editors, charts, analytics, polyfills, or compatibility dependencies. A React framework may split and stream code in ways a raw package comparison does not capture. The only defensible comparison is the production build for the same user flow.

Before changing frameworks, record:

• route-level JavaScript transferred on first load;
• parsed and executed JavaScript on representative devices;
• hydration and interaction timing;
• third-party script cost;
• the portion attributable to framework code rather than application features.

Use those measurements to decide whether the migration addresses a real bottleneck.

Signals: reactive values in Preact

Preact documents Signals as reactive primitives. A signal holds a value, a computed signal derives from other signals, and an effect can respond to dependencies. Components can read signal values without moving every piece of state into a component-local hook.

import { computed, signal } from '@preact/signals'

const quantity = signal(1)
const unitPrice = signal(12)
const total = computed(() => quantity.value * unitPrice.value)

export function CartTotal() {
  return <output>{total}</output>
}

Signals can reduce the amount of component plumbing for shared or frequently updated values. They do not make every UI faster automatically. Rendering cost still depends on component structure, DOM work, effects, data fetching, and the frequency and shape of updates. Profile the actual interaction before and after a state-model change.

preact/compat: evaluate, do not assume

Preact's switching guide documents aliases that redirect React-oriented imports to preact/compat. A Vite configuration can establish a contained pilot:

import { defineConfig } from 'vite'

export default defineConfig({
  resolve: {
    alias: {
      react: 'preact/compat',
      'react-dom': 'preact/compat',
      'react-dom/test-utils': 'preact/test-utils',
      'react/jsx-runtime': 'preact/jsx-runtime',
    },
  },
})

Run the existing unit, integration, and browser suites after applying the aliases. Pay special attention to portals, controlled inputs, refs, event behavior, Suspense, testing utilities, and packages that inspect React internals.

The migration should stop if a required dependency relies on an unsupported API or if the compatibility adapter creates more maintenance work than the measured delivery benefit justifies.

React 19 and framework requirements

React 19 added capabilities including Actions and the use API. React frameworks can also depend on server/client behavior that a client-side alias cannot reproduce. If an application uses those features, list them before a Preact pilot and verify each one against current Preact documentation.

React is often the lower-risk choice when a framework owns rendering, routing, data loading, and server components as one integrated system. The "nobody gets fired for choosing React" phrase captures familiarity, but familiarity is not a technical benchmark. The decision should rest on the application's supported APIs, maintenance capacity, and measured delivery constraints.

Native events and behavioral differences

Preact documents differences from React, including event and rendering behavior. These differences may be invisible in ordinary components and material in complex ones. Tests should cover event propagation, focus management, input composition, and browser accessibility behavior rather than only snapshot markup.

React Native also remains a separate platform requirement. There is no "Preact Native." If the product shares components or team practices with a React Native application, that constraint may outweigh a client-bundle reduction on the web.

Dated package activity

The official npm API reported 143,911,781 downloads for React and 25,527,492 for Preact during 2026-08-13 through 2026-08-19. Dividing those same-period values gives a 5.64x ratio.

The repository snapshot dated 2026-08-16 recorded React 19.2.8 with 247,283 GitHub stars and Preact 10.29.8 with 38,819. These figures help establish current package identity and activity. They do not prove that one framework has proportionally more compatible libraries, available engineers, or production reliability.

See the live package comparison at pkgpulse.com/compare/preact-vs-react.

Explore related comparisons: HTMX vs React, React vs Vue, and Redux vs Zustand. Related guides: Angular vs React, HTMX vs React, and Qwik vs React.