Czkawka Windows HEIC support can be confusing: you scan a folder full of modern photos, but some HEIC, AVIF, or RAW files never appear. No error, no warning, just missing images.
In most cases, the issue is not Czkawka’s scanning logic. It is codec support.
The standard Windows build of Czkawka usually works well for common image formats such as JPEG and PNG. However, modern formats like HEIC, HEIF, AVIF, and camera RAW often require additional decoding libraries. Without those libraries, Czkawka may not be able to read those files properly.
This post explains why the regular Windows build may skip these formats, and how separate “additional codecs” Windows builds solve the problem by bundling the libraries needed to decode them.
The Quick Explanation
On Windows, the standard Czkawka build may not include the optional image-decoding libraries required for HEIC, HEIF, AVIF, and RAW files.
Additional-codecs builds compile Czkawka or Krokiet with those features enabled and ship the required DLLs alongside the executable. As a result, these files can be detected, decoded, and processed correctly.
In other words, if your photo library contains iPhone photos, AVIF images, or camera RAW files, the additional-codecs build may be the version you actually need.
Why Czkawka Windows HEIC Support Is Missing in the Standard Build
This issue is not unique to Czkawka. Many Windows applications ship a baseline build that supports common formats like JPEG and PNG, while leaving out formats that require extra native libraries.
There are several practical reasons for this.
Optional native dependencies
Formats like HEIC, HEIF, AVIF, and RAW usually require external C or C++ libraries. They are not always handled by simple, built-in dependencies.
That means support for these formats often needs to be enabled separately during the build process.
Windows packaging complexity
Even when the application compiles successfully, distributing the correct set of DLLs on Windows can be tricky.
The app needs those DLLs available at runtime, not just during compilation. If the DLLs are missing, misplaced, or not packaged with the executable, the application may not be able to decode the files.
Licensing and patent concerns
Some codec stacks may involve licensing, patent, or redistribution considerations. These vary by format and library, but they can make maintainers cautious about bundling everything by default.
Keeping the default build minimal reduces complexity and avoids unnecessary risk.
Build stability
A minimal Windows build is easier to maintain, reproduce, and keep stable across compiler, dependency, and CI changes.
The result is that the standard Windows artifact can be perfectly functional for common image formats, while still being unable to decode certain modern photo formats. When that happens, those files may appear to be “invisible” during scans.
Which Formats Are Most Commonly Affected?
The main formats users tend to notice are HEIC, AVIF, and RAW.
HEIC and HEIF
HEIC and HEIF files are common on iPhones and many modern phones. If you are scanning a photo library exported from a phone, this is often the first missing format you will notice.
Without the right codec support, these files may not appear in image scans or similarity comparisons.
AVIF
AVIF is increasingly used for efficient image storage and web exports. It offers strong compression, but it also requires specific decoding support.
If AVIF support is missing, these files may be skipped or ignored by image-focused tools.
Camera RAW
Camera RAW formats include files such as CR2, CR3, NEF, ARW, and DNG, depending on the camera.
RAW support is especially useful if you are scanning photography archives, but it can be more complicated because support depends on the camera format and the decoding library being used.
How Additional Codecs Improve Czkawka Windows HEIC Support
An additional-codecs build is essentially the same application, but compiled and packaged with extra image-decoding support enabled.
Typically, that means support through libraries such as:
- libheif for HEIC and HEIF files
- libavif, often with dav1d, for AVIF files
- LibRaw for camera RAW files
Just as importantly, these builds also include the required DLLs in the ZIP file. That allows the application to load the codecs properly on a clean Windows machine.
What you should notice
With the additional-codecs build:
- HEIC and HEIF images appear in scans instead of being skipped
- AVIF files are recognized correctly
- RAW files become scannable, depending on the tool mode and workflow
For users with modern photo libraries, this can make a major difference. The app itself may feel the same, but the number of files it can actually process is much better.
Download the Additional Codecs Build
I publish separate Windows additional-codecs artifacts here:
Download: https://github.com/cfelicio/czkawka/releases
Installation Instructions for Windows
- Download the additional-codecs ZIP file.
- Right-click the ZIP and choose Extract All.
- Run the included
.exefrom the extracted folder.
Important: keep the .exe and the bundled .dll files in the same directory.
If you move only the .exe somewhere else, Windows may not be able to find the codec DLLs. In that case, the app can fall back to the same “missing files” behavior.
How to Test Czkawka Windows HEIC Support
The easiest way to confirm support is working is to create a small test folder with known sample files.
Add a few files such as:
- one
.heicfile, such as an iPhone photo - one
.aviffile - one RAW file, if relevant to your workflow
Then point the app at that folder and confirm the files are detected or processed where expected.
If HEIC, AVIF, or RAW files still do not appear, the most common causes are:
- you downloaded the standard build by mistake
- the DLLs were not extracted correctly
- the
.exewas moved away from the bundled DLLs - your scan settings or extension filters exclude those formats
If you are specifically testing Czkawka Windows HEIC support, start with a known-good .heic file from an iPhone or another reliable source. That makes it easier to tell whether the problem is the build, the settings, or the file itself.
Are These Builds Official?
No. These are community or personal additional artifacts, not the primary upstream Windows release.
The goal is straightforward:
- build from the same upstream source for a given release or tag
- enable the extra codec features
- bundle the required native libraries
- make those formats work out of the box on Windows
If you maintain these builds, it is worth clearly documenting:
- which upstream tag they are built from
- which extra libraries are included
- how they differ from the default upstream Windows build
That way, users understand what they are downloading and why it differs from the standard release.
Why Not Include These Codecs in the Main Windows Build?
In an ideal world, the default build would include everything.
In practice, bundling additional codec stacks can increase:
- build time
- CI complexity
- artifact size
- native dependency maintenance
- risk of breakage when Windows toolchains change
A split approach keeps the standard Windows build simple while giving users with large photo libraries a more capable option.
For many users, the standard build is enough. But if your workflow depends on HEIC, AVIF, or RAW files, the additional-codecs build is usually the better choice.
FAQ
Does this change Czkawka’s core behavior?
No. It mainly affects whether certain image formats can be decoded and handled, especially in image-focused tools.
The duplicate-finding logic and general workflow remain the same.
Will this help if Czkawka sees the file but cannot preview it?
Often, yes. Previewing and image processing usually depend on the same decoding libraries.
If the file appears but cannot be previewed or processed correctly, missing codec support may still be the cause.
Does it support every RAW format?
Not necessarily. RAW support depends on what LibRaw supports and what your specific workflow needs.
It is a major improvement over having no RAW support, but it is not a guarantee for every camera model or every edge case.
Is AVIF support included?
Yes, in the additional-codecs build, AVIF support is included through libavif, commonly with dav1d for AV1 decoding.
Do I need the additional-codecs build if I only scan JPEG and PNG files?
Probably not. If your photo library only contains common formats like JPEG and PNG, the standard Windows build may be enough.
The additional-codecs build is most useful for users scanning modern phone photos, web image exports, or camera archives.
Conclusion: Czkawka Windows HEIC Support Matters for Photo Libraries
If you scan photo libraries on Windows, Czkawka Windows HEIC support matters.
Without the right codecs, files such as HEIC, AVIF, and RAW images may be skipped or ignored. With the additional-codecs build, Czkawka can process the formats commonly found in modern photo collections.
Same app. Same purpose. Better format support for real-world photo libraries.