Lens Chief Ray Angle (CRA) and CRA Mismatch: How to Match a Lens to Your Image Sensor
A lens can cover the sensor format, thread on cleanly, and meet its MTF spec, and still ship magenta corners. Chief ray angle is the compatibility check most spec reviews skip.
Chief ray angle (CRA) is the angle between the optical axis and the chief ray (the ray from an off-axis scene point through the center of the aperture stop), measured at the image plane. CRA mismatch is when the lens's ray angles deviate from the incidence angles the sensor's microlens array was built to accept, producing corner color shading, crosstalk, and illumination falloff. Match lens edge CRA to the sensor's design CRA within roughly ±3°, then confirm with flat-field and corner MTF measurements.
What is the chief ray angle (CRA) of a lens?
Chief ray angle (CRA) is the angle between the chief ray (the ray from an off-axis object point that passes through the center of the aperture stop) and the optical axis at the image plane. CRA grows with image height, so the single value quoted for a lens is usually the maximum at the edge of the image circle.
On axis, light arrives perpendicular to the pixel. Toward the corner the bundle tilts more, and the datasheet CRA curve plots that tilt against image height. To first order the angle is set by the exit pupil position:
Exit pupil distance is the design lever, and vendors often quote it even when the full CRA curve is not. Sit it far from the image plane and chief rays stay nearly perpendicular (approaching image-space telecentricity), but the lens needs larger rear-group apertures and a longer body. Compact modules push it close to the sensor to cut z-height, and edge CRA climbs to 25–35° in mobile-heritage designs.
CRA is a separate axis of compatibility from focal length and coverage. The Commonlands field of view calculator and EFL calculator settle the geometric side of lens selection; CRA decides whether the light that geometry delivers reaches the pixels efficiently.
What is CRA mismatch between a lens and a sensor?
CRA mismatch is the difference between the lens's chief ray angle and the incidence angle the sensor's microlenses were designed to accept at the same image height. Each pixel sits under a microlens; sensor designers shift those microlenses laterally toward the optical axis so that oblique light still lands on the photodiode.
A 0° CRA sensor has microlenses centered over each photodiode and expects near-perpendicular light. A 28° CRA sensor offsets its microlenses progressively toward the array center, tuned for a lens that tilts edge bundles steeply. Datasheets publish this acceptance curve against image height, as a linear profile or a non-linear one shaped for a specific lens family.
CRA mismatch is a design incompatibility, not an assembly defect. Sensor tilt, decenter, and defocus are mechanical errors with their own diagnostics, covered in the Commonlands sensor alignment guide. The two interact: with tilt or decenter present, the mismatch turns asymmetric and harder to correct, since one corner runs at a larger effective angle than its opposite.
How does CRA mismatch cause color shading and vignetting?
CRA mismatch reduces light capture, drives optical crosstalk between neighboring pixels, and produces radial color shading (often a magenta or green corner tint) plus illumination falloff beyond the lens's natural cos⁴ roll-off. Because the loss differs per color channel on Bayer sensors, luma-only flat-field correction lifts brightness but leaves a chroma error. Per-channel correction holds only under the calibration illuminant.
The color shading is a Bayer effect. An oblique ray that enters through a green filter can land partly on the neighboring red or blue photodiode, and each channel has a slightly different acceptance geometry through the cover glass stack, so the crosstalk is asymmetric across channels.
That is why RGB sensors are more sensitive than monochrome. A mono sensor collects every photon into one channel, so angular error costs signal without a color signature, and it tolerates a substantially wider mismatch. Push an RGB part past its limit and the tint deepens while the image signal processor's (ISP's) corrective corner gain amplifies noise, hurting low-light and HDR performance.
Even a matched pairing loses some corner illumination to the lens's natural cosine-fourth falloff. Mismatch adds channel-dependent loss on top, which is why mismatched corners look both dark and tinted. Baseline falloff and image circle margin are covered in the relative illumination guide. For separating CRA-induced corner softness from ordinary aberration falloff, corner measurements in the MTF curve guide show a healthy center-to-corner gap.
Why do image sensors ship in multiple microlens CRA variants?
Sensor manufacturers sell the same silicon with different microlens shift profiles, called CRA variants, under different ordering codes. So the variant, not just the sensor model, determines which lenses pair cleanly. Confirm the exact microlens/CRA option with the manufacturer.
The driver is packaging: a thin phone module forces the exit pupil close to the sensor and edge CRA to 25–35°, while an industrial camera has room for a longer lens with near-perpendicular chief rays. Their microlens shift and profile differ accordingly.
| Application class | Typical design CRA | CRA profile | なぜ |
|---|---|---|---|
| Mobile and consumer | 25–35° at image edge | Non-linear, tuned to a lens family | Enables thin modules under 10mm z-height |
| Industrial and machine vision | 0–15° at image edge | Linear | Matches conventional glass optics with distant exit pupils |
Put the microlens variant on the purchase order, not just the sensor model: two reels of the "same" sensor with different CRA variants behave like different parts on the line. If the design still has sensor flexibility, prefer a low-CRA industrial variant, which accepts the widest range of machine vision optics. The Commonlands sensor reference pages list format dimensions and pixel specifications for common parts.
What CRA tolerance should you target?
Match lens edge CRA to the sensor's microlens design CRA within roughly ±3° for clean corners with minimal ISP correction. Acceptance limits widen as design CRA falls: low-CRA industrial sensors (below 10°) tolerate a relatively wide mismatch before artifacts become unacceptable.
| Sensor design CRA | Typical RGB tolerance | Common applications |
|---|---|---|
| Below 10° | Widest | Machine vision, industrial inspection |
| 10–20° | 中程度 | Security, automotive |
| Above 20° | Narrowest | Consumer, mobile |
Monochrome versions tolerate a wider mismatch than the RGB tolerance shown, since they carry no color channels to unbalance. Treat every figure here as a screening threshold, not a guarantee. The real limit depends on the datasheet CRA curve, cover glass stack, wavelength band, and how much ISP correction is acceptable in production. NIR needs extra care, because microlens angular response is wavelength dependent, so a pairing that passes in visible light can shade differently at 850nm. The Commonlands NIR imaging guide covers band-specific validation.
CRAの不一致はソフトウェアで修正できますか？
Only partially. A shading calibration works in fixed lighting, but it encodes the spectrum of the light source it was built under. Change the illuminant (daylight to LED, warm to cool office light) and the per-channel corner loss changes shape, because the crosstalk is wavelength dependent, so the cast returns in a different color. Software also cannot recover lost signal: corner gain raises noise, and edge contrast that was never captured is gone.
The practical hierarchy Commonlands recommends: fix the mismatch optically with a compatible lens or the right sensor CRA variant, then let the ISP clean up the small residue. A ±3° residual is a routine calibration task; a 20° mismatch is a science project that may still miss quality targets in some lighting.
How do you test for CRA mismatch in the lab?
Test with flat-field captures and corner MTF, not datasheet values alone. Photograph a uniform white target under representative lighting, map center-to-corner brightness per color channel, then run slanted-edge MTF (per ISO 12233) at the corners. Compare 2–3 lens candidates on the same rig and pick the one needing the least correction.
- Define constraints first. Sensor model and exact CRA variant, pixel size, datasheet CRA curve, cover glass stack, wavelength band, target F/#, and the ISP correction overhead you can accept.
- Build a lens shortlist. Screen for image circle coverage and focal length, then filter for CRA compatibility against the sensor curve. Include a known-stable baseline such as the Commonlands Low Distortion 1.8mm M12 Lens (CIL018).
- Capture flat fields. Uniform white target at three or more gain and exposure settings per candidate. Compute per-channel imbalance at 80% of image radius as the primary CRA indicator.
- Run corner MTF. Slanted-edge target at the corner under production-like focus, temperature, and illumination. CRA crosstalk shows up as contrast loss near Nyquist (0.5 cycles per pixel).
- Decide go/no-go. The ISP gain map needed to equalize corner brightness and SNR is a direct proxy for mismatch severity. Accept the candidate needing the least correction. After shading correction, reject any whose corner SNR at your darkest specified illuminance, or whose corner MTF at your target frequency, falls below spec.
Keep the geometry fixed: hold working distance constant between tests. M12 lenses typically have a fixed aperture, so each candidate runs at its own F/#. The depth of field calculator helps pick a working distance that keeps every candidate in usable focus. For measured MTF evidence on a calibrated bench, the Commonlands Trioptics HR2 MTF testing service ($199) compares candidates before a design commitment.
How do you match M12 lenses to Sony IMX sensors?
Confirm the active-area diagonal, pull the CRA curve for the exact IMX variant from the datasheet, shortlist 2–3 M12 lenses that cover the format, and benchmark flat fields and corner MTF on one rig. Lock the design on the lens that needs the smallest correction gain map.
Sony IMX sensors dominate compact embedded vision, and many M12 lenses target IMX-class formats. That does not mean any M12 lens pairs cleanly with any IMX part: acceptance CRA varies across the family and across microlens variants of the same part. Two IMX-specific cautions sit on top of the lab method above.
Confirm the diagonal from the datasheet active-area dimensions, not the nominal format name. A label like 1/2.3" or 1/4" is not a reliable proxy for the true diagonal. The CMOS sensor size guide explains the naming gap. Then check whether the datasheet gives a full-field acceptance curve or only a recommended maximum edge CRA, and use the full curve when you have it.
Draw candidates from the M12 lens collection. For inspection work on 1/2" and smaller formats, the Commonlands No Distortion 6mm M12 Lens (CIL062) is a predictable-edge option. For mixed visible and NIR illumination in robotics and outdoor systems, the Commonlands CIL239 fisheye holds focus across the band, with less than 8 microns of focus shift from 550nm to 850nm. Short focal lengths in compact bodies produce the steepest edge chief rays, so validate wide-angle and fisheye candidates first.
Lenses and testing services for CRA-sensitive designs
よくある質問
Commonlands matches lens CRA to sensor microlens designs when recommending lenses. These answers cover why that match matters.
What is the chief ray angle in a camera lens?
Chief ray angle is the angle between the optical axis and the chief ray (the ray from an off-axis scene point that passes through the center of the aperture stop), measured at the image plane. It increases with image height, so lens datasheets usually quote the maximum value at the edge of the image circle.
What causes CRA mismatch between a lens and a sensor?
CRA mismatch occurs when the lens's chief ray angle at a given image height differs from the incidence angle the sensor's shifted microlenses were designed to accept there. Common causes include pairing a mobile-heritage high-CRA sensor variant with an industrial low-CRA lens, cover glass stack differences, and tight z-height packaging constraints.
Why are RGB sensors more sensitive to CRA mismatch than monochrome sensors?
The Bayer color filter array converts angular error into per-channel imbalance, which shows up as visible color shading. Monochrome sensors have no color channels to unbalance, so they tolerate a substantially wider mismatch than an equivalent RGB part, though vignetting and corner sharpness loss still appear at large mismatches above about 20°.
What CRA tolerance should I target for machine vision cameras?
Aim to match lens edge CRA to the sensor's design CRA within about ±3°. Acceptance limits depend on the sensor: low-CRA industrial parts (below 10°) tolerate a relatively wide mismatch, and monochrome versions tolerate more than RGB, while high-CRA mobile parts (above 20°) are far less forgiving and need a close match. Validate with flat-field and corner MTF tests.
How do I match M12 lenses to Sony IMX sensors?
Confirm the active-area diagonal, pull the CRA curve for your exact IMX variant from the datasheet, shortlist 2–3 M12 lenses with sufficient image circle, then benchmark RGB flat fields and corner MTF on the same rig. Choose the lens that meets image quality targets with the smallest ISP correction map.
Get a CRA-matched lens recommendation
Send your sensor part number (including the CRA variant suffix) plus working distance and target field of view, and our San Diego engineering team will shortlist compatible lenses. Commonlands is ISO 9001:2015 certified, and orders placed before 12 PM PST ship the same day.