# Item

Published: November 19, 2026

<img width="640" height="400" class="rounded-2xl ring-1 ring-black/7 dark:ring-zinc-700" src="/img/blog/item_hero.png" alt="A profile item with an avatar and an Edit profile button, above a group of settings rows: a two-factor switch, a language menu, a next payment amount, and a sign out button" />

Meet **Item**: a row with a heading, a line of supporting text, and a control at the end.

It's the row you've built a hundred times for settings pages, account details, billing screens, and team lists. Now it's one component, with the alignment and spacing already worked out.

```blade
<flux:item>
    <flux:item.heading>Two-factor authentication</flux:item.heading>
    <flux:item.subheading>Ask for a code when you sign in on a new device.</flux:item.subheading>

    <flux:item.actions>
        <flux:switch aria-label="Two-factor authentication" checked />
    </flux:item.actions>
</flux:item>
```

## Group them up

Wrap items in `flux:item.group` and they share one bordered surface, with a faint rule between each row:

```blade
<flux:item.group>
    <flux:item>...</flux:item>
    <flux:item>...</flux:item>
    <flux:item>...</flux:item>
</flux:item.group>
```

The surface matches a default card, so groups sit comfortably next to the [new Card](/blog/2026-09-28-card). And a lone item draws that same surface itself. No wrapper needed.

## Anything at the end

`flux:item.actions` takes buttons, a switch, a dropdown, a badge, or just a value. It sits at the end of the row, centered on the heading and subheading no matter how tall either side gets. Put several things in there and they sit side by side.

```blade
<flux:item>
    <flux:item.heading>Next payment</flux:item.heading>
    <flux:item.subheading>December 4, 2026</flux:item.subheading>

    <flux:item.actions>
        <flux:heading>$60.00</flux:heading>
    </flux:item.actions>
</flux:item>
```

The subheading is optional. Without one, an item is a single line that's still as tall as a small button, so a row with a switch and a row with just a value stay even in the same group.

## Lead with media

<img loading="lazy" width="640" height="260" class="rounded-2xl ring-1 ring-black/7 dark:ring-zinc-700" src="/img/blog/item_media.png" alt="A team list of items, each led by an avatar, with an Owner label, an Admin role menu, and an options button at the end of each row" />

Put an avatar, an icon, or anything else in `flux:item.media` to lead the row. It's centered on the text beside it, with the spacing already set:

```blade
<flux:item>
    <flux:item.media>
        <flux:avatar size="sm" circle src="..." />
    </flux:item.media>

    <flux:item.heading>Josh Hanley</flux:item.heading>
    <flux:item.subheading>josh@example.com</flux:item.subheading>

    <flux:item.actions>
        <flux:dropdown align="end">
            <flux:button size="sm" variant="ghost" icon:trailing="chevron-down" inset="right">Admin</flux:button>

            <flux:menu>...</flux:menu>
        </flux:dropdown>
    </flux:item.actions>
</flux:item>
```

## Fits wherever you put it

<img loading="lazy" width="640" height="280" class="rounded-2xl ring-1 ring-black/7 dark:ring-zinc-700" src="/img/blog/item_narrow.png" alt="A narrow item group where the Browse and Install buttons have moved below the text, while the switch on the next row stays at the end" />

On a narrow item, a labeled button moves under the text so the heading keeps its room. Switches, values, menus, and icon buttons are compact enough to stay at the end of the row.

The item goes by its own width, not the screen's. It's a container query under the hood, so the same markup does the right thing on a phone, in a modal, or tucked into a sidebar.

## All. The. Details.

**Long text wraps**: Long words and email addresses break onto the next line instead of running under the actions.

**Real headings**: Pass `level` to `flux:item.heading` to render an actual `h2`, `h3`, and so on, so your page outline stays meaningful.

**Ready-made examples**: The docs include copy-and-paste examples for team members, connected apps, billing, notifications, and a danger zone.

And of course, Item is built from plain, semantic markup. The controls you put inside it, like switches, buttons, and dropdowns, keep all of their keyboard navigation, focus behavior, and screen reader support.

Item is part of free Flux, available in **v2.22.0**.

---

[Check out the item docs →](https://fluxui.dev/components/item)
