Download websites that use Kirki Customizer Framework

About Kirki Customizer Framework

Nobody shops for Kirki Customizer Framework. A site owner picks a WordPress theme, and somewhere upstream the theme author decided to build its options panel on a framework rather than write Customizer code by hand. The result is a dependency that reaches live sites by inheritance, which makes it a very different kind of signal from a plugin someone installed on purpose.

What the signal carries is information about the builder, not about the buyer. A theme that ships with the framework tends to come from a commercial theme shop or an agency with a house style, because those are the teams that need color pickers, typography selectors and repeatable field groups often enough to standardize on a toolkit. Released in 2014 and written in PHP under the MIT license, the framework sits in the layer of WordPress work that end users never see and never name. When a researcher asks which sites were built by professionals rather than assembled from a free directory theme, presence of a developer framework is one of the more honest proxies available.

Detection here is inferential and we would rather say so. The framework is visible when it emits its own control scripts, stylesheets or recognizable markup to the front end. Themes that bundle it, compile it away, or load its interface only inside the administrative area can carry the code without exposing anything a crawler can see. So the published population should be read as a floor rather than a census, and the WordPress plugins classification describes the surrounding platform more than it describes the component itself.

As of October 2026 we detect Kirki Customizer Framework on 123 sites. The number matters less than what can be done with the list. Plugin and theme vendors use an installed base like this to size the addressable market for an add-on that has to speak to the same field API. Agencies use it to find sites whose options panel they already know how to work with before a redesign pitch. Maintenance and security teams use it because a framework baked into a theme upgrades on the theme author schedule and not on the site owner schedule, so stale copies accumulate quietly and invisibly.

A per-domain lookup answers whether one site uses the framework. Repeating that lookup domain by domain answers almost nothing, because the useful question runs the other way. Which hosts, which countries, which domain endings and which neighboring plugins cluster around theme shop WordPress builds, and how that cluster moves between refreshes of the data. Those are questions about a whole population, and they need the population in a file you can group and filter yourself.