How to Choose a LiDAR: The 2026 Buyer's Guide

Most LiDAR purchases go wrong at the same place: the buyer sorts a spec table by range, picks the sensor that sees furthest, and discovers on the robot that the useful number was never range. A warehouse AMR that travels at 1.5 m/s and stops in half a meter gains nothing from 200 m of range; what it needs is dense returns in the near field, a clean scan through forklift exhaust and dust, and a safety rating the plant auditor will accept. A survey drone mapping a quarry needs the opposite: long range, tight range accuracy, and a wavelength that survives full noon sun off wet rock. The same word, LiDAR, covers a $200 hobby scanner and a $10,000 automotive-grade unit, and the spec that decides your project is almost never the one printed largest on the datasheet.

The order that works starts with the platform and the scene, not the sensor catalog. What is the LiDAR mounted on, how fast does it move, how far away is the thing it must detect in time to react, what is the smallest object that matters at that distance, and what does the environment throw at it: sun, rain, dust, spray, vibration, and the reflectivity of the surfaces you actually care about. Fix those and the architecture picks itself. A slow indoor robot wants a 2D safety scanner or a compact 3D spinner. A highway vehicle wants a long-range solid-state unit at 1550 nm. A survey drone wants a lightweight scanner with survey-grade range accuracy tied to GNSS/RTK. Only after the use case is nailed down do points-per-second, channel count, and field of view start to mean something, because now you are trading them for a known scene and a known reaction distance.

This guide is the buying hub for LiDAR on this site. It gives you a decision framework by use case (mobile-robot navigation, mapping and survey, autonomous vehicles, drones, and industrial safety), the specs that actually decide a purchase and how they trade against each other, the scanning-architecture question (mechanical spinning versus solid-state MEMS, flash, and OPA), the wavelength and eye-safety math (905 versus 1550 nm), the split between safety-rated and perception LiDAR that trips up first-time industrial buyers, cost bands with what each buys, and the vendor landscape by category. Throughout it points at the deeper LiDAR and depth cameras guide and at the live sensor leaderboard, where you can sort real LiDAR and depth sensors by range, resolution, field of view, and price instead of trusting a brochure.

The take: Choose the use case before the sensor. The platform, its speed, and the distance at which it must detect a target set the range and resolution you need; the scene and the environment pick the scanning architecture and the wavelength; and the application (a safety stop versus a perception input) decides whether you need a certified safety-rated LiDAR or a raw point-cloud sensor. Range is the spec buyers over-weight and near-field resolution, weather robustness, and safety rating are the specs they under-weight. Answer two questions first, "how far and how small must I detect, and how fast am I closing on it," and "does this LiDAR stop a machine or feed a perception stack," and the shortlist writes itself. Everything after that is trading points-per-second against field of view against price for a job you have already defined.

Companion reading: LiDAR & depth cameras, depth sensing: stereo, ToF, structured light, SLAM & localization, self-driving cars & autonomous vehicles, robot safety & functional safety, and how to choose an AMR or AGV.

Table of contents

1. Key takeaways
2. Start with the use case, then read the specs
3. Scanning architecture: mechanical vs solid-state
4. Range, range accuracy, and the returns that matter
5. Resolution: channels, points per second, and field of view
6. Wavelength and eye safety: 905 vs 1550 nm
7. Environmental robustness: sun, weather, and IP
8. Safety-rated LiDAR vs perception LiDAR
9. Interfaces, point-cloud output, and compute
10. Cost bands and what each buys
11. The vendor and ecosystem landscape
12. Integration and total cost of ownership
13. A repeatable selection process
14. Frequently asked questions
15. Changelog

Start with the use case, then read the specs

Five buyer segments cover almost every LiDAR purchase, and each weights the specs differently. Find your platform here, then let it tell you which numbers to chase and which to ignore.

Use case	What decides the buy	Typical range	Typical field of view	Architecture that usually wins
Mobile-robot navigation (AMR/AGV)	Near-field density, 360 coverage, safety rating	10 to 100 m	360 H, narrow to 30 V	2D safety scanner + compact 3D spinner
Mapping and survey	Range accuracy, point density, GNSS/RTK tie-in	100 to 300 m	360 H or corridor, wide V	Survey-grade spinner or scanning payload
Autonomous vehicles	Long-range small-object detection, reliability	150 to 300+ m	120 forward, or 360 roof	Solid-state / long-range at 1550 nm
Drones and UAV	Weight, range accuracy, power draw	40 to 250 m	corridor to 70 wide	Lightweight solid-state or compact spinner
Industrial safety	Certified stop, response time, coverage	3 to 40 m protective	270 H, 2D plane	Certified 2D safety scanner

A sentence each on what actually decides the fit, because the headline range figure is usually a distraction.

