Hi @HLeung21 and everyone
cc @CommunityTeam
It should now be possible in all portals to generate the raw HTML embed code – the UI is slightly different then before and HubSpot has hidden this feature a bit.
After publishing your form (orange ‘Review and update’ button in the top right corner), you should see this. Follow the numbers to get the embed code:
Best regards!
Hi @LSkovslundNie and everyone
cc @CommunityTeam
It should now be possible in all portals to generate the raw HTML embed code – the UI is slightly different then before and HubSpot has hidden this feature a bit.
After publishing your form (orange ‘Review and update’ button in the top right corner), you should see this. Follow the numbers to get the embed code:
Best regards!
Hi @AndoniHernandez
cc @CommunityTeam
It should now be possible in all portals to generate the raw HTML embed code – the UI is slightly different then before and HubSpot has hidden this feature a bit.
After publishing your form (orange ‘Review and update’ button in the top right corner), you should see this. Follow the numbers to get the embed code:
Best regards!
Hey @karstenkoehler !
Thank you so much for your reply! I did try it and it seems to be working as it should. That’s definitely something we’ll be using in the future 
This works, but please bring back RAW HHTML!
Hi all,
For me the proposed solution doens’t fix the issue as there is still some sort of hubspo styling that is overwritting the styling from website pafges. Also here encoutered issues with not being able to embed Hubspot forms on a non-Hubspot website, was forced to use Legacy forms in order to embed raw HTML so visitors had a seamless experience, rather than embedding a form that doesn’t fit style nor rest of website look and feel.
Hi all,
I agree -- as @CPossen8 mentioned, there’s still some kind of styling applied to the new HubSpot forms, even when using the embed code. This makes the new forms totally unusable for our site. We need support for raw HTML, similar to how it was implemented for the legacy forms editor.
Hi Karsten, Apparently this still doesn’t work. I’ve got a client who has integrated the Postcode look up API with all legacy forms and is trying to do it with the new forms but can’t using the method you described. I believe the non-legacy form renders inside an iframe, as opposed to rendering as a raw HTML element on our external webpage. Meanwhile, the legacy form does not use an iframe when embedded on a webpage, enabling the postcode lookup tool to interact with the raw HTML and thus work as expected.
I agree. The new form builder is a big improvement, but the inability to customize forms with HTML and CSS makes it harder to match branding and create more engaging user experiences. Having that flexibility would make the builder even more powerful.
Hi Everyone,
Thank you all for taking the time to submit, vote and comment on this Idea.
I’m Sabari, the PM for HubSpot’s Forms tool.
I am excited to share an update that this feature is currently in development. I will keep this thread updated once it moves to Beta.
Regards,
Sabari
Hi all,
is this really still an issue where an update/development is required?
Since some time it is already possible to use the new forms as RAW HTML, if you select “Developer Code” in the “Get embed code” area after publishing a form:
Yes, in this case you need to extend your websites CSS with some new commands to get the HubSpot form styled but it is not a big deal… we successfully use it since severa months.
Here is the related knowledge and explanation:
Best regards,
Dominik