How to Choose a Machine Vision Camera: The 2026 Buyer's Guide

Most machine vision camera purchases go wrong at the same place: the buyer starts from megapixels. A quality engineer needs to read a data matrix code on a moving conveyor, sees one camera at 5 MP and another at 12 MP, picks the bigger number for margin, and then finds on the line that the parts blur because the sensor has a rolling shutter, the code sits out of focus because the lens working distance was wrong, and the whole read fails in the plant's overhead fluorescent light because there was no controlled illumination. Resolution was almost the last thing that mattered, and it was the only thing they checked.

The order that works starts with the task and the feature you have to measure or detect, not the camera. What are you inspecting, how small is the smallest defect or feature you must resolve, how fast is the part moving, how much does the part vary, and what does the light in the cell do to the image. That description fixes the imaging chain: the field of view sets the resolution you actually need, the part speed decides global versus rolling shutter, the feature contrast decides mono versus color and the lighting, and the working distance and sensor size pick the lens. A machine vision camera is a sensor, a shutter, an interface, a lens mount, and a lighting plan, and you are buying all five at once, wrapped in an application that lives or dies on the image before any software runs.

This guide is the buying hub for machine vision cameras on this site. It gives you a decision framework by application (inspection, robot guidance, measurement and metrology, code reading), the specs that decide an imaging chain and how to trade them, the resolution-to-feature math that catches most buyers, budget tiers with what each buys, the interface and lens choices that decide integration, the 2D-versus-3D fork, the vendor landscape by category, and the total-cost math that goes well beyond the camera body. Throughout it points at the deeper machine vision guide and at the live sensor leaderboard, where you can compare real cameras and other sensors instead of trusting a datasheet.

The take: Choose the task before the camera. The smallest feature you must resolve and your field of view set the resolution, the part speed sets the shutter (global for anything moving, rolling only for static or slow scenes), the feature contrast sets mono versus color and the lighting, the working distance and sensor format pick the lens, and the data rate and cable run pick the interface. Two questions eliminate most of the market fast: "what is the smallest feature I must see, over how big a field" and "how fast is the part moving when I capture it." Answer those first and the shortlist is three or four models across two vendors. Resolution is a result of the math, not the starting point, and the lens and lighting decide the image long before the sensor does.

Companion reading: machine vision, robot perception & pose estimation, LiDAR & depth cameras, depth sensing: stereo, ToF, structured light, how to choose a LiDAR, and edge AI & robot compute.

Table of contents

1. Key takeaways
2. Start with the application, then the imaging chain
3. Resolution and the feature-size math
4. Shutter: global vs rolling
5. Sensor: mono vs color, pixel size, CMOS generation
6. Interface: GigE Vision, USB3, Camera Link, MIPI
7. Lenses, optics, and working distance
8. Lighting is half the system
9. Area-scan vs line-scan
10. 2D vs 3D
11. Budget tiers and what each buys
12. The vendor and ecosystem landscape
13. Integration, SDK, and total cost of ownership
14. A repeatable selection process
15. Frequently asked questions
16. Changelog

Start with the application, then the imaging chain

Four application classes cover almost every machine vision camera purchase, and each weights the specs differently. Find your task here, then let it tell you which numbers to prioritize and which sibling guide to read next.

Application	What it measures	Weight most	Typical setup
Inspection (defect, presence)	Surface flaws, presence/absence, print quality	Resolution, lighting, contrast	Area-scan, controlled light, mono or color
Robot guidance	Part position and pose for pick/place	Global shutter, calibration, often 3D	2D or 3D, global shutter, fast interface
Measurement / metrology	Dimensions, gauging, tolerance	Resolution, telecentric optics, stability	High-res mono, telecentric lens, backlight
Code reading (1D/2D)	Barcodes, data matrix, OCR	Resolution on the code, shutter, lighting	Mono, global shutter, often a smart camera

A sentence each on what actually decides the fit.

Inspection. Detecting surface defects, verifying presence and correct assembly, checking print and label quality. The deciding factors are resolving the smallest defect you care about across the whole part and lighting the scene so the defect shows up as contrast. Color matters when defects are color-defined (a wrong-colored wire, a stain); otherwise mono is sharper and more sensitive. This is the broadest class and the one where lighting technique earns or loses the job.

Robot guidance. Finding a part's position and orientation so a robot can pick or place it. A moving part or a moving camera demands a global shutter, and the whole chain has to be calibrated to the robot's coordinate frame. Planar parts on a belt need 2D location; parts jumbled in a bin need 3D. The perception side of this is covered in robot perception and pose estimation, and the depth options in depth sensing.

