Luminous efficacy calculator

Enter the total light output in lumens and the power consumed in watts, and the calculator divides the first value by the second. The result helps compare how effectively lamps, luminaires, LEDs, and other sources turn electrical input into visible light. It is a direct engineering ratio, not an estimate of lifetime, color quality, illuminance at a surface, or total energy cost.

What luminous efficacy measures

Luminous efficacy expresses how much visible-light output a source produces for each watt of electrical power it consumes. The calculator uses total luminous flux, measured in lumens, as the numerator and electrical input power, measured in watts, as the denominator. A source producing 800 lumens while drawing 10 watts therefore has a luminous efficacy of 80 lumens per watt. This ratio is useful because raw lumen output alone does not reveal the input needed to create that light. Two lamps can deliver similar brightness while drawing substantially different power. The value describes performance at the stated operating point, so measurements should represent the same stable condition. Use the complete luminaire's input power when evaluating a finished fixture, including driver or ballast losses. Use only the emitter's power when the intended comparison is specifically between emitters. State that boundary whenever results are shared, because mixing system-level and component-level measurements creates an apparently precise but misleading comparison. Luminous efficacy is distinct from radiant efficiency: lumens weight optical radiation according to human visual sensitivity, whereas radiant quantities measure physical optical power without that weighting.

How to enter and interpret the values

Enter a positive luminous flux in lumens and a positive electrical power in watts. Both figures should come from compatible measurements: the lamp or fixture should be in the same configuration, at the same drive setting, and preferably at a stable operating temperature. The algorithm evaluates luminous efficacy as luminous flux divided by electrical power, then rounds only the reported ratio to the selected number of decimal places. The original input values remain visible in the result so the calculation can be checked and reproduced. Zero power is rejected because division by zero has no finite result, while negative flux or power is outside the intended physical model. A higher lumens-per-watt result means more photometrically weighted light output for each input watt, but it does not automatically mean better light for every application. Color rendering, spectral distribution, glare control, beam shape, dimming behavior, thermal management, and service life may matter alongside efficacy. When comparing products, also confirm whether the published lumen figure is initial or maintained output and whether the wattage covers the entire product. Consistent measurement boundaries matter more than extra decimal places.

Using the result in design and comparison work

Use the result as one input to lighting selection, energy estimates, laboratory records, or quality-control checks. For a product comparison, calculate every candidate with the same definition of power and the same kind of lumen measurement. For a prototype, record the operating current, temperature, optical configuration, and measurement method next to the result so later tests remain comparable. A change in efficacy can indicate improvements or losses caused by a driver, diffuser, thermal condition, or optical assembly, but the ratio alone cannot identify which component caused the change. This calculator also does not convert lumens into lux, because illuminance depends on area, distance, beam distribution, and geometry. Nor does it predict electricity use over time; that requires power multiplied by operating duration. If an efficacy value looks unexpectedly high or low, verify unit prefixes first, then check whether the flux and power values describe the same boundary. Milliwatts entered as watts or a bare LED's lumen output divided by a complete fixture's input can distort the result dramatically. For API automation, each request costs $0.002; the same deterministic arithmetic can be run in the browser for an immediate check.