lucky.graphics

resources

Free Icons for Commercial Use: License and Selection Guide

Free icons for client work, checked against each set's LICENSE file: MIT, ISC and Apache 2.0 sets, Font Awesome Free's CC BY icons, and Simple Icons' per-logo licenses counted.

Published
October 2, 2026
Updated
October 28, 2026
Topic
resources
Reading time
20 min
Review
Reviewed against the primary source

Free Icons for Commercial Use: License and Selection Guide

Yes, you can use free icons commercially when the set's own license says so, and the open-source sets below (Lucide, Heroicons, Tabler, Phosphor, Feather, Iconoir, Bootstrap Icons and Material Symbols) all allow commercial use without a visible credit, as we read their license files, provided the license text travels with the files. Brand-logo collections and "free" tiers on download sites are where that answer changes.

Icons feel too small to carry legal weight. They do. An icon set is software and artwork at the same time, and the license decides whether you can use it in client work, bundle it into an app, or hand it to another designer as part of a template.

This guide covers the part most roundups skip. It compares free icon sets against the license files in their own repositories, read on October 28, 2026, explains what MIT, ISC, Apache 2.0, CC0, and CC-BY actually allow in practice, and gives you a selection framework and a checklist to run before anything ships.

Note: this is practical guidance for working designers, not legal advice. If a project has a legal review, bring the actual license texts to it.

Free Icon Licenses in One Pass

If you need icons for commercial client work today, start with one of these verified open-source sets and confirm the license on the project page before you commit:

  • Lucide - ISC license, with the icons it inherited from Feather still under Feather's MIT license (its LICENSE file lists them). Outline style, drawn on a 24-pixel grid. Good default for product interfaces.
  • Heroicons - MIT license, from the Tailwind Labs team. Outline and solid styles at 24px, plus solid sets at 20px and 16px.
  • Tabler Icons - MIT license. Large outline set with filled variants.
  • Phosphor Icons - MIT license. Multiple weights from thin to bold, plus fill and duotone.
  • Feather Icons - MIT license. Small, clean outline set. Lucide describes itself as a fork of Feather, so expect overlap in style.
  • Iconoir - MIT license. Clean outline set with a slightly softer feel.
  • Bootstrap Icons - MIT license. Solid fit if the project already uses Bootstrap.
  • Material Symbols - Apache License 2.0, from Google. Variable-font icons with weight, fill, grade and optical-size axes.
  • Simple Icons - the project is released under CC0, but its own disclaimer says that does not make every icon CC0. Brand and logo marks only; check each icon's license entry, and trademark rules apply to the logos themselves.

Under MIT, ISC, Apache 2.0, and CC0, commercial use is allowed and, as we read those texts, no visible credit is required in the finished design. You still keep the license notice in the project files. The traps are elsewhere: attribution-based licenses such as Font Awesome Free's icon license, per-icon licenses inside brand collections and aggregator sites, and redistribution rules when icons travel inside templates, UI kits, or apps. The rest of this guide walks through each one. This is general information about how these licenses read, not legal advice.

Why "Free" Icons Still Have Licenses

Five misunderstandings cause most icon problems.

1. Free to download is not free to use commercially. Some sites offer a free tier that covers personal projects only, and a paid tier for client work. The download button rarely says which tier you just took. Read the license page, not the button.

2. One site can host five different licenses. Aggregator sites collect icons from many authors. Two icons side by side in search results can carry different terms, including per-icon attribution requirements. A site-wide assumption is not a license.

3. The license covers the file, not the trademark. Even where a logo file is offered under an open license, the logo is still a trademark you cannot use to imply endorsement. License and trademark are separate questions, and both need an answer.

4. Using an icon and redistributing an icon are different acts. Most open licenses allow both, with the notice kept. Some free tiers allow use in a finished design but forbid packaging the raw SVG files into a template, UI kit, or asset bundle you give away or sell.

5. Sets change hands and change terms. Projects get renamed, move repositories, or update licenses. Keep a dated copy of the license text with your project files so the terms that applied when you downloaded the set are documented.

The Five License Patterns You Will Actually Meet

You do not need to read every open-source license ever written. Five patterns cover nearly every free icon set a designer will touch.

MIT License

The most common license in this space. Heroicons, Tabler Icons, Phosphor Icons, Feather Icons, Iconoir, and Bootstrap Icons all use it.

