Apple Icon Image format

The file format consists of an 8 byte header, followed by any number of icons.

• ^1. The value inside the parenthesis is the uncompressed length for ARGB and 24-bit RGB icons.
• ^2. it32 data always starts with a header of four zero-bytes (tested all icns files in macOS 10.15.7 and macOS 11). Usage unknown, the four zero-bytes can be any value and are quietly ignored.
• ^†. These formats are supported in standalone icns files but do not display properly if used as application icon inside a .app package.

• Mono icons with alpha mask can display three colors: white, black, and transparent.
• The 4-bit an 8-bit icons use a fixed color palette with 16 colors and 256 colors, respectively.
• The 24-bit RGB format consists of the three compressed channels tightly packed (see Compression). The it32 icon must start with a four-byte header, see footnote above.
• The ARGB format consists of the ascii values for 'ARGB' and the four compressed channels tightly packed (see Compression).

• the ARGB fields also accept files in PNG format – but not vice versa, you can not put ARGB images in any of the PNG-only fields (tested on macOS 11).
• ARGB images are only supported in macOS 11 and newer – macOS 10.15.7 does not display ARGB images. Yet, even the ARGB keys can be displayed on macOS 10.15 if you set a JPEG 2000 or PNG image (see footnote on usage in app packages above).
• The 24-bit RGB icons (is32, il32, ih32, it32) also allow images in JPEG 2000 and PNG format (tested on macOS 10.15.7 and macOS 11).
• The support for newer image types seems to be introduced later than the key field (see previous two points). Therefore, the supported OS version may not be accurate or adjusted based on file format.

• The table of contents is a list of all contained types (4 byte type-name + 4 byte length).
• The data for all nested icns files does not contain the icns file-header. So, if you want to save the data to a file you have to prepend the icns header.

Element types that deal with ARGB (32-bit) or RGB (24-bit) image formats require different types of headers before the binary data. It is important to note that this header is part of the image data and is not the 4-byte big endian icon element type value (e.g. ic04 or ic05).^[5]

ARGB ElementsARGB images must have their binary portion of the image data preceded by the four byte 'ARGB' header. After that, instead of each pixel with each of its four channels stored together (e.g. ARGBARGBARGB), an image with three pixels would be stored in individual channels of pixel data (e.g. AAARRRGGGBBB). In addition, each channel of pixel data needs to be encoded as mentioned below.

RGB ElementsRGB images have their binary portion of the image data preceded by four zero byte characters only when the element type is 'it32'. In all other cases, no header is needed. Channel data is separated as with the ARGB binary data (e.g. RRRGGGBBB instead of RGBRGBRGB). Each channel must also be encoded as mentioned below.

Mask ElementsMask elements are not encoded like ARGB and RGB image color channel data. The data is the same as that of an ARGB image except only the alpha channel data is provided. So for an image that has two pixels, ARGBARGB, the mask data is AA.

Over time the format has been improved and there is support for compression of some parts of the pixel data. The 24-bit RGB (is32, il32, ih32, it32, icp4, icp5) and ARGB (ic04, ic05, icsb) pixel data are compressed (per channel) with a format similar to PackBits.^[6]Some sources mention that the OS supports both compressed or uncompressed data chunks.^{[citation needed]} However, manually crafting icns files with uncompressed 24-bit RGB or ARGB images will not display properly – at least on newer macOS releases (tested on macOS 11).

Here is a GitHub repo with some swift code that appears to pass the test for both encoding and decoding as described here: ByteRunLengthCoder

The following pseudocode decompresses the data:

While there is compressed data:    Read one byte as an unsigned number N    If N < 0x80:        Output the next (N + 1) bytes    Else:        Output the next byte (N - 0x80 + 3) times

Example: 02 01 02 02 80 03 81 04 82 05 should decompress to 01 02 02 03 03 03 04 04 04 04 05 05 05 05 05

The following pseudocode compresses the data:

function Encode(input data)  Initialize output as an empty array  Set index to 0  While index < the count of data    Initialize sequence as an empty array    Set count to 0    // Unique sequence    While count ≤ 0x7F and index < count of data      If index + 2 < count of data and data[index] = data[index+1] and data[index] = data[index+2]        Break the loop  // Start of a repeating sequence      End If      Append data[index] to sequence      Increment index      Increment count    End While    If sequence is not empty      Append (count - 1) to output      Append all items in sequence to output    End If    If index ≥ count of data      Break the loop    End If    // Repeating sequence    Set repeatedByte to data[index]    Set count to 0    While count ≤ 0x7F and index ≤ data and data[index] = repeatedByte      Increment index      Increment count    End While    If count ≥ 3      Append (0x80 + count - 3) to output      Append repeatedByte to output    Else  // Less than 3 repeating bytes      Append (count - 1) to output      Repeat (count) times        Append repeatedByte to output      End Repeat    End If  End While  Return outputEnd function

Example: 01 02 02 03 03 03 04 04 04 04 05 05 05 05 05 should compress to 02 01 02 02 80 03 81 04 82 05

As of macOS 11, there are certain issues / bugs with the file format:

1. Setting is32+ics8 or ih32+ich8 will display a proper icon. But setting il32+icl8 ignores the transparency mask and displays an icon without transparency.
2. Compressed ARGB data is not interpreted correctly. The last value of the blue channel (aka. the very last value) is ignored and treated as if it were all zero-bytes. Usually this is no issue since most icons will have transparency at the bottom right corner anyway. However, it can become an issue if the last value is a repeating byte (see Compression). Potentially, up to 130 pixels can lack the blue channel value.
   A workaround is to append an additional byte at the end which is interpreted as a control character without following data. You can compare the difference with these two examples:
   • 69636E73 00000024 69633034 0000001C 41524742 FFFFFBFF FF00FB00 FF00FB00 FFFFFBFF
   • 69636E73 00000025 69633034 0000001D 41524742 FFFFFBFF FF00FB00 FF00FB00 FFFFFBFF 00
3. macOS 10.15.7 (likely earlier) and later versions have an issue displaying PNG and JPEG 2000 icons for the keys icp4 (16x16), icp5 (32x32), and icp6 (64x64). The keys work fine in a standalone icns file but if used in an application, the icons are displayed completely scrambled. Either use the new ARGB format ic04 and ic05 (macOS 11+) or the old 24-bit RGB + alpha mask format. Use the latter with the old keys is32+s8mk and il32+l8mk, or with the newer keys icp4+s8mk and icp5+l8mk (writing RGB data into PNG fields^[2]). If using ARGB image data, make sure to provide alternative formats for macOS 10.15 and earlier. This issue is especially tricky to detect if you provide both, 16x16 and 16x16@2x icons, because if you connect your Mac to a non-retina monitor, the non-retina 16x16 icon will be used and thus the icon will be displayed scrambled. The icp6 field does not seem to be used in application icons and can safely be ignored. Additionally, if you don't provide the smaller icon sizes at all the bug will also manifest when the OS scales down your larger PNG/JPEG 2000 icons, so make sure to render smaller sizes and include them.

Various image viewers can load *.icns files, and free and open source converters from or to PNG also exist.^[7][8] GTK+ can load *.icns resources since 2007.^[9] Other tools supporting the format include the Apple Icon Composer and icns Browser, The Iconfactory, and IconBuilder.
MacOS^{[clarification needed]} offers the built-in iconutil command line tool to pack and unpack *.icns files.

• ICO format on Windows
• X PixMap format for X11

• IconFamily (last update 2013) – Open source Objective C class to read and write Apple icns files
• osxiconutils (not maintained) – Command line tools to work with Apple icns files
• icnsutil – Python library to read and write icns files
• icns - Rust crate to read and write icns files
• createicns - C library to read and write icns files
• icon_records_extractor - C library to extract all icns records as their own icons include dark mode icns.