Mobile-robot navigation (AMR/AGV). An indoor or campus robot needs to localize, map, and avoid obstacles while moving at walking pace. What matters is a full 360-degree horizontal field so nothing sneaks in from the side, dense returns in the first 10 to 30 m where the robot will actually stop, and, for anything that shares space with people, a separate certified safety scanner that commands the stop. Long range is close to useless here; a 40 m clean 3D scan beats a 200 m sparse one every time. This is the segment the AMR and AGV buyer's guide covers end to end, and the localization side is in the SLAM guide.

Mapping and survey. A LiDAR bolted to a drone, backpack, or vehicle to build a point cloud of terrain, infrastructure, or buildings. Here range accuracy (how tightly each measured distance matches truth) and point density decide the deliverable, and the LiDAR is only half the system: it must be tied to a GNSS/RTK position and an IMU so every point lands in world coordinates. Absolute range matters for altitude and standoff, but a 3 cm range error on a survey job is a failed survey while it would be invisible on an obstacle-avoidance robot.

Autonomous vehicles. A car at highway speed closes 30 m every second, so it must detect a small, dark, low-reflectivity object (a tire in the lane, a pedestrian in dark clothing) far enough out to react. That drives long range at low reflectivity, tight angular resolution at distance, and automotive-grade reliability and temperature range. This is where 1550 nm and long-range solid-state units earn their premium. The full stack context is in self-driving cars and autonomous vehicles.

Drones and UAV. Weight and power are the hard constraints. A LiDAR on a UAV competes with battery for every gram, so the market is lightweight compact scanners and solid-state units, sized for the platform's payload and flight time. Corridor mapping, powerline inspection, and terrain following each want a different field of view. The platform limits are covered in drone and UAV hardware.

Industrial safety. A LiDAR whose job is to stop a machine or an AGV before it hits a person. This is a regulated product: it must be certified to a safety performance level and standard, have a validated response time, and offer configurable protective and warning fields. Point-cloud richness is beside the point; the certification and the response time are the product. This is a separate purchase from perception LiDAR and is treated in its own section below.

Rule of thumb: If you cannot state the detection distance for your smallest relevant target at your worst-case reflectivity, plus how fast you are closing on it, you are not ready to compare LiDAR. "Detect a person in dark clothing at 60 m while closing at 20 m/s" is a spec. "Long range" is not.

Scanning architecture: mechanical vs solid-state

How the LiDAR steers its beam across the scene is the first structural fork, and it shapes coverage, reliability, cost, and how the point cloud looks. Four broad approaches cover the market.

Architecture	How it scans	Field of view	Strengths	Weaknesses
Mechanical spinning	Rotating assembly of laser/detector rows	Full 360 H, fixed V	Full surround, dense mature clouds, proven	Moving parts, wear, height, cost at high channel count
Solid-state MEMS	Micro-mirror steers beam	60 to 120 forward	No large moving parts, compact, robust	Forward field only, mirror is a small moving part
Flash	Illuminate whole scene, detector array	Wide, fixed	No scanning, instant frame, rugged	Shorter range, resolution limited by array
OPA / true solid-state	Electronically steered phased array	Forward, programmable	No moving parts at all, steerable	Emerging, cost and maturity still developing

Mechanical spinning. The established architecture, and still the default for robotics that needs 360-degree awareness. A stack of laser and detector rows spins, giving a full horizontal ring and a fixed vertical fan of channels. It delivers dense, well-understood point clouds and the widest coverage, which is why AMRs, survey rigs, and rooftop autonomous-vehicle sensors still use it heavily. The costs are mechanical: a spinning assembly wears, adds height, and gets expensive as channel count climbs. Velodyne (now Ouster) built this category; Ouster, Hesai, and RoboSense all ship strong spinners.

Solid-state MEMS. A tiny micro-mirror steers the beam across a forward field of view, so there is no large rotating mass. This buys a compact, vibration-tolerant, lower-cost sensor with automotive reliability, at the price of coverage: you get a forward cone (commonly 60 to 120 degrees horizontal), not a full ring. It suits forward-looking automotive perception and robots that only need to see where they are going. Many "solid-state" units on the market are MEMS, so read whether the field is forward-only before you assume 360.

Flash. The LiDAR floods the whole scene with a single pulse and reads the return on a detector array, like a depth camera with its own illumination. There is no beam steering at all, so it is rugged and captures a full frame at once with no motion blur, which suits short-range, high-frame-rate tasks. The tradeoff is range and resolution: spreading the energy over the whole scene limits how far it reaches and the array pixel count caps resolution.

OPA and true solid-state. An optical phased array steers the beam electronically with no moving parts whatsoever, and can in principle point anywhere in its field on demand. It is the most robust architecture in theory and the least mature in practice, still climbing the cost and performance curve in 2026. Treat it as promising for specific programs rather than a safe default.