What it means in practice:

  • Use the icons commercially and privately, in client work, products, and print.
  • Modify them and redistribute them, including inside paid products.
  • The copyright notice and license text must stay with the copy of the files. In practice, that means the LICENSE file travels with the icon folder in your repo or handoff packet. No credit is required in the visible design.

ISC License

Lucide uses the ISC license for its own icons. Its LICENSE file then lists the icons derived from the Feather project, by name, under Feather's MIT license, so a Lucide folder carries both notices. ISC is a short permissive license that works like MIT for a designer's purposes: commercial use, modification, and redistribution are allowed, and the copyright and permission notice must travel with the copy. No visible attribution is required in the interface.

Apache License 2.0

Material Symbols uses Apache 2.0. It permits commercial use, modification, and distribution, and it adds an explicit patent grant that MIT and ISC do not spell out. Keep the license and any NOTICE file with the copy. No visible credit is required in the design.

CC0 1.0

CC0 is a public-domain dedication: the person applying it waives the copyright they hold. The CC0 text itself says "No trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document." That limit matters most for logo collections. Simple Icons applies CC0 to the project, and its disclaimer adds that this "doesn't mean to imply that all icons within the project are also CC0". CC0 waives only the rights of the person applying it, and the logos in the collection belong to the brands. The section on Simple Icons' own data below shows what that means in numbers. CC0 answers a copyright question only for what the person applying it owns. It does not give you permission to suggest a company endorses your product.

CC-BY and attribution-required free tiers

Creative Commons Attribution (CC-BY) allows commercial use, but you must credit the creator in the way the license asks. Some stock and icon sites run free tiers on this pattern: the icons are free if a credit line or link appears wherever they are used. That condition is easy to accept in a first mockup and painful later in an app, a packaging run, or a client site where the credit was never placed. If a set requires attribution, record exactly where the credit must go before you design around it, and confirm the client accepts it.

The practical order of preference for client work is simple: MIT, ISC, Apache 2.0, or CC0 sets first, because nothing needs to appear in the finished design. CC-BY sets are usable, but only when the attribution is planned and documented from the start.

Verified Sets Compared

The table below is the original asset for this guide. Every license entry was checked against the set's own project or repository page. Style notes describe how the set is drawn, which is the part you cannot learn from a license. Pick by style and license together, then verify the license once more on the project page before the project ships, because terms can change.

SetLicenseStyleBest fitWatch out for
LucideISC, plus MIT for Feather-derived iconsOutline, 24px grid, rounded capsProduct UI, SaaS dashboards, web appsOutline only; very small sizes can thin out
HeroiconsMITOutline and solidTailwind projects, marketing plus product in one systemSmaller catalog; three sizes (24, 20, 16) to manage
Tabler IconsMITOutline with filled variantsLarge products that need wide concept coverageConsistency check when mixing filled and outline
Phosphor IconsMITThin to bold weights, fill, duotoneOne set across marketing and product, emphasis statesWeight choice must be fixed early or the set drifts
Feather IconsMITMinimal outlineLightweight sites, small icon needsSmall catalog; Lucide covers more concepts
IconoirMITOutline, softer geometryEditorial and lifestyle products that want a friendlier lineCheck coverage for technical concepts
Bootstrap IconsMITMixed outline and filled glyphsBootstrap-based builds, quick product workVisual tie to the Bootstrap ecosystem
Material SymbolsApache 2.0Variable font: weight, fill, optical sizeAndroid-adjacent products, Google-ecosystem designReads as a Google product if the brand should not
Simple IconsCC0 for the project; per-icon license entries where knownBrand and logo marksFooter social links, integration pagesCheck each icon's license entry and the brand's own guidelines

Three reading notes for the table. First, license sameness is not style sameness: sitting two outline sets together in one interface usually shows, because stroke weight, corner radius, and grid differ. Second, the filled or solid variant of a set is for emphasis states and small sizes, not a second style to mix freely. Third, Simple Icons belongs in a different mental category from the rest: it solves "I need the mark of a service we integrate with," not "I need interface glyphs," and the license question is asked per logo, not per set.

Catalogue Size, Counted

Roundups describe sets as "large" or "small" without numbers. We counted the SVG files in each repository's main icon folder on October 28, 2026, at the commit noted in the sources. Counts are for one style, because Heroicons and Phosphor ship each icon in several styles, and Tabler adds filled versions of part of its set.

