Where Custom CSS Works in GoHighLevel (and Where It Doesn't)

Written by Niyamul Islam Sajal, COO & GHL Certified AdminOctober 21, 20263 min readGoHighLevel

Open a GoHighLevel funnel page, click Settings, and scroll until a box labeled Custom CSS shows up. That field is the most visible of several places the platform lets you style things through code.

Knowing which one applies matters more than knowing CSS syntax. GoHighLevel custom CSS isn't one setting in one menu. It's a handful of separate injection points, each tied to a different part of the builder.

Where GoHighLevel Custom CSS Actually Lives

Page-level CSS sits inside the Funnel or Website Builder. Open a page, go to Settings, and whatever you paste there applies only to that one page.

For something sitewide, the Website Settings area has a Tracking Code section that doubles as a global styling slot, alongside the usual domain and favicon options covered in HighLevel's own overview of site-level settings.

We handle this split during GHL setup and configuration for agencies that want one look across every funnel page.

Forms, surveys and quizzes don't use either of those fields. They carry their own Custom CSS box, under Sites, Form Builder, then the Styles tab's Advanced section, and it only affects that one form.

Community groups go further still. Memberships, Communities, Groups, then a group's Settings and Branding tab holds separate Custom CSS and Custom JavaScript fields, with a Test Preview step before anyone flips on Live Mode.

Injection pointWhere to find itWhat it touches
Page-level CSSFunnel or Website Builder, page SettingsJust that one page
Tracking Code / global CSSWebsite Settings, Tracking Code sectionEvery page across the site
Form, survey or quiz CSSSites, Form Builder, Styles tab, AdvancedFields and buttons inside that one form
Community group CSS/JSMemberships, Communities, Groups, Branding, Advanced OptionsThat one group, with a Test Preview and Live Mode split

The Iframe Problem With Forms, Surveys and Quizzes

Paste CSS into a funnel page's Custom CSS field hoping to restyle an embedded form, and nothing inside that form changes.

HighLevel's own support article on adding custom CSS to forms, surveys and quizzes is direct about why: the form loads inside an iframe, so page-level CSS only styles the container around it, never the fields or buttons inside.

To reach those, open the form itself in the Form Builder and use its own Custom CSS box instead. The same limit applies to forms embedded on external sites. Style the iframe wrapper; what's inside stays untouched.

The same article carries one warning worth keeping: avoid overusing !important. It's an easy habit to fall into once a style refuses to apply, and it tends to make the next override fail the same way.

Why Sitewide Styling Still Feels Like a Workaround

A feature request on HighLevel's own ideas board explains why teams doing custom build work on GoHighLevel sites keep reaching for workarounds.

Submitted in August 2025 and still carrying an open status update as of April 2026, it says the page builder's side panel offers no element-level CSS option, only page-level, which makes consistent styling across repeated sections impractical.

The newer color picker compounds that: it doesn't accept CSS variables such as var(--color-primary), which worked in the older version. Teams end up declaring variable values through custom fields instead, since the panel itself won't hold that styling.

None of this is officially supported. HighLevel says plainly it does not provide guidance, recommendations or support for custom code, a line taken from its own guide to community group branding.

If a builder update breaks a rule written months ago, there's no support ticket that fixes it. There's only a support arrangement with someone who's actually watching for it.

Know which of the four boxes is being edited before touching any code. A rule that works in a form's Custom CSS field won't work in a funnel page's Settings, and a sitewide fix belongs in Tracking Code, not on one landing page.

Cover photo by Bibek ghosh on Pexels

Sources (4)

Need help implementing this in GoHighLevel?

Our team builds, automates, and scales GoHighLevel systems for agencies every day. Book a free call and we'll map out exactly what to ship next.

Book a free call