x
Send Your Inquiry Today
Quick Quote

Street Light Design Guide for Lumens Wattage Lux Uniformity and Optics

A street light does not have one standard lumen value. The required output depends on road width, pole height, spacing, layout, optical distribution, target maintained illuminance, uniformity, and environmental losses. Lumens and watts are useful inputs, but the road surface result must be verified photometrically. This guide is for lighting designers, project engineers, contractors, technical buyers, and distributors who need to move from an initial product range to a defensible street-lighting configuration. It explains the required inputs and the final verification step without treating an example as a universal standard.

Understand lumens watts lux and foot candles

Lumens and watts describe the light source or luminaire; lux and foot-candles describe light received on a surface. That distinction is the starting point for answering how many lumens is a street light. A lumen rating can help screen candidate fixtures, but it cannot by itself prove that a road will meet its target.

TermPlain-language meaningPrimarily describesWhat it cannot prove
Lumens (lm)Total visible light emitted by a source or luminaire.Luminaire output.The average or minimum light on a road.
Watts (W)Electrical power consumed by the luminaire under a stated condition.Energy input.Light output, optical reach, or uniformity.
Lux (lx)One lumen distributed over one square metre of surface.Illuminance on the road surface.Performance without the calculation grid and measurement conditions.
Foot-candles (fc)Illuminance in lumens per square foot; 1 fc is approximately 10.76 lx.Illuminance on the road surface.Compliance with a requirement unless the applicable criterion is known.

 

Lux cannot be converted from lumens using a fixed multiplier. The result depends on geometry, mounting height, spacing, optical distribution, tilt, surface reflectance, calculation area, and losses. Two luminaires with the same lumen output can produce different average and minimum values because they place light in different parts of the roadway.

For an initial screen, efficacy is useful: lumens divided by watts gives lumens per watt. It is not a substitute for a photometric model because efficacy does not describe where the light goes. Treat the wattage and lumen value as candidate inputs, not as the final design result.

Estimate an initial lumen and wattage range

There is no single mandatory lumen or wattage range for every road. The table below is an illustrative preselection tool for early discussions, not a local regulation or a final design. The actual starting point should come from road geometry, the project’s maintained illuminance and uniformity criteria, and the available photometric file.

ApplicationIllustrative starting range per luminaireIllustrative wattage rangeAssumptions
Local or residential road8,000–20,000 lm50–120 WNarrow roadway, moderate mounting height, controlled spacing, and no unusual obstruction.
Collector road15,000–30,000 lm100–200 WWider cross-section or higher traffic demand; layout and uniformity still govern.
Wider traffic road25,000–50,000 lm150–300 WMultiple lanes or greater mounting height; requires optical modelling.
Parking or service road8,000–30,000 lm50–200 WRoadway or drive aisle rather than a general area-lighting calculation.
Industrial access road15,000–50,000 lm100–300 WVehicle mix, dust, mounting conditions, and maintenance exposure must be confirmed.

 

These ranges are deliberately broad. A lower-output luminaire may be correct when poles are closer, mounting height is lower, or the optic is tightly matched to the road. A higher-output luminaire may still fail when spacing is excessive or light is sent outside the calculation area. Do not turn the table into a replacement rule such as “replace every 250 W fixture with a 150 W LED.”

For a product screen, collect the luminaire wattage, tested lumen output, efficacy, input voltage, optical distribution, mounting options, control settings, and maintenance assumptions together. Keep values from the same model, power setting, and configuration. A datasheet lumen value may represent a nominal or tested condition, so the project calculation should use the matching photometric file.

Account for mounting height spacing and layout

Mounting height changes the distance, intensity, glare exposure, and road area that one luminaire must cover. Spacing changes how neighboring light patterns overlap. These geometry variables can invalidate a lumen-only selection even when the fixture output looks adequate.

Single-sided layouts place poles on one edge of the road and often require an optic that pushes light across the carriageway. Staggered layouts alternate poles on opposite sides, while opposite layouts place poles across from each other. The choice affects dark zones, cross-road balance, glare, pole count, and the minimum-to-average relationship.