SetFolder countedSVG files
Tabler Iconsicons/outline (plus 1,054 in icons/filled)5,203
Simple Iconsicons3,467
Bootstrap Iconsicons (670 of them are -fill variants)2,078
Font Awesome Freesvgs/solid (plus 273 regular and 609 brands)2,001
Lucideicons1,999
Phosphor Iconsassets/regular (one of six weights)1,512
Iconoiricons/regular1,383
Heroiconsoptimized/24/outline324
Feather Iconsicons287

Two cautions keep the numbers honest. A count is not coverage: 324 well-chosen Heroicons may cover a marketing site better than 5,000 icons cover a niche dashboard, so search each candidate set for your ten hardest concepts before deciding. And counts change with every release, which is why the commit is recorded. Material Symbols is missing from the table because its repository is too large for a single listing, and we did not count it another way.

How Royalty-Free Icon Libraries Handle Free Tiers and Pricing

Royalty-free icon libraries handle free tiers and pricing in one of two ways: open-source sets have no paid tier for the license at all, while freemium marketplaces give icons away on condition of a credit and sell a subscription that removes the credit and the download limits. Royalty-free means you do not pay per use; it does not mean the free tier carries the same rights as the paid one.

Open-source sets: one license, no tier. Lucide, Heroicons, Tabler Icons, Feather and the other MIT, ISC, Apache 2.0 or CC0 sets in the table above grant the full commercial license to everyone. Nothing about the license changes if you pay or donate, so the free download is the complete product.

Freemium marketplaces: credit or subscription. Flaticon's terms are a clear example of the pattern (read November 16, 2026). Its standard Flaticon License (section 8.1) lets you use and modify content only by crediting the website and the creator, and section 4.2 puts free downloads under a daily download limit. Section 9 says a Premium subscription lets you use the content without the credit, lifts the download count limit, and gives access to all content. Section 9 also keeps the prohibited uses in sections 7 and 8, so paying does not unlock everything: content as the main element of items for resale, such as t-shirts, cups and postcards, needs a separate per-item Merchandising License under section 8.2. Subscriptions renew automatically unless cancelled.

Open-core sets: a free set beside a paid set. Font Awesome ships Font Awesome Free under the three licenses described below, and its plans page lists paid Pro and Pro+ plans as upgrades from the Free plan (checked November 16, 2026). The Free files keep their own license whatever you buy, so check which package an icon in your project actually came from.

The practical test is the same in every case: before a client project, write down which tier each icon came from, whether that tier needs a visible credit, and what happens to icons already shipped if the subscription lapses. Flaticon's section 8.1 ties attribution-free use to content downloaded during the subscription term, which is the clause to read before cancelling. Sources: Flaticon terms of use, sections 4.2, 8.1, 8.2 and 9, and the Font Awesome plans page, both checked November 16, 2026.

Picking by Use Case

License first, then fit. Work through the scenario that matches your project.

SaaS dashboard or web app

Choose Lucide, Tabler Icons, or Phosphor Icons. You need wide concept coverage (arrows, files, charts, users, settings, status) and a stroke system that stays readable at 16 to 20 pixels. Fix one stroke weight and one size scale before screens multiply. Our icon design principles guide covers the grid, keyshape, and optical-sizing rules behind this choice.

Marketing site plus product

Choose a set with both outline and solid or fill variants, such as Heroicons or Phosphor Icons. Marketing pages want larger, friendlier glyphs; product screens want quiet ones. One family with two variants keeps the brand coherent without mixing libraries.

Mobile app

Choose Phosphor Icons for its weight range, or Lucide if the app is outline-led and web-shared. Test at the smallest shipped size on a real device. Thin strokes that look elegant in a design tool can disappear on a mid-range phone screen.

Ecommerce

Choose Tabler Icons or Lucide for cart, shipping, payment, and account concepts, then check gaps before you start. Trust and payment marks are a separate question: card and wallet logos are trademarks, usually supplied through the payment provider's brand resources, not through an icon set.

Brand and social marks

Use Simple Icons to find the file, check that icon's license entry and the brand guidelines link where the data file has one, then apply trademark common sense: use a company's mark to say "find us there" or "we integrate with this," never to imply partnership or endorsement that does not exist. When a platform publishes its own brand guidelines, those guidelines govern size, clear space, and color. Emoji raise a similar split: the character is free to type, but each vendor's drawing carries its own terms, and our comparison of emoji licenses by set shows which ones allow print, merch and app use.

SVG, Icon Font, or Component Package

