If you are searching for how to translate lux and lumens, how to translate candela, or how to preserve illuminance, luminous flux, luminous intensity and photometric specifications across languages, the first rule is that lux, lumen and candela measure different things. A light source with more lumens does not automatically produce the same number of lux everywhere, and candela is not simply another word for brightness.
Lighting translation matters in architectural lighting, LED product datasheets, workplace standards, vehicle lamps, projectors, flashlights, street lighting, photography, displays, emergency lighting and electrical specifications. A target-language document can become technically wrong if lm is translated as lx, if candela is confused with total luminous flux, if illuminance levels lose their measurement plane, or if beam angle and distance are omitted from a lux claim.
This guide explains how to translate lux, lumens, candela and related photometric measurements without changing lighting meaning. It covers lx, lm, cd, luminous flux, luminous intensity, illuminance, luminance, cd/m², beam angle, efficacy in lm/W, colour temperature, CRI, measurement distance, maintained illuminance, emergency-lighting levels and how to verify translated specifications against the source photometric file, test report or manufacturer datasheet.
Why lighting translation needs photometric precision
Photometry describes visible light in several related dimensions. Lumens quantify luminous flux: the total amount of visible-light output weighted to human visual response. Candela describes luminous intensity in a direction. Lux describes illuminance received on a surface and equals lumens per square metre. Luminance describes light leaving or being emitted/reflected from an area in a direction and is commonly expressed in cd/m².
Those quantities are connected but not interchangeable. The same lamp can produce different lux values at different distances or beam angles. Two luminaires with the same lumens can distribute light differently and therefore create different illuminance patterns.
Lighting documents also mix photometric and colour-quality properties. Correlated colour temperature in kelvin and colour rendering index do not measure how much light reaches a surface. Translation should keep output, distribution, colour appearance and colour fidelity in separate conceptual lanes.
The safest workflow is to protect the source quantity, value, unit and measurement geometry first, translate the descriptive language second, and derive or convert related values only when the source provides enough optical information.
A reliable translation method
1. Identify the photometric quantity
Determine whether the source gives luminous flux, luminous intensity, illuminance, luminance, efficacy or another lighting property. Do not translate every light-related number as “brightness.”
2. Protect lm, lx and cd
Lumens, lux and candela are different SI-derived units. Keep each abbreviation attached to its value and preserve capitalization conventions used by the source style.
3. Preserve distance and measurement plane
Lux values can depend strongly on distance and where the measurement is taken. Keep “at 1 m,” “on the work plane,” “at floor level” and similar geometry with the value.
4. Keep beam geometry separate from output
Beam angle, field angle and distribution affect where lumens go. Preserve angular values and do not translate a narrow beam as “brighter” without context.
5. Keep luminance distinct from illuminance
Lux measures light arriving on a surface; cd/m² measures luminance from a surface or display. Do not use one term for the other.
6. Preserve maintained versus initial values
Lighting designs may distinguish initial illuminance from maintained illuminance after depreciation factors. Keep the design-state qualifier with the number.
7. Keep colour properties in their own category
CCT, CRI, TM-style colour metrics and spectral information describe colour, not light quantity. Translate their labels accurately without replacing lm or lx.
8. Verify against photometric data
Check the target against the manufacturer datasheet, photometric file, lighting calculation or test report. A translated value should describe the same optical quantity under the same geometry.
Thirty-eight recurring lighting-translation problems
1. Luminous flux in lumens
A source such as 1200 lm states total luminous flux. Translate the label and preserve lm. Do not change it to 1200 lx, because lux requires an area/geometry context.
For QA, confirm whether the source gives lamp lumens, luminaire lumens or delivered lumens. Optical losses can make those values differ even for the same product family.
2. Illuminance in lux
A requirement such as 500 lx on the work plane is a received-light condition. Preserve the surface or plane because the same room can have different lux values at floor, desk and wall level.
Do not translate 500 lx as “500 lumens.” The target reader needs to understand that this is illuminance at a location.
3. Luminous intensity in candela
A source value such as 20,000 cd describes directional luminous intensity. Keep cd and any beam direction or angle tied to the value.
High candela can come from concentrating light into a narrow beam; it does not necessarily mean a larger total lumen output.
4. Luminance in cd/m²
Displays, signs and illuminated surfaces may be specified in cd/m². Preserve the square-metre denominator and translate the property as luminance rather than illuminance.
A value of 500 cd/m² should not become 500 lux. Those quantities describe different optical relationships.
5. Nits as display luminance
Consumer display specifications often use “nits” as a common name corresponding to cd/m². Preserve the source marketing term or pair it with the technical unit when helpful.
Do not translate nits as lumens or lux simply because all are colloquially called brightness.
6. Lumens per watt
Luminous efficacy in lm/W relates visible-light output to electrical power. Keep the ratio and distinguish luminaire efficacy from LED package efficacy when the source does.
Do not translate lm/W as energy efficiency percentage. It is a photometric/electrical ratio with its own units.
7. Beam angle
A spotlight may specify a 10°, 24° or 60° beam. Preserve the degree symbol and whether the angle is beam or field angle.
Beam angle affects intensity distribution and lux at distance. It should not be translated as a lumen value.
8. Lux at a stated distance
Flashlights and projectors may state 10,000 lx at 1 m. Keep the distance. A lux claim without distance is incomplete for a directional source.
If converting metres to feet for a target market, keep the original value or recompute the geometry only if the source supports such a derived claim.
9. Peak beam intensity
Portable lighting products may state peak beam intensity in candela. Preserve “peak” and avoid presenting the number as an average across the beam.
Where beam distance is derived from intensity under a standard criterion, keep the derivation concept separate from the candela measurement.
10. Beam distance
Flashlight specifications may list metres of beam distance. This is a distance criterion derived under a standard or threshold, not luminous intensity itself.
Translate the distance and test-standard context without replacing it with a candela or lumen figure.
11. Initial lumens
A new lamp or luminaire may have an initial luminous flux higher than its maintained output after ageing. Preserve the “initial” state.
Do not mix initial lumen output with a maintained illuminance design target.
12. Maintained lumens
Some LED documentation reports lumen maintenance over time. Keep the ageing interval and percentage or absolute lumen value attached.
Terms such as L70 or L80 should remain technical lifetime criteria rather than being translated as seventy or eighty lumens.
13. Maintained illuminance
Lighting codes often specify maintained lux levels. Preserve “maintained” because it incorporates depreciation assumptions and differs from initial design illuminance.
A target specification should produce the same long-term lighting design criterion as the source.
14. Average illuminance
A calculation may report average lux across a grid. Keep “average” separate from minimum or maximum values.
Do not select the average as the only number when uniformity requirements also depend on the minimum.
15. Minimum illuminance
Minimum lux can be a compliance threshold. Preserve the inequality or minimum label exactly.
In emergency lighting, low numerical values can still be safety-critical because they apply to escape routes and specific measurement locations.
16. Maximum illuminance
Some applications limit excessive illumination, glare or light-sensitive exposure. Keep maximum limits distinct from design targets.
Do not assume more lux is always better.
17. Illuminance uniformity
Uniformity may be a ratio such as minimum to average illuminance. Preserve the ratio definition and do not translate it as a percentage unless the source does.
Two projects can have the same average lux but very different uniformity.
18. Work-plane height
Office and task-lighting calculations specify a work plane, often above floor level. Keep the height and plane orientation attached to the illuminance requirement.
Translating “500 lx” without “at 0.8 m work plane” can change the measurement geometry.
19. Vertical illuminance
Security, facial recognition and display lighting may require vertical lux rather than horizontal lux. Preserve the plane orientation.
Lux uses the same unit, but the measurement surface direction changes the value and purpose.
20. Horizontal illuminance
Many workplace and roadway criteria use horizontal illuminance. Keep it distinct from vertical or cylindrical measures.
Table headings should retain orientation words even when space is limited.
21. Emergency escape-route lux
Emergency-lighting requirements may specify minimum illuminance along a route, centre line or floor plane. Translate the location and time after power failure together with the lux threshold.
Do not replace the emergency criterion with normal lighting levels.
22. Street-lighting illuminance
Roadway specifications can use illuminance or luminance methods. Preserve which method the source standard uses.
A cd/m² road-luminance requirement should not be translated as a lux requirement simply because both describe lighting quality.
23. Display luminance
Monitors and signs commonly use cd/m² or nits. Keep peak, sustained, full-screen or typical qualifiers where present.
Do not replace display luminance with room illuminance; they refer to different optical conditions.
24. Projector lumens
Projector specifications may use a named lumen test convention. Preserve the measurement standard or marketing qualifier rather than shortening every claim to generic lumens.
Screen illuminance and image luminance depend on screen size, gain and room conditions; they are not direct translations of projector lumens.
25. LED package versus luminaire lumens
An LED source may produce more raw lumens than the finished fixture after optical and thermal losses. Keep “source,” “module” and “luminaire” output terminology distinct.
Do not publish the larger number as finished product output unless the source states that relationship.
26. Colour temperature
A value such as 3000 K describes correlated colour temperature, not light output. Translate warm/cool appearance language while preserving kelvin.
Do not infer higher lumens from higher CCT; they are separate properties.
27. Colour rendering index
CRI or Ra describes colour-rendering quality under a specified method. Preserve the metric and value without converting it to percent brightness.
Keep high-CRI marketing claims separate from lumen or lux specifications.
28. Photometric distribution
Luminaires may be described as narrow, wide, batwing, asymmetric or other distribution types. Translate the distribution concept while preserving the photometric curve or file.
Distribution determines where light goes; it is not another unit of output.
29. IES/LDT photometric file reference
Lighting calculation files contain measured intensity distributions. Preserve filenames, model identity and test metadata rather than translating machine-readable content casually.
A localized datasheet should still point to the same photometric file for the same luminaire variant.
30. Candela per kilolumen
Photometric tables may normalize intensity by luminous flux. Preserve cd/klm units and do not relabel normalized intensity as absolute candela.
If absolute intensity is derived, verify the lumen basis and scaling factor.
31. Glare rating beside illuminance
Lighting designs may list glare indices together with lux. Keep glare as a separate visual-comfort metric.
Do not describe a lower glare number as lower illuminance unless the source explicitly connects them.
32. Light meter range
A lux meter may specify measurement range, resolution and accuracy. Keep these as instrument characteristics rather than room-lighting criteria.
Preserve lx units and any range-switching notation.
33. Lux-meter accuracy
Instrument accuracy may be ±3% of reading plus digits or another expression. Translate the uncertainty formula exactly rather than simplifying it to a fixed lux error.
Measurement uncertainty and target illuminance are different fields.
34. Daylight illuminance
Daylight measurements can change rapidly with sky conditions. Preserve whether values are measured, simulated, average or design-day assumptions.
Do not present one measured lux value as a universal daylight level.
35. Horticultural lighting alongside lux
Plant-lighting documents may use photon-based metrics as well as lux. Keep photometric lux separate from photosynthetic photon measurements because human visual weighting and plant-response metrics are different.
Do not convert one to the other without a known spectral distribution and an explicit calculation method.
36. Automotive headlamp intensity
Headlamp regulations may specify intensity at defined angular points. Preserve candela, test angle and beam pattern location.
Do not replace regulatory point intensity with total headlamp lumens.
37. Conversion from foot-candles to lux
Some source documents use foot-candles while targets prefer lux. Treat this as a verified illuminance-unit conversion and retain the original when traceability matters.
Do not confuse the word “candle” in foot-candle with candela as a direct one-to-one unit substitution.
38. Derived lux from intensity and distance
A simple point-source approximation can relate candela and lux at a distance, but real luminaires have beam geometry and finite size. If the target adds a derived lux figure, state the assumptions.
Translation itself should preserve the measured or published source quantity rather than replacing it with a calculated one.
Common failure modes
Changing lumens into lux
Total luminous flux and surface illuminance are different quantities.
Calling candela total light output
Candela is directional luminous intensity.
Dropping distance from a lux claim
Directional-source illuminance changes strongly with distance.
Confusing cd/m² and lux
Luminance and illuminance use different units and describe different optical relationships.
Using colour temperature as brightness
Kelvin describes colour appearance, not light quantity.
Using CRI as an efficiency measure
CRI describes colour rendering, not lumens per watt.
Dropping maintained/initial qualifiers
Lighting performance changes over time and design criteria can refer to different lifecycle states.
Ignoring measurement plane
Horizontal, vertical and work-plane lux are not interchangeable.
Worked practice
Practice 1: Office lighting
Situation: Design target is 500 lx maintained on a desk-height work plane.
Reasoning: Preserve maintained, lux and work-plane geometry; do not replace the requirement with fixture lumens.
Practice 2: LED luminaire
Situation: A fixture outputs 3000 lm at 120 lm/W.
Reasoning: Keep luminous flux and efficacy as separate but related properties.
Practice 3: Flashlight
Situation: Product lists 2000 lm, 50,000 cd and a beam distance.
Reasoning: Preserve all three because they describe total output, directional intensity and a derived/referenced distance criterion.
Practice 4: Display
Situation: Monitor peak luminance is 1000 cd/m².
Reasoning: Keep luminance units and peak qualifier; do not translate as room illuminance.
Practice 5: Emergency route
Situation: A minimum floor-level lux requirement applies after power failure.
Reasoning: Preserve minimum, location and emergency time condition.
Practice 6: Projector
Situation: Projector output is stated in a named lumen convention.
Reasoning: Keep the measurement convention rather than shortening the claim to generic “brightness.”
Practice 7: Road lighting
Situation: Standard uses road-surface luminance in cd/m².
Reasoning: Preserve luminance method; do not substitute a lux criterion from another design method.
Practice 8: Foot-candle conversion
Situation: A US specification gives illuminance in foot-candles and the target needs lux.
Reasoning: Convert as illuminance units, retain the original for traceability where useful and do not confuse foot-candle with candela.
Photometric files, calculators and AI
Manufacturer datasheets, laboratory photometry, IES/LDT files and lighting-calculation reports are the strongest sources for translation. They identify whether a value is measured output, normalized intensity, design illuminance or a derived criterion.
Photometric calculators can relate intensity, distance and illuminance under defined geometry, but real fixtures have angular distributions. Keep assumptions visible and preserve measured source data even when target calculations are added.
AI can explain lux, lumens and candela, but it may use “brightness” loosely. Ask it to name the exact photometric quantity and unit before rewriting, then verify the target against the original photometric source.
How this fits the wider eduKate translation system
Lighting translation combines quantities, geometry, visual terminology and product specifications. The broader method is developed in Master Art of Translation | The Complete System for Moving Meaning Between Languages. Vocabulary depth connects to the Vocabulary Learning Hub, while quantity, spatial relationship and comparison language connect to How English Works.
FAQ
Are lumens and lux the same?
No. Lumens describe luminous flux; lux describes illuminance on a surface.
What does candela measure?
Directional luminous intensity.
Is cd/m² the same as lux?
No. cd/m² is luminance; lux is illuminance.
Can more lumens mean fewer lux?
At a particular point, yes, if the higher-lumen source distributes light much more broadly or the geometry differs.
Is kelvin a brightness unit?
No. It is used for colour temperature.
Is CRI a light-output unit?
No. CRI describes colour-rendering performance.
Why must distance stay with lux claims?
Illuminance from directional sources changes with distance and beam geometry.
Can foot-candles be converted to lux?
Yes. They are both illuminance units; verify the conversion independently.
Can AI calculate lux from lumens?
Only with sufficient distribution and geometry assumptions. Translation should preserve the published source quantity first.
What is the simplest rule?
Protect the exact photometric quantity, unit, geometry and measurement condition before translating the descriptive language.
Final checklist
- Is the source quantity lumens, lux, candela or cd/m²?
- Are lm, lx, cd and cd/m² kept distinct?
- Are distance and measurement plane retained?
- Are beam and field angles preserved?
- Are initial and maintained values kept separate?
- Are colour temperature and CRI kept distinct from output?
- Are average, minimum and maximum illuminance labelled correctly?
- Are normalized photometric units preserved?
- If a conversion or derived value was added, were geometry and assumptions checked?
- Would the target describe the same lighting performance as the source?
Lighting translation succeeds when the target reader sees the same amount, direction and distribution of visible light as the source reader. Protect lm, lx, cd and cd/m², keep measurement geometry and lifecycle qualifiers intact, and verify every derived value against the underlying photometric data before publication.