Choose by what is known
Choose the lux to lumens calculator when the target illuminance is known and the question is how much light output the zone needs. Choose the lumens to lux calculator when the installed or proposed lumens are known and the question is what maintained illuminance they may produce.
The direction matters because the record changes. Lux to lumens creates a target-to-output allowance before fittings are selected. Lumens to lux checks a selected or existing lighting group against an area, utilisation factor, maintenance factor and task plane. Measured lux belongs in a separate evidence record before anyone tries to infer fixture output from it.
| Known input | Better calculator | Record it creates |
|---|---|---|
| Target lux and assessed area are known. | Lux to lumens | Required lumens for the plane or zone. |
| Fitting count and lumens per fitting are known. | Lumens to lux | Estimated maintained lux from installed lumens. |
| Target lux, fitting output and watts are all being compared. | Fixture count | Rounded fitting count, installed lumens and connected load. |
| Existing room readings or point readings are being checked. | How to measure lux levels | Measured illuminance record for the same plane, point set and control state. |
Search phrasing points to the direction
The user's wording usually reveals which direction is useful. If the question starts from a target, area or task plane, the answer is an allowance. If it starts from a known fitting, installed lumens or a proposed count, the answer is a check. If the wording starts from a meter reading, the owner record is measured evidence rather than a reverse lumen claim.
| User job in search language | Direction | Record boundary |
|---|---|---|
| How many lumens do I need for this room? | Lux to lumens, then fixture count if a fitting is selected. | Target plane, area, UF and MF still need to be named. |
| What lux will these lights give? | Lumens to lux. | Installed lumens, same area and factor assumptions. |
| I have a lux meter reading; what does it prove? | Measurement guide and reading records. | Same point set, daylight condition and switch state stay with the record. |
| Is this LED replacement as bright? | Lumens to lux plus measured records where available. | Output, beam, CCT, CRI/Ra and control state stay visible. |
| How many fittings should be scheduled? | Fixture count after the lumen allowance is known. | Rounded count, installed lumens and connected load. |
| What is the difference between lux and lumens? | Lighting units table before choosing a calculation direction. | Unit meaning is separate from a project record. |
For Australian room, tenancy and small-project records, this split prevents a broad "lumens" question from becoming a single shortcut. The direction should match the known evidence, then the schedule line can carry the result into spacing, load and measurement checks.
Lux to lumens answers the allowance question
Lux to lumens is the cleaner path for early planning. It keeps the target, area, utilisation factor and maintenance factor together before the fitting count is rounded. That is useful for a kitchen bench, office desk zone, warehouse aisle, lobby, garage workbench or any other surface where the task plane needs its own allowance.
The allowance record should name the owner plane, the reason the target was selected, the area take-off and whether the result covers a whole room or a local zone. In Australian records, that keeps a bench, desk group, aisle run or mixed room from being collapsed into one loose room label.
Do not treat the required lumens as a luminaire schedule by itself. It still needs a selected luminaire output, count, spacing check, glare note and connected-load record where relevant.
| Lux-to-lumens field | What to record | Related route |
|---|---|---|
| Target lux | Planning level, project brief or table row basis. | Lux levels for Australia |
| Assessed area | Actual task plane or room zone, not a loose room name. | Task plane records |
| UF and MF | Delivery and maintenance assumptions. | Utilisation factor |
| Result | Required maintained lumen allowance. | Lighting calculation formulas |
| Handoff | Selected luminaire output and count once a fitting is known. | Fixture count |
Lumens to lux answers the checking question
Lumens to lux is stronger when the lighting group already exists or a fitting schedule has been proposed. It asks whether the known lumens, area and factors produce a sensible maintained-lux estimate. That makes it useful for retrofit checks, count changes, value-engineering notes and before/after comparisons.
Installed lumens are not the same as delivered light on the task plane. The result still depends on distribution, room shape, finishes, obstructions, maintenance and the surface being assessed. A known-output check is strongest when the fitting count, output basis, switched group and assessed plane stay on the same line.
| Lumens-to-lux field | What to record | Why it matters |
|---|---|---|
| Installed lumens | Fitting count multiplied by lumens per fitting. | Separates output from wattage and count. |
| Area | Same plane or zone used for the comparison. | Avoids comparing a room average with a task surface. |
| UF and MF | Delivery and maintenance assumptions. | Explains why the estimate is not just lumens divided by area. |
| Control state | Full output, dimmed setting or switched group being assessed. | Keeps measured and estimated records comparable. |
| Estimated lux | Maintained illuminance estimate. | Can be compared with a target or measured record. |
Maintained assumptions must travel with the record
Both directions rely on maintained-lumens assumptions. If UF, MF, task-plane area or control state disappear, the result becomes hard to compare with a later count change or measured reading.
| Assumption | Keep visible because | Where it travels |
|---|---|---|
| Utilisation factor | It represents the assumed delivery from fittings to the assessed plane. | Allowance records and known-output checks. |
| Maintenance factor | It keeps ageing, dirt and maintenance assumptions out of hidden notes. | Allowance records, estimates and comparison notes. |
| Task plane | It defines the surface being planned or checked. | Task plane records and task plane terms. |
| Measured condition | It explains daylight, dimming, switching and point position. | Lux meter reading records and measured evidence. |
When fixture count is the better owner
If the real question is "how many fittings", go to the fixture count calculator. Count is where rounding becomes visible. A required allowance of 5,000 lm with an 800 lm fitting becomes seven fittings, not 6.25 fittings, and the schedule should then show 5,600 installed lumens before spacing, glare and load are checked.
A count decision owns rounding, connected load and installed lumens. It does not replace the target-to-output allowance or the known-output check; it sits between them when a fitting output has been chosen.
| Count decision | Why it belongs in fixture count | Companion check |
|---|---|---|
| Rounding up | The installed lumens can overshoot the allowance. | Fixture count rounding table |
| Rounding down comparison | One fewer fitting may miss the target. | Lumens to lux calculator |
| Connected load | Count multiplied by input watts sets the load. | Lighting power density examples |
| Set-out | Count still needs spacing and edge checks. | Downlight spacing calculator |
Keep both directions in the same record
A tidy lighting note often uses both calculators. First calculate the lumen allowance from the target. Then select a fitting, round the count, and use installed lumens to check the estimated maintained lux. If measured readings are available, record them separately with the same task plane, control state and daylight condition.
Keep the direction labels explicit: target-to-output planning, fitting-count decision, known-output checking and measured-lux evidence. That makes the note easier to review later when a tenant, designer, electrician or facility manager is looking at a different part of the same record.
| Record stage | Calculator or table | Stronger wording |
|---|---|---|
| Allowance | Lux to lumens | Desk task plane, 12 m2, target and factor assumptions recorded. |
| Selection | Fixture count | Selected luminaire output, rounded count and installed lumens recorded. |
| Check | Lumens to lux | Estimated maintained lux after rounding and factors recorded. |
| Measurement | Lux meter reading records | Same plane, same switch state, same daylight condition. |
Owner page handoffs
Each owner page should keep the record it is best placed to explain. The handoff is a short note that says which record should be checked beside it, not a claim that one number settles the whole lighting outcome.
| Owner page | Record it owns | Handoff to keep beside it |
|---|---|---|
| Lux to lumens | Target, area, UF, MF and required lumen allowance. | Fixture count when a luminaire output is chosen. |
| Fixture count | Rounded count, installed lumens and connected load. | Lumens to lux for the maintained-lux check after rounding. |
| Lumens to lux | Known-output estimate against the same area and assumptions. | Measured illuminance record when site readings exist. |
| Lux meter reading records | Point set, control state, daylight condition and plane. | Measured illuminance term for record wording. |
| Lighting calculation formulas | Formula structure and unit conversion support. | Calculator page that owns the project decision. |
Measured readings do not reverse the calculation by themselves
A meter reading can sit beside either direction, but it should not be treated as a clean reverse calculation unless the same area, plane and condition are known. A desk point reading after a retrofit may be useful evidence, yet it does not state the whole-room average or the output of every fitting.
A stronger measured record includes the point set, meter position, task plane, switch or dimming state, daylight condition and any visible obstruction or failed fitting. Without those fields, the reading is still useful, but it is a site observation rather than a full explanation of installed output.
| Measured evidence | Better comparison | What to avoid |
|---|---|---|
| One task-plane point | Compare with the target for that same point or local task. | Treating one point as the whole room. |
| Small point grid | Compare average, low point and high point beside the estimate. | Hiding weak points behind a single value. |
| Before and after readings | Keep the same point set and control state. | Mixing daylight or dimmed states without a note. |
| Daylight-affected reading | Label daylight condition before comparing with electric light. | Reading daylight as installed lumens. |
Common mix-ups
| Weak shortcut | Better record |
|---|---|
| Using lumens per fitting as if it were room brightness. | Convert installed lumens to estimated lux with area, UF and MF. |
| Applying one room target to every bench, desk, wall and floor surface. | Split the task plane records before calculating. |
| Ignoring rounding after a lumen allowance. | Show rounded count, installed lumens and overshoot or shortfall. |
| Treating watts as brightness. | Read watts as connected load and lumens as output. |
| Comparing a night target with a daylight meter reading. | Keep the measured illuminance condition with the record. |
| Recording a lux estimate without UF, MF or plane notes. | Keep maintained assumptions with the allowance, count and check records. |