Coupons
Help
  • FAQ
    browse most common questions
  • Live Chat
    talk with our online service
  • Email
    contact your dedicated sales:

Is KiCad’s Windows UI Finally Going Modern? An Ambitious Fluent UI Experiment

Author : Alex Chen | PCB Design & High-Speed Engineering Specialist

November 17, 2026


For years, KiCad's Windows interface has looked more traditional than its macOS counterpart and some Linux desktop environments. Recently, the wxWidgets community introduced an experimental backend based on WinUI 3 and successfully ran part of KiCad with it. The result offers an early look at what a KiCad interface closer to Windows 11 Fluent UI might look like. However, this is currently only a technical experiment and has not been officially endorsed or adopted by the KiCad project.

Users who work with KiCad across multiple operating systems may have noticed a clear difference: the Windows version has never looked quite as modern as versions running on macOS or certain Linux desktop environments.

This is not entirely a KiCad-specific issue. KiCad relies heavily on the cross-platform GUI framework wxWidgets. On macOS, wxWidgets can use native interface capabilities such as Cocoa. On Linux, different GTK versions and desktop themes can also provide a relatively modern visual appearance. On Windows, however, KiCad has traditionally depended on wxWidgets' conventional Windows desktop control system.

As a result, even though KiCad's functionality, PCB editor, and 3D Viewer continue to evolve, elements such as menus, buttons, dialog boxes, and toolbars still retain much of the appearance associated with classic Win32 desktop software.

This is why many Windows users have the following impression:

KiCad is a powerful application, but its interface does not look like a modern Windows application.

 

A New wxWidgets Backend Based on WinUI 3

That situation recently received an interesting technical development. A developer in the wxWidgets community opened an experimental pull request that attempts to add a new backend based on WinUI 3 and the Windows App SDK.

In practical terms, the goal is to give wxWidgets applications an opportunity to use a more modern Windows 11 interface while retaining the existing application framework.

The more interesting part is that the pull request author used KiCad as a real-world test of the new backend. Part of KiCad was successfully compiled and run with the experimental wxWinUI backend, and screenshots were published.

KiCad running with the experimental wxWinUI backend KiCad interface with Windows Fluent UI styling

The results already show more modern buttons, menus, rounded corners, and toolbars, along with an overall visual style closer to Windows 11 Fluent Design.

The developer later shared a video showing a build approaching a usable state and described it as a "KiCad Fluent UI edition" that was "almost working." This is more significant than a simple demonstration involving a few wxWidgets controls: a large and complex EDA application was actually brought up using the new Windows backend.

 

Why Can KiCad Change Its Interface This Way?

The underlying reason is straightforward: KiCad uses wxWidgets for its graphical user interface.

The two configurations can be understood as follows:

  • Traditional Windows version: KiCad → wxWidgets → traditional Windows UI
  • Experimental configuration: KiCad → wxWidgets → WinUI 3 / Fluent UI

The main attraction is that KiCad would not necessarily need to redesign its entire user interface from scratch to obtain a more modern Windows appearance. Instead, the wxWidgets backend would provide a different platform-level implementation for the same application framework.

This is therefore more than simply applying a new visual theme to KiCad. It involves changing how wxWidgets implements its Windows interface. Many basic controls, including buttons, menus, toolbars, text fields, lists, and notebook controls, are already able to run in the experimental environment. Development has also begun on features such as Mica backgrounds, dark mode, and Fluent-style visual behavior.

If this direction eventually matures, Windows users could see a substantial improvement in KiCad's visual consistency with the rest of the operating system. The potential benefit would not be limited to the appearance of a single dialog or toolbar. A platform-level backend could provide a more consistent treatment across many application components while allowing KiCad to retain its existing GUI architecture.

 

This Is Not an Official New KiCad UI

There is an important distinction that should not be overlooked. The screenshots may easily lead to the conclusion that KiCad is preparing to switch to WinUI 3. That is not currently the case.

First, the pull request was submitted to the wxWidgets project, not to KiCad. Second, it remains an experimental draft pull request. The author has explicitly stated that the implementation cannot yet be considered production-ready and does not even reach beta quality. Many bugs and incomplete areas remain.

More importantly, there is currently no evidence that the KiCad core development team has approved, accepted, or decided to adopt this approach.

At this stage, KiCad is primarily being used by the pull request author as a large, real-world application for validating the new backend. In other words, someone has produced a Fluent UI version of KiCad for experimental purposes, but that does not mean the official KiCad project is developing a Fluent UI edition.

KiCad is also much more than a collection of buttons, menus, and dialog boxes. The application includes complex Advanced User Interface components, custom controls, the PCB canvas, OpenGL-based functionality, and the 3D Viewer. Some of these modules have not yet been fully adapted to the new Windows backend.

Consequently, a considerable amount of work would be required before this approach could become part of an official KiCad release. Compatibility would need to extend beyond basic controls to the application's specialized editors, rendering paths, docking behavior, and other custom interface components.

A more accurate description of the current situation is:

This experiment provides the first clear demonstration that a more modern Windows version of KiCad is technically possible.

 

How LLM-Assisted Development Made the Experiment Possible

This pull request also has an interesting development background. The author has stated that the large-scale porting effort made extensive use of large language model assistance. The project continued for more than a month and involved hundreds of dollars in model-inference costs. At the same time, the developer carried out substantial manual testing, debugging, code review, and iteration.

The author also acknowledged that without LLM assistance, attempting an engineering project of this scale might not have been practical. This reflects a broader change in software development: AI tools can reduce the initial cost of exploring complex infrastructure work, even though the resulting code still requires real testing and engineering review.

In the past, an individual developer might have found it difficult to attempt a project such as creating a new Windows GUI backend for wxWidgets. With AI agents and LLMs, a developer can at least build prototypes more quickly, automate a significant amount of repetitive implementation work, and then expose the result to real applications and open-source communities for validation.

That does not guarantee that the pull request will be accepted by wxWidgets, nor does it indicate that KiCad will adopt the backend. The long-term outcome remains uncertain. However, the experiment provides a useful technical reference point for both projects.

For users who have long felt that the Windows version of KiCad looks somewhat dated, the experiment offers a clear preview of what a modernized interface could look like. If KiCad eventually gains a native-looking modern Windows UI, it could resemble this Fluent Design-oriented implementation.

Alex Chen | PCB Design & High-Speed Engineering Specialist Alex Chen | PCB Design & High-Speed Engineering Specialist

Alex Chen is a senior PCB design engineer with extensive experience in high-speed and high-density circuit design. He specializes in signal integrity, impedance control, and multilayer PCB layout optimization. At AIVON, he reviews and refines content related to PCB design principles, EDA tools, and advanced layout techniques. His expertise helps engineers avoid common design pitfalls and improve performance, reliability, and manufacturability in complex PCB projects.

Related Tags


2026 AIVON.COM All Rights Reserved
Intellectual Property Rights | Terms of Service | Privacy Policy | Refund Policy