Free online PNG to DLL converter

A Windows application may require an image inside a DLL instead of as a separate PNG file, for example when its resource loader expects a library or an existing DLL must receive a replacement asset. This is a resource-packaging operation, not a normal image-format conversion.

What the PNG format is

PNG (Portable Network Graphics) is a lossless raster format used by web browsers, screenshot utilities, design software such as Adobe Photoshop and GIMP, and developers receiving interface assets from designers. It supports alpha transparency and is commonly used for screenshots, logos, icons, diagrams, textures, and user-interface graphics. A PNG stores pixel data and metadata; it does not contain executable functions or exported symbols.

What the DLL format is

DLL (Dynamic-Link Library) is a Windows Portable Executable library format. A DLL can contain native code, exported functions, manifests, dialogs, strings, icons, and arbitrary data resources. Applications load libraries at runtime with APIs such as LoadLibrary, and retrieve resources with FindResource, LoadResource, LockResource, and SizeofResource.

A resource-only DLL is appropriate when the requirement is to distribute an image inside a library without adding executable code. A DLL expected to provide particular functions, classes, resource identifiers, or calling conventions must be built or modified to match that interface; placing a PNG in a generic DLL does not create those exports.

How to package a PNG in a DLL

Build a resource-only DLL with Windows tools

1. Install the Windows SDK or Visual Studio Build Tools and open the Developer Command Prompt for Visual Studio.
2. Place the image in a working directory as image.png.
3. Create resources.rc with this line:
   101 RCDATA "image.png"
4. Compile the resource script:
   rc.exe /fo resources.res resources.rc
5. Link the resource into a DLL without an entry point:
   link.exe /DLL /NOENTRY /OUT:image.dll resources.res

The resulting image.dll contains the original PNG bytes as resource type RCDATA and numeric identifier 101. A compatible program must request that exact type and identifier, read the bytes, and decode them with Windows Imaging Component, GDI+, or another PNG-capable library. The DLL does not automatically display the image or expose a general-purpose image API.

Build a normal application DLL

If the library must also export functions, create a DLL project in Visual Studio and add the PNG as a custom data resource in its resource script, for example 101 RCDATA "image.png". Build the project normally and provide the exported functions, resource names, calling conventions, and target architecture required by the host program. Resource-editor workflows vary by Visual Studio version; using an explicit RCDATA entry avoids assuming that an imported PNG will become a standard Windows bitmap resource.

Use a standard icon or bitmap resource

Some programs do not search for PNG bytes. They expect a standard resource such as ICON or BITMAP. Prepare those files with desktop software such as ImageMagick:

magick image.png image.ico
magick image.png image.bmp

Declare the resource type in resources.rc:

101 ICON "image.ico"
102 BITMAP "image.bmp"

Compile and link the script with the same rc.exe and link.exe commands. An ICO file can contain multiple icon sizes and color depths. BMP conversion can remove or alter alpha transparency and usually produces a larger file. An RCDATA resource containing a PNG is not interchangeable with an ICON or BITMAP resource.

Use an existing DLL

Make a backup before editing. Resource Hacker can replace compatible icons, bitmaps, dialogs, and other resources through Action → Replace Icon or Action → Replace Bitmap; provide the format that the selected resource type accepts and save under a new filename. Replacing a raw PNG requires locating its RCDATA resource and preserving its type and identifier. Do not replace an arbitrary DLL's bytes or rename a PNG to .dll.

Use the built-in converter

For a simple packaged-resource conversion, the free converter on 101convert.com can be used without installing software. Verify that its output is a valid resource DLL, that the PNG remains accessible under the expected resource type and identifier, and that it does not need exports required by a specific application. For controlled builds or application development, the Windows SDK or Visual Studio tools provide explicit resource names, identifiers, and linker settings.

Compatibility and quality limits

• Embedding a PNG normally preserves its original bytes, lossless compression, dimensions, and alpha channel; it does not make the image executable or improve its compression.
• The consuming program must know the resource type, identifier, and data format. A generic resource-only DLL cannot satisfy an application expecting a predefined export, RT_BITMAP, an icon group, or a particular ABI.
• A 32-bit DLL must be loaded by a 32-bit process, and a 64-bit DLL by a 64-bit process. Build the library for the architecture of the host application.
• Editing a signed DLL invalidates its digital signature and may break checksums, version validation, installers, updates, or application loading. Modification also requires permission under the software's license.