Where Are Plymouth Themes and Config Stored?
Where Plymouth keeps themes and config on Linux, and why editing config alone never changes the boot screen.
Last updated
Plymouth themes live in a shared themes folder with one directory per theme. The daemon config names the active theme in a single short file. Initramfs hooks embed the chosen theme into the boot image for each distro family.
That last step is the famous gotcha: editing config without rebuilding changes nothing on screen. Theme roots also vary by distro build paths, so confirm the directory before installing third party themes. List and set commands report the live state without guessing. List installed themes before setting a new default.
Where Plymouth stores this, by platform
/usr/share/plymouth/themes
Canonical theme root with one folder per theme plus the default symlink. Config lives in etc plymouth. Rebuild the initramfs after every change or boot stays the same.
Frequently asked questions
I changed the Plymouth theme but boot looks the same. Why?
Rebuild the initramfs for your distro after every theme or config change. Debian uses the update initramfs command, Fedora uses dracut, Arch uses mkinitcpio. The boot image embeds a copy of the theme, so disk edits alone never reach the screen.
How do I list installed Plymouth themes?
List the theme directory to see installed names, since some distros build themes into a different data root. Check the alternatives symlink for the active default. The daemon config file names the theme that the next rebuild embeds.
Notice an outdated path? Let us know.