Find every duplicate STL in your library.
Meshory fingerprints every model by its actual file contents and its geometry, and finds identical copies across all the folders, drives and NAS mounts you point it at, collected into one Duplicates view. Everything runs on your machine; nothing is uploaded.
Nobody downloads a model twice on purpose.
But it happens anyway: the dragon you grabbed again months later because you couldn't find the first one. The dragon_final_FINAL.stl rename before a print. The ZIP you extracted twice into different folders. The backup drive that became a second library. A few years of collecting, and the same models are scattered across your disks under a half-dozen names, invisible in a file manager, because nothing about the filenames says they're the same.
A duplicate STL finder that compares names would miss almost all of them. Meshory compares the files themselves.
Content fingerprints, not filename guesses.
- 01
Point it at your folders
Add the folders and drives where your models already live. Meshory scans them in place, and nothing is moved, renamed, or uploaded.
- 02
Every model gets a fingerprint
Each model is fingerprinted twice: a content hash of its actual bytes, and a geometry hash of the mesh itself. Filenames, folders and file encodings don't matter, only the model.
- 03
Copies show up as one group
Files with the same fingerprint are the same model. The Duplicates view collects every copy into a single card: three downloads of the same dragon become one group listing all three locations, ready to review.
Certain matches, separated from guesses
Bulk grouping covers two certain tiers: identical file contents, and identical geometry (the same mesh saved as a different file). Rotated, rescaled or re-tessellated near-copies surface separately as “likely duplicates” for you to review, never mixed into bulk cleanup.
Local drives, NAS and archives
Network sources are duplicate-scanned too. Hashing runs in short background batches so NAS scans stay fast and the drive stays responsive. Copies inside ZIP, RAR and 7Z archives are covered as well.
You stay in control
Meshory shows you the copies. It never deletes, moves, or renames anything. Your files stay exactly where they are until you decide otherwise.
How the two tiers work
A hash finds your re-downloads and is structurally blind to your re-exports. What each tier catches, and why you want both, is in hash-based vs. geometry-aware detection.
Repair or cleanup?
If a pack's models are broken rather than redundant, that's a different job entirely. Start with cleaning up downloaded STL packs to diagnose which one you have.
The bigger cleanup
Deduplication is step one of a larger overhaul. The complete system (folders, tags, naming, thumbnails, NAS) is the guide to organizing your whole STL library.
Duplicate finder questions
Does it catch renamed copies?
Yes, that's the point. Detection uses a fingerprint of the file's actual bytes, so dragon.stl and dragon_final_FINAL.stl group together if their contents are identical, no matter which folders they live in.
Will it match edited or re-exported models?
A re-export of the same mesh groups automatically via the geometry tier, even though the file bytes differ. Heavier variants (rotated, rescaled or re-tessellated copies) appear as “likely duplicates” in a separate review tab and never join bulk cleanup. A genuinely modified model stays separate.
Which formats does it cover?
Every model Meshory indexes gets a content fingerprint: STL, 3MF, OBJ, STEP and FBX alike. Detection works on file contents, not file types.
Does it delete or modify my files?
Never. Meshory groups copies so you can see the redundancy; any cleanup is yours to do, with full information. It never moves, renames, or deletes anything in your library.
What about models on a NAS or network drive?
Covered. Network sources are indexed and browsable right away, and duplicate hashing runs in short background batches so scans stay fast and the drive stays responsive. NAS copies join the Duplicates view as the batches complete.
Will it work on a OneDrive, Google Drive or iCloud folder?
Yes. Meshory recognizes cloud-synced folders (including Google Drive's mounted drive letter) and treats them gently: duplicate hashing runs as the same paced background pass as on a NAS, and it only reads files whose size matches another file's, so it never bulk-downloads your whole library. Files it does read are downloaded by your sync client once, and you can return them to cloud-only afterwards.
Does any of this leave my machine?
No. Scanning, hashing and grouping all run locally. Your files are never uploaded; there's no cloud and no account.