Rule of thumb: If you need to see all around the robot, start with a mechanical spinner and accept the moving parts. If you only need to see forward, are fighting vibration or a temperature range, or are going into a vehicle at volume, a solid-state MEMS unit is usually the better buy. Match the field of view to what the platform actually has to watch, not to the largest number available.

Range, range accuracy, and the returns that matter

Range is the most quoted and least understood LiDAR spec, because vendors quote it under conditions you will rarely meet. Read three things behind the headline number.

Maximum range and the reflectivity it assumes. A LiDAR's range depends heavily on how reflective the target is. Datasheets often quote a big number against a 80 or 90 percent reflective target (a road sign, white cardboard) and a much smaller number against a 10 percent target (dark asphalt, black clothing, a wet tire). The 10 percent figure is the one that matters for safety and perception, because the objects you most need to detect are often dark and low-reflectivity. A unit advertised at 200 m may see a dark pedestrian at 40 to 70 m. Always find the low-reflectivity range and size your reaction distance to that.

Range accuracy and precision. Accuracy is how close a measured distance is to truth; precision (or noise) is how much repeated measurements of the same point scatter. Perception LiDAR typically holds a few centimeters of accuracy, which is fine for obstacle avoidance. Survey and mapping demand tighter, often 1 to 3 cm or better, because the point cloud is the deliverable and error compounds across a scan. If you are mapping, this is your headline spec, not maximum range.

Minimum range and the blind zone. Every LiDAR has a near blind zone where it cannot measure, often a few centimeters to a meter depending on design. On a small robot that operates in tight spaces, a large minimum range leaves a dead ring around the sensor where obstacles vanish. Check it; it is easy to miss and painful on a compact platform.

Multiple returns. A single laser pulse can hit more than one surface (a leaf then the ground behind it, rain then a wall) and a good LiDAR reports several returns per pulse. This matters for survey through vegetation (you want the ground return under the canopy) and for perception in rain, dust, and snow, where the first return may be a particle and the last is the real object. If you work in foliage or weather, count the returns the sensor reports.

Spec	Perception robotics	Survey and mapping	Autonomous vehicle
Max range (10% target)	20 to 80 m	100 to 250 m	100 to 250 m
Range accuracy	2 to 5 cm	1 to 3 cm or better	2 to 5 cm
Minimum range	check for tight spaces	standoff-dependent	not critical
Returns per pulse	1 to 2 for weather	2 to 3 for vegetation	2 to 3 for weather

War story: A team building an outdoor delivery robot picked a LiDAR on its headline 100 m range and set the emergency-stop distance from that. In testing the robot repeatedly failed to see a person in a dark coat until roughly 45 m, because 100 m was the 90 percent reflectivity figure and a dark coat returns closer to 10 percent. At 2 m/s they had margin, but the same mistake on a faster platform would have been a collision. They resized every safety distance to the low-reflectivity range. Read the reflectivity behind the range number before you trust it.

Resolution: channels, points per second, and field of view

Resolution is what decides whether the LiDAR sees the object at all, and it is three numbers working together, not one.

Channel count and vertical resolution. A spinning LiDAR's channels are the number of laser rows stacked vertically, from 16 up to 128 and beyond. More channels pack the vertical fan tighter, so a distant object subtends more scan lines and is easier to classify. At range the vertical gap between beams grows, so a 16-channel unit may put only one line on a person at 30 m while a 64-channel unit puts several. Vertical resolution, quoted in degrees between beams, is the spec to compare across units; fewer degrees between beams is denser.

Points per second. The total measurement rate, from a few hundred thousand points per second on entry units to several million on high-end and dual-return sensors. Higher rate fills the cloud faster and supports higher frame rates or denser scans, which helps perception software find small objects and helps survey hit point density targets. Read it together with frame rate, because points-per-second spread thin over a fast frame rate gives a sparse individual frame.

Field of view, horizontal and vertical. Horizontal is 360 degrees on a spinner and a forward cone (60 to 120 degrees typical) on solid-state. Vertical is the fan height, commonly 30 to 45 degrees on perception spinners and narrower on some units. The vertical field decides how much of a tall object or a slope you capture from a fixed mounting height, and it interacts with where you mount the sensor. A narrow vertical fan mounted low may never see an overhanging obstacle or the top of a pallet.

Frame rate. How many full scans per second, typically 10 to 20 Hz for spinners, higher for some solid-state and flash units. Faster platforms need higher frame rates so the world does not move too far between scans. A robot at 2 m/s moves 20 cm between frames at 10 Hz, which is usually fine; a vehicle at 30 m/s moves 3 m at 10 Hz, which argues for a faster frame or motion compensation.

You want more	You give up	When it is worth it
Channel count / vertical resolution	Cost, sometimes size	Small-object detection at range, classification
Points per second	Cost, data bandwidth	Dense survey, fast perception
Field of view (360)	Solid-state reliability	Surround awareness on mobile robots
Frame rate	Points per frame	Fast platforms, motion at speed

