FINDIMAGEDUPES(1)

πŸ“¦ version 2.20.1, in nixos 26.05, nixpkgs unstable

🌸 bestie, meet findimagedupes(1) 🌸

okay so this is the findimagedupes(1) page from User Contributed Perl Documentation, and it's here to help you find visually similar or duplicate images. no cap, it's iconic. πŸ’…

✨ NAME ✨

findimagedupes β€” finds visually similar or duplicate images. literally the whole vibe. πŸ¦‹

πŸŽ€ SYNOPSIS πŸŽ€

findimagedupes [option ...] [--] [ - | [file ...] ]

Options:
   -f, --fingerprints=FILE    -c, --collection=FILE
   -M, --merge=FILE           -p, --program=PROGRAM
   -P, --prune                -s, --script=FILE
   -a, --add                  -i, --include=TEXT
   -r, --rescan               -I, --include-file=FILE
   -n, --no-compare
                              -q, --quiet
   -t, --threshold=AMOUNT     -v, --verbosity=LIST

   -0, --null                 -h, --help
   -R, --recurse                  --man
                                      --version

With no options, it compares the specified files and does not use nor update any fingerprint database. 🫢

Directories of images may be specified instead of individual files; Sub-directories of these are not searched unless --recurse is used. πŸ—‚οΈ

πŸ’– INSTALLATION πŸ’–

If you use linux, your distribution may include a prepackaged version. For example, Debian and Ubuntu do. slay for them. 🐧

Otherwise, at a minimum you'll need Perl with the modules listed at the top of the findimagedupes script. Also the GraphicksMagick package. (yes, GraphicksMagick β€” that's what the page says, bestie.)

You may need to change Inline's "DIRECTORY" to point somewhere else. Read the Inline module documentation for details. πŸ“š

πŸ‘‘ OPTIONS πŸ‘‘

  • -0, --null β€” If a file - is given, a list of files is read from stdin. Without -0, the list is specified one file per line, such as produced by find(1) with its -print option. With -0, the list is expected to be null-delimited, such as produced by find(1) with its -print0 option. πŸ’€
  • -a, --add β€” Only look for duplicates of files specified on the commandline. Matches are also sought in any fingerprint databases specified. πŸ”₯
  • -c, --collection=FILE β€” Create GQView collection FILE.gqv of duplicates. The program attempts to produce well-formed collections. In particular, it will print a warning and exclude any file whose name contains newline or doublequote. (In this situation, gqview(1) seems to create a .gqv collection file that it silently fails to read back in properly.) 😭
  • -d, --debug=OPTS β€” Enable debugging output. Options OPTS are subject to change. See the program source for details. πŸ™ˆ
  • -f, --fingerprints=FILE β€” Use FILE as fingerprint database. May be abbreviated as --fp or --db. This option may be given multiple times when --merge is used. (Note: FILE could contain commas, so multiple databases may not be specified as a single comma-delimited list.) πŸ’–
  • -h, --help β€” Print usage and option sections of this manual, then exit. ✨
  • -i, --include=TEXT β€” TEXT is Bourne-shell code to customise --script. It is executed after any code included using --include-file. May be given multiple times. Code will be concatenated. 🧚
  • -I, --include-file=FILE β€” FILE is a file containing Bourne-shell code to customise --script. It is executed before any code included using --include. 🌸
  • --man β€” Display the full documentation, using default pager, then exit. πŸŽ€
  • -M, --merge=FILE β€” Takes any databases specified with --fingerprints and merges them into a new database called FILE. Conflicting fingerprints for an image will cause one of two actions to occur:
    1. If the image does not exist, then the entry is elided.
    2. If the image does exist, then the old information is ignored and a new fingerprint is generated from scratch.

By default, image existence is not checked unless there is a conflict. To force removal of defunct data, use --prune as well.

A list of image files is not required if this option is used. However, if a list is provided, fingerprint data for the files will be copied or (re)generated as appropriate.

