Czkawka for now contains two independent frontends - the terminal and graphical interface which share the core module. Using Rust language without unsafe code, helps to create safe, fast with small resource requirements. This code also has good support for multi-threading.
The GUI are built from different pieces:
- Red - Program settings, contains info about included/excluded directories which user may want to check. Also there is a tab with allowed extensions, which allow user to choose which type of files want to check. Next category is Excluded items, which allow to discard specific path with use of
*wildcard -/home/*means that e.g./home/rafal/will be ignored but no/home/czkawka/. The last one is settings tab which allow to save configuration of program, reset it and load it when needed. - Green - This allow to choose which tool we want to use.
- Blue - Here are settings to current tool, which we want/need to configure
- Pink - Window in which result of searching are printed
- Yellow - Box with buttons like
Search(starts searching with current selected tool),Hide Text View(hide text box at the bottom with white overlay),Symlink(create symlink to selected file),Select(shows options to select specific rows),Delete(deletes selected records),Save(save to file result of searching) - some buttons are only visible when at least one result is visible. - Brown - Small informative field to show informations e.g. about number of found duplicates files
- White - Text window to show possible errors/warnings e.g. when failed to delete folder due no permissions etc.
There is also an option to see image previews in Similar Images tool.
There are several buttons which do different actions:
- Search - starts searching and shows progress dialog
- Stop - button in progress dialog, allows to easily stop current task. Sometimes it may take a few seconds until all atomic operations ends and GUI will be able to use again
- Select - allows selecting multiple entries at once
- Delete - delete entirely all selected entries
- Symlink - create symlink to selected files(first file is threaten as original and rest will become symlinks)
- Save - save initial state of results
- Hamburger(parallel lines) - used to show/hide bottom text panel which shows warnings/errors
- Add (directories) - adds directories to include or exclude
- Remove (directories) - remove directories to search or to exclude
- Manual Add (directories) - allows to write by hand directories(may be used to write non visible in file manager directories)
- Save current configuration - saves current GUI configuration to configuration file
- Load configuration - loads configuration of file and override current GUI config
- Reset configuration - reset current GUI configuration to default
It is possible to open selected files by double clicking at them.
To open multiple file just select desired files with CTRL key pressed and still when clicking this key, double click at selected items with left mouse button.
To open folder containing selected file, just click twice at it with right mouse button.
Czkawka CLI frontend is great to automate some tasks like removing empty directories.
To get general info how to use it just try to open czkawka_cli in console czkawka_cli
You should see a lot of examples how to use this app.
If you want to get more detailed info about certain tool, after its name just write at the end -h or --help to get more details about tool.
By default all tools only write about results to console, but it is possible with specific arguments to delete some files/arguments or save it to file.
For now Czkawka store few config and cache files on disk:
czkawka_gui_config.txt- stores configuration of GUI which may be loaded at startupcache_similar_image.txt- stores cache data and hashes which may be used later without needing to compute image hash again - editing this file may cause app crashes.cache_broken_files.txt- stores cache data of broken filescache_duplicates_Blake3.txt- stores cache data of duplicated files, to not get too big performance hit when saving/loading file, only already fully hashed files bigger than 5MB are stored. Similar files with replacedBlake3to e.g.SHA256may be shown, when support for new hashes will be introduced in Czkawka.
Config files are located in this path
Linux - /home/username/.config/czkawka
Mac - /Users/username/Library/Application Support/pl.Qarmin.Czkawka
Windows - C:\Users\Username\AppData\Roaming\Qarmin\Czkawka\config
Cache should be here:
Linux - /home/username/.cache/czkawka
Mac - /Users/Username/Library/Caches/pl.Qarmin.Czkawka
Windows - C:\Users\Username\AppData\Local\Qarmin\Czkawka\cache
- Manually adding multiple directories
You can manually edit config fileczkawka_gui_config.txtand add/remove/change directories as you want. After setting required values, configuration must be loaded to Czkawka. - Slow checking of little number similar images
If you checked before a big amount of images(several tens of thousands) and them still exists on disk, then information's about it are loaded from cache and save to it, even if you have check now only a few images. You can rename cache filecache_similar_image.txt(to be able to use it again) or delete it - cache will regenerate but with lower amount of entries it should load and save a lot of faster.
Duplicate Finder allows you to search for files and group them according to a predefined criterion:
-
By name - Groups files by name e.g.
/home/john/cats.txtwill be treated like a duplicate of a file named/home/lucy/cats.txt. This is the fastest method, but it is very unreliable and should not be used unless you know what you are doing. -
By size - Groups files by their size (in bytes and perfect matches only). It is as fast as the previous mode and usually gives better results with duplicates, but I also do not recommend using it if you do not know what you are doing.
-
By hash - A mode containing a check of the hash (cryptographic hash) of a given file which determines with great probability whether the files are identical.
This is the slowest, but almost 100% sure way to check the files.
Because the hash is only checked inside groups of files of the same size, it is practically impossible for two different files to be considered identical.
It consists of 3 steps:
-
Grouping files of identical size - allows you to throw away files of unique size, which are already known to have no duplicates at this stage.
-
PreHash check - Each group of files of identical size is placed in a queue using all processor threads (each action in the group is independent of the others). In each such group a small fragment of each file (2KB) is loaded in turn and then hashed. All files whose partial hashes are unique within the group are removed from it. Using this step usually allows me to reduce the time of searching for duplicates even by half.
-
Checking the hash - After leaving files that have the same beginning in groups, you should now check the whole contents of the file to make sure they are identical.
-
-
By hashmb - Works the same way as via hash, only in the last phase it does not check the whole file but only its first megabyte. It is perfect for quick search of possible duplicate files.
Searching for empty files is easy and fast, because we only need check the file metadata and its length.
At the beginning, a special entry is created for each directory containing - the parent path (only if it is not a folder directly selected by the user) and a flag to indicate whether the given directory is empty (at the beginning each one is set to be potentionally empty).
First, user-defined folders are put into the pool of folders to be checked.
Each element is checked to see if it is
- folder - this folder is added to the check queue as possible empty -
FolderEmptiness::Maybe - anything else - the given folder is "poisoned" with the
FolderEmptiness::Noflag, indicating that the folder is no longer empty. Then each folder directly or indirectly containing the file is also poisoned with theFolderEmptiness::Noflag.
Example: there are 4 checked folders which may be empty /cow/, /cow/ear/, /cow/ear/stack/, /cow/ear/flag/.
The last folder contains a file, so that means that /cow/ear/flag is not empty and also all its parents - /cow/ear/ and /cow/,
but /cow/ear/stack/ may still be empty.
Finally, all folders with the flag FolderEmptiness::Maybe are defaulted to empty.
From each file inside the given path its size is read and then after sorting it, e.g. 50 largest files are displayed.
Searching for temporary files only involves comparing their extensions with a previously prepared list.
Currently files with this extensions are considered as temporary files -
["#", "thumbs.db", ".bak", "~", ".tmp", ".temp", ".ds_store", ".crdownload", ".part", ".cache", ".dmp", ".download", ".partial"]
Zeroed files very often are results of e.g. incorrect file downloads.
Their search consists of 3 parts:
- Collecting a list of all files with a size greater than 0
- At start, 64 bytes of each file are checked to discard the vast majority of non-zero files without major performance losses.
- The next step is to check the rest of the file with bigger parts(32KB)
To find invalid symlinks we must to find first a symlnks.
After searching for them you should check at which element it points to and if it does not exist, add this symlinks into the list of invalid symlinks, pointing to a non-existent path.
The second mode is to detect recursive symlink. Unfortunately, this mode does not work and it display when using it, an error of a non-existent target element, but it is implemented by counting the jumps of the symlink and after exceeding a certain number (e.g. 20) it is considered that the given symlink is recursive.
This is a mode to find identical music files through tags.
The number of tags to choose from is limited by an external library.
First, music files with one of the extensions [".mp3", ".flac", ".m4a"] are collected.
Then for each music file its tags are read.
Then, for each selected tag by which we want to search for duplicates, we perform the following steps
- For each input file we read the value of the currently checked tag
- If it is empty, we ignore the file, if it has a value, we throw it into an array whose key is this value
- After checking all files, arrays containing only one element are deleted
- The remaining files are used as initial data for checking the next tag selected by the user
- After checking all tags, the results are displayed in groups
It is a tool for finding similar images that differ e.g. in watermark, size etc.
The tool first collects images with specific extensions that can be checked - [".jpg", ".jpeg", ".png", ".bmp", ".tiff", ".tif", ".pnm", ".tga", ".ff", ".gif", ".jif", ".jfi", ".ico", ".webp", ".avif"].
Next cached data are loaded from file to prevent hashing twice same file.
Automatically cache which points to non existing data is deleted.
Then a perceptual hash is created for each image which isn't available in cache.
Cryptographic hash (used for example in ciphers) for similar inputs gives completely different outputs
11110 ==> AAAAAB
11111 ==> FWNTLW
01110 ==> TWMQLA
Perceptual hash at similar inputs, gives similar outputs
11110 ==> AAAAAB
11111 ==> AABABB
01110 ==> AAAACB
Computed hash data is then thrown into a special tree that allows to compare hashes using Hamming distance.
Next this hashes are saved to file, to be able to opens images without needing to hash it more times.
Finally, each hash is compared with the others and if the distance between them is less than the maximum distance specified by the user, the images are considered similar and thrown from the pool of images to be searched.
This tool is created to find files which are corrupted or have invalid extension.
At first files from specific group(image,archive,audio) are collected and then this files are opened.
If an error happens when opening this file then it means that this file is corrupted or unsupported.
Only some file extensions are supported, because I rely on external crates. Also some false positives may be shown(e.g. image-rs/jpeg-decoder#130) so always open file to check if it is really broken.