The license allows the use; the format decides how painful the next two years are.

Inline SVG is the default recommendation for web work. Icons inherit text color through currentColor, scale cleanly, and can be labelled for assistive technology. Decorative icons get aria-hidden. Meaningful icons get a visible label or an accessible name. Ship only the icons the project uses, not the whole set.

Component packages (for example, the React or Vue packages several sets publish) give you the same SVG output with typed props for size and stroke. They are the practical choice inside a component codebase, and tree-shaking keeps unused icons out of the bundle.

Icon fonts are the legacy option. They are easy to drop in and hard to control: alignment drifts, screen readers may announce stray characters, and a failed font load can show boxes where actions should be. Choose SVG unless a platform constraint forces the font. Note that the format can change the license, too: Font Awesome Free puts its icon fonts under the SIL Open Font License and its SVG and JS icons under CC BY 4.0, as the next section explains.

Font Awesome Free: Three Licenses in One Download

Font Awesome's free edition is the clearest example we found of why "what license is this set under?" can have more than one answer. Its LICENSE file, read at the repository's 7.x branch, splits the download three ways:

  • Icons: "licensed under a Creative Commons Attribution 4.0 International License and applies to all icons packaged as SVG and JS file types."
  • Fonts: "the SIL OFL license applies to all icons packaged as web and desktop font files", with "Font Awesome" declared as a Reserved Font Name.
  • Code: "the MIT license applies to all non-font and non-icon files."

All three licenses ask for attribution in some form, and the file says so plainly: "Attribution is required by MIT, SIL OFL, and CC BY licenses." It then explains how Font Awesome expects that to be met: "Downloaded Font Awesome Free files already contain embedded comments with sufficient attribution, so you shouldn't need to do anything additional when using these files normally." It asks users not to "actively work to remove them from files".

That sentence is the practical test for a designer. Each SVG in the download opens with a comment that starts with an exclamation mark, for example "Font Awesome Free 7.3.1 by @fontawesome" followed by the license link and "(Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License)". That leading exclamation mark is the "legal comment" convention, and SVGO's removeComments plugin keeps such comments by default. If you ship the files as downloaded, or optimize them with SVGO's defaults, the credit survives. If you redraw the icons into components, paste only the path data into a design file, or configure a tool to strip every comment, the attribution the license relies on goes with it, and you should restore it or add a credit where your project lists third-party licenses. The SVG optimization guide covers the plugin settings. The brand icons in the same download carry a separate warning: they "are trademarks of their respective owners", and the file asks that brand logos not be used "for any purpose except to represent the company, product, or service to which they refer."

What Simple Icons' Own Data Says About Logo Licenses

Simple Icons collects clean SVGs of company logos, 3,467 of them in its data file, and an earlier version of this guide summarised it as "CC0". The project's DISCLAIMER file is more careful: "Simple Icons is released under CC0 - though that doesn't mean to imply that all icons within the project are also CC0. Please see individual licenses where available." It also says that "the absence of license data for a particular icon does not imply that the icon is not released under a license", and that the project "cannot be held responsible for any legal activity raised by a brand".

The license data lives in the project's data file, one entry per icon. We counted it at the commit noted below. Our Simple Icons profile records the license, the count, and the per-icon findings for quick reference.

Simple Icons: how many icons carry their own license entryOf 3,467 icons in the Simple Icons data file, 3,243 (93.5 percent) have no license entry and 224 (6.5 percent) have one. Among those 224, Apache 2.0 is most common (49), then Creative Commons BY-SA (44), MIT (29), Creative Commons BY (24) and custom owner terms (23); 11 are non-commercial Creative Commons licenses and 12 are CC0.All 3,467 icons in the data fileNo license entry: 3,243 (93.5%)License entry: 224 (6.5%)The 224 icons with a license entry, by licenseApache 2.049Creative Commons BY-SA44MIT29Creative Commons BY24Custom (link to owner terms)23GPL or AGPL17CC012Non-commercial Creative Commons (NC)11MPL 2.07BSD 3-Clause5Creative Commons BY-ND (no derivatives)2Unlicense1
Simple Icons: how many icons carry their own license entryCounted from the license field of each icon entry in data/simple-icons.json. Creative Commons versions are grouped (for example BY-SA 2.0, 2.5, 3.0 and 4.0); orange bars mark licenses that bar commercial use or derivatives. The project says the absence of license data does not mean an icon is unlicensed.Source: simple-icons/simple-icons repository, commit 90646e4b, data file and DISCLAIMER.md, checked October 28, 2026.
Show the data as a table
License in the icon entryIcons
No license entry3,243
Apache 2.049
Creative Commons BY-SA44
MIT29
Creative Commons BY24
Custom (link to owner terms)23
GPL or AGPL17
CC012
Non-commercial Creative Commons (NC)11
MPL 2.07
BSD 3-Clause5
Creative Commons BY-ND (no derivatives)2
Unlicense1

