Remix Icon license v1.0: what changed in January 2026, and who has to act

The Remix Icon license changed in January 2026. Remix Icon is still free for apps, websites and SaaS products, but the new text bans logo use, standalone icon packs and competing icon libraries. If your icons are interface elements, nothing breaks. If you use one as a brand mark, sell a pack, or ship under a strict open-source policy, read on.

We read the license text, the maintainers' notice, the npm registry and the related GitHub threads on October 25, 2026. Licenses and package metadata change, so check the live files before you rely on anything here. This is not legal advice: read the current terms yourself, and take advice from a lawyer where real money depends on the answer.

What the Remix Icon license v1.0 changed

In the v4.8.0 tag, the README said the icons were under the Apache License 2.0 with one extra request: "The only thing we ask is that these icons are not for sale." On January 25, 2026 the maintainers committed Remix Icon License v1.0, and the v4.9.0 tag (January 27) is the first tagged release that carries it.

The maintainers' license change notice says the old setup, Apache-2.0 plus extra terms, "created conflicts with the original Apache-2.0 license itself". It lists what stays the same (commercial use, modification, optional attribution) and what is "clarified": no standalone icon products, no use as "the primary value of a paid product", no use as logos or brand identities, and no competing libraries.

The license text itself is more specific than that summary. Four clauses matter in practice:

• Section 2.1 permits use in "Software products and SaaS platforms" and in "Websites, web applications, and mobile applications".
• Section 3.1 bars selling the icons as a standalone product. Its own example of a banned product is "Premium Icon Pack – 2,000+ Icons for $29"; its example of a permitted one is "Website or app templates that include Icons as UI elements".
• Section 3.2 bars a competing icon library "even if the Icons are modified with only minor or superficial changes (such as color, size, stroke width, corner radius, or layout)".
• Section 3.3 bars using the icons, "whether modified or unmodified", as "A logo, trademark, or brand identifier", and names logos made by "applying simple modifications such as color changes, rotation, combination, or layout".

Two things the text does not contain, on the copy we read: the word "patent" does not appear, and there is no governing-law or jurisdiction clause. If your legal team expects either, ask before you adopt it.

Who is fine, and who has to act

In our reading, most product teams are in the first row. The other rows are where the new text bites.

The open-source row is not hypothetical. A Backstage maintainer asked the CNCF for an exception for Remix Icon License v1.0. On May 8, 2026 a CNCF reply said the license "is not an open source license (specifically, it contains restrictions on competitive uses)", so no exception was possible, although "Backstage is welcome to continue using prior versions licensed under Apache-2.0". A separate commenter on the notice thread, who described how Linux distributions judge licenses, argued that the icons would be stripped from Debian, Fedora and Ubuntu packages. That is one person's reading, not a distribution's decision.

Wrapper libraries are a gray area. The author of a Svelte wrapper asked in the thread whether it counts as a competing library under Section 3.2; the maintainer replied that the project "has not violated our agreement". That is a comment, not an amendment to the license, so a wrapper author who needs certainty should ask for it in writing.

If you are a maker launching a product, the logo row is the one to check first. Section 3.3 names the stock-icon-plus-color-change logo directly. We covered the same question for typefaces in Can I use Google Fonts in a logo. In our view, no off-the-shelf icon makes a good logo regardless of its license, because anyone else can download the same shape. Upfynd's Branding & Identity category lists 70 products as of October 2026 if you need a proper mark.

Why a license scanner may still report Apache-2.0

The npm registry entries for remixicon show version 4.9.1, published January 29, 2026, with the metadata field "license": "Apache-2.0". We downloaded that tarball: its package.json says Apache-2.0, yet the License file inside begins "Remix Icon License v1.0". A tool that reads only the metadata field will report the wrong license.

The repository's package.json was corrected to "Remix Icon License v1.0" in a commit on April 28, 2026, but the latest npm release is still 4.9.1, which predates that fix. So the registry field stays stale until a new release ships.

Other projects repackage the set. The react-icons build configuration we read labels its Remix Icon set "Apache License Version 2.0" while pinning a Remix Icon commit (9fb7967) from April 28, 2026, after the change. We did not inspect what the published react-icons package ships, so treat that as a reason to look, not a finding about its users.

How to check which Remix Icon license your project ships

1. Find the installed version: run npm ls remixicon, and check any wrapper such as @remixicon/react.
2. Open the License file inside the installed package, not the license field in package.json. The v4.8.0 tag ships Apache-2.0; the v4.9.0 and v4.9.1 tags start with "Remix Icon License v1.0".
3. If you redistribute icons in an app or site, keep the License file with them. Section 5 says that when distributing "the complete Icon library or substantial portions thereof" you must retain existing copyright notices and should include a copy of the license.
4. Search your product for any Remix icon used as a logo, favicon or app icon.
5. If a policy blocks the new terms, pin to 4.8.0 as a stopgap, as Backstage said it was doing, or switch libraries. The Backstage maintainer said in the notice thread that staying on 4.8.0 is not something they "consider viable long-term".

One more consequence: under Section 10, rights "terminate automatically" on breach, though you "may continue to use the Icons in projects already distributed" before termination. A logo problem is therefore worth fixing before it becomes a dispute.

Permissively licensed alternatives to Remix Icon

If you cannot accept Section 3, these libraries ship plain permissive licenses. We read each LICENSE file on October 25, 2026; the push dates are GitHub's figures for the same day.

These licenses grant the right to use, copy, modify and distribute with a notice requirement, and none of the three contains a logo clause. That is a statement about the text, not a promise that an icon can be trademarked, so Section 3.3's logic still applies in practice: do not build your brand on a shared icon.

To browse more sets, Upfynd's Design Resources category lists 128 products as of October 2026, including icon search tools such as Iconbuddy and Iconduck. Before you copy a set from any aggregator, open the library's own License file, because the license that matters is the one that ships with the version you download.

What we did not verify

We did not test how any scanner behaves, and we have not seen a legal opinion on Section 3.2 or Section 3.3. The maintainers say the change "does not affect normal usage in apps, websites, UI kits, templates". That is their statement, and the License file is what governs. If real money depends on a reading of the terms, such as a template business or an icon-heavy product, ask the maintainers a specific question in their thread and take legal advice.