You want KDE Plasma. You have two paths.
You just finished a clean install of Fedora Workstation. The GNOME desktop feels polished but rigid. You want widgets, a system tray, and a right-click context menu that actually does what you expect. Or maybe you are looking at the download page, staring at the Workstation ISO and the KDE Spin ISO, and wondering if you should just start over. You don't need to reinstall. You can add KDE Plasma to your existing system, or you can choose the Spin from the start. Both paths are valid. The choice depends on how much you want to mix desktop environments and how much disk space you have to spare.
A botched display manager switch can leave you at a text console. Know how to switch back before you proceed.
What's actually happening
Fedora packages desktop environments as groups. A group is a curated set of packages that work together. The KDE Plasma group pulls in the shell, the file manager, the settings daemon, and a default set of applications. When you install the group on top of Workstation, you are adding a second desktop session. The system keeps GNOME as the default. You select which desktop to load at the login screen.
The KDE Spin is different. It ships with KDE as the base. It omits GNOME packages entirely. The Spin uses less disk space and avoids the overhead of running two display managers and two sets of background services. The Spin also includes KDE-specific defaults for fonts, themes, and system settings that match the Plasma experience. Installing the group on Workstation leaves GNOME defaults in place. You might see GNOME applications appear in the KDE application menu. You might notice conflicts in notification handling or file manager associations.
Run dnf group list to see what groups are available on your system. The list changes based on your enabled repositories.
Understanding DNF groups
Fedora uses groups to bundle related packages. A group is not a single package. It is a definition file that lists mandatory and optional packages. When you install a group, dnf reads the definition and installs everything listed as mandatory. Optional packages are skipped unless you ask for them. The KDE Plasma Workspaces group includes the shell, the window manager, the file manager, and the settings application. It does not include office suites, games, or development tools. Those are separate groups or individual packages. You can see what is in a group before installing it.
Here's how to inspect the contents of the KDE group before you commit to the download.
dnf group info "KDE Plasma Workspaces"
# WHY: Lists all packages included in the group definition.
# WHY: Shows mandatory packages that will be installed automatically.
# WHY: Shows optional packages that you can add manually if needed.
Check the output for Mandatory Packages. These are the core components. If you see a package you don't want, you can exclude it with --exclude, but excluding core packages often breaks the session. Stick to the defaults unless you have a specific reason to deviate.
Check the group info before you install. Knowing what you are pulling in prevents surprise disk usage.
Install KDE on existing Workstation
Here's how to add the KDE Plasma session to an existing Fedora Workstation installation. The command installs the group and resolves dependencies. The process takes time depending on your internet speed and disk performance.
sudo dnf groupinstall "KDE Plasma Workspaces"
# WHY: Installs the KDE Plasma shell and core utilities without pulling in every KDE application.
# WHY: The quotes are required because the group name contains spaces.
# WHY: dnf resolves dependencies and asks for confirmation before downloading.
Disk space is the first constraint. The KDE Plasma Workspaces group adds roughly 1.5 to 2 gigabytes of packages. Your system needs free space for the download and the installation. Run df -h / to check. If you are low on space, clean the cache first.
sudo dnf clean all
# WHY: Removes cached package metadata and headers to free disk space.
# WHY: Useful when dnf reports insufficient space for the transaction.
# WHY: Run this before the install if your root partition is nearly full.
When you upgrade Fedora, run sudo dnf upgrade --refresh weekly. This command updates all packages and refreshes the metadata cache. It keeps your KDE installation in sync with the rest of the system. Do not confuse dnf upgrade with dnf system-upgrade. dnf upgrade updates packages within the current release. dnf system-upgrade crosses major releases, such as Fedora 40 to Fedora 42. They are different commands.
Check disk space before you start. A failed transaction leaves a half-installed system.
Switch the display manager
The installation pulls in sddm, the Simple Desktop Display Manager. SDDM replaces GDM as the default display manager. GDM is the login screen you see on Workstation. SDDM is the login screen designed for KDE. The switch happens automatically. If you prefer GDM, you can switch back, but SDDM handles KDE sessions more reliably. SDDM supports Plasma theming and session management features that GDM does not provide.
Here's how to ensure SDDM is set as the default display manager after the install.
sudo systemctl set-default sddm.service
# WHY: Sets SDDM as the display manager that starts on boot.
# WHY: KDE Plasma expects SDDM for proper session management and theming.
# WHY: This command updates the symlink in /etc/systemd/system/default.target.
If you ever need to switch back to GDM, run sudo systemctl set-default gdm.service. The change takes effect on the next reboot. You can also switch the display manager at runtime with sudo systemctl isolate sddm.service, but a reboot is safer. The isolate command stops the current session abruptly.
Reboot after the install. The display manager switch takes effect on the next boot.
Verify the session
Log out of your current session. The login screen should now look different. SDDM presents a wallpaper and a session selector. Click the session icon, usually a gear or a KDE logo, and select Plasma. Enter your password. The desktop loads. You should see the Plasma panel at the bottom, the application launcher in the corner, and the system tray on the right. Open the application menu. Look for Dolphin, the KDE file manager. If Dolphin opens and shows your home directory, the installation is complete.
Here's how to confirm the Plasma shell is running from the terminal.
systemctl --user status plasma-plasmashell
# WHY: Checks the status of the Plasma shell service in your user session.
# WHY: Active (running) means the desktop environment is loaded correctly.
# WHY: Failed status indicates a missing dependency or a crash on startup.
You can also check the desktop identifier. This variable tells applications which desktop environment is active.
echo $XDG_CURRENT_DESKTOP
# WHY: Prints the active desktop environment identifier.
# WHY: Output should contain KDE or X-KDE for a Plasma session.
# WHY: This confirms the shell is actually running Plasma and not a fallback.
Run the echo command. If the output says KDE, the session is active.
Common pitfalls and errors
Application conflicts are common when mixing environments. You might have both Nautilus and Dolphin installed. The system needs to know which one opens folders. KDE tools usually prefer Dolphin. GNOME tools prefer Nautilus. If you see the wrong file manager opening, check the default application settings in System Settings. KDE stores these preferences in ~/.config/. GNOME stores them in dconf. The settings do not sync automatically.
When you modify configuration files, edit files in /etc/. Never edit files in /usr/lib/. Files in /usr/lib/ belong to packages. Package updates overwrite changes in /usr/lib/. Changes in /etc/ persist across upgrades. Fedora follows this convention strictly.
If the login screen fails to load, you get a black screen or a text console. Boot into a TTY with Ctrl+Alt+F3. Log in. Check the journal.
[FAILED] Failed to start SDDM Display Manager.
See "systemctl status sddm.service" for details.
If you see [FAILED] Failed to start SDDM Display Manager, the display manager crashed. This often happens when the GPU driver is missing or the configuration file has a syntax error. Check the journal for the root cause.
journalctl -xeu sddm.service
# WHY: Shows the log output for SDDM with explanatory context.
# WHY: The -x flag adds help text for common errors.
# WHY: The -e flag jumps to the end of the log so you see the latest failure.
Plasma runs best on Wayland. GNOME also runs on Wayland. Both environments support X11 for legacy compatibility. If you select Plasma, the system starts the plasma-session service. This service launches the window manager, the panel, and the background processes. If you see kwin_wayland: failed to create platform, the window manager cannot initialize the display backend. This often happens with proprietary NVIDIA drivers that lack Wayland support for the current kernel. Switch to the X11 session at the login screen. Click the session selector and choose Plasma (X11). If X11 works, the issue is specific to Wayland. Update your drivers or check the kernel version.
Run journalctl -xe first. Read the actual error before guessing.
The KDE Spin ISO
The KDE Spin is a separate download. It is not just Workstation with KDE installed. The Spin is built from a different kickstart file. The kickstart file defines the base system. The Spin kickstart excludes GNOME packages entirely. It includes KDE packages as the default. It also sets different defaults for fonts, themes, and system services. The Spin uses sddm from the start. It does not install gdm. The Spin is smaller. It downloads faster. It installs faster.
The Spin is the right choice for a fresh install. If you are already running Workstation, the Spin is not an option. You cannot "convert" Workstation to the Spin. You must reinstall. The group install is the only path for an existing system.
Fedora releases a new version every six months. The KDE Spin and Workstation both follow this cycle. When you upgrade, both environments upgrade together. The KDE Spin does not get stuck on an older version. Use dnf system-upgrade to cross major releases. Plan your upgrades around the six-month cycle. The N-2 release goes end-of-life when N+1 ships. Keep your system current to avoid security gaps.
Pick the path that matches your hardware and your risk tolerance.
Decision matrix
Use the KDE Spin when you want a clean system with no GNOME packages and maximum disk efficiency. Use the KDE Spin when you are installing on a machine with limited storage or older hardware. Use the group install on Workstation when you want to keep GNOME as a backup session in case KDE misbehaves. Use the group install when you are already deep into a Workstation setup and don't want to migrate your data. Use the group install when you need to test KDE applications alongside GNOME tools for development work. Stay on Workstation with GNOME if you only care about the default experience and don't need desktop customization.