A Mac app that finds files from plain-language searches such as “pdfs from gmail last week”, "videos over 1GB", "photos from Greece" and by the text inside images and PDFs. Everything stays on the Mac.
This is exactly how I think about files — by what was in them or where they came from, not the filename. I like that it all stays local too. Curious how it holds up on a big library: does it build its own index or lean on Spotlight, and how does re-indexing work when a lot of files change at once?
Looking for a file by what was inside it is much closer to how people remember their work. Combining that with limits like file type or size would make a vague memory easier to narrow down.
About Findy on Product Hunt
“Find Files on Your Mac by what you remember”
Findy launched on Product Hunt on November 16th, 2026 and earned 78 upvotes and 7 comments, placing #21 on the daily leaderboard. A Mac app that finds files from plain-language searches such as “pdfs from gmail last week”, "videos over 1GB", "photos from Greece" and by the text inside images and PDFs. Everything stays on the Mac.
Findy was featured in Productivity (665.8k followers) and User Experience (369.8k followers) on Product Hunt. Together, these topics include over 216.4k products, making this a competitive space to launch in.
Who hunted Findy?
Findy was hunted by Adrian Topka. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Findy stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
This is exactly how I think about files — by what was in them or where they came from, not the filename. I like that it all stays local too. Curious how it holds up on a big library: does it build its own index or lean on Spotlight, and how does re-indexing work when a lot of files change at once?