Measurement and metrology. Non-contact gauging of dimensions to a tolerance. This class wants high resolution, a telecentric lens to remove perspective error, a stable backlit or coaxial setup, and thermal and mechanical stability, because you are trusting the pixels as a ruler. Sub-pixel edge detection extracts more than the raw pixel count, but the optics have to earn it.

Code reading. Reading 1D barcodes, 2D data matrix and QR codes, and printed text (OCR). The key spec is enough resolution on the code itself (a rule of thumb is a minimum number of pixels per module or per cell), a global shutter if the code moves, and even lighting that avoids specular glare on shiny or curved surfaces. This class is often served by a smart camera with reading software built in rather than a bare camera plus a PC.

Rule of thumb: If you cannot state the smallest feature you must resolve and the size of the field it lives in, you are not ready to pick a camera. "Read a 12-mil data matrix on a 40 mm part moving at 0.3 m/s under overhead light" is a camera filter. "Inspect the part" is not.

Resolution and the feature-size math

The single most common machine vision mistake is buying resolution as a headline number. The resolution you need is a calculation from the field of view and the smallest feature, and buying past what the optics can deliver wastes money and slows the system down.

The math is simple. Take your field of view (the area the camera must see, in millimeters), divide by the smallest feature or defect you must reliably detect, and multiply by the number of pixels you want across that feature. A common minimum is three pixels across the smallest feature for detection, and five or more for reliable measurement or code reading. That gives the pixels needed along each axis.

Worked example: a 100 mm wide field, a 0.2 mm smallest defect, and three pixels across it needs 100 / 0.2 times 3, which is 1,500 pixels across. A 2 MP camera (roughly 1,920 by 1,200) covers it with margin. If you demand five pixels across the defect for a measurement, you need 2,500 pixels across and a 5 MP sensor. Push the defect to 0.05 mm over the same field and you need 6,000 pixels, into 12 MP-plus territory or a second camera covering half the field each.

Two cautions save real money here. First, the lens has to resolve what the sensor demands: a high-megapixel sensor behind a cheap lens produces a blurry image at full resolution, and you paid for pixels the optics cannot fill. Match the lens resolving power (often quoted in line pairs per millimeter or as a supported megapixel rating) to the sensor. Second, more pixels means more data, which means a faster interface, more compute, and often a slower frame rate, so buy the resolution the task needs and stop.

Field of view	Smallest feature	Pixels/feature	Pixels needed (1 axis)	Sensor class
50 mm	0.1 mm	3	1,500	2 MP
100 mm	0.2 mm	3	1,500	2 MP
100 mm	0.05 mm	5	10,000	12 MP+ or multi-camera
300 mm	0.5 mm	3	1,800	3 to 5 MP
500 mm	0.2 mm	5	12,500	line-scan or multi-camera

War story: A team bought a 20 MP camera to inspect a large panel, confident that more pixels meant more margin. The stock C-mount lens they paired it with resolved well under what the sensor could sample, so at full resolution the image was soft and the small scratches they needed to catch smeared across several pixels with no contrast. They were reading a 20 MP file that carried maybe 6 MP of real detail. A proper high-resolution lens, matched to the sensor, cost more than they expected and fixed it. The pixels were never the problem; the optics were.

Shutter: global vs rolling

This is the fork that catches more first-time buyers than any other, because rolling-shutter cameras are cheaper and the defect only shows up on moving parts.

Rolling shutter exposes the sensor row by row, so different parts of the frame are captured at slightly different times. On a static, well-lit scene it is fine and often cheaper and higher-resolution per dollar. On a moving part it smears and skews the image: a fast object leans, a round part turns oval, and edges blur, which wrecks measurement and code reading. Rolling shutter belongs in microscopy, static inspection, and slow, controlled scenes.

Global shutter exposes every pixel at the same instant, freezing motion cleanly. It is the default for any moving part, any moving camera (a camera on a robot wrist), continuous conveyors, and indexed lines where the part may still be settling. The Sony Pregius family of global-shutter CMOS sensors became the industrial standard for exactly this reason, and most modern industrial cameras use them. Global shutter costs a little more and historically traded some resolution or sensitivity, but modern sensors have narrowed that gap.

The practical rule is blunt: if the part or the camera moves during exposure, buy global shutter. Do not try to freeze a moving part with a rolling-shutter camera and a fast exposure, because the row-timing skew remains even at short exposure. Reserve rolling shutter for scenes that hold still.