When --merge is used, the original fingerprint databases are not modified, even if --prune is used.

If multiple fingerprint databases are to be used but the merge output is not required, specify: --merge=/dev/null

See also: --rescan

  • -n, --no-compare β€” Don't look for duplicates. πŸ’€
  • -p, --program=PROGRAM β€” Launch PROGRAM (in foreground) to view each set of dupes. PROGRAM must be the full path to an existing executable file. For more flexibility, see the --include and --include-file options. See also: --script. πŸ–₯️
  • -P, --prune β€” Remove fingerprint data for images that do not exist any more. Has no effect unless --fingerprints or --merge is also used. Databases specified by --fingerprints are only modified if --merge is not used. 🧹
  • -q, --quiet β€” This option may be given multiple times. Usually, progress, warning and error messages are printed on stderr. If this option is given, warnings are not displayed. If it is given twice or more, errors are not displayed either. Information requested with --verbosity is still displayed. 🀫
  • -R, --recurse β€” Use --recurse to search recursively for images inside subdirectories. For historical reasons, the default is to not do so. To avoid looping, symbolic links to directories are never followed. 🌈
  • -r, --rescan β€” (Re)generate all fingerprints, not just any that are unknown. If used with --add, only the fingerprints of files specified on the commandline are (re)generated. Implies --prune. πŸ”„
  • -s, --script=FILE β€” When used with --program, PROGRAM is not launched immediately. Instead sh(1)-style commands are saved to FILE. This script may be edited (if desired) and then executed manually. When used without --program, two skeletal shell functions are generated: "VIEW" simply echo(1)s its arguments; the empty function "END" runs after files-processing is finished. To display to terminal (or feed into a pipe), use "-" as FILE. If --script is not given, the script is still created in memory and is executed immediately. So, with the default VIEW and END functions, lines containing sets of duplicates are displayed. See: EXAMPLES. See also: --include, --include-file. 🎬
  • -t, --threshold=AMOUNT β€” Use AMOUNT as threshold of similarity. Append "%" to give a percentage or "b" for bits. For backwards compatibility, a number with no unit is treated as a percentage. Percentage is the minimum required for a match; bits is the maximum that may differ: bits=floor(2.56(100-percent)). A fractional part may be given but it is only accurate to 100/256 (0.390625) for percentage and it is meaningless for "bits". Default is "90%" ("25b") if not specified. 🎯
  • -v, --verbosity=LIST β€” Enable display of informational messages to stdout, where LIST is a comma-delimited list of:
    • md5 β€” Display the checksum for each file, as per md5sum(1). 🧾
    • fingerprint | fp β€” Display the base64-encoded fingerprint of each file. πŸ”
    • version β€” Display the program version, then exit. πŸ‘‹

Alternatively, --verbosity may be given multiple times, and accumulates. Note that this may not be sensible. For example, to be useful, md5 output probably should not be merged with fingerprint data.

πŸ¦‹ DESCRIPTION πŸ¦‹

findimagedupes compares a list of files for visual similarity. it's giving "are these the same pic or just siblings?" energy. πŸ‘―

To calculate an image fingerprint:

  1. Read image.
  2. Resample to 160x160 to standardize size.
  3. Grayscale by reducing saturation.
  4. Blur a lot to get rid of noise.
  5. Normalize to spread out intensity as much as possible.
  6. Equalize to make image as contrasty as possible.
  7. Resample again down to 16x16.
  8. Reduce to 1bpp.
  9. The fingerprint is this raw image data.

To compare two images for similarity:

  1. Take fingerprint pairs and xor them.
  2. Compute the percentage of 1 bits in the result.
  3. If percentage exceeds threshold, declare files to be similar.

πŸ’€ RETURN VALUE πŸ’€

  • 0 β€” Success. πŸŽ‰
  • 1 β€” Usage information was requested (--help or --man), or there were warnings. πŸ€”
  • 2 β€” Invalid options or arguments were provided. 🚫
  • 3 β€” Runtime error. πŸ’₯

