Open-source project
tabler/tabler-icons avatar
tabler/tabler-icons

Tabler Icons: 6257 glyphs, fifteen packages, one version number, and no filled partner for most of them

A set of over 6100 free MIT-licensed high-quality SVG icons for you to use in your web projects.

22,673 stars1,279 forksJavaScriptMIT

At a glance

What is it?
Tabler ships an MIT-licensed SVG icon set through fifteen npm packages that all move together. The grid and stroke are consistent, but the filled variant covers a small minority, the framework packages track framework majors, and the themable forms stop at SVG.
Who is it for?
Tabler suits teams that want one consistent grid and stroke across a product, install a single package per format or framework, and accept that colour comes from currentColor in inline or sprite markup. It does not suit projects needing a filled variant of every name, a Vue package for anything below Vue 3, a single Svelte package that spans both majors, or a themable dark mode that also depends on the PNG, PDF or EPS output.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 1 day ago.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • tabler/tabler-icons22,673 ★ · +922
Star history
Repository2026-09-212026-11-15
tabler/tabler-icons21.8k22.7k

922 Stars in the last 55 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The 6220 count is generated, and filled covers about a sixth of it

The headline number is written by a script, not typed by hand. The count sits inside comment markers in the README so the build can rewrite it, and it splits into 5203 outline icons and 1054 filled ones, which adds up to the 6257 in the summary line. That split is the first thing to understand about the library, because it is not symmetric. Outline is the default style and it is what nearly every name exists as. Filled is a minority style with a little over a thousand entries, so for the large majority of names there is no filled counterpart to switch to. A design that assumes fill is available as a variant of every icon will stall on individual symbols. The total also does not describe any single file you load. The sprite package ships separate outline and filled sprites, so 6257 is a catalogue size rather than the number of symbols in the asset you end up referencing.

currentColor handles colour, but stroke-width stays an attribute in the markup

The 24 by 24 grid with a 2px stroke is the shared contract, and the shipped markup carries it explicitly rather than leaving it to the surrounding stylesheet. Every inline icon repeats fill none, stroke currentColor, stroke-width 2, stroke-linecap round and stroke-linejoin round, and it opens with a bounding path set to stroke none that spans the full box. Because the stroke resolves from currentColor, colour changes are a plain CSS assignment. The example stylesheet sets the class to red, 32 pixels square and stroke-width 1.5, and that last value is the warning: resizing is free, but thinning the stroke means overriding an attribute the markup already set. Weight is therefore a property of your stylesheet, not of the library, and two icon sets at the same size will not match until you set stroke-width on both.

Image and background-image forms throw away the one thing CSS could control

An icon delivered as an image source or a CSS background-image cannot inherit anything, because currentColor is a property of the element that contains the markup, not of a file fetched by URL. The colour of those icons is fixed by the asset and the stylesheet that points at it. Hover states, dark mode and inherited text colour all stop at that boundary, and the only way past it is a second file per colour. Three delivery forms are described for the plain SVG package: an image source, a CSS background-image, and inline markup. The consequence for anyone choosing a delivery method is that the two cheapest options are the two that lock an icon to one colour for the life of the page, and that is a decision made at the template layer long before anyone notices it is the wrong one. Sprite markup sits on the other side of that line and behaves like inline SVG.

Three sprite files, and a wrong name renders nothing instead of erroring

The sprite package flattens the set into single files and changes how icons are addressed. Instead of a file per glyph you install @tabler/icons-sprite and point a use element at the sprite with the icon name appended after a tabler- prefix, using xlink:href with the file path and the fragment in one value. Three files ship: the main sprite for outline icons, tabler-sprite-filled.svg for filled icons, and tabler-sprite-nostroke.svg for outline icons with no fixed stroke width. Two consequences follow. A name absent from the sprite you included renders as an empty box rather than a visible failure, because a reference to a missing symbol produces nothing to look at. And the nostroke sprite breaks the 2px convention the rest of the set is built on, so dropping it into an interface beside the default sprite gives two different line weights next to each other in the same toolbar.

One version number spans all fifteen packages

Fifteen packages come out of this repository and every one of them carries the same version number, currently 3.50.0, released on October 27, 2026 after v3.49.0 on October 5 and v3.48.0 on September 22. The starting point is the raw SVG package, installed with the package manager of your choice:

sh
npm install @tabler/icons
sh
yarn add @tabler/icons
sh
pnpm add @tabler/icons

The same instruction covers every row of the package table: replace @tabler/icons with the entry you need. The latest release can also be downloaded from GitHub if you would rather not add a dependency.