Rule of thumb: Moving part or moving camera means global shutter, full stop. Rolling shutter is only for static scenes or slow, well-lit microscopy. The extra cost of global shutter is trivial next to a line that reads wrong every time a part is in motion.

Sensor: mono vs color, pixel size, CMOS generation

Once the shutter is fixed, the sensor's other properties trade sensitivity, sharpness, and cost.

Mono vs color. A monochrome sensor captures light at every pixel. A color sensor puts a Bayer color filter over the pixels and interpolates the missing colors, which costs roughly a factor in effective resolution and cuts sensitivity because each pixel sees only one color band. For measurement, gauging, code reading, and most defect detection, mono is sharper, more sensitive, and the right default. You also control contrast precisely by pairing a mono camera with colored lighting (a red light on a red-on-red print, for instance). Buy color only when the task genuinely depends on hue: sorting by color, detecting color-defined defects, or inspecting color print. When in doubt, mono.

Pixel size. Larger pixels collect more light, giving better sensitivity, dynamic range, and low-light performance, at the cost of a bigger, more expensive sensor for the same resolution. Industrial CMOS pixels commonly run from about 2.5 to 5 microns. Small pixels pack more resolution into a small, cheap sensor but need more light and a lens that can resolve them. For fast lines with short exposures or dim scenes, larger pixels help; for bright, static, high-resolution work, small pixels are efficient.

CMOS generation and quality metrics. Modern industrial cameras use CMOS almost exclusively; CCD is legacy. The specs that matter beyond resolution are quantum efficiency (how much of the incoming light becomes signal), read noise, dynamic range, and the maximum frame rate at full resolution. Sony's Pregius and Pregius S global-shutter lines and the Starvis family for low light are the common sensor references, and the camera vendor's datasheet reports the resulting quantum efficiency and dynamic range. For most applications, a current-generation Sony global-shutter sensor at the resolution your math demands is the safe choice.

Choice	Pick when	Cost / tradeoff
Mono	Measurement, gauging, code reading, most inspection	Sharper, more sensitive, cheaper for the same detail
Color	Color sorting, color-defined defects, color print	Lower effective resolution, less sensitive
Larger pixels (4 to 5 um)	Fast lines, short exposure, low light	Bigger, pricier sensor per pixel
Smaller pixels (2.5 to 3.5 um)	Bright, static, high-res work	Needs more light and a sharper lens

Rule of thumb: Default to mono and only pay for color when the decision depends on hue. A mono sensor with the right colored light beats a color sensor guessing at contrast, and it does it at higher effective resolution.

Interface: GigE Vision, USB3, Camera Link, MIPI

The interface is decided by three things: how much data the camera produces (resolution times frame rate times bits), how far the cable has to run, and how many cameras you need on one system. Match those to the standard rather than defaulting to whatever the camera ships with.

USB3 Vision. Up to about 5 Gbps, cheap, plug-and-play, and it powers the camera over the cable. The catch is cable length, practically limited to around 3 to 5 m (longer with active or fiber cables). It suits a single camera close to a PC: benchtop inspection, a compact cell, a lab. It is the easy default for one camera and a short run.

GigE Vision. Gigabit Ethernet at 1 Gbps, with cable runs up to 100 m and Power over Ethernet on many cameras, so one Ethernet cable carries data and power a long way. It is the workhorse for factory installations, multi-camera systems (a switch fans out to several cameras), and cameras mounted far from the controller. Bandwidth is lower than USB3, so at high resolution and frame rate it can be the limit, which is where 5GigE and 10GigE step in for more data over the same cabling. GigE is the default for most industrial multi-camera or long-run deployments.

Camera Link and CoaXPress. High-bandwidth interfaces for the fastest and highest-resolution cameras, especially line-scan and high-speed area-scan. Camera Link needs a frame grabber card and short cabling but delivers deterministic high throughput. CoaXPress (CXP) runs very high bandwidth (up to 12.5 Gbps per coax lane, more when bonded) over long coax cable with power, and it has largely become the choice for demanding line-scan and high-speed work. Both need a frame grabber, which adds cost and a PCIe slot.

MIPI CSI-2. The board-level interface used in embedded vision, connecting a bare sensor module directly to a system-on-module (NVIDIA Jetson, a Raspberry Pi, custom carrier boards). It is short-range, low-cost, and the route for embedded and volume products where the camera lives inside the device rather than plugging into a PC. Pair it with the compute choices in edge AI and robot compute.

