Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Explainers · Explainer

What Is Kirki WordPress? Explained

What Is Kirki WordPress? Explained

Short answer

Kirki is a free WordPress plugin that began as a Customizer framework for theme developers. It adds extra controls such as typography, color palettes, sliders and sortable lists to Appearance, Customize, and many classic themes ask you to install it so their style options work.

Key takeaways

  • Kirki extends the WordPress Customizer with richer controls.
  • Many classic themes require it for their style options.
  • It saves settings the normal WordPress way, as theme mods or options.
  • Newer releases also add page building features.
  • Block themes rarely need Kirki because they use theme.json.
  • Back up and test before removing it from a live site.

What is Kirki in WordPress?

Kirki is a free WordPress plugin that started as a toolkit for theme developers, making it easier to add rich options to the WordPress Customizer.

You will find it on the Kirki plugin page on WordPress.org, where it has been listed for many years.

Most site owners meet Kirki without choosing it. A theme tells them to install it, and the theme's settings then appear in Appearance > Customize.

In recent versions the plugin has also grown into a visual page builder, so the name now covers two related things: the classic Customizer framework and a newer site building tool.

What problem does Kirki solve for theme developers?

Kirki saves developers from writing a lot of repetitive Customizer code, because it turns long control definitions into short configuration arrays.

WordPress core already has the Customizer API, which lets a theme register panels, sections, settings and controls.

The core API is powerful, but building a color picker, a typography control or a sortable list by hand takes a lot of PHP and JavaScript.

Kirki wraps that work. A developer describes the control they want, such as a font family selector, and Kirki builds the control, saves the value and can even print the matching CSS on the front end.

That last part matters. With plain core code, the developer must also write the code that reads the saved value and outputs styles. Kirki can generate that output automatically.

What controls does Kirki add to the Customizer?

Kirki adds dozens of extra control types that core does not ship, such as typography, color palettes, sortable lists, image radio buttons, sliders and repeaters.

Common examples include:

  • Typography: font family, weight, size, line height and letter spacing in one control, with Google Fonts support.
  • Color and color palette: pickers with alpha transparency and preset swatches.
  • Slider and dimension: number ranges and CSS units such as px, em and rem.
  • Sortable: drag-and-drop lists, often used to reorder header elements.
  • Radio image and radio buttonset: visual layout choices instead of plain text radio buttons.
  • Repeater: lists of grouped fields, such as social icons or slides.

Each of these saves its value the normal WordPress way, as a theme mod or an option. So the data stays in your database even if the visual control looks custom.

How does Kirki work under the hood?

Kirki sits on top of the core Customizer: it registers normal settings and controls through the official API, then adds its own scripts and styles to render richer fields.

Because it uses the core API, it does not replace the Customizer. It extends it.

When you change a Kirki control, the live preview updates like any other Customizer field. Some controls use postMessage, which updates the preview without a full refresh.

When you click Publish, the values are stored with set_theme_mod() or in the options table, depending on how the developer configured them.

On the front end, Kirki can read those values and print inline CSS, load Google Fonts and apply the styles. That is why uninstalling Kirki can change how a theme looks, even though your saved data is still there.

Why does my theme ask me to install Kirki?

Your theme likely uses Kirki for its Customizer options, so without the plugin those options either disappear or fall back to plain defaults.

Many free and premium themes, especially on marketplaces, recommend Kirki through an admin notice right after activation.

Some themes bundle the framework inside their own code. Others ask you to install the separate plugin so it can be updated through WordPress.org.

If the notice appears, the safest move is to read your theme's documentation. If it lists Kirki as required, install it from Plugins > Add New.

Our guide on how to update plugins in WordPress covers keeping it current once it is installed.

Who makes Kirki today?

Kirki was created by Aristeides Stathopoulos, later passed to developer David Vongries, and was then acquired by the WordPress company Themeum.

WP Tavern covered the hand-over in David Vongries takes over as new owner of the Kirki Customizer Framework and later reported that Themeum acquired Kirki.

The source code is public on GitHub, which is useful for developers who want to read the control definitions or report issues.

Ownership changes are normal in WordPress, but they are a good reason to check the changelog before each major update.

Is Kirki a page builder now?

Recent releases of Kirki on WordPress.org describe it as a freeform page builder and website builder as well as a Customizer tool, so the plugin now does more than its original job.

