01Anchor the job: sensor, distance, field of view
A lens spec starts from what it must image, not from lens jargon. Name the sensor (model or format + pixel pitch), the working distance, and the field of view — either the angle or “I need to see an object this wide at this distance.” Those three facts anchor everything else.
02Choose the f-number with the diffraction limit in view
The f-number sets how much light the lens collects and how deep the focus zone is. Smaller f-number = more light, shallower depth of field. But there is a floor nobody escapes: diffraction.
03Specify sharpness as MTF at Nyquist
“Sharp” is not quotable. The measurable request is contrast (MTF) at the highest spatial frequency your sensor can use — its Nyquist frequency, which is 1/(2·pixel pitch).
04Name the waveband — and stick to it
Glass dispersion, coating design, and even which glasses are allowed all follow from the spectrum: visible (roughly 420–680 nm), visible+NIR (to 950 nm for IR illumination), SWIR, or a single laser line.
05Bound the envelope, mount, and back focal distance
The mechanical facts vendors get burned by: maximum barrel length and diameter, the mount (M12, C/CS, custom thread), and the back focal distance — the clearance between the last glass surface and the sensor, including any filter glass in the path.
06Set the environment and quantity
Temperature range, humidity, vibration/shock, and washdown/sealing silently drive glass choice, housing material, and adhesives. Quantity drives everything about price: a one-off prototype and a 10k/year production part are different designs.
07Defer the rest — by name, to the vendor
Element count, glass selection, aspheres vs. spheres, coating recipe, exact tolerancing: that is the lens designer's craft. A good spec lists these explicitly as “vendor's choice, meeting the requirements above” — an empty section reads as an oversight; a deferred list reads as competence.
Worked example: a machine-vision inspection lens
The whole chain, numbers shown — the same derivations the SpecBuildr interview performs and prints in your spec's math appendix.
The mistakes that make quotes expensive
Frequently asked questions
What does a lens manufacturer actually need to quote a custom lens?
Seven things: sensor (or detector) details, working distance and field of view, f-number, a measurable sharpness target (MTF at a stated frequency), waveband, mechanical envelope and mount, and environment plus quantity. With those, a vendor can quote without a round of clarifying questions.
How do I work out the focal length I need?
From the sensor width and field of view: EFL ≈ sensor width / (2·tan(FOV/2)). You almost never pick focal length first — it falls out of what you must image.
What f-number should I ask for?
The smallest (brightest) your depth-of-field allows, bounded below by diffraction: the spot is about 2.44·λ·N, and once that exceeds your pixel pitch you are past the useful floor. On small pixels that usually means f/2–f/5.6.
What is MTF at Nyquist and why should my spec say it?
MTF is measured contrast at a spatial frequency; Nyquist (1/(2·pixel pitch)) is the finest detail your sensor can record. Asking for a stated MTF at Nyquist turns “sharp” into a number a test bench can verify.
Can I write a lens spec without an optics background?
Yes — if something asks the right questions in your language. That is exactly what the SpecBuildr interview does: you answer in plain engineering terms, and it derives the optical quantities and runs the physics checks.
Skip the blank page
The interview asks you these exact questions in plain language, runs the physics checks, and prints a complete, quotable spec — free.
Start the lens interview →