Awesome

phosphor-icons-tailwindcss

A TailwindCSS plugin for the Phosphor icon set.

Installation

1. install package:

   pnpm add -D phosphor-icons-tailwindcss # or via npm, yarn, ...
   

2. register the plugin in your tailwind.config.js:

   // tailwind.config.js
   import phosphorIcons from "phosphor-icons-tailwindcss";
   
   /** @type {import("tailwindcss").Config } */
   export default {
   	plugins: [phosphorIcons()],
   };
   

   Or if you are using Tailwind 4:

   /* app.css, or whatever your entry CSS is */
   @import 'tailwindcss';
   @plugin 'phosphor-icons-tailwindcss';
   

[!IMPORTANT] This package only supports ESM. It should work well in most projects today, especially those using Vite.

Usage

You need to add two classes to your markup:

1. the base ph class,
2. an specifier class with the syntax: ph-[<name><--weight>], corresponding to your desired icon.

[!NOTE] weight is optional and defaults to "regular" if not specified.

For example:

<p>
	<span class="ph ph-[info] text-xl"></span> <!-- render the regular info icon -->
	<i class="ph ph-[pulse--duotone] text-red-500"></i> <!-- render the pulse icon in duotone weight -->
</p>

<div class="ph ph-[file-css] h-6 w-6"></div>

For all available icon names and weight, visit phosphoricons.com.

The output CSS look something like this:

@layer icons.base {
	.ph {
		--ph-url: none;
		width: 1em;
		height: 1em;
		background-color: currentcolor;
		color: inherit;
		mask-image: var(--ph-url);
		mask-size: 100% 100%;
		mask-repeat: no-repeat;
	}
}

@layer icons {
	.ph-\[info\] {
		url('data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyNTYgMjU2IiBmaWxsPSJjdXJyZW50Q29sb3IiPjxwYXRoIGQ9Ik0xMjgsMjRBMTA0LDEwNCwwLDEsMCwyMzIsMTI4LDEwNC4xMSwxMDQuMTEsMCwwLDAsMTI4LDI0Wm0wLDE5MmE4OCw4OCwwLDEsMSw4OC04OEE4OC4xLDg4LjEsMCwwLDEsMTI4LDIxNlptMTYtNDBhOCw4LDAsMCwxLTgsOCwxNiwxNiwwLDAsMS0xNi0xNlYxMjhhOCw4LDAsMCwxLDAtMTYsMTYsMTYsMCwwLDEsMTYsMTZ2NDBBOCw4LDAsMCwxLDE0NCwxNzZaTTExMiw4NGExMiwxMiwwLDEsMSwxMiwxMkExMiwxMiwwLDAsMSwxMTIsODRaIi8+PC9zdmc+');
	}

	/* ...truncated... */
}

Configuration

You may pass a configuration object to the plugin to customize the generated CSS. The following shows the default configuration:

// tailwind.config.js
import phosphorIcons from "phosphor-icons-tailwindcss";

/** @type {import("tailwindcss").Config } */
export default {
	plugins: [phosphorIcons({
		prefix: 'ph', // for the icon classes
		layer: 'icons', // for the CSS layer
		customProperty: '--ph-url',
	})],
};

Similarly, for Tailwind 4:

@import 'tailwindcss';
@plugin 'phosphor-icons-tailwindcss' {
	prefix: ph;
	layer: icons;
	custom-property: --ph-url; /* use the kebab-case alias to avoid auto-format by stylelint / prettier */
}

Why ph-[info] and not ph-info?

You may notice this library utilizes Tailwind's support for arbitrary value, i.e ph-[info] instead of ph-info to map to the regular info icon. This is to avoid unnecessary parsing during development, especially for Taliwind language server. Arbitrary value syntax allows parsing ad-hoc only the icons actually being used. Otherwise, parsing 9000+ icons may cause slow-down that negatively impacts developer experience.

CSS layer

By default, the plugin generates CSS in the icons layer. This is to ensure the generated CSS is isolated and can be easily overridden by other utility classes, or extended upon. You can change the layer by specifying layer option in the config object, as discussed in Configuration, or passing null to skip any layering.

Tailwind 4

Sorting works differently in Tailwind 4, so the generated CSS is nested inside @layer utilities, that is:

@layer utilities {
	@layer icons.base {
		.ph {
			/* truncated base rule */
		}
	}
	@layer icons {
		.ph-[info] {
			/* truncated specifier rule */
		}
	}
}

[!NOTE] Notice the base rule is inside a sub-layer: this is to ensure specifier classes always have higher specificity, no matter if they are declare before or after the base rule in your CSS source.

Usage with Tailwind @apply directive

You may utilize @apply to extend your use case beyond just for icons. This is helpful if you want to reuse the icon source in other CSS.

In the following example, @apply [ph-bell] makes --ph-url available for use:

/* notification.css */
.notification {
	&::before {
		@apply [ph-bell];

		mask-image: var(--ph-url);
		mask-size: 100% 100%;
		mask-repeat: no-repeat;
		background-color: currentcolor;
	}
}

[!NOTE] Note that you should only apply a specifier class, NOT the base class.

Acknowledgements

You may find @iconify/tailwindcss helpful if you are already using the iconify ecosystem in your codebase.

phosphor-icons-tailwindcss tries to stay minimal by only covering Phosphor icons, and it references directly @phosphor-icons/core for the SVG assets.