htmx is a 14 KB JavaScript library that lets any HTML element trigger AJAX requests, swap chunks of HTML into the page and respond to WebSockets or Server-Sent Events — without a single line of fetch(), a build step, or a virtual DOM. We rate it 87/100 — the most pragmatic frontend tool to land in years for backend-heavy teams, but a poor fit if your product is a rich single-page application or your team has built its career around React.

What is htmx?

htmx was created by Carson Gross as a renamed and trimmed-down successor to his earlier intercooler.js project, with the first htmx-branded release shipping on November 24, 2020. The library extends HTML with about a dozen new attributes — hx-get, hx-post, hx-target, hx-swap, hx-trigger, hx-boost, hx-push-url and friends — that let any element issue HTTP requests and patch the response straight into the DOM. As of April 29, 2026, the project sits at roughly 47,900 GitHub stars, more than the React, Vue or Svelte repositories had at the same age.

The problem htmx solves is structural: most CRUD apps do not need a client-side runtime, a state-management library and a JSON serializer pretending to be a UI layer — they need to render some HTML, post a form and replace a piece of the page. htmx restores the original web's request/response model while keeping the UX expectations of 2026 (no full page reloads, smooth transitions, partial updates). The result is a rendering pipeline that lives almost entirely on the server, in whatever language the team already writes — Django, Rails, Phoenix, Laravel, Go, ASP.NET, Express, FastAPI — with HTML as the wire format and htmx as the thin glue.

htmx clean URL versus a complex SPA URL with hash routing — htmx's pitch in one image: clean, server-rendered URLs vs. SPA hash-bang URLs. Every htmx interaction stays a real HTTP request you can debug, log, cache, and bookmark.

Key Features of htmx

AJAX from any element, not just forms: hx-get, hx-post, hx-put, hx-patch and hx-delete can be attached to a div, tr, li or span. The response can be HTML, which is swapped into the DOM at a target you choose with hx-target and hx-swap.
14 KB minified + gzipped: The entire library is smaller than a single React render bundle's source map. There is no compiler, no Babel, no JSX — you drop a <script> tag and it works.
Server-Sent Events and WebSockets via extensions: Real-time UIs are first-class through the official sse and ws extensions, which replaced the deprecated 1.0 hx-sse and hx-ws attributes in htmx 2.0.
View transitions and CSS-driven animation: Class-swap helpers (hx-swap="outerHTML transition:true") hook into the modern View Transitions API for native, hardware-accelerated effects without any JavaScript.
History and back-button support: hx-push-url="true" turns any partial-page swap into a real browser history entry, so the back button, deep links and copy-paste URLs keep working.
Out-of-band swaps: A single response can update multiple, unrelated parts of the page using hx-swap-oob="true" — the simplest cross-pane state update on the web.
Idiomatic with Hyperscript or Alpine.js: For the tiny sliver of UI that actually needs client-side state, htmx pairs well with Alpine.js or Carson Gross's companion language Hyperscript — both small, both attribute-based.
Quarterly releases, no churn: The maintainers publicly modeled the project on jQuery's API stability promise. htmx 2.0 shipped on June 17, 2024 and the 2.x line has shipped roughly four point releases since with no breaking changes.

A short HTML snippet showing an htmx-powered button replacing an element with a server response — The canonical htmx demo: `hx-post="/clicked" hx-swap="outerHTML"` replaces the button with whatever HTML the server returns — no JavaScript, no JSON, no client-side state.

What Users Say About htmx

Sentiment is unusually polarized for an OSS library. The 2.0 release announcement on Hacker News drew more than 800 points and 400 comments — the top thread is a Django shop reporting they shipped an entire customer-facing dashboard in htmx + server-rendered templates with "less JavaScript than the React loading skeleton it replaced." Reddit's r/htmx and r/webdev regulars echo the theme: backend developers and small teams love it, and a non-trivial number of formerly React-only shops report cutting their frontend headcount or pulling juniors into full-stack work because the cognitive load is lower.

The complaints are real and consistent. A widely-cited "Less Htmx Is More" thread argued that once a single page exceeds about a dozen interacting hx-* attributes the magic-string indirection becomes harder to reason about than equivalent React. Multiple commenters note that htmx leans on server round-trips for things SPAs handle locally, which makes it slow on bad networks unless you implement loading indicators (which the docs do explain, but easy to miss). The docs themselves get mixed reviews — the Hypermedia Systems book by Carson Gross, Adam Stepinski and Adam Pasch is the closest thing to a canonical tutorial, and it is a $40 paperback or a free online read. Konfig's review of 1,000+ developer opinions summarized the consensus as "extremely productive for the right shape of app, frustrating outside it."

htmx Pricing

