勛圖tv 繚 ENGINEERING GUIDE
SMD vs COB vs DOB LED: Package and Driver Architecture
SMD, COB and DOB do not always describe three competing LED package types. SMD commonly describes a surface-mounted packaged component, COB describes chip-on-board construction, and DOB is often used for driver-on-board integration. Some sellers also use DOB for other concepts, including diffusion-on-board. A meaningful comparison begins by defining the term in the supplier's actual document.
This page separates emitter packaging from driver placement so a buyer can compare like requirements. It does not rank one acronym as universally better. For the electrical operating window, continue to LED driver PCB circuit design; for horticultural photon requirements, use the grow-light PCB guide.
Put packaging and circuit integration on separate axes
A packaged surface-mount LED is installed as a component with defined terminals, footprint and package characteristics. A COB light source integrates bare dies on a substrate with associated interconnections and optical materials. Both descriptions still leave important details open, including die arrangement, thermal path, optical area and electrical configuration.
Driver-on-board describes where current-control or power circuitry is located. It can coexist with different emitter packaging approaches. It does not, by itself, mean that a product is isolated, non-isolated, dimmable or suitable for a particular input supply. Those properties require the actual circuit and product specification.
Ask the supplier to define ambiguous marketing terms in a drawing or data sheet. A photograph of a yellow emitting area is insufficient to establish construction. Likewise, a board carrying LEDs and several additional components does not reveal the control method or insulation arrangement. Compare documented functions and interfaces rather than guessing from visual similarity.
Compare two independent design axes
| Term | What it describes | Still to establish |
|---|---|---|
| SMD LED | A packaged surface-mounted emitter | Part, optics, current and heat path |
| COB LED | Chip-on-board light-source construction | Die network, substrate and mounting |
| Driver-on-board | Location/integration of drive circuitry | Topology, isolation and thermal interaction |
| DOB in a listing | Potentially ambiguous terminology | Supplier definition and exact product drawing |
Start with the light-engine requirement
Specify the output quantity, spectral or color requirement, emitting area, intended optics and operating current. A compact source can interact differently with a lens than a distributed array. An apparent package-efficiency advantage may not survive the complete optical system if the beam or mixing requirement changes.
Record the electrical operating range and the current-control arrangement. A COB module may contain many dies in a series/parallel network, while a distributed SMD array can also be configured in many ways. The count of visible packages does not determine string voltage. Obtain the allowed drive conditions and the meaning of any typical performance figures.
Consider service and replacement requirements. A board with individually placed packages and an integrated COB light engine have different repair and handling implications. Neither construction should be selected purely from the possibility of replacing one visible part. The approved repair process, optical matching and thermal interface must remain valid after repair.
| Review item | What to establish |
|---|---|
| Terminology | Supplier definition of SMD, COB and any use of DOB. |
| Optics | Output quantity, spectrum/color, emitting area and installed optics. |
| Electrical | Actual string arrangement, driver location and operating window. |
| Thermal | Comparable reference points and full installed heat path. |
| Decision | Exact evidence, unresolved tradeoffs and controlled substitutions. |
Compare thermal paths with their boundaries visible
Follow heat from the emitting junctions through the package or substrate, attachment, PCB or carrier, interface material and housing. The weakest part of this path may sit outside the item being compared. A low package thermal-resistance number does not establish the temperature of the complete luminaire.
Check whether a quoted thermal value uses the same reference points and test conditions. Junction-to-solder-point, junction-to-case and system-to-ambient values cannot be inserted interchangeably into one calculation. The footprint, attachment area and actual board construction also matter. Keep the intended heatsink and enclosure in the comparison rather than evaluating a bare light source in isolation.
Assembly process requirements differ by exact component and construction. Use the selected supplier's handling, reflow or attachment instructions. Avoid assuming every COB is mounted by the same process or every SMD package tolerates the same rework profile. The final BOM and process documents should identify the actual component revision.
Examine what driver integration changes
Locating the driver near the emitters can shorten some connections and simplify a mechanical arrangement, but it also places driver losses and sensitive control circuitry near LED heat. Review component temperatures, optical shadowing, electrical separation and service access. A smaller assembly is not automatically easier to cool or qualify.
If the driver is remote, include cable behavior, connector reliability, startup and output compliance in the review. The board still needs an interface specification. Moving a function off the LED substrate changes the system boundary rather than eliminating that function or its cost.
For a distributed product, the LED strip design guide explains rail drop and feed placement. A strip's use of surface-mounted LEDs does not settle whether its current control is local or remote. Treat package, electrical segment and installation topology as related but distinct decisions.
LED architecture comparison record
LED architecture comparison record
Use the current inputs and keep the assumptions
Load the example to inspect its units, then clear it before entering your own revision. Example values are deliberately labeled assumptions. Complete every field; an empty numeric input is not zero. Record the operating condition behind a value rather than copying the first number found on a component summary. For a comparison, keep the measurement boundary and units consistent.
Calculate after checking the inputs. Any edit invalidates the old result and disables its report download until you calculate again. An edited example remains identified as an example. Results and reports are generated locally without uploading a circuit or populating Contact. Attach the downloaded text manually if it helps explain the question. You can request a review directly without completing the tool.
| Input | What to establish before using it |
|---|---|
| Review reference | Nonconfidential revision label. |
| Requirements and evidence 繚 CSV | Status is Open, Recorded or Not applicable. A recorded claim needs a reference; an exclusion needs a reason. |
Use an evidence matrix instead of a universal winner
Enter each important requirement with a reference to the exact product document, drawing or measured result. Use open when a question remains unresolved, recorded when a specific reference is available, and not applicable only with a reason. The tool validates the structure of the entries, not the truth of a supplier's claim.
A useful comparison might show that one candidate meets the optical-area requirement but lacks documented dimming behavior, while another has the needed electrical interface but requires a larger housing. Those tradeoffs should remain visible. Counting completed rows into a single score can obscure the requirement that actually determines suitability.
Record the operating conditions behind every efficiency, output and thermal figure. Do not compare a typical room-temperature LED result with a measured hot luminaire result as if they described the same boundary. If comparable evidence is unavailable, request it or prototype the relevant condition; do not fill the gap with an attractive marketing number.
Carry the selected construction into purchasing and acceptance
The RFQ should identify the chosen emitter part or construction, permitted alternatives, board or carrier dimensions, drive interface and mechanical mounting. State the optical and electrical acceptance scope and whether the supplier is delivering a light engine or a finished luminaire. Include binning and traceability requirements when they matter to the product.
After a choice is made, preserve the rationale and the documents used. A later substitution may retain the same acronym while changing footprint, thermal behavior or optical distribution. Require review of the affected interfaces rather than treating SMD, COB or DOB as a sufficient replacement specification.
勛圖tv can review a defined PCB or assembly request with those files and requirements. The useful starting point is the physical construction and deliverable, not an unsupported claim that one packaging style always lasts longer or costs less. A clear comparison reduces the risk of buying components that fit the label but not the application.
Specify optical and electrical conditions together
An LED board has an electrical operating point and an optical result, and both depend on the thermal boundary. Record current, temperature, package/bin identity and measurement geometry with any light-output value. A nominal package name does not establish color consistency, lifetime or fixture performance.
Separate the board from the driver, optics and housing in the acceptance plan. The assembled luminaire may introduce thermal interfaces, wiring losses and optical redistribution that are absent at board test. Preserve the exact reference point for temperature measurements and the operating duration used to reach the test condition. For procurement, identify required electrical tests, optical sampling, mechanical integration and traceability. A component datasheet or allowance calculator cannot substitute for those agreed deliverables.
Standards, source context and limits
Use the exact device revision and application conditions when applying manufacturer guidance. Reference designs are evidence about a specified implementation, not automatic validation of a modified board. Workmanship inspection, functional verification, product safety and application performance are different acceptance tasks. Public summaries do not replace the applicable licensed standards or a project-specific acceptance specification.
For fabrication scope and the agreed construction requirements, see PCB manufacturing.