Interface	Bandwidth	Cable reach	Power over cable	Frame grabber	Best for
USB3 Vision	~5 Gbps	3 to 5 m	Yes	No	Single camera, short run, benchtop
GigE Vision (1G)	1 Gbps	up to 100 m	PoE (many)	No	Multi-camera, long runs, factory
5G/10GigE	5 to 10 Gbps	tens of m	PoE (some)	No	High-res + high frame rate over Ethernet
Camera Link	up to ~6.8 Gbps	short	No	Yes	High-speed area-scan, deterministic
CoaXPress	12.5+ Gbps/lane	long coax	Yes	Yes	Line-scan, high-speed, high-res
MIPI CSI-2	high, board-level	cm	Yes	No	Embedded, board-level, volume products

Most industrial cameras that use GigE Vision, USB3 Vision, or CoaXPress also speak GenICam, the standard that lets any compliant camera work with any compliant software. The machine vision guide covers the standards stack in more depth.

Rule of thumb: One camera close to a PC, use USB3. Cameras spread across a machine or a long run, use GigE with PoE. When resolution times frame rate blows past a gigabit, step up to 5/10GigE or CoaXPress and budget a frame grabber. Do not pick the interface on the camera you liked; pick it on your data rate and cable run.

Lenses, optics, and working distance

The lens decides the image as much as the sensor, and a mismatched lens quietly wastes the sensor you paid for. Four parameters tie the lens to the application.

Focal length and field of view. For a given working distance and sensor size, the focal length sets the field of view. Short focal length gives a wide field, long focal length a narrow field. You pick focal length to make your required field of view land on the sensor at your working distance, using the lens calculators every optics vendor publishes. Get this wrong and the part does not fit the frame or fills so little of it that resolution is wasted.

Working distance. How far the lens sits from the part. This is fixed by the mechanics of the cell (where the camera can physically mount) and it constrains the focal length and lens choice. State the working distance you actually have before shopping lenses.

Sensor format and mount. The lens must cover the sensor's diagonal (its optical format, quoted as a fraction like 1/1.8 inch, 2/3 inch, 1.1 inch), or the corners of the image go dark and soft (vignetting). A lens rated for a smaller format on a larger sensor fails at the edges. The mechanical mount is usually C-mount for industrial cameras (the standard 1 inch, 32 TPI thread), with CS-mount, S-mount (M12) for compact and embedded cameras, and F-mount or larger for big sensors. Match the mount and confirm the lens covers the sensor format.

Telecentric lenses for measurement. A standard lens has perspective: parts farther away look smaller, and a part's apparent size changes with its distance and position in the field, which introduces error into gauging. A telecentric lens has a constant magnification across its depth of field, removing perspective error, so it is the correct choice for precision measurement and metrology. It is bulkier and more expensive and its field of view cannot exceed the front lens diameter, but for dimensional gauging it is what makes the measurement trustworthy.

Rule of thumb: Fix the working distance from the cell mechanics, pick the focal length to land your field of view on the sensor, and confirm the lens covers the sensor format and mount. For dimensional measurement, budget a telecentric lens from the start; a standard lens turns perspective into measurement error you will chase forever.

Lighting is half the system

Lighting decides whether the feature you care about shows up as contrast, and it is the single most underrated part of a vision system. A correctly lit scene makes the software easy; a poorly lit scene makes it impossible regardless of camera quality.

The technique matters more than the brightness. Backlighting throws the part into silhouette and is unbeatable for measuring outlines and detecting holes and edges. Dome and diffuse lighting wraps even light around shiny or curved parts and kills glare, which is what specular surfaces (metal, glass) need. Dark-field lighting rakes light across a surface at a low angle so scratches and engraving light up against a dark background. Coaxial (on-axis) lighting shines through a beam splitter down the optical axis for flat reflective surfaces. Structured light projects a pattern for 3D. Ring lights are the general-purpose starting point but often the wrong answer for shiny parts. Getting the geometry right is what separates a robust inspection from one that drifts with every ambient-light change.

Two practical points. First, control the ambient light or overpower it: overhead factory lighting flickers, changes across shifts, and defeats an uncontrolled setup, so most reliable installations shroud the station or use strobed lighting bright enough to dominate ambient. Strobing a bright LED synchronized to the camera exposure both freezes motion and swamps ambient, and it is standard on fast lines. Second, wavelength is a tool: red, blue, or infrared light plus a matching filter can create contrast a broadband white light cannot, and pairing colored light with a mono camera is often cheaper and sharper than a color camera.

