KDE Plasma is agraphical shell developed by theKDE community forUnix-like operating systems. It serves as the interface layer between the user and the operating system, providing agraphical user interface (GUI) and workspace environment for launching applications, managing windows, and interacting with files and system settings. Plasma is designed to be modular and adaptable, with different variants tailored for specific device types, such asPlasma Desktop for personal computers,[a][4] andPlasma Mobile for smartphones.[5]
Plasma was first introduced in 2008 as part ofKDE Software Compilation 4, as a major technical overhaul, combining traditional desktop functionality with a widget-based system designed for flexibility and visual consistency. With the KDE brand repositioning in 2009, the KDE software compilation was split into three distinct projects: KDE Plasma,KDE Frameworks andKDE Gear, allowing each to develop and release on independent schedules.[6] As of the Plasma 6 series, feature updates are released every four months, with interim bugfix releases.
From KDE SC 4.0 to KDE SC 4.2, the default theme, "Oxygen", was characterized by dark tones. In KDE SC 4.3, it was replaced by the new "Air" theme, which predominates in transparency and white as the base color. New themes for Plasma can be chosen and installed through software like Discover or online at store.kde.org.
With the release of KDE SC 4.11 on 14 August 2013, Plasma 4 was placed into a feature freeze and turned into a long-term stable package until August 2015. On 15 July 2014, Plasma 4's successor, Plasma 5, was released.[14]
Plasma featurescontainments, which are essentially applets that contain other applets. Two examples of containments are the desktop background and the taskbar. A containment can be anything the developer wants: an image (eitherraster graphics or anSVG image), animation, or evenOpenGL. Images are most commonly used, but with Plasma the user could set any applet as the desktop background without losing functionality of the applet. This also allows for applets to be dragged between the desktop and the taskbar (two separate containments), and have a separate visualization for the more confined taskbar.
Plasma separates components into "data engine" and their visualization counterparts. This is intended to reduce the total programming effort when there are multiple possible visualizations of given data, and to make it easier for the data engine and the workspaces to be written independently.
The scalable nature of the Plasma widgets allows for them to be resized and rotated to any size, with only a brief pause to redraw themselves. TheKross scripting framework allows developers to write widgets in a variety of programming languages in addition toC++.[15]
KRunner in Plasma 4.3
KRunner is a versatile tool for several functions.[16] It replaces the dialog box "Run Command" fromK Desktop Environment 3, and also inherits from the application launcher feature, expanding the possibilities through a modular plug. KRunner stores previously entered commands and searches, accessible via an auto-complete feature.KRunner can be shown on the desktop via the keyboard combinationAlt+F2 or by selecting "Run Command ..." in the desktop menu.
These functions are handled by the plugin:
Application launcher: Type at least three letters of the desired name or description. KRunner shows applications associated with the terms of the search and allows the selection of the desired one.
Calculator: Simply enter the desired operation to show the result. It also supports sophisticated expressions.
Contacts can search for entries in KDE's address book, allowing users to directly open, for example,KMail to write an e-mail. The address of the recipient of your choice is automatically added to the message.
Unit Converter converts values between different units of measure.
Web history: Search history of recently visited sites inKonqueror.
Recent documents: Search for recently opened files.
This is a list of widgets that the current release version of Plasma supports. Not all widgets are supported by default in allLinux distributions; some may require different packages or even a recompilation of Plasma.
First-generation native widgets (inC++,JavaScript,Ruby, orPython. In many distributions, the Ruby and Python bindings must be downloaded separately as packages.)
Second-generation native widgets written in QML[17]
Previous Plasma Workspaces releases also supportedEdje gadgets andE17 modules. Support for those was developed in 2008[20] but removed later, in 2010.[21][22]
Google Gadgets were also supported.[18] After Google announced the discontinuation of its two services that utilize Gadgets – Google Desktop[23] andiGoogle[24] – KDE removed support for this widget engine in March 2013.[25]
Plasma 5 with the Breeze Dark theme, with Konsole and Dolphin, core KDE applications
Plasma 5 is the fifth generation of the graphical workspaces environment created byKDE primarily for Linux systems. Plasma 5 is the successor of Plasma 4 and was first released on 15 July 2014.[26][27][28] It includes a new default theme, known as "Breeze", as well as increased convergence across different devices. The graphical interface was fully migrated toQML, which usesOpenGL for hardware acceleration, resulting in better performance and reduced power consumption.[26][27]
Plasma Mobile is a Plasma 5 variant for Linux-based smartphones.
It improves support forHiDPI displays and ships a convergablegraphical shell, which can adjust itself according to the device in use. 5.0 also includes a new default theme, dubbed Breeze. Qt 5's QtQuick 2 uses a hardware-acceleratedOpenGL(ES)scene graph (canvas) to compose and render graphics on the screen, which allows for the offloading of computationally expensive graphics rendering tasks onto theGPU, freeing up resources on the system's mainCPU.[26]
KDE Plasma 5 uses theX Window System andWayland. Support for Wayland was prepared in the compositor and planned for a later release.[26] It was made initially available in the 5.4 release.[31] Stable support for a basic Wayland session was provided in the 5.5 release (December 2015).[32]
Support for NVIDIA proprietary driver for Plasma on Wayland was added in the 5.16 release (June 2019).[33]
KRunner, a search feature with many available plugins. In addition to launching apps, it can find files and folders, open websites, convert from one currency or unit to another, calculate simple mathematical expressions, and perform numerous other useful tasks.[34]
Flexible desktop and panellayouts composed of individualwidgets (also known as "Plasmoids") can be individually configured, moved around, replaced with alternatives, or deleted. Each screen's layout can be individually configured. New widgets created by others can be downloaded within Plasma.
Powerful clipboard with a memory of previously copied pieces of text that can be called up at will.
Systemwide notification system supporting quick reply and drag-and-drop straight from notifications, history view, and a Do Not Disturb mode.
Central location to control playback of media in open apps, the phone (with KDE Connect installed), or the web browser (with Plasma Browser Integration installed)
Activities, which allow users to separate methods of using the system into distinct workspaces. Each activity can have its own set of favorite and recently used applications, wallpapers, "virtual desktops", panels, window styles, and layout configurations. It also couples withksmserver (X Session Manager implementation) which keeps track of apps that can be run or shutdown along with given activity via subSessions functionality that keep track of state of applications (not all applications support this feature as they do not implementXSMP protocol).[35]
Encrypted vaults for storing sensitive data.
Night Color, which can automatically warm the screen colors at night, or user-specified times, or manually.
Styling for icons, cursors, application colors, user interface elements, splash screens and more can be changed, with new styles created by others being downloadable from within the System Settings application. Global Themes allow the entire look and feel of the system to be changed in one click.
Session Management allows apps that were running when the system shut down to be automatically restarted in the same state they were in before.
KDE Plasma 6 is the sixth and current generation of the graphical workspaces environment made by KDE. It is the successor to Plasma 5 and was initially released on 28 February 2024.[36][37]
Plasma 6 changes the default display server from X11 to Wayland, though the former is still available.[38]
As of version 6.4, the X11 version is no longer installed by default and the KWin (the KDE window manager) codebase is split intokwin andkwin_x11.Kwin is the default Wayland version and will see active development. New fixes are developed forkwin first and backported later tokwin_x11. Versionkwin_x11 is maintained until Plasma 7 and no new features are expected to be backported.[39]
Plasma Desktop is the default and primary variant of KDE Plasma, designed for desktop PCs and laptops. It offers full support for widgets, desktop effects, multiple monitors, and extensive customization options.
With the release of Plasma 6 as part of the KDE MegaRelease 6 (28 February 2024),Wayland became the default display protocol, although X11 remains available as an alternative.[40]
Notable improvements in Plasma 6 include:
Merging of the "Overview" and "Desktop Grid" effects, with improved touch gesture support.[41]
Support for HDR and ICC color profiles under Wayland.[42]
Accessibility improvements including color blindness correction filters.[43]
Default use of a "floating panel", with smarter auto-hide behavior ("Dodge Windows").[44]
Progress toward persistent session restoration, restoring app states and window locations across restarts.[45]
Plasma Netbook was a variant optimized for netbooks and small tablet PCs. It debuted with KDE Software Compilation 4.4 in 2010.[46] Development was discontinued with Plasma 5, and its features were merged into the main Plasma shell.
Plasma Active was a variant designed for touchscreen devices such as tablets. It featured applications like Kontact Touch and a document viewer from the Calligra Suite. It also introduced the "Contour" user interface, developed in 2011 by basysKom.[47] Plasma Active was succeeded by Plasma Mobile with the transition to KDE Frameworks 5.
Plasma Mobile is aimed at smartphones and small tablets operated via touch input. A version based on Qt 6 and KDE Frameworks 6 was released alongside Plasma 6.[48]
Key changes in recent Plasma Mobile versions include:
A redesigned home screen supporting grids, folders, paging, and app drawer with KRunner integration.[49]
Dropping support for Halium-based devices, focusing instead on mainline Linux-supported smartphones.[50]
Active development across distributions such as postmarketOS, with various ports to older devices in progress.
Plasma Bigscreen is a shell variant for smart TVs, large displays, and set-top boxes, optimized for remote control or controller-based navigation. It was first introduced with Plasma 5.26.[51]
Current status:
Initially dropped from the Plasma 6 release due to delayed Qt 6 porting.[52]
Actively revived by developers such as Devin Lin with UI rewrites, home screen redesign, TV control apps, and Raspberry Pi 5 testing.[53]
Packages are available in some distributions, including Fedora 42 (`plasma-bigscreen-5.27.80`).[54]
Currently, Flatpak is unsuitable for packaging Bigscreen as a system shell. Snap or image-based deployment may be explored. Nightly builds and testing images are being used in development.
Plasma Nano is a minimal shell designed for embedded, automotive, IoT, and other touchscreen-based low-resource devices. It provides only essential UI elements for building custom lightweight interfaces.[55]
Status:
Available in distributions like Alpine Linux (`plasma-nano 6.4.5` in the edge repository).[56]
Also packaged in openMamba and other independent distributions.[57]
Documentation remains limited. Community discussions point to a need for clearer guidance on customization and deployment scenarios.[58]