Rule of thumb: Pick channel count and vertical resolution from the smallest object you must detect at your maximum detection distance, then check that your frame rate keeps the world from moving too far between scans. Buying 128 channels for a slow indoor robot that stops in half a meter is spending on resolution nobody will use; buying 16 channels for highway perception strands you with objects that fall between the beams.

Wavelength and eye safety: 905 vs 1550 nm

The laser wavelength is a quiet spec with large consequences for range, weather, cost, and safety, and the two dominant choices sit at opposite ends of a clear trade.

905 nm. The common wavelength in robotics and lower-cost automotive LiDAR. Silicon detectors work at 905 nm, which keeps the sensor cheap and mature. The catch is eye safety: 905 nm sits in the near-infrared where the eye's lens focuses the beam onto the retina, so the maximum permissible exposure limits how much optical power you can emit and stay Class 1 (eye-safe). That power ceiling caps range and hurts performance against sun and haze. For most indoor and short-to-medium-range robotics, 905 nm is the right and economical choice.

1550 nm. Further into the infrared, where the eye's fluid absorbs the light before it reaches the retina, so the eye-safe power limit is far higher. That lets a 1550 nm LiDAR emit much more optical power within Class 1, reaching further and punching through bright sun, haze, and light rain better than 905 nm can. The cost is the detector: silicon does not work at 1550 nm, so these units use indium gallium arsenide (InGaAs) detectors, which are more expensive. This is the wavelength of choice for long-range automotive LiDAR (Luminar built its business on 1550 nm) where seeing a dark object far out in daylight is the whole job.

Both can be built to Class 1 eye-safe, which is the rating you want for any product operating around people. The difference is what performance you can reach while staying eye-safe: 1550 nm buys range and sun robustness for money, 905 nm buys economy at the cost of ultimate range.

	905 nm	1550 nm
Detector	Silicon (cheap, mature)	InGaAs (costlier)
Eye-safe power ceiling	Lower	Much higher
Range at Class 1	Shorter to medium	Long
Sun / haze robustness	Moderate	Better
Cost	Lower	Higher
Typical use	Robotics, short-medium automotive	Long-range automotive

Rule of thumb: For indoor and short-to-medium-range robotics, 905 nm is the economical default and there is no reason to pay for 1550 nm. When you need long range in bright daylight against dark objects (highway autonomy, long-standoff perception), 1550 nm is what makes the eye-safe power budget work, and the detector premium is the price of that range. Confirm Class 1 eye safety on any sensor that operates near people regardless of wavelength.

Environmental robustness: sun, weather, and IP

A LiDAR that performs on a bench and fails in the rain is a common and expensive surprise. Three environmental factors decide whether the sensor survives your scene.

Sunlight. Bright sun floods the detector with background near-infrared and raises the noise floor, cutting effective range, especially at 905 nm. Vendors quote performance under a solar irradiance figure (often around 100 klux for full sun); confirm the range you need holds at full sun, since the shaded lab number will read optimistic. Outdoor robots and vehicles live in this, so it is a real filter.

Rain, fog, dust, and snow. Airborne particles scatter and absorb the beam, cutting range and generating false returns from the particles themselves. Multi-return processing and good firmware filtering help distinguish a raindrop from a wall, but no LiDAR sees through heavy fog or a snowstorm the way it sees through clear air. If you operate outdoors in weather, ask for degraded-condition performance figures and test in real rain, because the clear-air datasheet is optimistic. This is a large part of why autonomous vehicles fuse LiDAR with radar, which shrugs off weather; that fusion is covered in the sensor fusion guide context of the depth-sensing guide.

Ingress protection and mechanical robustness. The IP code rates sealing against dust (first digit) and water (second). Outdoor and mobile LiDAR wants IP67 or better so dust and spray do not reach the optics or electronics. Beyond IP, check operating temperature range (automotive units span roughly -40 to +85 C, robotics units less), and shock and vibration ratings for anything on a vehicle, drone, or rough-terrain robot. A spinning LiDAR's bearing life under continuous vibration is a real reliability number on a mobile platform.

Environment	What to check	Why
Full sun outdoors	Range at ~100 klux	Solar noise cuts range, worse at 905 nm
Rain, fog, snow	Multi-return, degraded-condition range	Particles scatter beam, false returns
Dust, spray	IP67+, sealed optics	Contamination kills range and reliability
Vehicle, drone, rough terrain	Vibration/shock rating, temp range, bearing life	Mechanical failure and drift

Safety rule: Specify the environmental performance before you compare resolution or range, and validate it in the real condition. A LiDAR whose range collapses in the rain your robot works in, or whose optics fog and clog with the dust in your plant, has no other specs worth reading. Weather robustness is why safety-critical outdoor systems fuse LiDAR with radar rather than trusting the point cloud alone.

