Free Icons for Commercial Use: Every License, Explained in Plain English
Heroicons, Lucide, Font Awesome, Material Symbols — which "free" icons are actually safe to ship in commercial products, what attribution really requires, and the five traps hiding in icon licensing.
Icora Team
Product Research
Short answer first: yes, the major open-source icon libraries are genuinely free for commercial work. Heroicons in a paid SaaS product, Lucide in a client project, Material Symbols in an app you sell — all fine, no payment, no permission email. The risk in icon licensing is almost never the famous libraries. It is the long tail of "free icon" download sites where the terms are unclear, buried, restrictive, or quietly different from what the download button implied.
This guide teaches you to read an icon license in thirty seconds: what each common license actually requires, and the five traps that generate real problems for real teams.
The License Cheat Sheet
| Library | License | Commercial Use | Visible Credit Required |
|---|---|---|---|
| Heroicons, Feather, Tabler, Phosphor, Bootstrap Icons | MIT | Yes | No — keep the license text in your source |
| Lucide | ISC (MIT-equivalent) | Yes | No — keep the license text in your source |
| Material Symbols, Remix Icon | Apache 2.0 | Yes | No — keep license and NOTICE files |
| Font Awesome Free | CC BY 4.0 (icons) + OFL (fonts) + MIT (code) | Yes | Yes — CC BY requires attribution |
| CC0 / public domain sets | CC0 1.0 | Yes | No |
Always confirm against the library's own license file before shipping — licenses do occasionally change between versions. Here is what each family of licenses means in practice.
MIT and ISC: keep the notice, do anything
MIT and ISC ask one thing: preserve the copyright notice and license text when you redistribute the software. If you install the icons through npm, the license file riding along in node_modules and your bundled attributions already satisfy this. There is no obligation to put "icons by Heroicons" in your footer — ever. Use them in client work, paid products, printed material, whatever.
Apache 2.0: MIT plus paperwork
Apache 2.0 behaves like MIT for practical icon use, with two additions: an explicit patent grant (good for you) and the requirement to preserve NOTICE files if the project ships one. Material Symbols under Apache 2.0 is why you can embed Google's entire icon set in a commercial app without a second thought.
CC BY 4.0: free, but credit is not optional
Creative Commons Attribution is a genuinely commercial-friendly license with one real obligation: visible attribution. You must credit the source, link the license, and indicate if you made changes. An about page, credits screen, or documentation page all work. This is Font Awesome Free's model for its icons — if footer or credits-page attribution is unacceptable in your project (some client brands forbid it), either buy the Pro license or pick an MIT library instead.
The Five Traps
- "Free for personal use." This phrase means *not free for commercial use*. It is the most common gotcha on font and icon download sites, and using such assets in client work is a straightforward license violation.
- Attribution you cannot deliver. CC BY credit must survive into the final product. If the client's design forbids a credits line, the license is not satisfiable — resolve it before shipping, not after the invoice.
- Brand logos are trademarks. The X, Meta, or Apple glyph inside an icon set is governed by each company's brand guidelines, not by the set's MIT license. The license covers the drawing; the trademark covers the use. Follow the platform's official brand rules.
- No redistribution or resale. Nearly every free license lets you ship icons *inside* a product, but not repackage and sell the icons themselves as a set. "Free" is not "yours to resell."
- License drift. Download sites change terms, and sets that were free in one version go freemium in the next. Save a copy of the license text with a date alongside the assets — it is your evidence of the terms you accepted.
Pro Tip
Keep a LICENSES.md in every project listing each third-party icon set, its license, its source URL, and where it is used. It takes five minutes, and it turns every future "are we allowed to use this?" conversation into a lookup.
Client Work: Who Holds the License?
Freelancers and agencies inherit an extra duty: the license travels with the product, not with you. Document which sets you used and hand that documentation over at delivery. If a set requires attribution, the *client's* site must carry it — and keep carrying it through their future redesigns, which is exactly the kind of requirement that gets silently dropped and discovered later. MIT-licensed libraries make this whole category of problem disappear, which is one reason developers default to them.
What About AI-Generated Icons?
An honest answer, because this area is genuinely unsettled: the US Copyright Office has taken the position that purely machine-generated images, with no meaningful human authorship, are not copyrightable — while human selection, arrangement, and substantial editing of AI output can be. Practically, that means heavily edited generations are on firmer ground than raw output, and keeping your prompts and edit history is cheap insurance.
Platform terms matter just as much as copyright law. Check what the tool you use actually grants: on Icora, marketplace purchases come with a non-exclusive usage license, and every pack sets its own remix policy — the marketplace guide spells out how buying, selling, and remixing interact.
When Buying (or Making) Beats Free
Free libraries are excellent and generic by design — the same Lucide arrows appear in thousands of products. When you need a distinctive style or coverage of a niche the big sets ignore, paid packs are cheap compared to designer time; browse the Icora marketplace to see what specialist creators produce. And if you are on the other side of that trade, our guide to selling icon packs online covers the economics honestly. The third option is making your own set — which used to be the expensive route, and increasingly is not.
The cleanest license is the one on icons made for you: generate a set matched to your brand at icora.io/create, refine it in the Studio, and ship it with no attribution lines and no license archaeology.
Try Icora FreeFrequently Asked Questions
Can I use free icons in a commercial app?
Yes, if the license permits it. MIT, ISC, Apache 2.0, and CC BY all allow commercial use — CC BY additionally requires visible credit. Anything labeled "free for personal use" does not allow it.
Do I have to credit icon libraries?
For MIT, ISC, and Apache 2.0 libraries, no visible credit is required — keeping the license text in your source or dependencies is enough. For CC BY sets like Font Awesome Free, yes: name the source, link the license, and indicate changes.
Can I sell a product that uses free icons?
Almost always yes — shipping icons inside your app, site, or template is exactly what MIT-style licenses permit. What you generally cannot do is repackage the icons themselves and sell them as a standalone set.
Can I modify free icons?
MIT, ISC, Apache 2.0, and CC BY all permit modification. CC BY requires you to indicate that changes were made. Brand and social-media logos are the exception: trademark guidelines usually prohibit altering them regardless of the file license.
Who owns AI-generated icons?
It is legally unsettled and varies by jurisdiction. The US Copyright Office has said purely machine-generated art is not copyrightable, while meaningful human editing and arrangement can be. Check your generation platform's terms for the usage rights it grants, and keep your prompts and edit history.
Found this helpful? Share it!
Ready to Create Stunning Icons?
Put these principles into practice with Icora's AI-powered icon generator, professional studio tools, and developer-ready export.
Start Creating Free