How Windows stores icons inside a program
An icon inside an executable is not one image. It is a group of images at different sizes and colour depths, stored in the file's resource section, plus a small directory that lists them. Windows picks the size it needs at display time: 16×16 in a list view, 32×32 on the desktop, 256×256 in a large-icon view.
This tool walks that resource directory, reads every image in every group, and rebuilds them into standard files. Sizes from 16×16 to 256×256 come out exactly as the developer stored them, with no upscaling and no quality loss.
For a full explanation of the ICO format and how icon resources are embedded in PE files, read how Windows icons are stored in EXE files.
How to extract an icon from an EXE
- Open the file. Drop the .exe, .dll or .ico onto the box above, or click to browse. Only the file's resource section is read, so a large program opens instantly.
- Review the sizes. Every icon in the file is listed with each size it was stored at, its colour depth and its byte size. Most modern programs carry six or more sizes from 16×16 up to 256×256.
- Pick a format. Choose PNG for use in documents, websites and design tools. Choose ICO to reuse the icon as a Windows shortcut or application icon.
- Save it. Save a single size, save the largest as a PNG in one click, or export every size together as a single .ico file.
What you get out
- Every icon in the file — programs commonly hold several, such as a main application icon plus document-type icons.
- Every size of each icon, listed individually with its colour depth.
- PNG export — transparency preserved, at the icon's true pixel size.
- ICO export — either a single size, or one multi-size
.icocontaining every size, which is the format Windows expects.
Large sizes are usually stored as PNG inside the icon already, so those are extracted byte-for-byte. Smaller sizes are normally stored as bitmaps and are converted for PNG output.
Supported files
Accepted inputs are .exe, .dll, .ocx, .cpl,
.scr, .mun, .ico and .cur. Both 32-bit and 64-bit
executables work, on x86, x64 and ARM.
Dropping an .ico splits it into its individual sizes, which is the quickest way to get a
single PNG out of a multi-size icon file. Only the resource section is read rather than the whole
executable, so a 400 MB installer opens as fast as a small utility.
Why the file is never uploaded
The resource section is parsed by JavaScript in your browser, and PNG conversion uses a canvas on the same page. No server is involved, so the file is never transmitted and no copy remains after you close the tab.
This matters more than it first appears: the usual way to get an icon out of an executable is to upload that executable to a website. For internal tools, unreleased software or a client's application, that is a copy of a private binary sitting on someone else's disk.
When no icon comes out
Four cases produce nothing, and the tool says which one applies:
- No resource section. Console utilities and many small binaries carry no icons at all.
- Packed executables. UPX and similar packers compress resources, so nothing is readable until the file is unpacked.
- Icons loaded at runtime. Some applications read their icon from a separate file or a theme rather than embedding it.
- 16-bit icon libraries. Old
.iclfiles use the pre-1995 NE format, which this tool does not read.
Icons are also not upscaled. If a program only stored 32×32, that is the largest size available — no tool can invent detail that was never in the file.
Who extracts icons
- IT and deployment teams — building shortcuts, Start menu entries and software catalogue entries that match the real application.
- Designers — pulling an authentic app icon into a mockup, diagram or presentation instead of redrawing it.
- Documentation writers — illustrating instructions with the exact icon a reader will see on screen.
- Developers — recovering an icon from an old build when the original asset is lost.
- Anyone customising a desktop — reusing a program's icon for a custom shortcut or launcher.
Icon extraction compared with full EXE inspection
Use this tool when icons are all you want. It goes straight to the resource section and presents every size as a one-click download.
Use the EXE extractor online when you need the rest of the picture: publisher and version details, the code signature, imported libraries, embedded files, and the strings and URLs compiled into the binary. It also extracts icons, alongside everything else. For a plain archive rather than a program, the ZIP extractor opens the container and its contents.
For in-depth guides on binary inspection, read how to extract an icon from an EXE file, how Windows icons are stored in EXE files, and how to extract EXE files without installing software.
ICO format standards and extraction edge cases
An ICO file is a simple container: a 6-byte header (reserved word, type word: 1 for icon / 2 for cursor, image count), then one 16-byte directory entry per image (width, height, colour count, reserved, planes, bit count, data size, offset into the file).
Three extraction edge cases: (a) Windows Vista and later embed PNG images inside the ICO
container for the 256 × 256 size — those entries are saved as .png files; pre-Vista sizes
use the BMP DIB format and are converted to .png before saving; (b) a cursor file (.cur)
shares the ICO structure with type word 2 and stores a hotspot (x/y offset) in the planes
and bit-count bytes — the extractor reads both ICO and CUR files and reports hotspot data
when present; (c) when extracting from an EXE or DLL, the extractor reconstructs the ICO
container from the RT_GROUP_ICON and RT_ICON resources in the PE .rsrc section,
so all icon sizes defined in the executable are included in the output. For a deeper look at
how Windows embeds icons in executables, see the guide on
how Windows icons are stored in EXE files.
Frequently asked questions
How do I convert an EXE to ICO?
Drop the .exe into the tool above. The extractor rebuilds every stored icon group into a native multi-resolution .ico file that you can download in one click for Windows shortcuts or application icons.
How do I extract an icon from an EXE file?
Drop the .exe onto this page. Every icon it contains is listed at every stored size, and each one saves as a PNG or an ICO in one click.
Can I convert the icon to PNG?
Yes. Choose PNG for any size, or use Download largest as PNG for the highest resolution the file contains. Transparency is preserved.
Is my file uploaded to a server?
No. The executable is parsed and the PNG is generated inside your browser. Nothing is transmitted.
What size icon will I get?
Whatever the file actually stores, typically 16×16, 32×32, 48×48, 64×64, 128×128 and 256×256. The largest available size is shown for each icon. Icons are never upscaled.
Why does this EXE show no icons?
Either it has no resource section, which is common for console programs, or it is packed with UPX so its resources are compressed. The tool reports which case applies.
Can I extract icons from a DLL?
Yes. DLLs use the same resource format as executables. Windows system libraries such as shell32.dll hold hundreds of icons and all of them are listed.
Can I split an ICO file into separate images?
Yes. Drop the .ico in and every size inside it is listed separately, each one savable as its own PNG.
Does it work on macOS or Linux?
Yes. Parsing happens in the browser, so Windows icons extract on any operating system.