# Allow FontAwesome version 6 **URL:** \ **Category:** HubSpot Ideas\ **Tags:** design-manager, content\ **Created:** [May 26, 2023, 6:20pm UTC](https://community.hubspot.com/t/allow-fontawesome-version-6/82137 "2023-05-26T18:20:38Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![jnix284](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jnix284/32/29_2.png) [@jnix284](https://community.hubspot.com/u/jnix284)\ **Post date:** [May 26, 2023, 6:20pm UTC](https://community.hubspot.com/t/allow-fontawesome-version-6/82137/1 "2023-05-26T18:20:38Z")
Developers are limited to using version 5.14.0 and can’t update themes to version 6. Who: developers creating themes and marketers using themes What/goal: ability to use the latest icon sets Value: adds backwards compatibility If the theme was created with 5.0.10 it is not possible to update to 5.14.0 because 5.14.0 is not downward compatible with 5.0.10. Updating the icon\_set would break the icons on existing website pages where 5.0.10 was used. Fontawesome introduced downward compatibility with version 6, but since HubSpot doesn’t allow version 6, it’s not possible to update existing themes. **Editing to include that without this update, users can’t select TikTok or the new Twitter X icons.** **Editing to include the icon field now supports v6.4.2 which works for all new themes or custom themes (doesn’t resolve backwards compatibility issue).** ---
**Author:** ![LMaseraGarza](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/lmaseragarza/32/57633_2.png) [@LMaseraGarza](https://community.hubspot.com/u/LMaseraGarza)\ **Post date:** [September 26, 2023, 2:15pm UTC](https://community.hubspot.com/t/allow-fontawesome-version-6/82137/2 "2023-09-26T14:15:57Z")
I would love to be able to use the new X-twitter logo, but I can’t because it’s part of the 6.4.2 release. ---
**Author:** ![jaybaum](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jaybaum/32/30531_2.png) [@jaybaum](https://community.hubspot.com/u/jaybaum)\ **Post date:** [October 11, 2023, 1:58pm UTC](https://community.hubspot.com/t/allow-fontawesome-version-6/82137/3 "2023-10-11T13:58:59Z")
HubSpot - we need this! ---
**Author:** ![jnix284](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jnix284/32/29_2.png) [@jnix284](https://community.hubspot.com/u/jnix284)\ **Post date:** [November 4, 2023, 6:24pm UTC](https://community.hubspot.com/t/allow-fontawesome-version-6/82137/4 "2023-11-04T18:24:11Z")
The icon field now supports v6.4.2 which works for all new themes or custom themes but doesn’t include backwards compatibility which limits the ability for existing marketplace themes to update easily. ---
**Author:** ![bradhave](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bradhave/32/97235_2.png) [@bradhave](https://community.hubspot.com/u/bradhave)\ **Post date:** [November 8, 2023, 2:57pm UTC](https://community.hubspot.com/t/allow-fontawesome-version-6/82137/5 "2023-11-08T14:57:44Z")
@Jnix284 Is right. I was exited when I saw 6.4.2 was added. But I can’t acutally update it in my modules ![bradhave_0-1699455284653.png](https://d2qpr2jzcazej7.cloudfront.net/optimized/3X/3/6/36132e440feeb9732f8e7c3baaf9ec3e28c49b41_2_690x56.png) Even getting an issue from Chevron Left, which wasn’t even renamed. Looks like the ‘name’ is differenct ![bradhave_0-1699455539460.png](https://d2qpr2jzcazej7.cloudfront.net/original/2X/0/0f6618e4b1e400e73b5e261e88a536a66af5d28d.png) For reference: [https://fontawesome.com/docs/web/setup/upgrade/whats-changed#icons-renamed-in-version-6](https://fontawesome.com/docs/web/setup/upgrade/whats-changed#icons-renamed-in-version-6) ---
**Author:** ![JuanPBotero](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/juanpbotero/32/68963_2.png) [@JuanPBotero](https://community.hubspot.com/u/JuanPBotero)\ **Post date:** [November 8, 2023, 9:42pm UTC](https://community.hubspot.com/t/allow-fontawesome-version-6/82137/6 "2023-11-08T21:42:19Z")
@hubspot is there an ETA on this? ---
**Author:** ![lindahl](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/lindahl/32/220871_2.png) [@lindahl](https://community.hubspot.com/u/lindahl)\ **Post date:** [November 16, 2023, 1:31am UTC](https://community.hubspot.com/t/allow-fontawesome-version-6/82137/7 "2023-11-16T01:31:22Z")
I was directed here because the Twitter icon in the social module of Email DnD is incorrect. When can we expect an update? We already have almost 50 or 100 templates that include this module setting, it would be quite a hassle to update each one of them. ---
**Author:** ![NBarbieri](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/nbarbieri/32/77566_2.png) [@NBarbieri](https://community.hubspot.com/u/NBarbieri)\ **Post date:** [December 4, 2023, 5:22pm UTC](https://community.hubspot.com/t/allow-fontawesome-version-6/82137/8 "2023-12-04T17:22:44Z")
We’ve been having a frustrating time trying to get FontAwesome Pro 6.4.2 icons installed (specific icons to our industry which are missing from the icon’s library). It’s disheartening to see it’s a compatability issue. Hope this is resolved quickly! ---
**Author:** ![ChargeHubDesign](https://avatars.discourse-cdn.com/v4/letter/c/85e7bf/32.png) [@ChargeHubDesign](https://community.hubspot.com/u/ChargeHubDesign)\ **Post date:** [December 22, 2023, 7:27pm UTC](https://community.hubspot.com/t/allow-fontawesome-version-6/82137/9 "2023-12-22T19:27:42Z")
Yes please. I’d really love to be able to organically use our Font Awesome 6 Pro subscription within Hubspot, particularly thru the “Icon” Module. Right now, we would either need to create an image for each icon we want to use (Regular family, Pro collection). Or, we have to use HTML tags in the source code to add & modify the icons. Truly a sub-optimal experience for my team, who is going to have primarily marketing resources take care of managing the web content. Without this feature update, or compatibility with Font Awesome 6 / Pro, it will require a dev or myself to help make adjustments to these icons, and we’ll be unable to see them in the RTF input window, only in the preview. Please add this SOON, we’re really in need of this functionality. ---
**Author:** ![atotheme](https://avatars.discourse-cdn.com/v4/letter/a/87869e/32.png) [@atotheme](https://community.hubspot.com/u/atotheme)\ **Post date:** [January 17, 2024, 1:45pm UTC](https://community.hubspot.com/t/allow-fontawesome-version-6/82137/10 "2024-01-17T13:45:24Z")
I was also directed here because the Twitter icon in the social module of Email is incorrect. When can we expect an update to X? ---
**Author:** ![jnix284](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jnix284/32/29_2.png) [@jnix284](https://community.hubspot.com/u/jnix284)\ **Post date:** [January 17, 2024, 2:23pm UTC](https://community.hubspot.com/t/allow-fontawesome-version-6/82137/11 "2024-01-17T14:23:17Z")
@atotheme The icon field now supports v6.4.2 which works for all new themes or custom themes (it doesn’t include backwards compatibility which limits the ability for existing marketplace themes to update easily). I checked the Social Module for Email and confirmed that it is NOT using Font Awesome, HubSpot has a static PNG loaded for these icons: ![Jnix284_0-1705501282401.png](https://d2qpr2jzcazej7.cloudfront.net/original/2X/9/9e88c07ba9d744d9738a67669a36f9851881a760.png) ![Jnix284_1-1705501361226.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/4/0/407d2138ee1838828a3cf76583c30e5018f763c0.png) If Support directed you here for email, you can provide the above screenshot showing that the Email icon does not come from Font Awesome and that the Email product team needs to update the icon PNG directly. ---
**Author:** ![EdCupaioli](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/edcupaioli/32/103251_2.png) [@EdCupaioli](https://community.hubspot.com/u/EdCupaioli)\ **Post date:** [May 15, 2024, 7:08pm UTC](https://community.hubspot.com/t/allow-fontawesome-version-6/82137/12 "2024-05-15T19:08:49Z")
@Jnix284 I’m wanting to use the [pseudo elements](https://docs.fontawesome.com/web/add-icons/pseudo-elements) feature in my CMS modules so I uploaded all css and font assets to my theme. I added the font files to my account file directory and referenced that path in the fontawesome CSS. To be specific, I modified the line in my all.min.css that referenced the font files: ../webfonts to the path of my fonts to the full path to my fontawesome files I have in my account library: [URL]/hubfs/[path to fontawesome fonts] I could just load the icons globally in the head of my site, but I would assume I can get some speed savings if I loaded icons only when the module using them is present. I could just upload all the font files to the module but that’s not really a sustainable solution. You can use their [kit](https://docs.fontawesome.com/web/setup/use-kit/)feature for the simplest possible implementation but they rate limit it to 10K views per month. ---
**Author:** ![atotheme](https://avatars.discourse-cdn.com/v4/letter/a/87869e/32.png) [@atotheme](https://community.hubspot.com/u/atotheme)\ **Post date:** [May 16, 2024, 7:11am UTC](https://community.hubspot.com/t/allow-fontawesome-version-6/82137/13 "2024-05-16T07:11:02Z")
@Jnix284 sorry, I missed your reply. Thanks for your help on this! ---
**Author:** ![krzysztofgoncia](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/krzysztofgoncia/32/78471_2.png) [@krzysztofgoncia](https://community.hubspot.com/u/krzysztofgoncia)\ **Post date:** [September 20, 2024, 9:10am UTC](https://community.hubspot.com/t/allow-fontawesome-version-6/82137/14 "2024-09-20T09:10:23Z")
Extremely disappointing, Twitter became X more than a year ago. ---
**Author:** ![JMulchrone7](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@JMulchrone7](https://community.hubspot.com/u/JMulchrone7)\ **Post date:** [September 23, 2024, 4:24pm UTC](https://community.hubspot.com/t/allow-fontawesome-version-6/82137/15 "2024-09-23T16:24:49Z")
Someone reach out to Elon and tell him hundreds of thousands of companies are still using the wrong logo for X. This is so bizzare that Hubspot is stopping companies using the correct branding for something ---
**Author:** ![cnnrbyrm](https://avatars.discourse-cdn.com/v4/letter/c/13edae/32.png) [@cnnrbyrm](https://community.hubspot.com/u/cnnrbyrm)\ **Post date:** [October 21, 2024, 9:40pm UTC](https://community.hubspot.com/t/allow-fontawesome-version-6/82137/16 "2024-10-21T21:40:59Z")
@hubspot when are you going to address this issue? My IT team has discovered a possible scenario where our token is exposed to the frontend, and have chalked it up to the use of the twitter link, as opposed to the updated x link. This is unacceptable.