That shift can confuse people. A theme may only need the framework part, while the plugin's admin screens now promote building pages visually.

If you only installed Kirki because your theme needed it, you do not have to use the builder features. The Customizer controls keep working in the background.

If you want a dedicated builder, compare it with the options in our Gutenberg vs Elementor guide before you commit a whole site to one tool.

How does Kirki compare with core Customizer code and theme.json?

Kirki suits classic themes that rely on the Customizer, while block themes use theme.json and the Site Editor for styles instead.

ApproachBest forWho edits settingsExtra plugin needed
Core Customizer APIClassic themes, simple optionsSite owner in Appearance > CustomizeNo
Kirki frameworkClassic themes with many style optionsSite owner in Appearance > CustomizeYes, or bundled
theme.json and Site EditorBlock themesSite owner in Appearance > Editor > StylesNo

Block themes, such as the default Twenty Twenty-Five theme, do not show the Customizer menu by default. Their colors and fonts live in the global settings and styles system.

So if you use a block theme, Kirki is rarely needed. If you use a classic theme built around the Customizer, it can be central to how the theme works.

Is Kirki safe and good for performance?

Kirki is a long-running, widely installed plugin, but like any plugin it adds code, so keep it updated and only keep it if your theme or workflow needs it.

Performance impact is usually small on the front end. Most of its weight loads only inside the Customizer screen.

The main front-end cost is the CSS it prints and any Google Fonts it loads. Kirki has offered a way to download Google Fonts locally, which helps both speed and privacy.

If fonts are a concern, read our guide on hosting Google Fonts locally in WordPress.

As with all plugins, update it promptly. Security fixes for widely used plugins are published through normal updates.

What happens if I deactivate or delete Kirki?

Your saved settings usually stay in the database, but a theme that depends on Kirki may lose its custom styles, fonts or option panels until you reactivate it.

Before removing it, take a backup. Our guide on how to back up a WordPress site walks through the options.

Then deactivate the plugin and check your home page, header, footer and typography.

If anything breaks, reactivate Kirki. Nothing is lost by switching it off for a quick test, as long as you do not delete theme data.

If you plan to switch themes anyway, Kirki can go once the old theme is gone, because the new theme will not read the old Kirki settings.

Should you use Kirki on your site?

Use Kirki when your classic theme requires it or when you build classic themes and want rich Customizer controls with less code; skip it on block themes.

For site owners, the decision is usually made by the theme. If the theme needs it, keep it installed and updated.

For developers, Kirki is still a quick way to give clients friendly typography and color controls in a classic theme.

For new projects built as block themes, theme.json and the Site Editor cover most of what Kirki was designed to do, without an extra dependency.

If you are unsure which kind of theme you have, open Appearance. If you see Editor, it is a block theme. If you see Customize, it is a classic theme, and Kirki may be part of the picture.

Frequently asked questions

Is Kirki free?

Yes. The Kirki plugin is free to download from the WordPress.org plugin directory. Some newer builder features or add-ons may be sold separately, so check the plugin page for what is included in the free version.

Do I need Kirki if my theme recommends it?

If your theme lists Kirki as required, install it, because the theme's Customizer options rely on it. If it is only recommended, check the theme documentation to see which settings stop working without it.

Will deleting Kirki remove my theme settings?

Usually the saved values stay in the database, but the theme may stop printing the related styles or fonts. Reactivating Kirki normally brings the look back. Always take a backup before deleting plugins on a live site.

Does Kirki work with block themes?

Block themes do not use the Customizer for styles by default, so Kirki has little to do there. Block themes manage colors and fonts through theme.json and the Site Editor's Styles panel instead.

Is Kirki a page builder?

Recent versions describe Kirki as a freeform page builder as well as a Customizer framework. You can ignore the builder features if you only installed Kirki because your theme needs its Customizer controls.

Sources

  1. Kirki WordPress.org Plugins
  2. Customize API WordPress Developer Resources
  3. Global Settings & Styles (theme.json) WordPress Developer Resources
  4. Themeum Acquires Kirki Customizer Framework Plugin WP Tavern
  5. David Vongries Takes Over as New Owner of the Kirki Customizer Framework WP Tavern
  6. themeum/kirki GitHub

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.