About the project
Useful evidence, without false certainty.
ShutterActuations helps photographers understand what is embedded in an image while keeping the image on their own device.
Why this exists
Camera files can contain valuable technical history and surprisingly sensitive personal information. Existing tools often upload files, reduce the result to a single number, or imply that shutter-count detection works universally. This project takes a more careful approach.
Who maintains the project
ShutterActuations is an independently maintained camera-metadata project. The site maintainer is responsible for the checker, the explanatory guides, and the published research. Articles attributed to ShutterActuations describe work performed for this project; they do not imply endorsement by Nikon, Canon, OM System, or another camera manufacturer.
The experience documented here is practical software testing: running original camera files through the browser reader, comparing source tags, checking file-format boundaries, and observing network behavior. We do not claim to be a camera manufacturer’s service center or to have physically inspected the cameras represented in a public sample collection.
Our official public contact is contact@shutteractuations.com for questions, privacy concerns, and corrections. See the contact page for useful report details. Begin with the page or model involved rather than a private photograph.
How results are interpreted
Every shutter-count candidate is evaluated using its original tag name, metadata group, camera make and model, and available manufacturer context. A regular filename or image sequence counter is never presented as a verified shutter count.
Current scope
The interface accepts Nikon NEF, JPEG/JPG, TIFF, DNG, and browser-readable HEIC/HEIF or AVIF. The first pass reads available metadata; an optional local ExifTool WebAssembly reader inspects deeper manufacturer fields. Deeper MakerNote results remain model- and file-dependent.
What the published testing covers
The September 2026 corpus run covered 1,870 CC0 RAW files representing 931 camera-model labels across 85 manufacturers. The engine parsed 1,832 files, and 527 contained strongly named candidate counters. Research formats and production-accepted formats are reported separately.
For Nikon, all 273 NEF samples parsed and 264 exposed strongly named counters across 74 model labels. Application checks include a representative D40X original and a cached D2H sample that repeatedly yielded Nikon:ShutterCount = 4,350. These are file-level observations, not independent service verification of those cameras’ lifetime mechanical use.
Read the research report and sample evidence, repeat the D2H case study, or inspect our testing method and evidence levels.
Sources, attribution, and corrections
DETECTED ≠ VERIFIED: finding a named field is not independent verification of its physical meaning or lifetime total. Our 273-file Nikon report shows model-level findings, counter differences and negative examples.
Public samples come from the raw.pixls.us collection under their recorded licenses; we do not present them as our own photography. ExifTool provides manufacturer-tag documentation and decoding capabilities. Our contribution is the local browser workflow, compatibility measurements, selected comparisons, and practical interpretation of their limits.
Research articles identify source records and test dates where available. A correction should include the affected sentence, exact model or sample, and supporting evidence. Counter semantics, file acceptance, and mobile reliability are reviewed separately so a successful parse cannot silently become a universal support claim.
Editorial illustrations are labeled when generated with AI. They are not photographs of test hardware or proof of a recorded result. Hypothetical buyer scenarios are labeled separately from measured metadata.
Independence
The checker has no accounts or payments. It reads embedded metadata; it does not use AI to analyze your photograph or alter the image. Cloudflare Web Analytics is currently used for aggregate website usage and performance measurement; it operates separately from the local photo checker, which does not upload selected photos or extracted camera metadata for analysis.
Read the privacy explanation for the distinction between checking a file locally and choosing to share one for a separate research discussion.