Lighting technique	Reveals	Good for
Backlight	Outline, holes, edges	Measurement, presence, silhouette
Diffuse / dome	Even light, no glare	Shiny, curved, specular parts
Dark-field (low angle)	Scratches, engraving, texture	Surface defects, marks on flat parts
Coaxial / on-axis	Flat reflective detail	Mirrors, wafers, flat metal
Ring / directional	General surface	Broad inspection, starting point
Structured light	3D shape	Height, volume, 3D profiling

Rule of thumb: Spend on lighting before you spend on a better camera. A modest sensor with the right light geometry and a strobe that swamps ambient will out-inspect a premium sensor staring at a poorly lit scene. If the software team is fighting the image, the fix is almost always the light, not more pixels.

Area-scan vs line-scan

Most cameras are area-scan: a rectangular sensor captures a full 2D frame in one exposure. That is the right default for discrete parts, indexed stations, and anything that holds still or can be frozen with a global shutter and a strobe. It is simpler to set up, light, and program, and it covers the large majority of applications.

Line-scan cameras have a single row (or a few rows) of pixels and build an image line by line as the part moves under them, which requires an encoder to sync the line rate to the part's motion. They win in specific cases: continuous web material (paper, film, textile, metal coil) that never stops, very large or very long parts where a single area-scan frame cannot hold the needed resolution, cylindrical parts unrolled by rotation, and any job that needs very high resolution across a wide moving product. A line-scan setup builds an image of arbitrary length at high across-web resolution, which an area-scan camera cannot match on a continuous web.

Line-scan costs more in integration: it needs precise motion, an encoder, careful lighting of a thin bright line, and often a CoaXPress or Camera Link interface for the data rate. Choose it when the product is continuous or too big for area-scan resolution; otherwise area-scan is simpler and cheaper.

	Area-scan	Line-scan
Sensor	2D frame	1 or few rows, built by motion
Needs encoder	No	Yes
Best for	Discrete parts, stations	Continuous web, large/long parts, rotation
Setup complexity	Lower	Higher (motion, encoder, line lighting)
Interface	USB3/GigE common	Often CoaXPress/Camera Link

Rule of thumb: Discrete parts and indexed stations use area-scan. Continuous web, or a part too big to hold your resolution in one frame, use line-scan and budget the encoder, the line lighting, and the frame grabber that come with it.

2D vs 3D

The last big fork is whether a flat image answers the question or you need depth. 2D imaging (a normal camera) handles inspection, measurement in a plane, presence and absence, print and code reading, and locating parts on a flat surface. It is cheaper, faster, and simpler, and it is the right answer whenever the feature lives in a plane.

3D imaging captures shape and height, which you need for volume and height measurement, warpage and coplanarity, surface profiling, and, above all, robot guidance where parts are stacked or jumbled in a bin. The common 3D methods each have a niche. Stereo vision uses two cameras and triangulation, works in ambient light, and suits mid-range robot guidance. Structured light projects a pattern and reads its deformation for high-accuracy short-range shape capture, common in electronics and precision inspection. Laser triangulation (a laser line plus a camera, scanning the part) gives very high-accuracy height profiles for weld seams, glue beads, and surface profiling. Time-of-flight measures the time light takes to return for fast, longer-range but lower-resolution depth, useful in logistics and navigation. These methods and their tradeoffs are covered in depth in depth sensing: stereo, ToF, structured light, and the overlap with ranging sensors in LiDAR and depth cameras and how to choose a LiDAR.

3D costs more, runs slower, and adds calibration and processing complexity, so use it only when a 2D image cannot answer the question. Many cells that seem to need 3D actually just need good fixturing to present the part in a known plane, at which point 2D is cheaper and more robust.

Method	Accuracy	Range	Speed	Best for
2D area-scan	in-plane only	any	fast	Inspection, code, planar location
Stereo	mm	0.3 to several m	moderate	Robot guidance, ambient light
Structured light	tens of um to mm	short	moderate	Precision shape, electronics
Laser triangulation	um to tens of um	short	fast (profile)	Height profiles, seams, beads
Time-of-flight	cm	up to several m	fast	Logistics, navigation, coarse depth

Rule of thumb: Ask whether fixturing can present the part in a known plane. If yes, 2D is cheaper, faster, and more robust. Reach for 3D only when height, volume, shape, or a bin of jumbled parts makes depth unavoidable, then match the 3D method to your accuracy and range.

