How to Apply Custom Styling to a Specific Dropdown Field in a HubSpot Multi-Step Form

Hi everyone,

I’m currently working on a HubSpot multi-step form, and I need to display one particular field as pills instead of a standard dropdown.

Here’s my setup:

  • I’m using the developer code approach, embedding the multi-step form code inside a HubSpot module.
  • This module is then placed on a HubSpot website page.
  • By inspecting the rendered form, I identified the CSS classes for the dropdowns and applied custom styles to create the pill-style appearance.

The issue I’m facing is that the classes applied to the form fields are global, so my custom styling is affecting all dropdown fields, not just the specific one I want to modify.

My question:
Is there a way to target and style only a specific dropdown field — for example, using a unique selector, field ID, or HubL logic — so that the pill styling applies only to that field and not globally?

Any suggestions, workarounds, or best practices for handling this in HubSpot forms would be greatly appreciated.

Thanks in advance!

Hi @hafizusama,
Thank you for posting to the Community!
I understand that you want to add custom styling to your multi-step form to change field to ‘pills’ instead of a standard dropdown.
I’d like to tag in some of our Top Contributors to see if they have any suggestions -- Hi @ArtyCele @FazleRabbihx @MBERARD Do any of you all have any ideas for @hafizusama?
Happy Friday!
Cassie, Community Manager

Hi @hafizusama,

I ran into the same issue, and the only way I managed to style a specific field on a specific step was by using a custom CSS selector. It’s not the cleanest approach, but it worked for me:

.text-hero-multistep__form .hsfc-Step:nth-child(2):has(.hsfc-RadioFieldGroup__Options) .hsfc-RadioFieldGroup__Options .hsfc-FieldLabel {
 box-shadow: ...
}

Basically, I targeted the field based on its step order and structure. Not ideal, but it gets the job done when you can’t rely on unique field IDs or HubL logic.

Best,

Thank you so much @MBERARD for the solution, and thank you @chighsmith for tagging the relevant people.