Camera → trigger → flash compatibility

Will your whole flash chain actually work?

Choose a camera body, wireless trigger and flash or strobe. The lab separates basic firing from TTL, HSS, rear-curtain sync and radio-protocol compatibility—and shows when evidence is only partial.

Dataset reviewed 2026-09-27 · primary manufacturer evidence
Manufacturer-source backedUnknown ≠ incompatibleShareable setup linksNo account required
200camera bodies
40trigger variants
46flash / strobe choices
Choose your workflow

What are you trying to solve?

Start from the decision, not the catalog. The same evidence engine powers every path, so a quick route never weakens the compatibility rules.

03Plan a multi-light kitFind one trigger that can control every selected light with the features you require.04Explore coverage firstInspect exact body-test coverage before you commit to a camera or trigger ecosystem.
01

Start with your camera

We narrow everything else down from the exact body.

Quick start with a common bodySets the exact camera and opens the verified-only path. You can change it below.
Choose a camera to see only the trigger and flash paths that are fully verified in the current manufacturer-backed dataset.
✓

Pick your camera

Verified setups will appear as guided choices. No compatibility guesswork, no giant product list.

Manufacturer evidenceFeature-level checksNo account
Layered compatibility

Why a generic “compatible” label is not enough

The hot shoe can fit while TTL fails. A radio trigger can fire a strobe while HSS is unavailable. Two products can both say 2.4 GHz and still use incompatible protocols. FlashChain Lab keeps those layers separate.

Evidence standard

Evidence, not guesses

Model-level support is Verified only when the body appears in the encoded manufacturer-tested set or a product page explicitly lists it. Brand-level claims are Partial. Untested combinations remain Unknown.

Which flash problem are you solving?