icones.js.org

Icônes (icones.js.org) is an aggregator: it does not draw its own icons but indexes many open-source icon libraries behind one search box. The sets it carries differ in style, size, and license, so the practical question is not "what is the full list" but "which set fits my project." The site's own catalog is the authoritative source — open icones.js.org and browse the collection list, since sets are added and updated over time.

What "available on Icônes" means

Icônes hosts no icon files of its own. Each set is pulled from an upstream open-source project, and the site provides:

• A unified search across all indexed sets
• Per-set browsing so you can see a library's full range
• License information attached to each set
• Copy-ready output (SVG, and framework-specific formats such as JSX/Vue components)

Because the underlying libraries are third-party, the license shown on Icônes is the license of the original project, not of Icônes itself.

How the sets differ

When choosing, compare sets on four dimensions rather than on looks alone.

Style and consistency

Most indexed libraries are single-style by design. If your interface already uses one visual language, pick a set that matches it and stay within that set for a given context. Mixing sets is possible but usually requires manual adjustment of stroke weight and padding.

Coverage

Large general-purpose sets cover common UI actions (search, settings, user, arrow). Niche needs — brand logos, file types, specialized domain symbols — are often covered by dedicated sets rather than general ones. Search your actual required icons on Icônes first; a set that looks good but misses three of your glyphs will force a mix anyway.

License

This is the constraint that most often decides the choice. Licenses commonly seen across open-source icon projects include MIT and Apache-2.0 (permissive, generally require keeping the license notice) and CC-BY variants (require attribution). Some sets add their own terms. Read the license shown for the specific set on Icônes before shipping, especially for commercial products — the aggregator displays it, but the obligation comes from the upstream project.

A practical selection workflow

1. List your required icons. Write down the specific glyphs your project needs before browsing.
2. Search each term on icones.js.org. Note which sets return all of them.
3. Filter by style. Keep only sets matching your UI's outline/filled convention.
4. Check the license on the set's page against your distribution and commercial context.
5. Export a sample in your target format and verify alignment at your actual size.
6. Commit to one set where possible; document any second set you add and why.

Common pitfalls

• Choosing by first impression. A set that looks clean in the browser can misalign at small sizes or in dense toolbars.
• Ignoring the license until launch. Attribution or copyleft terms are cheapest to satisfy at the start.
• Assuming the list is fixed. Icônes reflects upstream projects; a set can gain icons or change license over time, so re-check if you depend on it long-term.
• Treating Icônes as the source of truth for licensing. It surfaces the license; the upstream repository is where the binding terms live.

If you need a single answer: browse the collection list on icones.js.org, shortlist by style and coverage for your specific icons, then let the license decide among the finalists.

Icons on Icônes are free to use only to the extent that the license of each individual icon set allows. Icônes (icones.js.org) is an aggregator: it does not own the icons and does not apply a single license to everything on the site. Each icon set keeps its own license, so the answer for any given icon depends on which set it comes from. Before using an icon in a project — especially a commercial one — check the license of that specific set and follow its terms, including any attribution requirement.

Why there is no single license for Icônes

Icônes collects and displays icons from many independent open-source icon sets. The site provides the browsing and search layer; the copyright and licensing stay with the original authors and projects.

That means:

• There is no "Icônes license" that covers all icons.
• Two icons that look similar on the site can carry different terms if they come from different sets.
• The license belongs to the icon set, not to the individual file you happen to download.

What licenses typically apply

Because the sets are independent open-source projects, the licenses vary from set to set. Common open-source licenses used by icon projects include permissive ones (such as MIT) and licenses that require attribution (such as CC BY). Some sets may also be released under copyleft or other terms.

The practical consequence is the same in every case: the specific set's license is the one that governs your use. Do not assume a permissive license just because the icon is easy to download.

How to check the license before you use an icon

1. Identify the icon set the icon belongs to. On Icônes, icons are grouped by set, so the set name is the key piece of information.
2. Find that set's license. Open the set's own repository or homepage (linked from the project) and read its license file or license statement.
3. Confirm the terms match your use. Check whether commercial use is allowed, whether attribution is required, and whether there are restrictions on modification or redistribution.
4. Comply with the terms. If attribution is required, include the credit in the form the license specifies. If the license is unclear, treat it as restricted until you can verify.

Quick reference

Common pitfalls

• Assuming the site grants the license. Icônes is a viewer/aggregator; the rights come from the icon set.
• Mixing sets in one project. If you combine icons from several sets, you may need to satisfy several licenses at once.
• Skipping attribution. Attribution requirements are easy to miss and are a frequent source of license violations.
• Treating "open source" as "no rules." Open-source licenses still carry conditions; permissive and attribution licenses differ in what they ask of you.

If you need a definitive answer for a specific icon, go to the source: open the icon set's repository, read its license, and use the icon only within those terms.