Safety-rated LiDAR vs perception LiDAR

The distinction that trips up the most first-time industrial buyers is that a safety-rated LiDAR and a perception LiDAR are different products with different jobs, and you cannot substitute one for the other.

Perception LiDAR produces a point cloud for software to interpret: mapping, localization, obstacle detection, classification. It carries no functional-safety certification, its failure modes are not certified, and nothing about it guarantees it will detect an obstacle every time. It is a rich input to a perception stack. Ouster, Hesai, RoboSense, Livox, and the automotive units all sit here. Use them to make a robot smart.

Safety-rated LiDAR is a certified protective device. A SICK, Pilz, Datalogic, or equivalent safety laser scanner is certified to IEC 61496 (electro-sensitive protective equipment) and rated to a performance level (typically PLd per ISO 13849) or a safety integrity level (SIL2 per IEC 62061), with a validated response time and defined, monitored failure behavior. It projects a 2D protective field, and when something enters that field it commands a machine stop through safety-rated outputs, with the whole chain designed so a fault leads to a safe state. This is what stops an AGV before it hits a person, or halts a machine when someone reaches in. The full framework is in robot safety and functional safety.

The practical consequences for a buyer:

• If a LiDAR's job is to prevent injury, it must be safety-rated and integrated into a safety function with a safety controller. A perception LiDAR and clever software do not satisfy an auditor or the machinery regulations, no matter how good the point cloud is.
• Safety scanners are usually 2D (a single scanning plane) with configurable protective and warning zones you can switch by speed or state. That is enough to guard a plane around an AGV or a machine, and it is a different capability from a 3D perception cloud.
• Many mobile robots carry both: a certified 2D safety scanner low down for the protective stop, and one or more 3D perception LiDAR for navigation and richer obstacle sensing. They do separate jobs and you budget for both.

	Perception LiDAR	Safety-rated LiDAR
Purpose	Point cloud for software	Certified protective stop
Certification	None	IEC 61496, PLd / SIL2
Output	Rich 3D/2D data	Safety-rated stop signal + zones
Typical dimensionality	2D or 3D, high resolution	2D scanning plane
Failure behavior	Undefined	Monitored, fails to safe state
Vendors	Ouster, Hesai, RoboSense, Livox	SICK, Pilz, Datalogic, Omron

Safety rule: Never use a perception LiDAR as a protective device. If the sensor's failure could injure someone, buy a certified safety-rated scanner, size the protective and warning fields to your stopping distance at speed, and integrate it through a safety controller under ISO 13849 or IEC 62061. The point-cloud quality of a perception unit is irrelevant to whether it is allowed to stop a machine.

Interfaces, point-cloud output, and compute

The LiDAR has to get its data into your system and you have to have the compute to use it. Getting the interface and the software right is the difference between a sensor that streams on day one and a week of driver work.

Physical and data interface. Most 3D perception LiDAR streams over Gigabit Ethernet using UDP packets, which handles the bandwidth of millions of points per second. Some compact and automotive units use USB or automotive interfaces; safety scanners often provide safety-rated digital outputs plus a configuration and monitoring interface. Confirm the interface matches your compute (an Ethernet port and the bandwidth headroom) and that the cabling and connectors suit a moving platform, where flex life and sealing matter. The wiring side is in the robot wiring and connectors guide referenced in the LiDAR deep guide.

Software, drivers, and ROS support. The value of a LiDAR is only realized through its driver and toolchain. Check for a maintained ROS 2 driver (most major vendors ship one), a clear point-cloud format and timestamping, and time-synchronization support (PTP or a hardware sync signal) if you fuse multiple sensors or tie the cloud to GNSS/IMU. A vendor with poor software support turns a good sensor into an integration project. Livox, Ouster, Hesai, and RoboSense all publish SDKs and ROS drivers of varying maturity; weigh the driver quality alongside the hardware.

Compute burden. A dense 3D point cloud at several million points per second is a real load on the onboard computer for filtering, registration, SLAM, and perception. Size the compute for the point rate you buy, because a high-channel LiDAR feeding a small single-board computer will drop frames or lag. The onboard compute tradeoffs are covered in the edge AI robot compute context of the depth-sensing guide; the point is to budget the processor alongside the sensor.

Calibration and extrinsics. A LiDAR only helps once you know exactly where it sits relative to the robot and the other sensors. Extrinsic calibration (LiDAR to IMU, LiDAR to camera, LiDAR to base) is a required step, more involved for survey and multi-sensor fusion. Factor the calibration effort and tooling into the project.

Rule of thumb: Weigh the software and driver support as heavily as the hardware specs. A LiDAR with a mature ROS 2 driver, clean timestamping, and PTP sync drops into a stack in an afternoon; one with a flaky SDK and no time sync eats a week and never quite fuses cleanly with your camera. Confirm the interface bandwidth and the onboard compute can carry the point rate you are buying.

