JetBrains IDEs are adopting a new rendering path on Linux. As you may remember, our IDEs started running in native Wayland mode in Linux Wayland sessions with 2026.1. Starting from 2026.3, the Vulkan rendering pipeline is enabled by default in this setup.
Nothing changes for X11, XWayland, or other operating systems. Vulkan rendering is not yet supported in Remote Development mode, but we’re planning to add this in one of the 2026.3 bugfix versions, following additional compatibility work.
Why Vulkan?
The rendering pipeline is the part of the IDE responsible for drawing the editor, tool windows, dialogs, popups, and other UI elements. Before 2026.3, native Wayland sessions used software rendering by default. Native Wayland provides a modern windowing and scaling model, but without Vulkan, the IDE’s graphics subsystem relies on software rendering. The window image is then kept in system RAM, while the CPU converts UI primitives – such as lines, rectangles, curves, text, and effects – into pixels. See this blog post for a more technical explanation. Although this work has been heavily optimized, it still consumes CPU resources that could be used for other tasks.
The cost becomes most visible when a large or complex area of the IDE has to be redrawn, for example when resizing a window, scrolling, typing, or displaying popups. Fractional display scaling makes the effect more noticeable because a non-integer scale requires the renderer to produce and compose more pixels.
This helps explain why a native Wayland session might have felt laggy, even on a system with a powerful GPU: The GPU wasn’t doing the main rendering work. Switching to the X11 toolkit could improve rendering performance by reducing the amount of work done by the CPU, but at the cost of native Wayland behavior and potentially blurrier output in the case of fractional scaling.
Vulkan keeps the native Wayland path while moving more of the rendering work from the CPU to the GPU. The actual performance benefits depend on the GPU, driver, desktop environment, and workload, so the improvement will not be identical on all systems.
The result is a stronger foundation for a responsive, modern IDE experience on Linux Wayland, particularly on systems with fractional display scaling or complex UI content.
Vulkan is designed to produce the same visual output as the other rendering backends, but with better responsiveness and reduced power consumption. The goal here is to improve efficiency in image rendering, not change the way the image looks.
How to tell whether Vulkan is enabled
Starting with version 2026.3, Vulkan rendering is enabled by default when you run your IDE in a native Linux Wayland session. No additional configuration is required.
If you previously switched to the X11 toolkit but are now running native Wayland sessions on Linux, make sure you remove the following option from Help | Edit custom VM options:
-Dsun.awt.toolkit.name=XToolkit
Then restart your IDE.
What comes next
We are continuing to improve the Vulkan rendering pipeline and native Wayland support with different Linux distributions, desktop environments, GPUs, drivers, and display configurations based on internal testing and user feedback.
Upcoming bug-fix releases will be focused on making the default behavior in a Wayland session more robust, especially in areas where users are more likely to notice issues. For example, our upcoming plans include:
- Adding missing Java 2D primitives to fix problems affecting color emoji and some shapes, as well as to close remaining visual gaps.
- Improving text rendering at fractional display scaling, where some configurations can still produce blurry fonts.
- Addressing issues with window presentation and incorrectly rendered views.
- Bringing Vulkan to additional usage scenarios, including remote development, once the remaining compatibility prerequisites are met.
The JetBrains Runtime roadmap also includes deeper GPU acceleration for antialiased geometry. This should allow more UI drawing operations to benefit from hardware acceleration instead of falling back to less efficient paths.
The longer-term 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.
Help us improve Vulkan on Linux
Despite our efforts to stabilize Vulkan rendering in the officially supported configurations, some hardware and software combinations may still produce unexpected results.
If you encounter rendering artifacts, flickering, missing content, crashes, or unexpectedly slow performance, please report the issue through our usual support channels, such as YouTrack or the support request form.
When reporting an issue, please include the following:
- The IDE name and build number.
- Your Linux distribution and desktop environment.
- Your GPU, graphics driver version, and display scaling factor.
- A screenshot or screen recording if the problem is visual.
- Complete IDE logs captured via Help | Collect logs and diagnostic data.
- Steps to reproduce the issue.
This information helps us narrow down where the problem originated: in the IDE, JetBrains Runtime, the desktop environment, or the graphics driver. It also helps us prioritize improvements for future releases.
If you encounter problems with rendering and suspect they may be caused by Vulkan, go to Help | Edit custom VM options… and add the following option:
-Dsun.java2d.vulkan=false
Then restart your IDE.
We hope Vulkan rendering will make our IDEs feel more responsive and consistent for Linux Wayland users. As always, we will continue refining the implementation and delivering improvements in upcoming releases