Budget tiers and what each buys

Machine vision camera pricing steps by capability, and the camera body is only part of the system cost. These bands are for the camera in 2026; lens, lighting, and software come on top.

Under $100: board and embedded modules. MIPI CSI-2 sensor modules and low-cost USB webcam-class cameras for embedded projects, prototyping, and volume products where the camera lives inside a device. Fine for development and non-critical vision, but they lack the sensor quality, global shutter, and standards support of industrial cameras.

$400 to $1,500: mainstream industrial area-scan. The volume tier. USB3 Vision or GigE Vision cameras with a current Sony global-shutter CMOS sensor from roughly 1.6 to 12 MP, GenICam support, and industrial build. Basler ace, Teledyne FLIR Blackfly and Grasshopper, IDS uEye, and Allied Vision Alvium and Manta live here. This covers most inspection, guidance, and code-reading tasks. Most industrial camera purchases land in this band.

$1,500 to $5,000: high-resolution, high-speed, and specialized. High-megapixel area-scan (20 MP and up), fast frame-rate cameras, 10GigE and CoaXPress models, entry line-scan, and higher-grade sensors. This tier is for demanding inspection, high-throughput lines, and large fields that need the pixels.

$5,000 to $15,000+: smart cameras, 3D, and line-scan systems. Self-contained smart cameras with reading and inspection software built in (Cognex In-Sight, Keyence), 3D sensors (structured-light and laser-profile heads), and high-end line-scan cameras with their frame grabbers. Here the camera becomes a system with software and processing rather than a bare sensor. Cognex and Keyence smart-camera systems in particular price on the built-in software and support, not the sensor alone.

Band	Get	Do not expect	Best for
< $100	MIPI/USB modules	Global shutter, standards, support	Embedded, prototyping, volume products
$400 to $1,500	GigE/USB3 global-shutter 1.6 to 12 MP	20 MP+, 3D, built-in software	Most inspection, guidance, code reading
$1,500 to $5,000	High-res, high-speed, 10GigE/CXP	Turnkey software, 3D	Demanding inspection, fast lines
$5,000 to $15,000+	Smart cameras, 3D, line-scan systems	A cheap total cost	Code reading turnkey, 3D, web inspection

Rule of thumb: A bare industrial camera plus lens and lighting is often cheaper and more flexible than a smart camera, but a smart camera with built-in software and a shorter integration can win on total cost for a standard code-reading or presence-checking job. Price the whole integration; the sensor is a small part of it.

The vendor and ecosystem landscape

The market splits into component camera makers and turnkey vision-system vendors, and knowing which is which shortcuts the shortlist.

Component camera makers (Basler, Teledyne FLIR, IDS, Allied Vision). These sell the camera and expect you (or an integrator) to add the lens, lighting, and software. Basler (Germany) is a volume leader with a broad, well-priced range (the ace and boost lines) and its own pylon SDK. Teledyne FLIR (formerly Point Grey) offers the Blackfly, Grasshopper, and Oryx lines across USB3, GigE, and 10GigE with the Spinnaker SDK, plus thermal cameras. IDS Imaging (Germany) makes the uEye range and pushes embedded and AI-on-camera vision. Allied Vision (Germany, part of TKH) covers the Alvium embedded line and the Manta and Mako industrial cameras, strong on embedded and board-level integration. All four are GenICam-compliant, so they interoperate with third-party vision software.

Turnkey and smart-camera vendors (Cognex, Keyence). These sell a vision system: a smart camera with inspection or code-reading software, lighting, and application support bundled. Cognex (USA) is the market leader in machine vision systems and the reference in barcode reading (the DataMan line) and In-Sight smart cameras, with its own VisionPro and In-Sight software. Keyence (Japan) sells vision systems with heavy application support and easy setup, priced accordingly. These win when you want a working inspection or code read with minimal integration and are willing to pay for the software and support. They cost more per unit and lock you into their ecosystem, which is the tradeoff for the fast deployment.

Sensor suppliers behind the cameras. Almost every industrial camera today uses a Sony CMOS sensor (Pregius and Pregius S global-shutter for machine vision, Starvis for low light), with onsemi (formerly Aptina) and a few others also present. The camera vendor packages the sensor with an interface, firmware, and an SDK, so two cameras with the same Sony sensor can differ in image quality through the electronics and tuning around it.

