Home > Articles > Programming > User Interface (UI)

Enhance Java GUIs with Windows Icons

Jeff Friesen shows how to make Windows icons available for use in your Java GUIs. After giving a tour of Microsoft's Icon Resource Format, used by Windows .ICO files to store icon images, he presents his own Java library for extracting icon images from these files. He even includes a Java application that uses this library to extract images, which the application subsequently displays.
Like this article? We recommend

Many years ago, Microsoft introduced the Icon Resource Format to specify the internal structure of icons—the Windows operating systems use icons to represent programs and other documents visually. Although Windows icons are often embedded in .EXE and .DLL files, they’re also stored in files with the .ICO extension.

The widespread availability of .ICO files is a good reason to think about using Windows icons with buttons and other GUI components to enhance Java GUIs. Because Java provides no direct support for reading Windows icons from .ICO files, this article introduces a Java library that accomplishes this task.

First we’ll take a tour of Microsoft’s Icon Resource Format. This tour provides insight into how the library works, which is helpful if you ever need to extend the library. After introducing the library, we’ll look at a Swing-based Windows icon viewer application that demonstrates the library’s usefulness.

Tour the Icon Resource Format

Microsoft’s Icon Resource Format specifies the format of a Windows icon resource. As Figure 1 illustrates, the Icon Resource Format organizes the resource into a header, a directory with one or more entries, and one or more images—unlike .ICO files, which adhere to this organization, I’ve encountered .EXE files that don’t store the header or directory portion of the format.

Figure 1

Figure 1 To accommodate different screen resolutions, a Windows icon resource can store multiple images.

The header is a six-byte data structure that begins with a two-byte reserved field, which should contain 0. This field is followed by another two-byte field, which must contain 1 to identify the resource as an icon resource. A third two-byte field completes the header by identifying the number of entries in the directory.

Directory of Images

Because an icon resource can store multiple images, immediately following the header is an image directory. Each directory entry describes one image in terms of its width and height, number of colors, number of color planes, number of bits per pixel, size, and location. The entry is conveniently described via this C structure:

typedef struct
  BYTE bWidth;     // Image width (in pixels)
  BYTE bHeight;    // Image height (in pixels)
  BYTE bColorCount;  // Number of image colors (0 if wBitCount is 8 or more)
  BYTE bReserved;   // Reserved (must be 0)
  WORD wPlanes;    // Number of color planes (typically 1)
  WORD wBitCount;   // Number of bits per pixel
  DWORD dwBytesInImage; // Number of bytes making up the image
  DWORD dwImageOffset; // Offset from start of header to the image

The bWidth and bHeight members express the image’s width and height dimensions. Although these members can record dimensions from 1×1 to 255×255 (including non-square dimensions such as 48×24), dimensions such as 16×16 and 32×32 are more common because various Windows shells support them.

If bWidth and bHeight contain zeroes, the dimensions must be read from the image data—this is true for those Windows Vista icon images whose dimensions are 256×256. Although the image data could specify higher dimensions such as 1024×768, most (if not all) of the Windows shells don’t support such images.

The bColorCount member records the number of colors. This value is usually two to the power of the wBitCount member’s value. If the value of wBitCount is 8 or higher, the number of colors exceeds 255, bColorCount contains 0, and the number of colors must be read from the image data.

The wPlanes and wBitCount members record information for determining the number of colors (by multiplying their values). Although wPlanes is supposed to be set to 1, some Windows icon resource entries store 0 in this member. In some cases, 0 is also stored in wBitCount.

Finally, the dwBytesInImage and dwImageOffset members record information that’s needed for reading the image data. The first member records the size (in bytes) of the image data, and the second member records the starting location of the image data (relative to the beginning of the header).

Image Data

The directory is followed by a sequence of images, in which each image is stored in one of two formats:

  • Portable Network Graphics (PNG)

Let’s look at each format in detail.


This older format expresses an image as a BITMAPINFOHEADER structure followed by an array of RGBQUAD structures, followed by the actual image bits (which are often expressed using XOR and AND bitmaps):

BITMAPINFOHEADER icHeader;  // Device Independent Bitmap (DIB) header
RGBQUAD     icColors []; // Color table
BYTE       icXOR [];  // DIB bits for XOR bitmap
BYTE       icAND [];  // DIB bits for monochrome AND bitmap