Cost bands and what each buys

LiDAR pricing steps by capability and application, and the sensor is only part of the system cost. These bands are for the sensor in 2026; integration and compute come on top.

$200 to $1,500: hobby 3D, entry 2D, and low-channel spinners. Low-channel spinning LiDAR (single-plane 2D units and 8 to 16 channel 3D scanners) and hobbyist and research sensors. This tier suits indoor robots, education, prototypes, and slow platforms that need coverage more than range or density. Do not expect long range, high resolution, or any safety certification.

$1,500 to $8,000: mainstream 3D perception LiDAR. The volume tier for robotics and light autonomy: 16 to 128 channel spinners and mid-range solid-state units from Ouster, Hesai, RoboSense, and Livox, with the range, resolution, and driver support that most AMRs, mobile robots, and mapping payloads need. Livox in particular pushed non-repetitive-scan LiDAR into this band at aggressive prices. Most robotics LiDAR purchases land here.

$4,000 to $12,000: certified safety scanners. SICK, Pilz, Datalogic, and Omron 2D safety laser scanners with IEC 61496 certification, configurable fields, and safety-rated outputs. The premium buys the certification and the validated response time, which is the product. AGV and machine-guarding buyers pay this for the ability to command a legal safety stop.

$500 to $10,000+: automotive-grade and long-range solid-state. Wide band because automotive LiDAR spans low-cost forward units to premium long-range 1550 nm sensors (Luminar, Innoviz, and the Hesai and RoboSense automotive lines). High volume drives some units low, while long-range flagship sensors sit high. Survey-grade integrated payloads (LiDAR plus IMU plus GNSS in one unit, from vendors like those building on Hesai and RIEGL cores) run several thousand to tens of thousands depending on accuracy.

Band	Get	Do not expect	Best for
$200 to $1,500	2D and low-channel 3D, hobby	Long range, safety cert	Indoor robots, prototypes, education
$1,500 to $8,000	16 to 128 ch spinners, mid solid-state	Safety cert, survey accuracy	AMRs, mobile robots, mapping payloads
$4,000 to $12,000	Certified 2D safety scanner	3D perception cloud	AGV guarding, machine safety
$500 to $10,000+	Automotive / long-range 1550 nm, survey payloads	A cheap total system	Vehicles, long-range, survey-grade

Sort the sensor leaderboard by price against range, resolution, and field of view to see where the value steps fall in the current generation rather than trusting a band chart in the abstract.

Rule of thumb: Buy the band your detection distance, resolution, and certification need require, then stop. Over-buying channels and range costs money and compute you will not use; under-buying resolution strands you with objects that fall between the beams, and under-buying a perception sensor for a safety job leaves you with a device an auditor will reject. The sensor price is the easy part; the compute, mounting, and integration are the rest.

The vendor and ecosystem landscape

The LiDAR market consolidated hard over the last several years, and knowing who owns which category shortcuts your shortlist.

Broad perception LiDAR (Ouster, Hesai, RoboSense). Ouster (which absorbed Velodyne, the company that created the modern spinning LiDAR) offers a wide digital-LiDAR range from short-range dome sensors to long-range units, with strong software and a large robotics install base. Hesai (China) is a volume leader across robotics and automotive, spanning compact spinners to long-range automotive units, and ships high point-rate sensors at competitive prices. RoboSense (China) covers a similar breadth with strong automotive traction and solid-state units. These three are the default starting point for a 3D perception LiDAR on a robot or vehicle.

Value and non-repetitive scan (Livox). Livox (a DJI affiliate) disrupted pricing with non-repetitive-scanning LiDAR that builds up density over time, delivering usable 3D perception and mapping at prices well below traditional spinners. It is popular in robotics, drone mapping, and cost-sensitive autonomy, with the caveat that the non-repetitive scan pattern behaves differently from a uniform spinner and some perception and SLAM software expects the uniform pattern. Read the scan pattern before assuming it drops in.

Automotive long-range (Luminar, Innoviz, plus Hesai and RoboSense automotive lines). Luminar built its name on 1550 nm long-range LiDAR for highway autonomy, chasing dark-object detection at distance (the company entered Chapter 11 restructuring in 2025, so confirm its supply status if you are designing it in). Innoviz supplies MEMS-based automotive LiDAR to OEM programs. Hesai and RoboSense both field automotive-grade long-range units in volume. This is the segment where 1550 nm, long range, and automotive qualification matter, and where design wins are program-by-program.

Safety-rated scanners (SICK, Pilz, Datalogic, Omron). SICK is the reference name in safety laser scanners, the microScan and nanoScan families guarding AGVs and machines worldwide, certified and widely accepted by auditors. Pilz, Datalogic, and Omron also field certified safety scanners. When the LiDAR's job is a legal safety stop, this is the category, and it is separate from the perception vendors above.

