Lucide 1.0 launches with over 1,600 icons and brand icons removed for leaner builds

Lucide 1.0 is here, and it changes the way developers ship icons. A 32% bundle size reduction for React, no more legal gray area with brand marks, over 1,600 consistently styled SVGs — all in a single stable package. If you build with React, Vue, Svelte, or Solid, Lucide 1.0 is a clear productivity and performance win.

Why Lucide removed brand icons in version 1.0

The most visible change in Lucide 1.0 is that every brand logo is gone. This isn't a whim, and it isn't just about design taste. The Lucide team cited three concrete drivers: mounting legal pressure from rights-holders, consistency headaches for the design system, and the time sink of keeping dozens of brand marks current as logos change (Lucide v1 release notes).

Brand marks are intellectual property, and redistributing them inside a general-purpose icon set creates licensing exposure for maintainers and downstream users alike. Removing them closes that question for every project that upgrades — one less audit concern, no surprise takedown risk sitting inside your bundle.

This move wasn't sprung on the community. Lucide, forked from Feather Icons, had deprecated brand icons since 2020 with public discussion trailing the decision for years, as contemporary coverage confirms. The v1 line was simply where the long-announced cut landed. Users who still need brand logos are pointed to Simple Icons, a library purpose-built for company marks with its own compliance approach.

The impact for design teams is positive: every icon in the UI now follows the same stroke, cap, and fill conventions, with no outlier brands warping the system's aesthetics. For the vast majority of interfaces, that is a net gain — consistency over novelty, and legal safety for all downstream adopters.

How much Lucide 1.0 reduced bundle size

The numbers are concrete and system-wide. Before 1.0, the lucide-react package weighed in at 11.4MB; the release cut it 32.3% to roughly 1MB gzipped. The mechanism: Lucide dropped the legacy UMD build and now ships ESM and CommonJS only — no dead module formats that every installer downloaded and almost nobody used (InfoQ on the release).

This is not an edge-case optimization. Lucide reports tens of millions of weekly downloads for React alone, with the whole ecosystem passing 30 million installs a week (Lucide v1 release notes). Every production build, CI job, and cold start just got meaningfully lighter:

npm install lucide-react@1.0
# installs ~1MB gzipped, not 11MB

Smaller JavaScript bundles mean faster load times for your users, faster deploys, and less weight on global CDN caches. Ten megabytes saved per app, multiplied across tens of millions of weekly installs, is tangible bandwidth and disk savings — and a model for how every dependency should treat legacy build targets.

New features and improvements in Lucide 1.0

Lucide didn't just remove icons and recut the package. Version 1.0 brings real new capabilities:

1. Context providers for every major framework. Set shared default props for all icons at once instead of repeating props at every call site. Supported across React, Vue, Svelte, and Solid:

// React example: set color and size for all icons
import { LucideProvider } from 'lucide-react';

<LucideProvider color="#222" size={20}>
  <IconA />
  <IconB />
</LucideProvider>

2. Modern Angular package. A standalone, up-to-date @lucide/angular implementation — no more shoehorning React or Vue artifacts into Angular projects.

3. Improved accessibility. aria-hidden is now set by default on icons, keeping decorative glyphs out of screen-reader output (Lucide v1 release notes).

4. Stable font code points and shadow DOM support. Web-font users get fixed code points per glyph, and the core lucide package now works inside shadow DOM — simpler integration for web components and isolated DOM use cases.

5. Revamped per-framework documentation. Each supported framework gets its own guides rather than React-centric docs with footnotes, which smooths both migration and onboarding.

6. Breaking renames with migration guides. The Vue package moved from lucide-vue-next to @lucide/vue, and several icon exports were normalized. Framework-specific migration guides cover the renames (Lucide v1 release notes).

How to upgrade to Lucide 1.0 today

Upgrading is direct but requires housecleaning. The migration path per framework:

1. Install the latest package for your framework:

npm install lucide-react@1.0
npm install @lucide/vue
npm install lucide-svelte@1.0
npm install lucide-solid@1.0
npm install @lucide/angular

Note the scoped names for Vue (@lucide/vue) and Angular (@lucide/angular) — these are the renamed v1 packages, so update imports accordingly rather than bumping the old names.

2. Replace removed brand icons. Anything rendering a brand logo breaks in 1.0. Search for brand-named imports and swap in Simple Icons or your own SVGs:

// BEFORE (breaks in Lucide 1.0)
import { Github } from 'lucide-react';

// AFTER — source brand marks from a dedicated set
// check the Simple Icons docs for exact import paths

3. Adopt the context provider for shared defaults to DRY up repeated size and color props, as shown above.

4. Audit for renamed exports. Review the official v1 guide and migration docs for normalized icon names, and run a find-and-replace pass across the codebase — automated refactoring scripts beat manual edits at scale.

5. Verify accessibility behavior. aria-hidden now defaults on, which is correct for decorative icons. If any icon carries meaning for assistive tech, confirm it is still exposed after the bump.

Where Lucide 1.0 sits among icon libraries

Lucide's story is distinctive: the community-driven successor to Feather Icons, it grew from a minimalist fork into a 1,600+ icon set without drifting into bloat, with the community curating new glyphs against strict SVG and stylistic conventions (InfoQ on the release). Feather remains the right call for tiny minimalist sets; brand-heavy dashboards belong with Simple Icons. Lucide now occupies the middle decisively: a full UI toolkit where every glyph matches, at a weight that respects your bundle budget.

For teams running a shared design system, that middle is exactly where you want your default. Document the icon set choice, the brand-mark policy, and the upgrade path with the same rigor you give any agent-readable design system — when your AI coding agent understands the conventions, migrations like the brand-icon cut become mechanical. The same thinking applies to components shared across web and mobile: one icon set, one convention, every platform.

What this enables

Lucide 1.0's changes compound at scale: dead weight cut from every build, legal unknowns eliminated, defaults standardized through context providers. Deploy pipelines run faster. UIs stay visually coherent. Nobody audits icons for trademark exposure. And performance gains land directly in first contentful paint.

With strong documentation, clear migration paths, and no legacy drag, this is a toolkit you can standardize on. The upgrade is a one-time effort — bump, grep for brand imports, run the visual diff suite, ship. And if you are scaffolding something new, start from foundations that already encode this discipline: browse the OTF kits — production-grade scaffolding your agent can ship without relearning dependency hygiene.

Sources

• Lucide v1 release notes — brand icon removal, UMD dropped, 30M weekly downloads, package renames, accessibility defaults, context providers, shadow DOM. Verified live.
• InfoQ on the Lucide v1 release — 1,600+ icons, 11.4MB to ~1MB gzipped (−32.3%), tens of millions of weekly npm downloads, 2020 deprecation trail. Verified at prep time.
• Simple Icons — recommended home for brand marks going forward. Verified at prep time.