Plymouth is the graphical boot splash system used by most major Linux distributions to display an animated screen, progress feedback and interactive prompts while the system starts up and shuts down. In Linux system initialization, it runs from the initramfs before the root file system is mounted, keeps the display occupied while systemd starts services, and then hands the screen over to the display manager or a text login.
Plymouth is often described simply as the boot splash, but its role is broader than decoration. It provides a single, consistent channel for user interaction during early boot, most importantly the passphrase prompt for an encrypted root volume, and it hides the flicker of mode changes that would otherwise occur between firmware, bootloader, kernel and desktop.
How Plymouth works during boot
Plymouth consists of a daemon called plymouthd and a client called plymouth, which other boot components use to send messages, update progress and request input. The daemon starts very early, normally as one of the first units inside the initramfs, and it opens the display through the kernel DRM/KMS interface or, as a fallback, the legacy framebuffer.
Because kernel mode setting sets the native resolution before Plymouth draws anything, the splash can appear at full resolution without the screen switching modes later. When the initramfs pivots to the real root, Plymouth keeps running, and the plymouth-quit and plymouth-quit-wait units stop it once the display manager or getty is ready to take over the console.
The following table lists the main components and what each one contributes to the boot sequence.
| Component | Type | Role during boot |
|---|---|---|
| plymouthd | Daemon | Owns the display and renders the active theme |
| plymouth | Client command | Sends messages, progress and prompt requests to the daemon |
| Renderer plugins | Shared libraries | Draw through DRM, framebuffer or a text console |
| Splash plugins | Shared libraries | Implement theme logic such as two-step or script |
| systemd integration units | Unit files | Start, stop and hand off Plymouth at the correct moments |
Plymouth themes and splash plugins
A Plymouth theme is a directory under /usr/share/plymouth/themes containing a .plymouth descriptor file and its images or scripts. The descriptor names a splash plugin (ModuleName) that defines how the theme behaves, so two themes using the same plugin differ only in artwork and settings.
Administrators select a theme with plymouth-set-default-theme, and on most distributions they must rebuild the initramfs afterward, because the theme files are copied into the early boot image. The table below compares the commonly shipped plugins.
| Splash plugin | Visual style | Typical use |
|---|---|---|
| two-step | Animation plus progress, vendor logo support | Default themes such as bgrt and spinner |
| script | Fully programmable with a small scripting language | Custom corporate or distribution themes |
| text | Simple text progress line | Systems without working graphics |
| details | Plain scrolling boot messages | Troubleshooting and server consoles |
| space-flares and fade-throbber | Older animated effects | Legacy desktop themes |
The bgrt theme deserves particular mention: it reads the firmware boot logo from the ACPI BGRT table and keeps it on screen, which produces a seamless transition from the UEFI vendor logo to the desktop with no visible change of image.
Password prompts and boot messages
Plymouth acts as the central agent for boot-time questions. When systemd-cryptsetup needs a LUKS passphrase, it uses the systemd password agent protocol, and Plymouth displays a graphical passphrase dialog inside the splash instead of a raw console prompt. The answer is passed back without the text ever being written to the screen or the log.
Plymouth also buffers boot messages from the console, so pressing Esc switches from the splash to the details view and shows the messages that were hidden. This switch is non-destructive: the boot continues, and the administrator can return to the graphical view by pressing Esc again.
plymouth ask-for-passwordrequests a secret through the active theme.plymouth display-message --textshows a short notice on the splash.plymouth --pingchecks whether the daemon is running.plymouth show-splashandhide-splashtoggle the graphical view.
Plymouth compared with related boot components
Plymouth is not a bootloader and not an init system; it is a presentation layer that sits alongside them. Confusion arises because the splash is the most visible part of startup, so problems in GRUB, the initramfs or systemd are often wrongly attributed to it. The table separates the responsibilities.
| Component | Stage | Main responsibility | Relation to Plymouth |
|---|---|---|---|
| GRUB | Before the kernel | Loads the kernel and initramfs | Ends before Plymouth starts |
| initramfs | Early user space | Finds and mounts the root file system | Contains and launches Plymouth |
| systemd | Early and late user space | Starts and supervises services | Starts and stops Plymouth units |
| Kernel command line | Kernel start | Passes boot parameters | Enables Plymouth with splash |
| Display manager | End of boot | Provides graphical login | Receives the display from Plymouth |
The splash only appears when the kernel command line contains splash and usually quiet; without these parameters, most distributions show plain text boot messages even when Plymouth is installed.
Configuring and troubleshooting Plymouth
Most configuration lives in /etc/plymouth/plymouthd.conf, which sets the default theme and the ShowDelay value, the number of seconds Plymouth waits before drawing anything. A short delay avoids a pointless flash of the splash on fast machines that boot in a second or two.
Typical problems relate to graphics drivers and the initramfs rather than Plymouth itself. The decision table below summarizes the most frequent symptoms.
| Symptom | Likely cause | Recommended fix |
|---|---|---|
| No splash, only text | Missing splash parameter or no KMS driver in initramfs | Add splash and include the GPU driver early |
| Low-resolution splash | Framebuffer fallback before KMS loads | Load the DRM driver in the initramfs |
| New theme not shown | Initramfs not regenerated | Rebuild with dracut, mkinitcpio or update-initramfs |
| Boot hangs at splash | A service is waiting, hidden behind the splash | Press Esc or boot with plymouth.enable=0 |
| Black screen before login | Handoff to display manager failed | Check plymouth-quit ordering and GPU driver logs |
For debugging, the kernel parameter plymouth.debug writes a detailed log to /var/log/plymouth-debug.log, and plymouth.enable=0 disables the splash for a single boot without uninstalling anything.
Limitations and common misconceptions
Plymouth adds a small amount of work to early boot, but it rarely slows startup measurably; a slow boot is almost always caused by a service, a device timeout or a network wait that the splash merely hides. Tools such as systemd-analyze reveal the real bottleneck.
- Hiding messages is not the same as fixing errors: failures still appear in the journal.
- On headless servers, Plymouth offers little value and is often removed or set to the details plugin.
- Proprietary graphics drivers loaded late can prevent a high-resolution splash.
- A broken theme usually falls back to text mode rather than blocking boot.
In plain words
Plymouth is the welcome screen of a Linux computer while it starts. Instead of showing hundreds of lines of technical text, it shows a logo or a small animation, much like the loading screen of a game.
It also has a practical job. If the disk is encrypted, Plymouth is the friendly box that asks for the password. If something goes wrong, pressing Esc pulls back the curtain and shows the detailed messages underneath.
A real-world example
A university IT department deploys Fedora laptops with full-disk encryption to 300 staff members. Early test units showed a text prompt for the LUKS passphrase at a low resolution, which users found confusing and occasionally reported as a fault.
The team confirmed that quiet splash was on the kernel command line, added the integrated GPU driver to the initramfs with dracut so that kernel mode setting happened early, and selected the bgrt theme so the manufacturer logo remained visible from power-on. After regenerating the initramfs, the laptops showed a clean graphical passphrase dialog at native resolution.
Support tickets about the startup screen dropped to almost zero, and technicians kept a simple instruction for diagnosis: press Esc during boot to see the hidden messages, or add plymouth.enable=0 for one boot when a deeper investigation is needed.