Survey and mapping (RIEGL, and integrated payload builders). RIEGL (Austria) is a long-standing survey-grade LiDAR maker for airborne and terrestrial mapping with high range accuracy. Many drone-mapping payloads integrate a LiDAR core (from RIEGL, Hesai, Livox, or Ouster) with an IMU and GNSS/RTK into a turnkey survey unit. When the deliverable is a georeferenced point cloud, shop the integrated payload and its accuracy specification, not the bare LiDAR.

How to choose among them. For a mobile robot needing perception, shortlist Ouster, Hesai, RoboSense, and Livox and weigh the ROS driver and software maturity alongside range and resolution. For a safety stop, buy SICK or an equivalent certified scanner and treat it as a separate line item. For a vehicle program, the automotive vendors compete on long-range dark-object detection and qualification. For survey, buy the integrated payload sized to your accuracy target. You can filter the sensor leaderboard by range, resolution, and field of view to build a like-for-like shortlist before you talk to a sales team.

Integration and total cost of ownership

The LiDAR sticker price is a fraction of what the sensing subsystem costs to field and run. Price the whole thing before you compare quotes.

Compute and software. A dense point cloud needs a processor to filter, register, and interpret it, plus the perception, SLAM, or mapping software to turn points into decisions. On a robot that is a real share of the bill of materials and the engineering budget, and it scales with the point rate you buy. A high-channel LiDAR with no compute plan behind it is a sensor that streams data nobody can use in real time.

Mounting, cabling, and calibration. The LiDAR needs a rigid, vibration-damped mount at the right height and angle, sealed cabling rated for a moving platform, and extrinsic calibration to the robot and the other sensors. Multi-sensor fusion (LiDAR plus camera plus IMU plus GNSS) adds time synchronization hardware and a calibration procedure that recurs whenever the rig changes. Budget the calibration effort, because a beautifully specified LiDAR that is not calibrated to the platform produces a point cloud in the wrong place.

Multiple sensors. Many platforms need more than one LiDAR: a safety scanner plus perception LiDAR on an AMR, or multiple units for full coverage on a vehicle. Count the real sensor set the application needs, not a single unit, and add the fusion cost.

Reliability and service life. A spinning LiDAR has a bearing with a finite life under continuous vibration, so mean time between failures and the replacement interval matter on a 24/7 robot. Solid-state units trade some coverage for better reliability here. Factor spares, the failure mode when a LiDAR degrades or dies, and whether the robot can operate safely on its remaining sensors.

Weather and cleaning. Outdoor LiDAR optics get dirty. Rain, dust, mud, and salt on the window cut range and generate noise, so field deployments need cleaning (manual, wiper, or air) and a maintenance schedule. This is a running cost and a source of unplanned downtime if ignored.

Rule of thumb: Budget the sensing subsystem, not the LiDAR. Price the sensor plus the compute to use its data, the mounting and cabling, the calibration effort, any second sensor the application needs, and the cleaning and spares over the service life. The LiDAR you agonized over on price is often a modest line next to the compute and integration that make it useful.

A repeatable selection process

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

1. State the use case in one sentence with a detection requirement. "Detect a person in dark clothing at 60 m while the vehicle closes at 20 m/s," or "map a corridor to 2 cm accuracy from a 15 kg drone." If you cannot, stop here until you can.
2. Fix the range from the low-reflectivity detection distance for your smallest relevant target, plus the reaction time your platform needs at speed. Ignore the headline high-reflectivity number.
3. Set the resolution (channel count, vertical resolution, points per second) so your smallest target is seen by enough scan lines at that distance, and confirm the frame rate suits your platform speed.
4. Pick the scanning architecture from the field of view the platform must watch: mechanical spinner for 360 surround, solid-state MEMS for a forward field with better vibration tolerance and reliability, flash for short-range rugged frames.
5. Choose the wavelength: 905 nm for economical short-to-medium robotics, 1550 nm where long range in bright sun against dark objects is the job. Confirm Class 1 eye safety near people.
6. Specify the environmental performance (range at full sun, degraded-condition behavior in your weather, IP rating, temperature, vibration) and validate it in the real condition.
7. Decide safety-rated vs perception. If the sensor could injure someone by failing, buy a certified safety scanner and integrate it through a safety controller; otherwise a perception LiDAR feeds the software. Many platforms need both.
8. Confirm the interface and software. Ethernet bandwidth, a maintained ROS 2 driver, timestamping and PTP sync for fusion, and onboard compute sized for the point rate.
9. Build the real budget: sensor plus compute, mounting, cabling, calibration, any second sensor, cleaning, and spares over the service life.
10. Shortlist on the leaderboard, ranking live models by range, resolution, and field of view, then validate the finalist against your worst-case target and environment before you commit.

