The files
- catalog.json: every camera and lens, with stable IDs, mount, sensor or coverage format, focal lengths, aperture, and the manufacturer references.
- compatibility.json: the feature-by-feature findings for 60 pairs, with conditions, citations, and review dates. Schema version 1, data revision 1.
Last updated 2026-09-08. Both files are static, need no account, allow cross-origin reads, and are publicly cached for an hour.
Reading compatibility.json
Each finding belongs to one exact camera, lens, and accessory chain, in the shooting mode that was checked. The status values:
- supported
- The cited documentation says the feature works under the stated conditions.
- limited
- It works with a requirement or restriction. Keep the conditions with the answer.
- unsupported
- The documentation says it does not work.
- not_verified
- The documentation does not settle it. Do not turn this into unsupported.
A firmware value of null means the documents did not give a version range, not that every version works. A feature missing from a pair was not checked, so do not read it as supported or unsupported. A supported autofocus finding says nothing about burst rate, video autofocus, or tracking unless a separate finding covers it.
IDs and joins
Join cameraId and lensId to the catalog. Source and rule IDs resolve within the same batch. Each finding's ID is also a permanent anchor on its compatibility page, so you can link to one feature. The packetSha256 value in a review record is an internal integrity hash of the research input, not a checksum of this file.
Using it
Please link back to the relevant compatibility page and keep the citations and conditions attached to any answer you show. The findings were produced by AI agents reading manufacturer documents and have not been tested by hand. The source documents stay with their publishers, and brand names identify products only. How the research works · How we check · Report a problem