As a simple example, increasing pole spacing without changing wattage reduces overlap between adjacent photometric distributions. The average may remain acceptable at some points while the minimum falls sharply between poles. Increasing mounting height can improve coverage in one direction, but it can also increase spill light, glare, and the need for a carefully controlled forward distribution.

Before selecting a package, document road width, lanes, shoulders, sidewalks, pole positions, mounting height, arm length, tilt, spacing, and layout pattern. Use the street-light pole-height and spacing guide when geometry becomes the main design question.

Select the optical distribution

Street-light optics should match the road direction, width, pole position, and mounting height. Type II through Type V labels are useful shorthand, but the actual photometric file is more reliable than the label alone. Review the candela distribution, forward throw, backlight, lateral spread, and cutoff behavior for the named configuration.

DistributionTypical planning useQuestions to verify
Type IINarrower roadways, lanes, or paths where the pole is near an edge.Does the forward throw reach the far edge without excessive spill?
Type IIIRoadways where the pole is offset from the road and more forward spread is needed.Does the distribution fit the road width and the pole setback?
Type IVBroader forward distribution for edge-mounted roadway applications.Is backlight controlled, and does the far-side minimum remain adequate?
Type VMore symmetric coverage around the luminaire, often considered for open or central placements.Does the project need a symmetric pattern, or would it waste light beyond the road?

 

Forward light is the portion directed along the roadway. Backlight travels behind the pole, while lateral spread controls how far the distribution reaches across the road. A pole at the edge, a pole in a median, and a pole beside a service lane may need different distributions even when the road width is similar.

Request the IES or LDT file for the exact product, power, optic, tilt, and mounting arrangement. The file should match the proposed configuration; a generic Type III label or a file from another power level is not enough to validate the design.

Use maintained illuminance and uniformity

A road-lighting design should be judged against maintained illuminance and uniformity, not only initial light output. Initial illuminance describes the new-installation condition. Maintained illuminance accounts for expected depreciation from dirt, aging, environment, and other project factors over the intended service period.

  • Average illuminance: the mean lux across the defined calculation grid.
  • Minimum illuminance: the lowest calculated or measured lux point within that grid.
  • Uniformity ratio: a relationship such as minimum-to-average or minimum-to-maximum, as defined by the project criterion.
  • Maintenance factor: a planning factor that reduces initial output to represent the maintained condition; its value must be stated and justified for the project.

A simplified maintained-value relationship is: maintained illuminance = initial illuminance × maintenance factor. For example, if a preliminary model produces 24 lx initially and the stated maintenance factor is 0.80, the simplified maintained average is 19.2 lx. This is a planning calculation, not proof that every grid point meets a requirement; minimum illuminance and uniformity must still be checked.

Project or local requirements may specify different target levels, ratios, grids, glare limits, or road classifications. Do not present one example value as a global regulation. Confirm the applicable project brief, authority requirement, owner specification, and calculation convention before finalizing the design.

Work through a simplified selection example

The following example shows the logic from a target condition to a candidate lumen package and optic. It is illustrative only and intentionally simplified. It does not replace an IES/LDT model.

  1. Define the geometry: assume a 7 m-wide two-lane road, 9 m mounting height, 30 m pole spacing, and a single-sided layout. Record the pole setback and arm projection separately; they change the optical demand.
  2. Define the planning target: assume an illustrative maintained average of 15 lx and a maintenance factor of 0.80. The actual target and uniformity ratio must come from the project criteria.
  3. Convert the target to an initial average planning value: 15 lx ÷ 0.80 = 18.75 lx. This is only the average condition; the minimum point still needs a separate check.
  4. Create a candidate screen: begin with a luminaire in an illustrative 15,000–30,000 lm range and select a roadway optic whose forward throw matches the 7 m cross-section and edge-mounted pole position.
  5. Model the exact arrangement: enter the luminaire file, mounting height, pole spacing, arm length, tilt, road boundaries, calculation grid, surface assumptions, and maintenance factor. Review average, minimum, maximum, and uniformity.

