Working with Icons and Images
Platform vs. Custom Icons
Plugins should reuse existing platform icons whenever possible. Use Icons list to browse existing icons. Platform icons are located in
AllIcons. Icons from plugins are located in corresponding
<PLUGIN_NAME>Icons class (e.g.,
If custom icons are required, please refer to detailed design guide.
How to organize and how to use icons?
The best way to deal with icons and other image resources is to put them to a dedicated source root marked as Resources Root, say icons or resources.
getIcon() method of
IconLoader can be used to access the icons. The path to the icon passed in as argument to
IconLoader.getIcon() must start with leading
Then define a class/interface in a top-level package called
icons holding icon constants as static fields:
When using Kotlin, fields must be annotated with
Use these constants inside plugin.xml when specifying
icon attribute for
<action> or extension point, as well in
icon attribute. Note that the package name
icons will be automatically prefixed and must not be specified.
IntelliJ Platform supports Retina displays and has a bundled dark theme called Darcula. Thus, every icon should have a dedicated variant for Retina devices and Darcula theme. In some cases, you can skip dark variants if the original icon looks good under Darcula.
Required icon sizes depend on the usage as listed in the following table:
Icon Size (pixels)
Node, Action, Filetype
As SVG icons can be scaled arbitrarily, they provide better results in HiDPI environments or when used in combination with bigger screen fonts (e.g., in presentation mode).
A base size denoting the size (in the user space) of the rendered image in 1x scale should be provided. The size is set via the
height attributes omitting the size units. If unspecified, it defaults to 16x16 pixels.
A minimal SVG icon file:
The naming notation used for PNG icons (see below) is still relevant. However, the
@2x version of an SVG icon should still provide the same base size. The icon graphics of such an icon can be expressed in more details via double precision. If the icon graphics are simple enough so that it renders perfectly in every scale, then the
@2x version can be omitted.
All icon files must be placed in the same directory following this naming pattern (replace .png with .svg for SVG icons):
iconName.png W x H pixels (Will be used on non-Retina devices with default theme)
iconName@2x.png 2*W x 2*H pixels (Will be used on Retina devices with default theme)
iconName_dark.png W x H pixels (Will be used on non-Retina devices with Darcula theme)
iconName@2x_dark.png 2*W x 2*H pixels (Will be used on Retina devices with Darcula theme)
IconLoader class will load the icon that matches the best depending on the current environment.
Here are examples of toolWindowStructure.png icon representations:
Default + Retina
Darcula + Retina
Animated icons are a way to show that plugin is now performing some long-time action. For example, when plugin is loading some data.
Any animated icon is a set of frames that loop with some delay.
To create a new animated icon, use the
AnimatedIcon. If you want to create an icon where frames follow each other with the same delay, use a constructor that accepts a delay and icons:
To create an icon from frames with different delays, use
AnimatedIcon.Frame. Each frame represents an icon, and a delay until the next frame.
If you want to show somewhere that there is a long process, you can use the predefined
AnimatedIcon.Default loader icon. This icon has a larger
Register resource bundle via
com.intellij.iconDescriptionBundle extension point to provide tooltips automatically for all
icon.<icon-path>.tooltip key in given resource bundle, where
<icon-path> is the icon path with leading slash and
.svg removed and slashes replaced with dots (e.g.,