Kirki

Quick take

Kirki is no longer only the Customizer framework many WordPress developers remember. The current 6.x product combines that established theme-customization layer with a freeform visual website builder, responsive design controls, forms, templates, interactions, and a growing dynamic-content system.

I would look at Kirki when the site needs more design freedom than a traditional Customizer setup, but I would not treat the 6.x branch as a small framework update. It is now a much broader site-building product, which changes the buying and compatibility questions compared with older Kirki releases.

Kirki has changed from a framework into a website builder

For years, Kirki was best known as a toolkit theme developers used to add better controls to the WordPress Customizer. That part still exists, but version 6 expanded the plugin into a full visual-building environment.

The new editor uses a freeform canvas instead of forcing every layout into rows and columns. You can design pages visually, adjust responsive states, work with reusable components, manage global styles, add forms, and use built-in interactions. Existing Customizer controls remain part of the plugin, so Kirki now serves two audiences at once: people building sites visually and developers maintaining themes that already depend on its Customizer API.

What the visual workflow looks like

Kirki’s current builder is designed around direct visual composition. You open a page in the editor, place elements on the canvas, adjust design properties, and switch between desktop, tablet, and mobile views while you work. Global styles help keep colors, typography, and spacing consistent across the project.

The free edition is already more than a basic demo. It includes the freeform canvas, core elements and components, responsive editing, basic interactions, a form builder, staging mode, full-site export and import, a Figma importer, and a starter template library.

Pro becomes relevant when the site depends on dynamic content, richer interaction timelines, popups, premium templates, collaboration, or developer handoff features.

Features that matter most

Freeform visual canvas

The canvas is the clearest difference from more structured page builders. Elements can be positioned with more freedom, which suits designers who think visually rather than in rows, columns, and nested containers. That freedom can be useful for custom landing pages and creative layouts, but it also places more responsibility on the person building the page to keep spacing and responsive behavior disciplined.

Responsive editing and design systems

Kirki provides desktop, tablet, and mobile editing along with global styles, CSS variables, class management, and reusable components. Those tools matter more as a site grows because they reduce the need to restyle the same design decision page by page.

The Customizer framework is still included

Developers can continue using Kirki’s Customizer capabilities, including more than 35 custom controls, conditional logic, real-time preview behavior, and automatic CSS generation. This is important for themes that already use Kirki as a dependency rather than as a visual page builder.

Forms and built-in site tools

The free product includes a visual form builder and submission management. Kirki also includes supporting site-building tools such as media management, staging, project import/export, and template assets. For a new site, this can reduce the number of separate utility plugins needed around the builder.

Dynamic content in Pro

Kirki Pro adds its CMS layer for collections, custom fields, dynamic templates, reference fields, visibility conditions, and scheduled publishing. This moves the product beyond static page design and into use cases such as directories, portfolios, service collections, and other structured content layouts.

Interactions and popup building

The free version includes basic interactions, while Pro unlocks the full interaction timeline and custom interaction builder. Pro also includes a visual popup builder with triggers, display rules, positioning, and animation controls. These features are useful when motion or conversion elements are part of the actual site workflow rather than decorative extras.

Collaboration and developer handoff

Pro includes real-time collaboration, editor comments, dev mode, and view-only client links. These features matter more to agencies and teams than to solo site owners because they reduce the friction between design review, client feedback, and implementation.

Who Kirki fits best

Kirki now fits two distinct groups. The first is designers, freelancers, and agencies that want a modern visual builder with fewer layout constraints. The second is developers maintaining themes or products that use Kirki’s Customizer framework.

I would consider it for a new design-heavy site when the freeform canvas is genuinely useful, or for an existing theme ecosystem where Kirki is already part of the stack. I would keep the setup simpler when the project only needs ordinary block-editor pages or when a theme already provides every customization control required.

Kirki Free vs Pro

The free plan is unusually broad. It includes the infinite canvas, core elements, responsive editing, unlimited breakpoints, Customizer controls, basic interactions, staging mode, a form builder, full-site export/import, the Figma importer, and 10 starter templates.

Pro is less about removing basic building limits and more about advanced workflows. It adds Kirki CMS and dynamic content, the full interaction timeline, popup building, 100+ premium templates, collaboration, comments, dev mode, client view-only links, and priority support.

For freelancers or businesses building one advanced site, Pro is the natural paid tier. Agencies working across several production sites should compare the unlimited-site Agency plan instead of stacking individual Pro licenses.

Compatibility deserves extra attention on older themes

The shift to Kirki 6 is significant enough that older theme integrations deserve testing before a production update. Kirki says the Customizer framework remains supported, but some users of older third-party themes have reported missing Customizer options or theme-specific compatibility problems after moving to the 6.x branch.

If a commercial theme depends on Kirki, I would check that theme vendor’s current compatibility guidance and test the update on staging first. This is especially important when Kirki is acting as a dependency for theme options rather than as the primary site builder.

Kirki compared with dedicated page builders

Breakdance, Bricks Builder, and Elementor are established visual builders with their own design systems and ecosystems. Kirki’s current distinction is the combination of a freeform canvas and its long-standing Customizer framework.

If you are choosing purely for visual page building, compare editor workflow, responsive control, dynamic-content needs, extension ecosystem, and licensing. If an existing theme already depends on Kirki, the decision is different because removing or replacing it may also affect theme customization functionality.

Kirki pricing

Pricing checked September 18, 2026. Kirki Free is available from WordPress.org. Kirki Pro costs $59 per year for one production site. The Agency plan costs $149 per year and supports unlimited sites. A Lifetime plan is available for a one-time $499 payment with unlimited sites and lifetime updates and support.

Paid subscriptions can expire without immediately disabling existing live-site features, but future updates, support, and access to new templates or apps require an active subscription unless you have the Lifetime license.

PluginSuggest verdict

Kirki is now much more ambitious than the Customizer framework many WordPress users remember. The free visual builder has enough functionality to evaluate seriously, while Pro targets dynamic sites, interaction-heavy designs, and agency collaboration.

I would shortlist it for designers who specifically want a freeform canvas and for developers whose themes already rely on Kirki. For an older Kirki-dependent theme, I would treat compatibility testing as part of the update process rather than assuming a major 6.x upgrade will behave exactly like the older framework-only releases.

Kirki FAQs