The simplified method cannot validate glare, spill light, exact minimum illuminance, pavement reflectance, obstructions, installation tolerances, driver settings, or compliance with a particular local requirement. It also cannot justify a final number of fixtures from lumens alone. If the minimum or uniformity fails, adjust spacing, mounting geometry, optic, output, or layout and recalculate rather than simply increasing wattage.

Verify the result with photometric files and simulation

The final selection should be verified with an IES or LDT-based photometric model using the exact luminaire configuration. The model should connect the road geometry and project criteria to measurable outputs instead of relying on a catalogue lumen number.

Required inputs normally include the road cross-section, lane and shoulder limits, pole coordinates, mounting height, arm length, tilt, spacing, layout, luminaire model and power, optic, input voltage, control setting, surface assumptions, calculation grid, and maintenance factor. State which values are measured, specified, manufacturer-provided, or illustrative.

Expected outputs include average illuminance, minimum illuminance, maximum illuminance, the selected uniformity ratios, an isolux plot, the calculation grid, and a luminaire schedule. The schedule should identify the model, wattage, optic, quantity, mounting condition, and control setting so the result can be reproduced.

A sample installation or field measurement may be appropriate when the project has unusual pavement reflectance, existing poles, complex intersections, steep grades, heavy obstructions, uncertain controls, or a high consequence of under-lighting. Field measurements should use a defined grid and calibrated equipment, and the installed configuration should be documented before comparing results with the model.

For an initial product match, provide FY LIGHTING with the road cross-section, pole positions, mounting height, spacing, target maintained light levels, voltage, and control method. FY LIGHTING can propose candidate lumen packages and optics for the project team to verify in a formal lighting calculation. The current SLE road/area-lighting series is listed with 100, 150, 200, and 300 W options, up to 170 lm/W, IP65 protection, and Type III, Type IV, and Type V distributions; the applicable lumen output, optic, voltage, and configuration must be checked for the selected model and project.

 

When reviewing the model, inspect the shape of the isolux plot rather than reading only the average. A broad, even pattern usually gives the design more tolerance to small installation differences than a narrow pattern with a high centre value and steep falloff. Pay particular attention to the far edge of the carriageway, the space between poles, lane boundaries, pedestrian areas, and any point where the road changes direction.

 

The calculation grid must represent the project decision. A grid that is too coarse can hide a low point, while a grid that extends beyond the maintained area can make the average appear lower than the area that actually governs the project. Record the grid spacing, boundaries, surface assumptions, and whether sidewalks, shoulders, medians, or conflict zones are included.

 

Controls also belong in the verification record. If the design uses a photocell, scheduled dimming, 0–10 V control, DALI, or another interface, identify the operating level used in the model and the level expected during each operating period. A fixture can produce a different lumen output at a reduced setting, so the selected photometric file or multiplier must represent that state.

 

For procurement, request the photometric file, product datasheet, installation instructions, control information, and a configuration schedule together. Confirm that the file name identifies the same family, wattage, optic, and mounting arrangement shown in the quotation. If a supplier changes the driver, lens, optic, or operating current, the calculation should be reviewed rather than assumed to remain valid.

 

If the project has an existing installation, measure before replacing. Record the existing pole coordinates, mounting height, arm orientation, luminaire tilt, circuit condition, and representative night-time levels. These records help distinguish a product-output problem from a geometry problem and can prevent a higher-wattage replacement from masking a spacing or aiming error.

 

Keep the initial estimate and the formal design separate in project documents. The estimate supports budget and product-family discussions; the formal calculation supports technical review. This separation makes assumptions visible and gives the owner a clear list of items to approve before purchase.

Uniformity should be read alongside the average, not after it. A design with a strong average and weak minimum can feel inconsistent to drivers and pedestrians, especially at transitions between poles. The correct corrective action may be a different optic or shorter spacing rather than more lumens, because extra output can increase glare and spill without filling the low points efficiently.