Three findings change how to use the set. First, 3,243 of 3,467 entries (93.5 percent) carry no license entry at all, which, by the project's own wording, tells you nothing either way about the icon's terms. Second, the 224 entries that do carry one are mostly not CC0: only 12 are, while 49 are Apache 2.0, 44 are a version of CC BY-SA and 29 are MIT, each with its own notice duty. Third, 11 icons carry a non-commercial Creative Commons license (BY-NC, BY-NC-SA or BY-NC-ND), and 23 point to a custom page of the owner's terms; a commercial project should read those before use. 839 entries (24.2 percent) also link to the brand's own guidelines, which govern size, color and clear space.

For uses such as a footer link to a social profile or a "works with" list on an integrations page, the brand's own guidelines are the governing document where the brand publishes them. Simple Icons is a convenient index of those marks, not a license to them.

Whatever the format, normalize before you ship: one viewBox convention, no fixed width and height baked into reusable components, stroke and fill set in one place, and a naming scheme the next designer can guess. A set you cannot search is a set you will duplicate.

The Redistribution Traps

Most icon trouble happens after the design is done, when files travel.

Templates and UI kits. If you sell or give away a template, theme, or UI kit that contains icon files, you are redistributing. MIT, ISC, and Apache 2.0 allow it with the license notice included. Attribution-required free tiers often forbid it or require credit from every end user, which you cannot deliver on their behalf. This is the single most common reason to reject a free tier.

Client handoff. Under MIT, ISC, and Apache 2.0, hand the client the icons with the LICENSE file included and note the set name and source in the handoff document. The client does not need their own license for these sets. That simplicity is a real reason to prefer them over commercial icon subscriptions, where the client's right to keep using the icons can depend on an account staying active.

App bundling. Embedding icons in an app is distribution of the files inside a binary. The permissive licenses above allow it; keep the license text in the app's open-source notices screen or credits file, which is where reviewers look for it.

Modified icons. Permissive licenses allow editing: recoloring, redrawing a detail, or merging concepts. Keep the original license with modified copies. If you redraw an icon so heavily that it becomes your own work, it is still cleaner to record where it started.

A Worked Example: Auditing Icons for a Client Dashboard

The following is a hypothetical example, written to show the audit order. No real client or numbers are involved.

A small team is building a client dashboard and has pulled icons from three places during design: Lucide for the main navigation, a handful of Feather icons in early screens, and two brand marks from Simple Icons for an integrations page.

The audit takes about twenty minutes:

  1. Lucide (ISC). Verdict: keep. Commercial use and app bundling are allowed; include the license text in the repo and the app's notices file. No visible credit needed.
  2. Feather (MIT). Verdict: replace with Lucide equivalents. Not a license problem; a consistency problem, plus a maintenance one, because two outline systems drift apart as screens are added. Feather stays a fine choice for a new lightweight project; it does not need to share this one.
  3. Simple Icons (project CC0; per-icon entries checked). Verdict: keep the files after checking each icon's license entry, and fix the usage. One mark sits next to text implying an official partnership that does not exist. The copy is rewritten to describe the integration plainly, and the mark gets the clear space the brand's own guidelines ask for.

End state: one interface set, one license family pattern, brand marks used descriptively. The audit output is a one-page note in the project folder: set names, source pages, license names, and where each license text is stored. That note is what the next designer, or a client's reviewer, actually needs.

Icon Audit Before Release

