dupeguru VS jdupes

Dupeguru

Posted link appears be misspelled

This appears to be actual link:

https://dupeguru.voltaicideas.net/

I used to use DupeGuru which has some photo-specific dupe detection where you can fuzzy match image dupes based on content: https://dupeguru.voltaicideas.net/

But I switched over to czkawka, which has a better interface for comparing files, and seems to be a bit faster: https://github.com/qarmin/czkawka

Unfortunately, neither of these are integrated into Photoprism, so you still have to do some file management outside the database before importing.

I also haven't used Photoprism extensively yet (I think it's running on one of my boxes, but I haven't gotten around to setting it up), but I did find that it wasn't really built for file-based libraries. It's a little more heavyweight, but my research shows that Nextcloud Memories might be a better choice for me (it's not the first-party Nextcloud photos app, but another one put together by the community): https://apps.nextcloud.com/apps/memories

If your photos are exact duplicates you can also use the freeware dupeGuru app.

If you want a some other GUI options, AllDup or DupeGuru might be of interest. AllDup has a rather weird interface, though, imo.

I used DupeGuru (https://dupeguru.voltaicideas.net/) in the past but I'm not sure it's the best solution for you. Try it, it's open-source.

dupeGuru

dupeGuru is a graphical application available for macOS that can scan multiple drives and identify duplicate files based on various criteria like name, size, and content https://dupeguru.voltaicideas.net/

I recommend the use of jdupes, a fork of the well-known fdupes, to find duplicate files.

200 lines of Nim [1] seems to run about 9X faster than the 8000 lines of C in fdupes on a little test dir I have. If you need C, I think jdupes [2] is faster as @TacticalCoder points out a couple of times here. In my testing, `dups` is usually faster than `jdupes`, though.

[1] https://github.com/c-blake/bu/blob/main/dups.nim

[2] https://github.com/jbruchon/jdupes

There's always the well-respected tool, Czkawka. Or, of the CLI is your thing, jdupes is a good option.

My research into this many years ago turned out that jdupes was the right / best solution I could find for my usecase.

https://github.com/jbruchon/jdupes

Though that works fine from a script perspective I'd like some more interactive way of sorting directories etc. Identifying is just the first step, jdupes helps with linking the files (both soft and hard links comes with caveats though!) but that is mostly to save space, not to help in reorganisation.

I can work it out by looking at https://github.com/jbruchon/jdupes.

I have looked at a few alternatives and think jdupes is the one for me. Then I found out it was not multi-threaded so will give it a go but the developer of jdupes recomended fclones (https://github.com/jbruchon/jdupes/issues/186) if you were dealing with large file systems and wanted multi-threading. But as I am using a HD it may not be necessary.

jdupes is a fork of the old standby fdupes, but it has a Win32 release as well as supporting POSIX.

jdupes is a tuned fork of the well-known fdupes, and has Win32 releases.