htmx is free and open source under the BSD-2-Clause license. There is no paid tier, no SaaS, no telemetry, and no “enterprise” SKU. The library is funded through three streams: GitHub Sponsors (Carson Gross's personal sponsor page lists JetBrains and several individual backers), corporate sponsorships listed on htmx.org (JetBrains, Craft CMS, ButterCMS, Bootcamp.coach, Sentry and others), and book and course sales for Hypermedia Systems.

Plan	Price	What You Get
The library	$0 forever	BSD-2-Clause source on GitHub, the 14 KB `htmx.min.js`, and all official extensions (sse, ws, alpine-morph, head-support, idiomorph, etc.).
Hypermedia Systems book	Free online or $40 paperback	The 250-page book that covers the architectural arguments behind htmx in depth.
Sponsorships	$5+/month optional	Voluntary support via GitHub Sponsors. No private features, no Discord roles, no NDA — just funding.

Who Should Use htmx?

Best for: backend-leaning teams (Django, Rails, Phoenix, Laravel, Go, .NET, Spring) shipping CRUD apps, internal tools, admin dashboards, marketing sites that need a touch of interactivity, and any product where the team's React skill is shallow but their server-side skill is deep. Solo developers and two-person SaaS teams in particular get an enormous productivity boost — one codebase, one language, one mental model.

Not ideal for: rich offline-capable single-page applications (Linear, Figma, Notion-class products), real-time collaborative editors with conflict-free replicated data types, mobile-first apps that need to feel native, or teams whose entire toolchain (TypeScript, design systems, component libraries, testing) is locked into a React/Vue ecosystem. htmx is also a poor fit if your backend is a pure JSON API serving multiple consumers (web, native, partner integrations) — you would end up duplicating templates and JSON endpoints.

htmx code snippet showing nested hx-target and hx-swap attributes — htmx attributes inherit through the DOM tree, so a parent's `hx-target` and `hx-swap` apply to all descendants — you write configuration once and pages stay readable.

Pros and Cons

Pros:

Tiny: 14 KB min+gzip is smaller than the average e-commerce site's tracking pixel payload.
No build step. Drop in a <script> tag and ship — no Webpack, no Vite, no npm install required for the basic case.
Works with every server stack — the library is language-agnostic because it speaks HTML.
BSD-2-Clause and genuinely community-funded; no rug-pull risk from a venture investor demanding a SaaS pivot.
jQuery-style API stability commitment — htmx 2.x sites are explicitly designed to keep working a decade from now.
Excellent companion ecosystem: Alpine.js, Hyperscript, idiomorph, Datastar and Templ for Go all compose cleanly.

Cons:

Magic-string attributes can drift — static analysis tools for hx-* attributes are rudimentary and there is no first-class TypeScript story.
Server round-trips for every interaction means weak networks (rural, mobile transit) feel laggy unless you add loading indicators and optimistic UI patterns yourself.
Docs are functional but dense — the best learning resource (Hypermedia Systems) is a separate $40 book.
Not the right tool for offline-capable PWAs, real-time multiplayer canvases, or anything that wants a JSON-first API for native clients.
Smaller hiring pool than React. Resumes mentioning htmx are still rare, even though the productivity story is strong.

Alternatives to htmx

Hotwire / Turbo Frames is htmx's closest philosophical cousin — a similar HTML-over-the-wire model, but tightly bound to Ruby on Rails and somewhat heavier (~40 KB). Unpoly is the original hypermedia-extension library; older than htmx, broader in scope, and more opinionated about navigation. Alpine.js is the natural companion, not a competitor — many real codebases use both. For full SPAs that still want to minimize JavaScript, Astro with the “islands” pattern, Phoenix LiveView on Elixir, and Rails 7+ Turbo Streams all chase the same goal from different angles. Datastar is a 2024 newcomer using a similar attribute-driven approach with WebTransport for real-time feeds.

Verdict: Is htmx Worth It?

For backend-leaning teams shipping CRUD apps in 2026, htmx is one of the highest-ROI dependencies you can add to a project. We have seen two-engineer teams ship features in a week that React shops staff with a four-engineer pod, and the long-tail maintenance story (no breaking changes, no toolchain churn, no dependency tree) is materially better than the JavaScript ecosystem norm. The 87/100 rating reflects the trade-off honestly: htmx is genuinely outstanding for its sweet spot, and a poor fit outside it. If you are deciding between htmx and React for a new internal tool, an admin dashboard, a B2B SaaS app, or a content-heavy site with light interactivity, default to htmx. If you are building Linear, Figma or a mobile-first social network, do not.

Frequently Asked Questions

Is htmx free?: Yes. htmx is BSD-2-Clause licensed and free for commercial use forever. There is no paid tier, no SaaS account, and no telemetry. Funding comes from GitHub Sponsors and corporate sponsorships listed on htmx.org.
How big is the htmx library?: About 14 KB minified and gzipped — smaller than the average tracking pixel bundle on a typical news site. There is no build step required to use it.
Do I still need React with htmx?: For most CRUD apps, internal tools, dashboards and content sites, no. For rich single-page applications (real-time canvases, offline-first PWAs, complex client-side state), yes — htmx is not designed for those workloads.
How does htmx compare to Hotwire / Turbo?: Both follow the same HTML-over-the-wire philosophy. htmx is framework-agnostic and lighter (14 KB vs ~40 KB for Turbo+Stimulus), works with any server, and has a more granular attribute API. Hotwire is more opinionated and ships with first-class Rails integration. Choose htmx outside Rails; Hotwire inside it.
Is htmx production-ready?: Yes. htmx 2.0 shipped on June 17, 2024 with an explicit jQuery-style API stability commitment. Production users include GitHub itself (parts of the issues UI), Twilio, Hotwire-era 37signals shops, and thousands of small-to-medium SaaS products visible at htmx.org/created-with-htmx.
Is htmx open source?: Yes — BSD-2-Clause. The full source is at github.com/bigskysoftware/htmx with roughly 47,900 stars as of April 2026.
Does htmx work with TypeScript?: The library itself ships htmx.d.ts types for the JavaScript API. There is no first-class compile-time validation of hx-* attributes in HTML — community tools like htmx-types and the JetBrains and VS Code htmx plugins close the gap with autocomplete and warnings, but it is not on par with TypeScript-native frameworks.

#frontend

Storybook

htmx