Launched this week
ShutterCount.org
Check any camera's shutter count in your browser
3 followers
Check any camera's shutter count in your browser
3 followers
Drop any JPEG or RAW file from your camera and instantly see the shutter actuation count, wear status vs. manufacturer-rated life, and full EXIF metadata — focal length, lens, ISO, aperture, and more. Works with Nikon, Sony, Canon, Fujifilm, Pentax, and Ricoh. Everything is parsed in your browser using JavaScript. Your files never leave your device.
Design Zine
Hey Product Hunt 👋
I built ShutterCount after struggling to verify the shutter count on a used camera I was about to buy. The seller didn't know. Most online tools require uploading your photo to a server — which felt wrong for something this personal.
So I built a version that runs entirely in your browser. Drop a RAW or JPEG, and the EXIF and maker note data is parsed locally using JavaScript. Nothing ever leaves your device.
What it does:
→ Reads shutter actuation count from Nikon NEF, Sony ARW, Canon CR3, Fujifilm RAF, Pentax PEF, Ricoh DNG, and most in-camera JPEGs
→ Shows wear status vs. manufacturer-rated shutter life
→ Displays full EXIF metadata — lens, focal length, ISO, aperture, capture date
It's still a work in progress. Testing and adding more camera models each day.
Would love to know: does it work for your camera? And what would make this more useful to you?
RiteKit Company Logo API
@ronaldsvilcins This is a smart approach to a real problem — privacy-first tools stand out because they actually respect user data instead of just claiming to. The browser-based parsing is elegant, and I'd imagine camera enthusiasts will appreciate not having to trust a server with their image files. Curious if you're planning to add batch processing or integration with photo libraries down the line.
Design Zine
@osakasaul Thanks Saul! Batch processing is actually on the roadmap, the main thing I want to validate first is that parsing multiple RAW files in parallel doesn't bog down the browser, since some of these files (especially Sony ARW and Canon CR3) require fairly heavy binary parsing. If there's enough interest I'll prioritize it. The no-server constraint stays regardless, each file would still be parsed locally, just queued up client-side.