We're not accepting new Brand icons

[mittalyashu]

Thank you for considering to add a new brand/company icon to Lucide. But, we're no longer accepting new brand icons.

To know more: feathericons/feather#763
We recommend using: https://github.com/simple-icons/simple-icons

We've an active issue for removal of existing brand icons, please do share your feedback.

[danielbayley]

@mittalyashu @ericfennis @karsa-mistmere @jguddas Would adding a Markdown icon violate this? (even if an abstraction)

[ericfennis]

@danielbayley markdown icon we should accept I think. Commonly used to indicate markdown fields for example.

[moeenio]

still a brand

[mittalyashu]

Kind of similar, if we start accepting library and framework logo's (React, Vue.js)

[karsa-mistmere]

@mittalyashu I don't think we should, React for one is objectively too detailed for our guidelines.

[epifaniofrancisco]

You should include a note on your website informing people that brands are no longer accepting new brand icons.

[ftzi]

While we very possible don't need further brand icons, should this library really deprecate all the existing brand icons?

This is the only issue I have with this library. I don't want to add another library just to handle 1 or 2 situations.

Every website will basically need the icon for Google, Instagram, X, and maybe Youtube, Linkedin, Whatsapp and Discord.

There are surely many icons which have way lesser usefullness than a Google icon, for example, which is on virtually all the login screens on the web nowadays.

[karsa-mistmere]

While we very possible don't need further brand icons, should this library really deprecate all the existing brand icons?

This is the only issue I have with this library. I don't want to add another library just to handle 1 or 2 situations.

Every website will basically need the icon for Google, Instagram, X, and maybe Youtube, Linkedin, Whatsapp and Discord.

There are surely many icons which have way lesser usefullness than a Google icon, for example, which is on virtually all the login screens on the web nowadays.

You need to realise that unfortunately this is completely beyond our control. These are not just icons we're talking about; they are brand logos protected by copyright, and we cannot legally alter and redistribute them. Even if we did, they could be flagged for removal at any time, just as it happened in simple-icons/simple-icons#11236

[justingolden21]

Agree with the other comment. This should be mentioned on the website, rather than having every single developer using social icons go to your site, search for "twitter x" and so on, search github issues, go through several links, and finally land on this issue mentioning you aren't taking new icons. I don't blame you for not doing it due to legal issues, but it's such a waste of my time and other developers' time.

[karsa-mistmere]

Agree with the other comment. This should be mentioned on the website, rather than having every single developer using social icons go to your site, search for "twitter x" and so on, search github issues, go through several links, and finally land on this issue mentioning you aren't taking new icons. I don't blame you for not doing it due to legal issues, but it's such a waste of my time and other developers' time.

Our top pinned issue is already "We're not accepting new brand icons".

Putting a large disclaimer on the site saying "no brand logos. period" is completely out of the question, we might as well add "no swastika icon, guys, sorry, but it's like super illegal".

We're already working on altering the icon list so that more information is included about icons, including deprecation notices for current brand icons, I think if anyone is still mistaken about this issue after that, it's very definitely no longer our fault.

[danielbayley]

we might as well add "no swastika icon, guys, sorry

Apparently, they're all the rage now… 🤦🏻‍♂️

[VIKTORVAV99]

Could this project not take the same stance as Microsoft has done with Cascadia Code Nerd Fonts and GitHub with Monaspace Nerd Fonts: https://github.com/githubnext/monaspace/releases/tag/v1.200

Basically include the logos in the package/font and if someone makes a fuss about it remove said icon at that time? Unless the icons are modified in such a way it no longer represents the brand I doubt many companies would care and might even be happy for the free advertising they get.

[epifaniofrancisco]

Agree with the other comment. This should be mentioned on the website, rather than having every single developer using social icons go to your site, search for "twitter x" and so on, search github issues, go through several links, and finally land on this issue mentioning you aren't taking new icons. I don't blame you for not doing it due to legal issues, but it's such a waste of my time and other developers' time.

Our top pinned issue is already "We're not accepting new brand icons".

Putting a large disclaimer on the site saying "no brand logos. period" is completely out of the question, we might as well add "no swastika icon, guys, sorry, but it's like super illegal".

We're already working on altering the icon list so that more information is included about icons, including deprecation notices for current brand icons, I think if anyone is still mistaken about this issue after that, it's very definitely no longer our fault.

The issue is that developers only realize an icon is deprecated after searching through GitHub issues or trying to use it in their projects. This creates unnecessary frustration and wasted time.

Why not add a clear warning on the website itself? As I proposed in PR #2618, a simple notice would proactively inform developers before they even attempt to use a deprecated icon.

[karsa-mistmere]

The issue is that developers only realize an icon is deprecated after searching through GitHub issues or trying to use it in their projects. This creates unnecessary frustration and wasted time.

Why not add a clear warning on the website itself? As I proposed in PR #2618, a simple notice would proactively inform developers before they even attempt to use a deprecated icon.

Deprecated icons are already marked as such by our packages. 🤷‍♂️

If you do not use our packages, the SVG code you copy being deprecated should not make any difference.

But again, we will add information about deprecated icons to the website, just not in the way it's proposed in #2618 and very definitely also not in the form of placing an ugly banner on the icons page as someone above suggested.