What that does not change is the version arithmetic. There is no independent version per format and none per framework, so a project that mixes a component package with the webfont or the PNG output moves all of them when it bumps one, and a reviewer reading a lockfile diff sees a single version change standing in for fifteen artifacts. The root manifest is marked private while its publishConfig sets public access, so the artifacts npm serves are produced from the packages workspace rather than from the repository root.

Framework coverage stops at the framework major, not the framework name

Framework support is broad but not even, and the two gaps that matter sit at the major version rather than at the icon level. The Vue entry is Vue 3 components specifically, so a project on an earlier Vue has no matching package name to install. Svelte is split across two packages instead of one: @tabler/icons-svelte is the Svelte 4 line and @tabler/icons-svelte-runes is the Svelte 5 line built on runes. An app on the newer major has to know which of the two it wants before it installs anything. The Angular entry is not a plain component set either, it ships Angular component and icon providers, which is a different shape of API from the others. Preact, SolidJS and Astro are covered without a version qualifier. The consequence is that picking a package by framework name alone is not enough, because the framework major decides the package.

Webfont stylesheets are subsets, and PNG, PDF and EPS sit past the themable boundary

The webfont package trades styleability for a single request. It ships an icon font together with CSS and SCSS files, and you include one of the stylesheets from the dist directory. Each stylesheet in the shipped table lists the icons it carries and the stroke width it uses, so check that table before choosing one. The static packages move further from the source: PNG, PDF and EPS are published alongside the SVG, which is what print and design tooling needs and what a runtime theme cannot reach. None of those three inherit currentColor, because a raster or vector file has no parent element to inherit from. The consequence for a reader with a dark mode product is that theming ends at the SVG boundary.

The build validates twice and rewrites the readme before packaging

The release path is one long chain in the root package.json, and several of its steps edit files rather than check them. `pnpm run build` runs validate, then update, then validate again with --hard, then optimize, then build the packages, then preview, then the changelog image, then zip, then update-readme. The individual pieces are plain Node scripts: validate runs node ./.build/validate-icons.mjs, update reaches node ./.build/update-icons.mjs through the update:icons alias, and optimize runs node ./.build/optimize.mjs, which also has its own test at node --test ./.build/optimize.test.mjs. The consequence for a contributor is that running the build locally is an editing pass, not a verification pass.

Editorial conclusion

Tabler suits teams that want one consistent grid and stroke across a product, install a single package per format or framework, and accept that colour comes from currentColor in inline or sprite markup. It does not suit projects needing a filled variant of every name, a Vue package for anything below Vue 3, a single Svelte package that spans both majors, or a themable dark mode that also depends on the PNG, PDF or EPS output. Before pinning, check which outline names have a filled partner, confirm the framework major your package targets, and read the stylesheet you load from the webfont dist directory to see which icons and which stroke width it actually carries.

Frequently asked questions

Are tabler icons free?

Yes. The set is 6257 free, MIT-licensed SVG icons for web projects, each designed on a 24x24 grid with a 2px stroke. The LICENSE file at the repository root is MIT.

How to install tabler icons?

Install the SVG package with the package manager of choice: `npm install @tabler/icons`, `yarn add @tabler/icons` or `pnpm add @tabler/icons`. Replacing that name with any other package in the table installs a format specific or framework specific version instead.

How to use tabler icons in HTML?

The icons are plain SVG files, so they can be used as an image source, as a CSS background-image, or inlined directly in your HTML. Inlined icons inherit currentColor, which lets CSS change their size, colour and stroke-width.

how to use tabler icons in react

Install @tabler/icons-react, the package that provides React components. The same release line exists for Vue 3, Svelte 4, Svelte 5 runes, Preact, SolidJS, Astro and Angular, all sharing the single version number 3.50.0.

what is tabler icons

Tabler Icons is a set of 6257 free, MIT-licensed SVG icons for web projects, built on a 24x24 grid with a 2px stroke and split into 5203 outline icons and 1054 filled ones. It is published to npm as @tabler/icons and fourteen other packages from one repository.

tabler icons vs font awesome

Tabler's own scope is 6257 icons, 15 packages, one shared version, and a filled style covering 1054 names against 5203 outline names. Any ranking against another set is something you would have to judge yourself.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. tabler/tabler-icons on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/tabler-tabler-icons.svg)](https://hysenlabs.com/projects/tabler-tabler-icons)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/tabler-tabler-icons.svg)](https://hysenlabs.com/projects/tabler-tabler-icons)

Was this useful?