Run this before any deliverable that contains icons. It pairs with the broader design asset licensing checklist, which covers fonts, mockups, photos, and AI images in the same pass.

  • One primary set: the interface uses one icon family, with any second set documented and justified.
  • License named: every set in the project has a named license (MIT, ISC, Apache 2.0, CC0, or a recorded attribution-based license such as CC BY), and every brand logo has its own entry.
  • Source saved: the official project or repository page for each set is recorded in the project files.
  • License text archived: a dated copy of each license is stored with the project, not just linked.
  • Attribution placed: if any set requires credit, the credit is in place everywhere the icons ship, and the client has accepted it.
  • Redistribution checked: templates, UI kits, and app bundles include the license notices and do not rely on a personal-use tier.
  • Brand marks reviewed: logo icons are used descriptively, with no implied endorsement, and follow the owner's brand guidelines where they exist.
  • Accessibility pass: decorative icons are hidden from assistive technology; meaningful icons have labels; color is never the only signal. See the accessible color systems guide for the pairing rules.
  • Format normalized: one viewBox, currentColor styling, consistent naming, unused icons removed.
  • Contrast checked: icon and label combinations meet the project's contrast target; verify with the contrast checker.

Choosing a Set: A Five-Step Filter

For an icon set you are about to adopt, answer in order. Stop at the first "no" and pick a different set.

  1. Can you name the license? If the site does not say, the set is not cleared for client work.
  2. Does it allow commercial use without visible credit? MIT, ISC, Apache 2.0, and CC0: yes, with the notice kept in the files. CC BY or an attribution free tier: only if the credit is planned, or, for Font Awesome Free, the embedded comments are kept. Personal use or NC: no.
  3. Does it cover how the files will travel? Templates, UI kits, and app bundles need redistribution rights, not just use rights.
  4. Is it one coherent system? One grid, one stroke logic, outline or filled held consistently. If you need two sets to cover the concepts, document why.
  5. Did it come from the source? The set's own site or repository, not a re-upload bundle with a friendly filename.

FAQ

Can I use MIT-licensed icons in a paid client project?

Yes. The MIT license allows commercial use, modification, and redistribution, including inside paid products. Keep the copyright notice and license text with the icon files in your repo or handoff packet. No credit is required in the visible design.

Do I need to credit Lucide, Heroicons, or Tabler in my app or website?

No visible credit is required. Lucide (ISC), Heroicons (MIT), and Tabler Icons (MIT) ask only that the license notice travel with copies of the files. Keeping the LICENSE file in your project and, for apps, in the open-source notices is the standard way to meet that.

Can I include free icons in a template or UI kit I sell?

With MIT, ISC, or Apache 2.0 sets, yes, as long as the license notice is included. With attribution-required free tiers, usually no: the credit condition would fall on every buyer, which the tier rarely permits. This is the most common reason designers replace a free tier before selling a template.

Are brand logos from Simple Icons free to use however I want?

Not automatically. The project is CC0, but its disclaimer says that does not make every icon CC0, and in its data file 3,243 of 3,467 icons have no license entry while 11 carry non-commercial licenses. Check the icon's own entry. The logos are also trademarks. Use them to refer to the company (a social link, an integration listing), follow the company's brand guidelines, and never present the mark in a way that implies endorsement or partnership that does not exist.

Can I modify an open-source icon or change its stroke and color?

Yes. MIT, ISC, and Apache 2.0 all allow modification. Keep the original license with modified copies, and keep edits consistent across the set: one changed stroke weight in three icons out of forty will read as a mistake, not a customization.

What is wrong with downloading icons from a big aggregator site?

Nothing, if you check each icon's own license. Aggregators mix authors and terms on one results page, so one icon may be MIT and the next may require attribution or forbid commercial use. The set-based sources in this guide are easier to audit because one license covers the whole system.

Icon font or SVG: which should I ship?

SVG, in almost every current project. It styles with currentColor, scales cleanly, supports accessible labelling, and lets you ship only the icons you use. Icon fonts remain acceptable where a platform constraint requires them, but they are harder to align, label, and debug.

What to Read Next

Several sets in this guide use Creative Commons terms. For what BY, SA, NC and ND mean clause by clause, and how to write an attribution line that satisfies them, read Creative Commons licenses explained for designers.

This guide is maintained by the Lucky Graphics editorial team and reviewed when the sets above change their terms. It is general information about how icon licenses work, not legal advice for a specific project.

Sources, read on October 28, 2026, at the commits noted: the LICENSE files of Lucide (be09619c), Heroicons (616b7a4d), Tabler Icons (ed177a08), Phosphor (2b75f3ad), Feather (3dc050d9), Iconoir (285be69c), Bootstrap Icons (e5684654), Material Symbols and its README (10ecc147), and Font Awesome Free (14c65a37); for Simple Icons (90646e4b), the LICENSE, DISCLAIMER and data file. Icon counts come from each repository's file tree at the same commits.