How to choose among them. For a component build where you or an integrator handle optics, lighting, and software, Basler, Teledyne FLIR, IDS, and Allied Vision compete on price, range, sensor availability, and SDK. For a turnkey code-reading or inspection job with minimal in-house vision engineering, Cognex or Keyence trade a higher price for a faster, better-supported deployment. Match embedded and board-level products to IDS and Allied Vision; match barcode reading to Cognex; match a broad, cost-effective component range to Basler and Teledyne FLIR.

You can line up cameras and other sensors on the sensor leaderboard to build a like-for-like shortlist before you talk to a sales team.

Integration, SDK, and total cost of ownership

The camera is a fraction of the installed vision system, and the buyers who compare camera prices and ignore the rest are comparing the wrong number.

GenICam and the SDK. GenICam is the standard that lets a compliant camera work with compliant software regardless of vendor, exposing features (exposure, gain, trigger) through a common interface over GigE Vision, USB3 Vision, or CoaXPress. Each camera vendor ships its own SDK (Basler pylon, Teledyne FLIR Spinnaker, IDS peak, Allied Vision Vimba) for lower-level control, and third-party libraries (HALCON from MVTec, Cognex VisionPro, OpenCV for custom work, and the deep-learning tools now common for defect detection) sit on top. If you standardize on a vision software package, confirm your cameras are supported; GenICam compliance usually guarantees it, but validate before you buy.

Compute. The camera produces pixels; something has to process them. A PC with a frame grabber, an industrial vision controller, a smart camera with onboard processing, or an embedded compute module (a Jetson for CSI-2 cameras) all serve different scales. High resolution and high frame rate demand more compute and faster storage, and modern defect detection with deep learning wants a GPU. Size the compute to the data rate and the algorithm, and see edge AI and robot compute for the embedded options.

The rest of the system. Beyond the camera, budget the lens (which can cost as much as the camera, more for telecentric), the lighting (controller, LED heads, strobe), mounting and enclosure, cabling (and the right cable rated for the interface and any cable-carrier flexing on a robot), the compute or controller, and the vision software licenses. Then add the engineering to set up, light, calibrate, program, and validate the application, which on a non-trivial inspection is often the largest single line. Calibration to a robot frame for guidance, and periodic recalibration, is its own recurring cost.

Total cost of ownership. Over the operating life, add software maintenance and licenses, spares, the labor to re-tune when the product changes, and the cost of false rejects and missed defects if the system is marginal. A robust, well-lit system that rarely false-rejects is worth paying for, because a vision station that stops the line on phantom defects costs more in downtime than the camera ever saved.

Rule of thumb: Budget the vision system, not the camera. Lens, lighting, compute, cabling, software, and engineering usually outweigh the camera body, and the engineering to make the image robust is the line most first-time buyers forget. The camera brand you agonized over is a small part of the number.

A repeatable selection process

Put it together into a checklist you can run for any purchase.

1. State the task and the smallest feature you must resolve, with the field of view it lives in and the part speed. "Detect a 0.1 mm defect over a 100 mm field on a part moving at 0.3 m/s." If you cannot, stop here until you can.
2. Compute the resolution from field of view divided by feature size times pixels per feature (three for detection, five for measurement or code reading). That fixes the sensor class.
3. Pick the shutter: global for any moving part or moving camera, rolling only for static or slow scenes.
4. Choose mono or color: mono by default, color only when the decision depends on hue.
5. Select the interface from data rate and cable run: USB3 for one short-run camera, GigE with PoE for long runs and multi-camera, 10GigE or CoaXPress for very high bandwidth, MIPI for embedded.
6. Design the optics: fix the working distance from the cell, pick the focal length to land the field of view on the sensor, confirm the lens covers the sensor format and mount, and choose telecentric for measurement.
7. Design the lighting before finalizing the camera: technique (backlight, diffuse, dark-field, coaxial), wavelength, and a strobe to swamp ambient. This is half the system.
8. Decide area-scan vs line-scan (continuous web or oversize part means line-scan) and 2D vs 3D (depth, height, or a jumbled bin means 3D).
9. Choose component or turnkey: component camera plus integrator for flexibility and cost, smart camera for a fast, supported standard job.
10. Build the real budget: camera plus lens, lighting, compute, cabling, software, and the engineering to light, calibrate, program, and validate. Shortlist on the sensor leaderboard and validate the finalist on your actual worst-case part and lighting before you commit.

Run this in order and the shortlist narrows to two or three cameras across one or two vendors you can buy with confidence. Skip the feature-size math and the lighting design and you will do what most first-time buyers do, which is buy on megapixels and discover on the line that the image was never good enough.

