preactjs

    preactjs/preact

    #281 this week

    ⚛️ Fast 3kB React alternative with the same modern API. Components & Virtual DOM.

    frontend
    components
    dom
    jsx
    preact
    react
    JavaScript
    MIT
    38.7K stars
    2.0K forks
    38.7K GitHub watchers
    Updated 6/23/2026
    View on GitHub

    Backblaze Generative Media Hackathon

    Build the next generation of AI media apps with Genblaze, stored on Backblaze B2. $10,000 in prizes.

    Enter the hackathon

    Loading star history...

    Use Cases & Benefits

    • Preact is a fast, lightweight 4kB alternative to React, providing the same modern API for building UI components with Virtual DOM.
    • It supports React-compatible features including hooks, ES6 classes, JSX, server-side rendering, hot module replacement, and a pluggable scheduler.
    • Preact's strengths include small size, high performance, and React compatibility; limitations may arise in very large React ecosystems or complex React-specific libraries.
    • Organizations can use Preact in production to build performant web apps with minimal bundle size, especially for projects requiring React-like APIs but optimized for speed and size.
    • Ideal use cases include mobile web apps, progressive web apps, and projects needing fast load times with React-style development experience.

    About preact

    [!NOTE] This is the branch for the upcoming release, for patches to v10 you need the v10.x branch

    Preact

    Fast 4kB alternative to React with the same modern API.

    All the power of Virtual DOM components, without the overhead:

    • Familiar React API & patterns: ES6 Class, hooks, and Functional Components
    • Extensive React compatibility via a simple preact/compat alias
    • Everything you need: JSX, VDOM, DevTools, HMR, SSR.
    • Highly optimized diff algorithm and seamless hydration from Server Side Rendering
    • Supports all modern browsers
    • Transparent asynchronous rendering with a pluggable scheduler

    💁 More information at the Preact Website ➞

    npm Preact Slack Community OpenCollective Backers OpenCollective Sponsors

    coveralls gzip size brotli size

    You can find some awesome libraries in the awesome-preact list :sunglasses:


    Getting Started

    💁 Note: You don't need ES2015 to use Preact... but give it a try!

    Tutorial: Building UI with Preact

    With Preact, you create user interfaces by assembling trees of components and elements. Components are functions or classes that return a description of what their tree should output. These descriptions are typically written in JSX (shown underneath), or HTM which leverages standard JavaScript Tagged Templates. Both syntaxes can express trees of elements with "props" (similar to HTML attributes) and children.

    To get started using Preact, first look at the render() function. This function accepts a tree description and creates the structure described. Next, it appends this structure to a parent DOM element provided as the second argument. Future calls to render() will reuse the existing tree and update it in-place in the DOM. Internally, render() will calculate the difference from previous outputted structures in an attempt to perform as few DOM operations as possible.

    import { h, render } from 'preact';
    // Tells babel to use h for JSX. It's better to configure this globally.
    // See https://babeljs.io/docs/en/babel-plugin-transform-react-jsx#usage
    // In tsconfig you can specify this with the jsxFactory
    /** @jsx h */
    
    // create our tree and append it to document.body:
    render(
    	<main>
    		<h1>Hello</h1>
    	</main>,
    	document.body
    );
    
    // update the tree in-place:
    render(
    	<main>
    		<h1>Hello World!</h1>
    	</main>,
    	document.body
    );
    // ^ this second invocation of render(...) will use a single DOM call to update the text of the <h1>
    

    Hooray! render() has taken our structure and output a User Interface! This approach demonstrates a simple case, but would be difficult to use as an application grows in complexity. Each change would be forced to calculate the difference between the current and updated structure for the entire application. Components can help here – by dividing the User Interface into nested Components each can calculate their difference from their mounted point. Here's an example:

    import { render, h } from 'preact';
    import { useState } from 'preact/hooks';
    
    /** @jsx h */
    
    const App = () => {
    	const [input, setInput] = useState('');
    
    	return (
    		<div>
    			<p>Do you agree to the statement: "Preact is awesome"?</p>
    			<input value={input} onInput={e => setInput(e.target.value)} />
    		</div>
    	);
    };
    
    render(<App />, document.body);
    

    Sponsors

    Become a sponsor and get your logo on our README on GitHub with a link to your site. [Become a sponsor]

               

    Backers

    Support us with a monthly donation and help us continue our activities. [Become a backer]


    License

    MIT

    Preact

    Discover Repositories

    Search across tracked repositories by name or description