Icônes is a browser-based icon explorer that lets you search across many open-source icon sets at once, preview any icon, and copy it out in the format your project needs. To use it, open icones.js.org, type a keyword into the search field, optionally narrow the results to one icon set, then copy the icon's name, its raw SVG, or a ready-made code snippet for your framework. No account or install is required to browse and copy — everything happens in the page.

Searching by keyword

The search box is the fastest way in. Type a plain word that describes what you want — home, user, arrow, settings, cart — and results update as you type.

A few things worth knowing about how the search behaves:

• It matches icon names, not concepts. Searching delete may miss an icon literally named trash, so try synonyms when a term returns little.
• Results span every bundled icon set at once, which is why a single query like arrow can return hundreds of matches.
• Spelling matters. These are English identifiers, so colour won't find color.

If a keyword returns nothing useful, switch to a broader term (chevron instead of chevron-double-left) or browse the set directly.

Browsing and filtering by icon set

Icônes aggregates many independent libraries — Material Design Icons, Font Awesome, Tabler, Phosphor, Lucide, Bootstrap Icons, and others. Each is a separate "set" with its own visual style and naming conventions.

To narrow things down:

1. Open the icon set list (usually shown as a sidebar or a picker on the main page).
2. Select a set to browse it in isolation, or use it as a filter on top of your search.
3. Scroll or keep typing to move through that set's icons.

Filtering by set is the practical way to keep a project visually consistent. Mixing a rounded set like Phosphor with a sharp one like Material Symbols tends to look unintentional, so pick one set early and stay in it.

Copying an icon into your project

Click any icon to open its detail view. From there you can take the icon in whichever form fits your stack:

The exact buttons and labels vary by icon and by set, but the pattern is consistent: select the icon, choose the output format, copy.

A concrete example

Say you need a shopping cart icon for a React navbar:

1. Search cart.
2. Filter to the set your project already uses (for example, Lucide).
3. Click the icon that matches your design.
4. Copy the React/JSX snippet.
5. Paste it into your component and adjust size, color, or stroke-width through the props the snippet exposes.

If you'd rather not add a dependency, copy the raw SVG instead and inline it — same visual result, no package.

Downloading and referencing icons

Beyond copy-paste, Icônes lets you grab the underlying asset. You can download an individual SVG, and in many cases pull the icon directly from its source package (for example, via npm) if you'd rather manage icons as a dependency than as pasted markup.

Two practical notes:

• Check the license of the source set, not just Icônes. Icônes is an explorer; each bundled library carries its own license terms. If you're shipping commercially, confirm the set you chose permits it.
• Downloaded SVGs are static. They won't respond to currentColor or CSS the way an inlined or component-based icon will, so pick the format based on whether you need to restyle it later.

Common snags

• "My search returns too much." Add the set filter, or use a more specific noun.
• "The icon I want isn't there." Icônes only shows sets it has indexed; a niche or brand-new library may not be included yet.
• "The copied code doesn't render." Framework snippets assume the matching package is installed — check that the import path resolves before debugging the markup.
• "It looks different in my app." Size, stroke width, and color are usually set by you, not baked into the icon; match those to your design tokens.

Icônes is a web-based icon browser and search tool that aggregates many open-source icon sets into a single interface. It is aimed at designers and developers who need to find, preview, and copy icons quickly. You can use it in a browser without creating an account.

What Icônes Does

Icônes solves a common problem: icon sets are scattered across separate projects, each with its own naming, formats, and search. Instead of visiting each collection individually, you search one place and get results across all of them.

Its core functions are:

• Unified search across many icon collections at once
• Live preview of each icon at a usable size
• Copy options so you can take the icon into your project
• Collection browsing when you want to explore a specific icon set

Who It Is For

If you only ever use one icon library and already know its names, Icônes adds less value. It becomes useful when you want to compare styles or search across libraries.

How to Use It

1. Open icones.js.org in a browser.
2. Type a term such as home, user, or arrow into the search field.
3. Browse the results, which are grouped by icon collection.
4. Select an icon to see its available formats and copy options.
5. Copy the SVG, the icon name, or the code snippet into your project.

The expected result is that you leave with an icon asset or identifier you can paste directly into your work, without downloading or installing anything.

Key Things to Know

• It is a browser tool, not a package. You use it to find and copy icons; you still add them to your project yourself.
• Collections are open source. The icons come from third-party libraries, so licensing follows each original set. Check the source collection's license before commercial use.
• No account is required for the browsing and copying workflow described above.
• Availability depends on the collections it indexes. If a specific icon set is not included, you will not find it here.

When to Use Something Else

Choose a dedicated icon package or your framework's built-in icon component when you need versioned dependencies, tree-shaking, or automated updates in a build pipeline. Use Icônes when the priority is fast visual search and one-off copying.