Run this in order and the shortlist narrows to one or two sensors you can buy with confidence. Skip the use-case and reflectivity steps and you will do what most first-time buyers do, which is pick on headline range and discover on the platform that the object you needed to see was dark, small, and too close to the beams.

Frequently asked questions

How much does a LiDAR cost? Entry 2D and low-channel 3D scanners run roughly $200 to $1,500, mainstream 3D perception LiDAR from Ouster, Hesai, RoboSense, and Livox about $1,500 to $8,000, certified 2D safety scanners $4,000 to $12,000, and automotive-grade long-range and survey-grade units from several thousand to tens of thousands. The sensor is only part of the cost; budget the compute to process the point cloud, the mounting and calibration, and any second sensor the application needs. Sort the sensor leaderboard by price against range and resolution to see the current value steps.

Mechanical spinning or solid-state, which should I buy? Buy a mechanical spinner when you need a full 360-degree field around a mobile robot and want a mature, dense point cloud, accepting the moving parts and the height. Buy solid-state (usually MEMS) when you only need to see forward, are fighting vibration or a wide temperature range, or are going into a vehicle at volume, since it is compact and more reliable but covers a forward cone rather than a full ring. Match the field of view to what the platform actually has to watch.

What is the difference between 905 nm and 1550 nm? The wavelength sets how much optical power you can emit while staying eye-safe. 905 nm uses cheap silicon detectors but the eye focuses that light on the retina, so the eye-safe power limit is lower and range and sun robustness are capped. 1550 nm is absorbed by the eye's fluid before the retina, so the eye-safe power ceiling is far higher, buying long range and better daylight performance, at the cost of more expensive InGaAs detectors. Use 905 nm for economical short-to-medium robotics and 1550 nm for long-range automotive.

Why is the detection range shorter than the advertised range? Advertised range is usually quoted against a highly reflective target (80 to 90 percent), while the objects you most need to detect are often dark and low-reflectivity (10 percent), and range against a 10 percent target is much shorter. A LiDAR advertised at 200 m may see a dark pedestrian at 40 to 70 m. Always find the low-reflectivity range and size your safety and reaction distances to that, not to the headline number.

Can I use a perception LiDAR as a safety sensor? No. A perception LiDAR carries no functional-safety certification, its failure modes are not certified, and it cannot legally command a machine stop as a protective device. If the sensor's job is to prevent injury, you need a safety-rated scanner (SICK, Pilz, Datalogic, or Omron) certified to IEC 61496 and integrated into a safety function under ISO 13849 or IEC 62061. Many robots carry both: a certified 2D safety scanner for the stop and a 3D perception LiDAR for navigation. See robot safety and functional safety.

Do I need LiDAR at all, or will cameras or radar do? It depends on the task. Cameras and stereo or ToF depth are cheaper and give color and texture but struggle with absolute distance, low light, and featureless surfaces. Radar sees through weather and measures velocity directly but has coarse angular resolution. LiDAR gives dense, accurate 3D geometry in a wide range of lighting, which is why it anchors mapping, SLAM, and safety-critical perception. Many robust systems fuse all three. The tradeoffs are in depth sensing: stereo, ToF, and structured light and the LiDAR and depth cameras guide.

How many channels do I need? Match channel count to the smallest object you must detect at your maximum detection distance. Slow indoor robots and simple mapping do well with 16 to 32 channels; dense perception and small-object detection at range want 64 to 128 or more, because the vertical gap between beams grows with distance and a low-channel unit may put only one scan line on a distant person. Buying more channels than the task needs spends money and compute; buying too few strands objects that fall between the beams.

What about rain, fog, and dust? Airborne particles scatter and absorb the beam, cutting range and generating false returns, and no LiDAR sees through heavy fog or a snowstorm the way it sees through clear air. Multi-return processing and firmware filtering help separate a raindrop from a wall, and outdoor optics need cleaning to stay clear. If you operate in weather, ask for degraded-condition figures, test in real rain, and fuse with radar for safety-critical outdoor work, since radar shrugs off weather that blinds LiDAR.

How do I get the point cloud into my robot software? Most 3D perception LiDAR streams over Gigabit Ethernet as UDP packets and ships a maintained ROS 2 driver, a documented point-cloud format, and time synchronization (PTP or hardware sync) for fusing multiple sensors. Confirm the interface bandwidth, the driver quality, and that your onboard compute can carry the point rate before you buy, because a sensor with a flaky SDK or no time sync turns into a week of integration and never fuses cleanly with your camera.

What matters most for a survey or mapping LiDAR? Range accuracy and point density, plus the tie-in to GNSS/RTK and an IMU so every point lands in world coordinates. Survey deliverables want 1 to 3 cm accuracy or better, and error compounds across a scan, so accuracy matters more than raw maximum range. Buy an integrated payload (LiDAR plus IMU plus GNSS) sized to your accuracy target rather than a bare perception sensor, and check multiple-return support if you map through vegetation to reach the ground under the canopy.