Htmx in a Nutshell

Htmx is a library that allows you to access modern browser features directly from HTML, rather than using javascript.

To understand htmx, first lets take a look at an anchor tag:

  <a href="/blog">Blog</a>

This anchor tag tells a browser:

"When a user clicks on this link, issue an HTTP GET request to '/blog' and load the response content into the browser window".

With that in mind, consider the following bit of HTML:

  <div hx-post="/clicked"
    Click Me!

This tells htmx:

"When a user clicks on this div, issue an HTTP POST request to '/clicked' and use the content from the response to replace the element with the id parent-div in the DOM"

Htmx extends and generalizes the core idea of HTML as a hypertext, opening up many more possibilities directly within the language:

  • Now any element, not just anchors and forms, can issue an HTTP request
  • Now any event, not just clicks or form submissions, can trigger requests
  • Now any HTTP verb, not just GET and POST, can be used
  • Now any element, not just the entire window, can be the target for update by the request

Note that when you are using htmx, on the server side you respond with HTML, not JSON. This keeps you firmly within the original web programming model, using Hypertext As The Engine Of Application State without even needing to really understand that concept.

It's worth mentioning that, if you prefer, you can use the data- prefix when using htmx:

  <a data-hx-post="/click">Click Me!</a>


Htmx is a dependency-free javascript library.

It can be used via NPM as "" or downloaded or included from unpkg or your other favorite NPM-based CDN:

    <script src=""></script>


The core feature of htmx is a set of attributes that allow you to issue AJAX requests directly from HTML:

  • hx-get - Issues a GET request to the given URL
  • hx-post - Issues a POST request to the given URL
  • hx-put - Issues a PUT request to the given URL
  • hx-patch - Issues a PATCH request to the given URL
  • hx-delete - Issues a DELETE request to the given URL

(Since most browsers only support issuing GET and POST, a request with one of the other three methods will actually be issued as a POST, with the X-HTTP-Method-Override header set to the desired method.)

Each of these attributes takes a URL to issue an AJAX request to. The element will issue a request of the specified type to the given URL when the element is triggered:

  <div hx-put="/messages">
    Put To Messages

This tells the browser:

When a user clicks on this div, issue a PUT request to the URL /messages and load the response into the div

Triggering Requests

By default, AJAX requests are triggered by the "natural" event of an element:

  • input, textarea & select are triggered on the change event
  • form is triggered on the submit event
  • everything else is triggered by the click event

If you want different behavior you can use the hx-trigger attribute to specify which event will cause the request.

Here is a div that posts to /mouse_entered when a mouse enters it:

   <div hx-post="/mouse_entered" hx-trigger="mouseenter">
      [Here Mouse, Mouse!]

If you want a request to only happen once, you can use the once modifier for the trigger:

   <div hx-post="/mouse_entered" hx-trigger="mouseenter once"">
     [Here Mouse, Mouse!]

There are few other modifiers you can use for trigger:

  • changed - only issue a request if the value of the element has changed
  • delay:<time interval> - wait the given amount of time (e.g. 1s) before issuing the request. If the event triggers again, the countdown is reset.

You can use these two attributes to implement a common UX pattern, Active Search:

   <input type="text" name="q" 
          hx-trigger="keyup changed delay:500ms" 
    <div id="search-results"></div>

This input will issue a request 500 milliseconds after a key up event if the input has been changed and inserts the results into the div with the id search-results.

Special Events

htmx provides a few special events for use in hx-trigger:

  • load - fires once when the element is first loaded
  • revealed - fires once when an element first scrolls into the viewport

You can also use custom events to trigger requests if you have an advanced use case.


If you want an element to poll the given URL rather than wait for an event, you can use the every syntax with the hx-trigger attribute:

  <div hx-get="/news" trigger="every 2s">

This tells htmx

Every 2 seconds, issue a GET to /news and load the response into the div

If you want to stop polling from a server response you can respond with the HTTP response code 286 and the element will cancel the polling.

Load Polling

Another technique that can be used to achieve polling in htmx is "load polling", where an element specifies an load trigger along with a delay, and replaces itself with the response:

<div hx-get="/messages" 
     hx-trigger="load delay:1s"

If the /messages end point keeps returning a div set up this way, it will keep "polling" back to the URL every second.

Load polling can be useful in situations where a poll has an end point at which point the polling terminates, such as when you are showing the user a progress bar.

Server Sent Events

Server Sent Events are a way for servers to send events to browsers. It provides a higher-level mechanism for communication between the server and the browser than websockets.

If you want an element to respond to a Server Sent Event via htmx, you need to do two things:

  1. Define an SSE source. To do this, add a hx-sse-src attribute on a parent element that specifies the URL from which Server Sent Events will be received.

  2. Specify the Server Sent Event that will trigger the element, with the prefix sse:

Here is an example:

    <body hx-sse-src="/sse_messages">
        <div trigger="sse:new_news" hx-get="/news"></div>

Depending on your implementation, this may be more efficient than the polling example above since the server would notify the div if there was new news to get, rather than the steady requests that a poll causes.

Request Indicators

When an AJAX request is issued it is often good to let the user know that something is happening since the browser will not give them any feedback. You can accomplish this in htmx by using htmx-indicator class.

The htmx-indicator class is defined so that the opacity of any element with this class is 0 by default, making it invisible but present in the DOM.

When htmx issues a request, it will put a htmx-request class onto an element (either the requesting element or another element, if specified). The htmx-request class will cause a child element with the htmx-indicator class on it to transition to an opacity of 1, showing the indicator.

  <button hx-get="/click">
      Click Me!
     <img class="htmx-indicator" src="/spinner.gif"/>

Here we have a button. When it is clicked the htmx-request class will be added to it, which will reveal the spinner gif element. (I like SVG spinners these days.)

While the htmx-indicator class uses opacity to hide and show the progress indicator, if you would prefer another mechanism you can create your own CSS transition like so:

    .htmx-request .my-indicator{

If you want the htmx-request class added to a different element, you can use the hx-indicator attribute with a CSS selector to do so:

      <button hx-get="/click" hx-indicator="#indicator">
        Click Me!
      <img id="indicator" class="htmx-indicator" src="/spinner.gif"/>  

Here we call out the indicator explicitly by id. Note that we could have placed the class on the parent div as well and had the same effect.


If you want the response to be loaded into a different element other than the one that made the request, you can use the hx-target attribute, which takes a CSS selector. Looking back at our Live Search example:

   <input type="text" name="q" 
          hx-trigger="keyup delay:500ms changed" 
    <div id="search-results"></div>

You can see that the results from the search are going to be loaded into div#search-results, rather than into the input tag.


htmx offers a few different ways to swap the HTML returned into the DOM. By default, the content replaces the innerHTML of the target element. You can modify this by using the hx-swap attribute with any of the following values:

  • innerHTML - the default, puts the content inside the target element
  • outerHTML - replaces the entire target element with the returned content
  • afterbegin - prepends the content before the first child inside the target
  • beforebegin - prepends the content before the target in the targets parent element
  • beforeend - appends the content after the last child inside the target
  • afterend - appends the content after the target in the targets parent element

Out of Band Swaps

If you want to swap content from a response directly into the DOM by using the id attribute you can use the hx-swap-oob attribute in the response html:

  <div id="message" hx-swap-oob="true">Swap me directly!</div>
  Additional Content

In this response, div#message would be swapped directly into the matching DOM element, while the additional content would be swapped into the target in the normal manner.

You can use this technique to "piggy-back" updates on other requests.

Note that out of band elements must be in the top level of the response, and not children of the top level elements.

Selecting Content To Swap

If you want to select a subset of the response HTML to swap into the target, you can use the hx-select attribute, which takes a CSS selector and selects the matching elements from the response.


By default, an element that causes a request will include its value if it has one. If the element is a form it will include the values of all inputs within it.

Additionally, if the element causes a non-GET request, the values of all the inputs of the nearest enclosing form will be included.

If you wish to include the values of other elements, you can use the hx-include attribute with a CSS selector of all the elements whose values you want to include in the request.

If you wish to filter out some parameters you can use the hx-params attribute.

Finally, if you want to programatically modify the parameters, you can use the configRequest.htmx event.

History Support

Htmx provides a simple mechanism for interacting with the browser history API:

If you want a given element to push its request URL into the browser navigation bar and add the current state of the page to the browser's history, include the hx-push-url attribute:

    <a hx-get="/blog" hx-push-url="true">Blog</a>

When a user clicks on this link, htmx will snapshot the current DOM and store it before it makes a request to /blog. It then does the swap and pushes a new location onto the history stack.

When a user hits the back button, htmx will retrieve the old content from storage and swap it back into the target, simulating "going back" to the previous state.

Specifying History Snapshot Element

By default, htmx will use the body to take and restore the history snapshop from. This is usually the right thing, but if you want to use a narrower element for snapshotting you can use the hx-history-elt attribute to specify a different one.

Careful: this element will need to be on all pages or restoring from history won't work reliably.

Requests & Responses

Htmx expects responses to the AJAX requests it makes to be HTML, typically HTML fragments (although a full HTML document, matched with a hx-select tag can be useful too). Htmx will then swap the returned HTML into the document at the target specified and with the swap strategy specified.

Sometimes you might want to do nothing in the swap, but still perhaps trigger a client side event (see below). For this situation you can return a 204 - No Content response code, and htmx will ignore the content of the response.

In the event of an error response from the server (e.g. a 404 or a 501), htmx will trigger the responseError.htmx event, which you can handle.

In the event of a connection error, the sendError.htmx event will be triggered.

Request Headers

htmx includes a number of useful headers in requests:

  • X-HX-Request - will be set to "true"
  • X-HX-Trigger - will be set to the id of the element that triggered the request
  • X-HX-Trigger-Name - will be set to the name of the element that triggered the request
  • X-HX-Target - will be set to the id of the target element
  • X-HX-Current-URL - will be set to the URL of the browser
  • X-HX-Prompt - will be set to the value entered by the user when prompted via hx-prompt
  • X-HX-Event-Target - the id of the original target of the event that triggered the request
  • X-HX-Active-Element - the id of the current active element
  • X-HX-Active-Element-Name - the name of the current active element
  • X-HX-Active-Element-Value - the value of the current active element
  • X-HTTP-Method-Override - the HTTP verb for non-GET and POST requests

Response Headers

htmx supports two special response headers:

  • X-HX-Trigger - can be used to trigger client side events, see the documentation for examples.
  • X-HX-Push - can be used to push a new URL into the browsers address bar

Request Order of Operations

The order of operations in a htmx request are:

  • The element is triggered and begins a request
    • Values are gathered for the request
    • The htmx-request class is applied to the appropriate elements
    • The request is then issued asynchronously via AJAX
      • Upon getting a response the target element is marked with the htmx-swapping class
      • An optional swap delay is applied (see the hx-swap-delay attribute)
      • The actual content swap is done
        • the htmx-swapping class is removed from the target
        • the htmx-settling class is applied to the target
        • A settle delay is done (default: 100ms)
        • The DOM is settled
        • the htmx-settling class is removed from the target

You can use the htmx-swapping and htmx-settling classes to create CSS transitions between pages.


In addition to the core AJAX functionality, htmx also has a few other tricks up its sleeve that help you build nice interfaces without javascript.

Class Swapping

Htmx supports an attribute, hx-classes that allows you to add, remove and toggle classes after a delay. This can be used to create CSS transition effects.

Here are some examples:

<!-- adds the class "foo" after 100ms -->
<div hx-classes="add foo"/> 

<!-- removes the class "bar" after 1s -->
<div hx-classes="remove bar:1s"/> 

<!-- removes the class "bar" after 1s
     then adds the class "foo" 1s after that -->
<div hx-classes="remove bar:1s, add foo:1s"/> 

<!-- removes the class "bar" and adds 
     class "foo" after 1s  -->
<div hx-classes="remove bar:1s & add foo:1s"/> 

<!-- toggles the class "foo" every 1s -->
<div hx-classes="toggle foo:1s"/>

Full documentation is available on the documentation page.


Htmx supports "boosting" regular HTML anchors and forms with the hx-boost attribute. This attribute will convert all anchor tags and forms into AJAX requests that, by default, target the body of the page.

This functionality is somewhat similar to Turbolinks.

Events & Logging

Htmx has an extensive events mechanism, which doubles as the logging system.

If you want to register for a given htmx event you can use the following javascript:

  htmx.on("load.htmx", function(evt) {

This event is fired every time an element is loaded into the DOM by htmx, and is effectively the load event. In fact this is so common, you can use the helper function:

  htmx.onLoad(function(target) {

This does the same thing as the first example, but is a little cleaner.

The full set of events can be seen on the reference page.


If you set a logger at htmx.logger, every event will be logged. This can be very useful for troubleshooting:

    htmx.logger = function(elt, event, data) {
        if(console) {
            console.log(event, elt, data);

Htmx can also send errors to a URL that is specified with the hx-error-url attributes. This can be useful for debugging client-side issues.

Htmx includes a helper method:


if you want to log everything while developing.

Configuring htmx

Htmx allows you to configure a few defaults:

  • htmx.config.historyEnabled - defaults to true, really only useful for testing
  • htmx.config.historyCacheSize - defaults to 10
  • htmx.config.defaultSwapStyle - defaults to innerHTML
  • htmx.config.defaultSwapDelay - defaults to 0
  • htmx.config.defaultSettleDelay - defaults to 100
  • htmx.config.includeIndicatorStyles - defaults to true (determines if the htmx-indicator default styles are loaded, must be set in a meta tag before the htmx js is included)

You can set them directly in javascript, or you can use a meta tag:

    <meta name="htmx-config" content='{"defaultSwapStyle":"outerHTML"}'>


And that's it! Have fun with htmx: you can accomplish quite a bit without a lot of code.