Why did my HighLevel course pages lose their styling?

Updated 4 August 2026 by Chantal Edouard-Betsy.

You added custom CSS to your HighLevel course, it looked lovely, and then one morning your HighLevel course pages lost their styling and went back to plain. You did not touch a thing. I promise you did not break it. What changed was the platform underneath you, and the fix is not where most people go looking.

Nearly everyone misdiagnoses this. The first instinct is that you fat-fingered something, or a setting lapsed, or the code was never any good. None of that. The styling is fine and still sitting there. It just is not being read anymore, and that is a platform change, not your mistake.

In this blog

• What actually happened to your course pages
• The fix: move your styling to the portal level
• Why copied stylesheets keep breaking
• Should you fix this yourself?
• FAQ
• Key takeaways

What actually happened to your course pages

HighLevel rebuilt its client portal. The whole thing, not a tweak. The new Unified Client Portal is a different build underneath, and your course pages now render inside that new shell rather than the old one.

Here is the part that bit people. Custom CSS you had added at the course level, the styling attached to one specific course, still saves and still shows as present. The new portal simply does not load it. So the code is there, the page is there, and the two are no longer talking. That is why it happened overnight with no change from you: the platform flipped, not your account.

If you have just moved onto the new portal, or you are about to, this is the thing to know going in. (New to it? Here is how to enable the new client portal.) It is a genuine upgrade in most ways. This one side effect just caught a lot of people off guard.

The fix: move your styling to the portal level

The styling has to live at the portal level now, not on each course. Your course pages render inside the portal shell, so the stylesheet that reaches them is the Client Portal branding one, not the per-course field you used before. Move your CSS there and the pages style up again.

There is a real bonus in this. Because the portal stylesheet covers the whole portal, one sheet now styles every course you run at once, instead of you pasting the same thing into each course separately. Less to maintain, in theory. Fewer places for it to drift out of sync.

If your branding is only colours and a logo, the built-in Client Portal settings may get you most of the way with no code at all. (More on that in how to brand your client portal.) It is the deeper, custom styling, the bits the settings do not reach, that has to move into the portal CSS by hand.

Why copied stylesheets keep breaking

Now the honest part, because I would rather you hear it from me than learn it the expensive way. HighLevel changes the portal often. It just proved that by rebuilding the entire thing. Every time it does, the class names and the structure underneath can shift, and CSS written against the old structure stops matching.

So a stylesheet you copied off someone in a Facebook group, or one a developer pasted in once and walked away from, is not really a fix. It is a fix with an expiry date. It will look perfect right up until the next portal update, and then some of it, or all of it, falls over again. This is exactly what just happened to a lot of people's course styling.

That is the real reason portal styling is a maintenance job and not a one-time task. Someone has to watch what HighLevel changes and keep the styling matched to it. This is one of the trade-offs of running your whole business on one platform: the platform moves fast, which is mostly a gift, but it means the polish needs keeping alive.

Should you fix this yourself?

If you are comfortable in CSS and you enjoy it, move your styling into the portal branding CSS and you are sorted, at least until the next update. Genuinely, go for it.

But if you are the founder, not the developer, and you would rather your client-facing pages just look right and stay right without you watching a changelog, this is the sort of thing worth handing over. I brand HighLevel portals properly and keep them maintained as the platform shifts, so a portal update does not undo your course pages while you are busy running your actual business.

FAQ

Why did my HighLevel course pages suddenly go plain?

Because the new Unified Client Portal stopped loading custom CSS set at the course level. Your styling still saves, but the rebuilt portal does not apply it, so course pages render unstyled even though you changed nothing. It is a platform change, not an error on your side.

How do I get my HighLevel course styling back?

Move the styling from the individual course into the Client Portal branding CSS. Course pages now render inside the portal shell, so the portal-level stylesheet is what reaches them. A single portal stylesheet then styles every course at once.

Did the new Unified Client Portal break custom CSS on purpose?

It was a side effect of rebuilding the portal, not a deliberate removal. The per-course custom CSS field still exists and still saves; the new portal shell just no longer loads it. The workaround is to style at the portal level instead.

Will my portal styling break again after the next HighLevel update?

It can. HighLevel changes the portal regularly, and updates can shift the underlying class names and structure, so CSS written against the old structure stops matching. This is why copied stylesheets rot over time and why portal styling needs ongoing maintenance rather than a single paste.

Can I style HighLevel course pages without code?

Partly. The built-in Client Portal settings cover brand colours, a logo, a favicon and a login image with no code. Anything beyond that, such as custom fonts and deeper colour and layout, needs CSS at the portal level, which is where course-page styling now lives.

Is it worth paying someone to maintain my portal styling?

If you are not the technical person and you want your client-facing pages to stay polished without watching for platform changes, yes. The value is not the initial paste, which anyone can copy. It is keeping the styling matched to a portal that HighLevel keeps changing, so it does not break again.

Key takeaways

• Your course pages went plain because the new Unified Client Portal stopped loading per-course custom CSS. You did not break anything.
• The fix is to move your styling into the Client Portal branding CSS, since course pages now render inside the portal shell. One stylesheet then covers every course.
• HighLevel changes the portal often, so copied stylesheets rot and break again at the next update.
• That is why portal styling is a maintenance job, not a one-time paste.
• Fine to do it yourself if you are comfortable in CSS. Worth handing over if you would rather it just stayed right.