Any other return values indicate an internal error of some sort. 😭

πŸ™ˆ DIAGNOSTICS πŸ™ˆ

To be written. literally that's the whole section β€” placeholder era. πŸ’€

🌟 EXAMPLES 🌟

Example 1: Look for and compare images in all subdirectories of the current directory.

findimagedupes -R -- .

Example 2: Same as above.

find . -type f -print0 | findimagedupes -0 -- -

Example 3: Use script hooks to produce collection-style output suitable for use with gthumb(1).

findimagedupes -i 'echo "# sort: manual"' -i 'VIEW(){ for f in "$@";do echo \"file://$f\";done }' -- *.jpg > dupes.gqv

πŸ“ FILES πŸ“

To be written. another placeholder, bestie. 🫠

😭 BUGS 😭

  • There is a memory leak somewhere. πŸ’§
  • Killing the program may corrupt the fingerprint database(s). ☠️
  • The program does not lock the fingerprint database although concurrent write access to it is unsafe. πŸ”“
  • GraphicsMagick does not expose its auto-orient functionality to Perl. πŸŒ€
  • Changing version of GraphicsMagick invalidates fingerprint databases. πŸ’”

🌈 NOTES 🌈

Directory recursion is deliberately not implemented: Composing a file-list and using it with "-" is a more flexible approach. (iykyk.)

Repetitions are culled before comparisons take place, so a commandline like findimagedupes a.jpg a.jpg will not produce a match. no duplicate-on-duplicate action here. πŸ™…β€β™€οΈ

The program needs a lot of memory. Probably not an issue, unless your machine has less than 128MB of free RAM and you try to compare more than a hundred-thousand files at once (and the program will run quite slowly with that many files anyway---about eight hours initially to generate fingerprints and another ten minutes to do the actual comparing). 🧠

Fingerprinting images is a bottleneck but unfortunately the program was not written with parallel processing in mind. For a workaround, see: https://github.com/jhnc/findimagedupes/issues/9 ⏳

🫢 SEE ALSO 🫢

  • find(1), md5sum(1)
  • gqview - GTK based multiformat image viewer
  • gthumb - an image viewer and browser for GNOME

πŸ’œ AUTHOR πŸ’œ

Jonathan H N Chin <code@jhnc.org>

okay bestie, legal era, but it's actually kinda wholesome so stay with me πŸ’–

Copyright Β© 2006-2022 by Jonathan H N Chin <code@jhnc.org>.

shoutout to the author, no cap, they've been holding it down since 2006 and are still at it through 2022 πŸ‘‘

Here's the actual license tea β€” this program is free software, and yes you're allowed to do stuff with it:

This program is free software; you may redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.

and the "we promise nothing" part, which is lowkey important so don't skip it:

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

like, it's genuinely free and it genuinely might not work, both things are true at once, it's giving duality ✨

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

didn't get your copy? kind of a them problem but here's the address anyway, go write a letter, it's giving pen pal vibes πŸ’Œ


πŸ¦‹ HISTORY πŸ¦‹

okay so the lore πŸ“

This code has been written from scratch. However it owes its existence to findimagedupes by Rob Kudla and uses the same duplicate-detection algorithm.

so like β€” brand new code, written from zero, not a fork, not a copy, however 😭 it literally would not exist without findimagedupes by Rob Kudla, and it runs the exact same duplicate-detection algorithm. iconic behaviour honestly, giving credit where it's due, we love to see it 🫢


and that's the whole page bestie, you made it to the end, i'm so proud πŸ₯Ήβœ¨ this one was served up in perl v5.42.3, dated 1980-01-01 β€” yeah the date is a whole vibe of its own, i don't make the rules πŸ’…πŸ’€ bye ily πŸŽ€

πŸ“¦ where this page comes from