I noticed in a video if you went to themes in admin, and clicked on the theme name, it opened up a page that allows you to customize the colors.
I just get a blank page. Is that a bug in my install or 8.8? All I want to do it change the pastel color scheme.
Changing the CSS in this software looks like it requires a master’s degree in web design.
Hello Vincent,
so far, themes (developing new ones, changing current one, etc.) isn’t really a supported feature at the moment in Suite 8.8.
The different themes in Suite 7 could be selected through the admin settings, which doesn’t do much anymore in Suite 8 now.
Wow, that post was 4 years so I guess it’s just going to happen
I have tried to follow videos of using a custom themes folder but they break my site.
All I really want to do is change the menu (navbar) and menu dropdown color. I don’t care if it gets overwritten in an update, and I can redo those minor changes.
.navbar {
{
background-color: #534d64;
}
The CSS in inspect points to public/dist/styles.d5a2e831ecac31c7.css)
not a CSS folder. I can’t even find the code after unminifying that file.
If it is part of Angular, you have to follow front end development guide.
I don’t understand, what does that have to do with CSS?
SuiteCRM v8s use the Angular for most of its front end.
No idea what that is. Sorry.
okay!
crazy, only wanted to change the navbar color, not learn another platform
thanks anyway
There is an easy workaround to this:
You can use something like that to simply inject the CSS from your browser.
Unfortunately, that is on browser level - not server level for everybody.
Is it still not possible in latest 8.9 version ?I see in my default extension the style is build & imported via index.html :
<link rel="icon" type="image/x-icon" href="extensions/defaultExt/app/src/favicon.ico">
<style>body{background:red!important}</style><link rel="stylesheet" href="styles.9ecc17796dbf302d.css" media="print" onload="this.media='all'"><noscript><link rel="stylesheet" href="styles.9ecc17796dbf302d.css"></noscript></head>
but never applied or imported; look like the index.html in the defaultext is never loaded so my custom style isnt aswell
It’s on the roadmap for the version 8.11:
For anyone struggling with this: I managed to change colors in SuiteCRM 8 by directly editing the compiled Angular CSS file located at public/dist/styles.[hash].css (in my case styles.d5a2e831ecac31c7.css). This controls the main SuiteCRM 8 modules UI.
However, keep in mind that SuiteCRM 8 has a dual frontend architecture — the Angular frontend uses that compiled CSS, but legacy views (dashboards, dashlets, and some admin pages) still use the legacy PHP theme, just like in SuiteCRM 7. For those, you need to override the CSS the same way you would in SuiteCRM 7, using the custom theme path under public/legacy/custom/themes/.
So in short: two separate CSS files, two separate frontends — changes to one won’t affect the other.
Hope this saves someone a few hours of confusion!
Hi,
According to the roadmap, this feature will likely be available in upcoming versions. However, I think you may have to wait at least a year or more before it arrives. 
If you can’t wait that long, you can try our tool here
All changes are upgrade-safe, and you can easily deploy them again with just one click if you accidentally make a mistake with the colors. You can also fully revert back to the original SuiteCRM theme anytime without needing any technical knowledge. 
Could you please share CSS code that you changed?
Thanks for the reply!
So crazy a simple thing like adding a piece of CSS is still not supported. Rly dont get why they keep on adding things when the basics are still not here in the V8.
Hi @creativologist, I ran into the same issue on 8.8 and can confirm this isn’t just a misconfiguration.
Right now, the “Themes” section in admin doesn’t seem to be functional in the way it was in SuiteCRM 7 (blank page, changes not persisting, etc.). From what I’ve found, color and theme customization in SuiteCRM 8 is not exposed via the UI yet.
For anyone trying to change colors (e.g. navbar, buttons), there are basically three options:
Edit the compiled CSS in /public/dist/styles*.css
→ Quick and works immediately, but will be overwritten on rebuild/update.
Proper way: modify SCSS variables in the frontend source and rebuild
→ More stable, but requires working with the Angular build process.
Temporary workaround: use browser-based CSS overrides
→ Only affects your local view.