Frequently asked questions

How many megapixels do I need? Compute it, do not guess. Divide your field of view by the smallest feature you must resolve, then multiply by the pixels you want across that feature (three for detection, five for measurement or code reading). A 100 mm field with a 0.2 mm defect and three pixels across needs 1,500 pixels per axis, which a 2 MP camera covers. Buying more megapixels than your optics can resolve wastes money and slows the system. The lens has to resolve what the sensor demands, or you are storing pixels with no real detail.

Global shutter or rolling shutter? Global shutter for anything that moves during exposure, which means conveyors, indexed lines, and any camera mounted on a robot. Rolling shutter exposes row by row and smears and skews moving parts, so it belongs only in static inspection and slow microscopy. A fast exposure does not fix rolling shutter, because the row-timing skew remains. Modern industrial cameras with Sony Pregius global-shutter sensors are the default for machine vision for exactly this reason.

Mono or color? Mono by default. A monochrome sensor is sharper and more sensitive because it skips the Bayer color filter and the interpolation, which makes it better for measurement, gauging, code reading, and most defect detection. You can create precise contrast by pairing a mono camera with colored lighting. Buy color only when the decision genuinely depends on hue: color sorting, color-defined defects, or color print inspection.

Which interface should I choose? Pick by data rate and cable run. USB3 Vision for a single camera close to the PC (3 to 5 m). GigE Vision for long runs (up to 100 m) and multi-camera systems, often with Power over Ethernet on one cable. When resolution times frame rate exceeds a gigabit, step up to 5/10GigE or CoaXPress and budget a frame grabber. MIPI CSI-2 for embedded, board-level integration inside a device. Do not default to the camera's interface; pick the interface first.

Do I need a smart camera or a component camera plus a PC? A smart camera (Cognex In-Sight, Keyence) bundles the sensor, software, and lighting for a fast, supported deployment on a standard job like code reading or presence checking, at a higher price and inside a closed ecosystem. A component camera (Basler, Teledyne FLIR, IDS, Allied Vision) plus a lens, lighting, and vision software gives more flexibility and lower hardware cost, at the price of more integration work. Choose the smart camera for a standard job with little in-house vision engineering; choose components for custom or cost-sensitive builds.

What lens do I need? Fix the working distance from where the camera can physically mount, then pick the focal length that lands your required field of view on the sensor at that distance, using the vendor's lens calculator. Confirm the lens covers the sensor's optical format (or the corners vignette) and matches the mount (usually C-mount for industrial cameras). For dimensional measurement, use a telecentric lens, which holds constant magnification across its depth of field and removes the perspective error that a standard lens introduces into gauging.

Why does everyone say lighting matters so much? Because lighting decides whether the feature you care about appears as contrast, and no camera recovers detail the light never revealed. The technique (backlight for outlines, diffuse for shiny parts, dark-field for scratches, coaxial for flat reflective surfaces) matters more than brightness, and controlling or strobing over ambient light is what makes an inspection robust across shifts. A modest camera with the right lighting beats a premium camera imaging a poorly lit scene, which is why lighting is the first place to spend.

When do I need 3D instead of 2D? When the answer depends on height, volume, shape, or depth, or when parts are stacked or jumbled in a bin and a robot must find their pose. 2D handles inspection, in-plane measurement, presence, and code reading more cheaply and quickly, so ask first whether fixturing can present the part in a known plane. If it can, stay 2D. If it cannot, match the 3D method (stereo, structured light, laser triangulation, or time-of-flight) to your accuracy and range. See depth sensing.

Area-scan or line-scan? Area-scan captures a full 2D frame and is the default for discrete parts and indexed stations. Line-scan builds an image line by line as the part moves and needs an encoder, and it wins on continuous web material (paper, film, metal coil), very large or long parts where one area-scan frame cannot hold the resolution, and cylindrical parts unrolled by rotation. Line-scan costs more in motion, encoder, line lighting, and often a frame grabber, so use it only when the product is continuous or too big for area-scan.

How much does a machine vision camera cost? A mainstream industrial area-scan camera with a current global-shutter sensor runs roughly $400 to $1,500, embedded modules under $100, high-resolution and high-speed models $1,500 to $5,000, and smart cameras, 3D sensors, and line-scan systems $5,000 to $15,000 and up. The camera is a fraction of the installed system: budget the lens (which can cost as much as the camera), lighting, compute, cabling, software, and the engineering to light, calibrate, and validate the application. Compare real cameras on the sensor leaderboard.