Road surface assumptions deserve a written note. Pavement reflectance, wet conditions, lane markings, concrete edges, walls, parked vehicles, trees, and seasonal foliage can change the result. If the project brief uses a defined road-surface classification, use that classification consistently in the model and do not mix it with a generic default from another calculation.

For a tender or RFQ, ask each supplier to state whether the quoted lumen value is delivered lumens, nominal LED lumens, or a tested value for the complete luminaire. Also request the power tolerance, dimming level, optic, correlated color temperature if relevant, and the warranty or operating conditions that apply to the named configuration. This keeps competing quotations comparable.

Finally, treat a preliminary configuration as a decision aid, not an approval. The owner, designer, or authority may require a specific calculation convention, documentation format, sample installation, or night-time acceptance measurement. Those requirements should be identified before ordering because they can affect the selected optic, mounting arrangement, controls, and quantity.

Avoid common street-light design mistakes

Most early design errors come from treating one catalogue number as the design. Each mistake below has a practical correction.

MistakeLikely consequenceCorrective action
Replacing by wattage aloneDifferent output, optics, mounting, or depreciation can leave dark zones or create spill light.Match maintained criteria, geometry, photometric file, and controls before comparing wattage.
Ignoring the maintenance factorThe new-installation average may look adequate while the planned maintained result is lower.State the factor, explain its basis, and check both initial and maintained conditions.
Using a generic optic labelThe same Type III or Type IV label can hide differences in throw, backlight, and lateral spread.Review the exact IES/LDT distribution for the selected power and optic.
Spacing poles too far apartMinimum illuminance and uniformity can fail between poles even if average light seems acceptable.Model the full spacing and inspect minimum points and isolux patterns.
Using the wrong mounting tiltThe distribution shifts away from the intended road area, increasing glare or spill.Confirm the tilt in the calculation and follow the fixture installation range.
Assuming dimming is verifiedThe operating output or control response may differ from the design setting.Confirm control protocol, dimming curve, fail-safe state, and the photometric setting used.

 

A useful handoff package should contain the road cross-section, pole layout, mounting details, target maintained levels, uniformity criteria, voltage, control method, required quantity, project location, and schedule. That information gives a supplier or lighting designer enough context to return a candidate configuration instead of an unsupported wattage recommendation.

Frequently Asked Questions

How many lumens does a 100 W street light produce?

A 100 W street light does not have one fixed lumen output. Efficacy, driver setting, thermal condition, optic, and model determine the result. Use the exact product datasheet and matching photometric file rather than applying a universal watts-to-lumens conversion.

How many lux should a street have?

The answer depends on the road classification, project brief, applicable local requirements, and the chosen calculation method. Define the target maintained average, minimum value, and uniformity criteria before selecting a luminaire; do not use one global lux value for every road.

What is the difference between lux and lumens?

Lumens measure the total visible light emitted by a source or luminaire. Lux measures how much light reaches a surface, so a road can receive different lux levels from luminaires with the same lumen output when geometry and optics change.

Why do two street lights with the same wattage perform differently?

They may have different efficacy, optics, thermal behavior, mounting conditions, driver settings, or lumen-maintenance assumptions. Compare the exact lumen output, photometric distribution, installation geometry, and maintained calculation—not wattage alone.

Conclusion

The answer to how many lumens is a street light is project-specific. Use lumen and wattage ranges only to screen candidates, then evaluate mounting height, spacing, layout, optical distribution, maintained illuminance, minimum illuminance, and uniformity. A formal IES/LDT calculation is the step that turns a catalogue number into a defensible roadway design.

Send the project geometry and target lighting criteria to FY LIGHTING for a preliminary street-light configuration review. Include the road cross-section, pole positions, mounting height, spacing, target maintained light levels, voltage, control method, and any required installation or verification conditions.

Sources

FY Lighting — Professional LED Solutions for Every Industry

FY Lighting specializes in high-performance LED systems for industrial, explosion-proof, and agricultural applications. From factory lighting to vertical farming solutions, we help clients worldwide achieve safety, efficiency, and sustainability.
en_USEnglish
Scroll to Top