Card templates for Home Assistant dashboards. Write a card once, use it everywhere.
Reusable cards, badges, rows and whole views, with variables, repeats over what Home Assistant
knows, and visual editors. The name comes from the original decluttering-card it continues.
We all use the same block of configuration over and over across a Lovelace dashboard, and none of us want to change the same thing in a hundred places. Define it once as a template, pass in what differs, and use it everywhere.
📖 The documentation is in the wiki, also published as a searchable site with a template builder, a placeholder playground and a page to try a template on. This page is the summary. What changed in each version is on the releases page.
The card is in the Home Assistant Marketplace. Open Settings → Marketplace, search for Decluttering Card Plus, install it and reload your browser. The Marketplace adds the dashboard resource for you.
On Home Assistant older than 2026.11 the Marketplace is still HACS, in the sidebar. The steps are the same, and this link opens the card there.
To install by hand, save every .js file of the latest release to
<config>/www/ (v2.4.0+: the editors and translations are files of their own beside the main
one) and add /local/decluttering-card-plus.js as a dashboard resource of type module. The
Installation page has the detail.
| You need | For |
|---|---|
| 2024.7 | everything, unless it is listed below |
| 2024.8 | badge: templates |
| 2024.11 | grid_options, which is what the sections view reads |
Define the template at the root of your dashboard configuration, level with views::
decluttering_templates:
room_light:
card:
type: tile
entity: '[[light]]'
name: '[[room]]'Then use it as many times as you like, filling in the holes:
type: custom:decluttering-card-plus
template: room_light
variables:
- light: light.living_room
- room: Living RoomTemplates can also be defined as a card on the dashboard itself, with a visual editor and a live preview, if you would rather not touch YAML. Quick Start goes on from here.
Picking a template and setting its variables in the visual editor, with a live preview.
- Cards, badges, Entities rows and
Picture elements — a template can hold any of the four, or a
group:of several cards that sit in a section as if each were written there. - Variables with defaults, fallbacks (
[[name|default:Unnamed]]), conditions ([[name|if:other]]), transforms ([[room|slug]],[[watts|div:1000]]), values read from Home Assistant ([[entity|friendly_name]], its area, floor, device or labels), whether an integration, card or icon set is installed ([[popup|if_card_exists]]), quoted text ([["Kitchen"|upper]]), and values a whole dashboard, view or section sets for every card in it. Dates and times ([[sensor|last_changed|relative]]), attributes ([[light|attr:brightness]]), plurals and numbers in the viewer's language, colours worked out from one ([[accent|lighten:20]]),unless:andswitch:, two lists or mappings joined into one ([[base|merge:extra]]), and values for a card that is narrow (variables_mobile:). - Repeating a template — one copy per item in a list, or per entity, area, device, floor or label Home Assistant knows about, filtered, sorted and grouped. Whole sections or views can be repeated too.
- List entries —
with:andrepeat:fill a block of config into a card's own lists, where a nested card cannot go. Rows and picture elements repeat in place, a template can leave slots for the card to fill with cards of its own, and decide withvisibility:which copies are worth building. - Templates for a whole dashboard or a single section, used from the dashboard and section strategies.
- Sharing templates between dashboards, or from one library
dashboard to all of them, plus templates shared by other people,
carrying their author, licence, requirements and the questions to ask on install. An
export takes the item templates and dashboard values it uses with it, and lists the custom
cards it needs under
requires:. - Templates built on templates with
extends:, withbase: trueto keep a parent that is only there to be extended out of the template picker, and one-off tweaks with a card's owncard:block laid over what its template builds. A template with afunction:is a step of your own:[[room|occupancy]]. - Visibility and styling inside a template.
- Visual editors that show what a card builds, where a template is used,
rename a template or a variable everywhere, turn existing cards into a template, and keep
the last 20 deleted or replaced templates to restore. Variables are edited as rows, with
help beside each field, and a template can show or hide its fields, or whole groups of them,
depending on the others. A field's shape can be named once and reused as a type of your own
(
decluttering_types:), and the card editor points out fields you set by hand that an edit left behind. The card editor shows each field's default, sets up a repeat as a form with its filters, order and a live count, and editstemplate_by_domainas a table. Templates are picked from a search box with descriptions and use counts, any field on the Card tab can be made a variable from its own menu, and the code editor colours placeholders and completes them after[[. checks:a template runs against the values it is given, andstrict:to decide, level by level, what an error or a warning does to the card. A card that cannot be built says why and offers the fix.- A health panel for missing templates, unset variables and unused templates, also as a card
or badge on the dashboard, and
debug: reportto write up what a card built, with an outline of what built what, what each variable worked out to and how, the card as written, its recent rebuilds and the checks that passed, a box to try a placeholder in, and any card inside that refused its config, ready to paste into an issue. It folds to a one-line bar, and one entity can switch every report on a page off. - In the editors: presets from a template's examples, a gallery to install templates from, a preview in light and dark at phone and tablet widths, a pause for previews that are expensive to build, an extends family tree, a diff against the library copy, and a converter from button-card templates and auto-entities. JSON schemas for YAML editors and a command-line linter check YAML dashboards outside Home Assistant.
The Configuration Reference lists every option.
| You want | Reach for |
|---|---|
| The same block of card YAML in a dozen places, with a few values changed | this card |
| A card per light, room or sensor, kept up to date as you add things | this card — for_each_from |
| A list that reorders itself by what is on, or hides what is off right now | auto-entities — this card builds once and does not follow state |
| One button styled every possible way, with heavy CSS and JS templating | button-card and its own templates |
| To compute a value from several entities | a Home Assistant template sensor, then show it with any card |
They coexist happily: a template here can hold a button-card, and an auto-entities card can hold cards built from a template here.
To try it without touching your own dashboards, paste
examples/demo-dashboard.yaml into a new dashboard's raw
configuration editor. Trying It Out has more ways in.
From decluttering-card, your existing configuration keeps working. This card also
registers the original custom:decluttering-card and custom:decluttering-template types
when the original is not installed, and decluttering_templates is unchanged. Install this,
remove the old card, and change nothing else. Do not run both: whichever loads first claims
the type names. Migrating from decluttering-card has the detail.
From Streamline card, rename streamline_templates: to decluttering_templates: and
custom:streamline-card to custom:decluttering-card-plus. _javascript keys are not run
here; Migrating from Streamline card shows what to use instead.
Common problems are in Troubleshooting. If you need to ask, put
debug: report on the card and paste what it gives you into an issue or the
forum thread.
The card speaks Arabic, Bengali, Chinese (Simplified and Traditional), Czech, Danish, Dutch, English, French, German, Hindi, Indonesian, Italian, Japanese, Korean, Polish, Portuguese, Russian, Spanish, Swedish, Turkish, Ukrainian and Urdu, following your Home Assistant profile. Adding a language is one file and no code: see Translations.
A shared template can carry its own words in several languages too. Put them in a
language: block, one mapping per language code, and write [[$key]] wherever the text
goes, in the card, a variable's label or description, or the template's description. Each
viewer gets their Home Assistant language, then the same language without its region, then
English, then the first one written. See Template Translations.
decluttering-card-plus builds on custom-cards/decluttering-card, which has not had
a release since April 2023, and on the work of three people:
- RomRider — the original card.
- j9brown — visual editors, and support for templating entity rows and picture elements as well as cards (upstream PR #78, unmerged).
- simbaja — modernisation to lit 3 and TypeScript 5, plus the
styleoption.
This project is maintained by tempus2016 and is copyright 2026
John MacKinnon. It began as a fork of RomRider's decluttering-card, which is copyright 2018
Alexandre Garcia, and parts of that original card remain in it — so both notices are carried in
LICENSE. Everything here is MIT licensed, as was all of the work it builds on.
CONTRIBUTING.md covers building, testing, the commit format releases are cut from, and the handful of changes that tend to get pushed back. Security reports go through SECURITY.md.
npm install # or npm ci
npm test # unit tests
npm run build # lint, then bundle into dist/
npm start # rebuild on change, served on :5000 for the dev container
