JetBrains IDEs on Linux with Wayland now draw their interface through Vulkan by default

  • PublicPublic
  • 20 Nov, 2026
JetBrains IDEs on Linux with Wayland now draw their interface through Vulkan by default

JetBrains IDEs are changing how they draw their interface on Linux. Native Wayland mode arrived in Linux Wayland sessions with version 2026.1. Starting with 2026.3, the Vulkan rendering pipeline is enabled by default in that setup, with no extra configuration required. X11, XWayland and other operating systems are unaffected. Remote Development mode does not support Vulkan yet. Support is planned for one of the 2026.3 bugfix releases, after further compatibility work.

The rendering pipeline draws the editor, tool windows, dialogs, popups and the rest of the UI. Before 2026.3, native Wayland sessions used software rendering. The window image lived in system RAM, and the CPU turned primitives such as lines, rectangles, curves, text and effects into pixels. Despite heavy optimization, this consumed CPU time. The cost was most noticeable when large or complex areas had to be redrawn, for example during window resizing, scrolling, typing or popup display. Fractional scaling made it worse because a non-integer scale forces the renderer to produce and compose more pixels.

This is why native Wayland sessions could feel laggy even on machines with powerful GPUs: the GPU was not doing the main rendering work. Falling back to the X11 toolkit reduced CPU load, but it sacrificed native Wayland behavior and could produce blurrier output with fractional scaling. Vulkan keeps the native Wayland path and moves more of the work to the GPU. It aims for identical visual output with better responsiveness and lower power consumption. Actual gains depend on the GPU, driver, desktop environment and workload.

Users who previously switched to the X11 toolkit and now run native Wayland should remove that option from Help | Edit custom VM options. If rendering problems appear to come from Vulkan, the new pipeline can be disabled in the same place by adding -Dsun.java2d.vulkan=false. JetBrains asks users to report rendering artifacts, flickering, missing content, crashes or unexpectedly slow performance via YouTrack or the support request form. Including system details in these reports helps determine whether a fault lies in the IDE, JetBrains Runtime, the desktop environment or the graphics driver.

Upcoming bug-fix releases will focus on making the default Wayland behavior more robust across distributions, desktop environments, GPUs, drivers and display configurations. The JetBrains Runtime roadmap also includes deeper GPU acceleration for antialiased geometry. This should let more drawing operations use hardware acceleration instead of slower fallback paths. In the longer term, the goal is to make the Wayland toolkit and its Vulkan pipeline suitable for broader OpenJDK use, while also exploring Vulkan-based rendering for Linux X11.