Microsoft’s BITMAPINFOHEADER structure, which appears below, provides information necessary for reading an image. Of this structure’s various members, only biSize, biWidth, biHeight, biPlanes, and biBitCount are significant for reading the image data—members other than these and biSizeImage are typically set to 0.

typedef struct
  DWORD biSize;
  LONG biWidth;
  LONG biHeight;
  WORD biPlanes;
  WORD biBitCount
  DWORD biCompression;
  DWORD biSizeImage;
  LONG biXPelsPerMeter;
  LONG biYPelsPerMeter;
  DWORD biClrUsed;
  DWORD biClrImportant;

The biSize member stores the structure’s size, which happens to be 40. A program reading a Windows icon resource checks the first four bytes of image data to see whether they consist of 40 followed by three zeroes. (Remember that this is little-endian byte order.) If this is the case, the program can assume that it has found a BITMAPINFOHEADER structure.

The biWidth and biHeight members store the image’s width and twice its height, respectively. If a directory entry’s width and height are set to 0, these members are accessed to determine the width and height (divided by two). biHeight originally was mandated to contain twice the image height to account for both the XOR and AND bitmaps.

The biPlanes and biBitCount members record information for determining the maximum number of colors used by the image. If a directory entry’s number of colors is 0, these members are accessed to calculate the number of colors. The calculation is expressed as two to the power of the result of multiplying these members’ values by each other.

If the number of colors is 256 or less, the BITMAPINFOHEADER structure is followed by an array of RGBQUAD structures. The number of colors determines the number of entries in this array. For example, there are 2 entries for a 2-color image, 16 entries for a 16-color image, and 256 entries for a 256-color image. Here’s the RGBQUAD structure:

typedef struct
  BYTE  rgbBlue;
  BYTE  rgbGreen;
  BYTE  rgbRed;
  BYTE  rgbReserved;

If the number of colors exceeds 256, the RGBQUAD array is not present. Pixel values directly describe colors, instead of serving as indexes into this array. For example, if biBitCount contains 32 (24-bit color and an 8-bit alpha channel), each pixel value’s four bytes respectively provide (from low address to high address) the blue, green, red, and alpha color components.

The number of colors determines the manner in which an image is stored. If this value is 256 or less, the image is stored as an XOR bitmap followed by an AND bitmap, in which each bitmap has biWidth by biHeight/2 dimensions. These two bitmaps are used to display images with transparent areas on the screen, as follows:

  1. The AND bitmap, a matrix of single-bit values, is first applied to preserve the screen background surrounding the image, and erase the area where the image pixels appear. Existing screen pixels are preserved by ANDing them with the AND bitmap’s corresponding 1 bits; existing screen pixels are erased (made black) by ANDing them with the AND bitmap’s corresponding 0 bits.
  2. Next, the XOR bitmap, a matrix of color indexes/values, is applied to display image pixels without affecting the screen background. This is accomplished by XORing black bitmap pixels with existing screen pixels. The black screen pixels (created in the previous step) are XORed with the corresponding bitmap pixels to merge the bitmap’s image with the screen.

If the number of colors describes a 32-bit image, the XOR and AND bitmaps are missing. Instead, a single bitmap with an eight-bit alpha channel is stored. The advantage of the alpha channel over the traditional XOR and AND bitmaps is that the alpha channel makes anti-aliasing possible; jagged edges found in non-horizontal and non-vertical lines (and arcs) are minimized by using various levels of translucency.

When reading an XOR, AND, or 32-bit image bitmap, it’s important to keep in mind that the bitmap is stored upside-down. In other words, the first stored row should appear at the bottom of a displayed image. Another item to remember is that each row of pixel values must be a multiple of four bytes. Zero pad bytes are stored at the end of a row to make sure that the row’s byte length is exactly divisible by four.

Portable Network Graphics (PNG) Format

Some icon resources store image data using the Portable Network Graphics (PNG) format. This format makes it possible to store compressed icon images. Compression is necessary because large images require lots of memory; for example, a single uncompressed 256×256 32-bit image requires 256 kilobytes of storage.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020