Commissioned Research
Top 10 Best Photometric Software of 2026

GITNUXSOFTWARE REVIEW

Business & Finance

Top 10 Best Photometric Software of 2026

Compare photometric software tools for lighting analysis, including Ladybug Tools, plus fit and tradeoffs for selecting the right workflow.

21 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

Agents extract product evidence with provenance, then collect written reviews and transcribe video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Photometric software turns IES profiles, surface reflectance, and scene geometry into validated illuminance and glare outcomes that support design, compliance, and operations. This comparison helps technical evaluators weigh tool fit across desktop and browser workflows, integration with CAD and Rhino ecosystems, and the tradeoff between ray-tracing simulation and calculation-driven turnaround.

Ladybug Tools is the best overall pick for lighting designers working in SketchUp and needing repeatable daylight and electric studies because it tightly links luminaire placement, photometry import, and visualization in one smooth flow, while LightStanza fits teams that want browser-based interactive daylight maps and standards reporting from shared building models.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Ladybug Tools

Tight SketchUp integration that links luminaire placement, photometry import, and lighting result visualization in one study flow.

Best for: Fits when lighting designers use SketchUp and need repeatable daylight and electric lighting studies with standard photometry files.

2

LightStanza

Editor pick

Interactive daylight studies connect imported building geometry, visual result maps, and standards reports in one browser workflow.

Best for: Fits when design teams need fast daylight studies, visual feedback, and certification documentation from shared building models.

3

AGi32

Editor pick

Radiosity method for interior illuminance prediction using lighting design grids and metric outputs.

Best for: Fits when lighting teams need repeatable point-grid calculations and interior bounce modeling.

Comparison Table

1
Ladybug ToolsBest overall
vertical specialist
9.4/10
Overall
2
8.7/10
Overall
3
vertical specialist
8.6/10
Overall
4
enterprise
8.5/10
Overall
5
enterprise
8.2/10
Overall
6
vertical specialist
7.8/10
Overall
7
enterprise
7.4/10
Overall
8
vertical specialist
7.1/10
Overall
9
enterprise
6.8/10
Overall
10
API-first
6.6/10
Overall
#1

Ladybug Tools

vertical specialist

Open-source environmental analysis toolkit for Rhino and Grasshopper including daylight and photometric simulation.

9.4/10
Overall
Features9.4/10
Ease of Use9.5/10
Value9.3/10
Standout feature

Tight SketchUp integration that links luminaire placement, photometry import, and lighting result visualization in one study flow.

Ladybug Tools is built for lighting studies inside a SketchUp-centered workflow, so geometry edits and re-runs stay tightly coupled to the modeling environment.

The software takes luminaire photometry inputs such as IES and EULUMDAT files and converts them into computable candela distributions for illuminance and luminance results.

Output generation supports common deliverables like isolux-style diagrams and false-color rendering that make point-by-point results easier to interpret.

The main limitation is that many advanced governance and large enterprise automation patterns are secondary to the interactive design loop.

Pros
  • +SketchUp-centered workflow connects geometry, runs, and visualization quickly
  • +Handles common luminaire photometry imports like IES and EULUMDAT files
  • +Produces isolux-style outputs and false-color rendering for lighting evaluation
  • +Good support for daylight and electric lighting comparison in one study flow
Cons
  • –Workflow depends on SketchUp modeling conventions and scene preparation
  • –Complex BIM-to-lighting pipelines need extra translation steps outside SketchUp
  • –Deep lighting system governance and RBAC controls are not the focus
  • –Large scene throughput can slow down when many point-by-point calculations are requested
Use scenarios
  • industrial lighting designers

    iterate luminaire layouts with geometry

    Comparable layout and illuminance results

  • architects and design sustainability teams

    compare facade and massing lighting

    Side-by-side design evidence

Show 2 more scenarios
  • landscape architects

    evaluate outdoor site light coverage

    Site-level environmental information

    Use outdoor environmental studies to inform site-level decisions tied to public-realm planning.

  • sustainable design consultants

    test comfort-related lighting effects

    Comfort indicators for refinement

    Combine weather context and modeled conditions to check comfort-related impacts of lighting design choices.

Best for: Fits when lighting designers use SketchUp and need repeatable daylight and electric lighting studies with standard photometry files.

#2

LightStanza

cloud

Cloud-based lighting analysis software for architectural spaces and daylight studies.

8.7/10
Overall
Features8.7/10
Ease of Use8.7/10
Value8.7/10
Standout feature

Interactive daylight studies connect imported building geometry, visual result maps, and standards reports in one browser workflow.

Architects, sustainability consultants, and façade designers can use LightStanza to test daylight conditions without building a separate simulation workflow. Model imports, interactive false-color views, grid-based results, and project reports connect design iterations to measurable outcomes. Support for common BIM and 3D modeling workflows reduces repeated geometry preparation.

The main tradeoff is scope. LightStanza centers on daylight analysis and does not replace specialist software for detailed luminaire layouts, candela distributions, or complete electric-lighting documentation. It fits projects where teams need quick daylight studies during concept and schematic design, especially for certification or internal design reviews.

Pros
  • +Browser-based workflow avoids workstation-specific simulation setup
  • +Interactive 3D results support rapid design comparisons
  • +Imports geometry from common BIM and modeling applications
  • +Generates standards-oriented daylight reports for project documentation
Cons
  • –Daylight focus leaves detailed electric-lighting design outside its scope
  • –Complex models may require careful geometry cleanup before analysis
  • –Advanced users have less control than specialist simulation engines
  • –Results depend on accurate materials, schedules, and sky conditions
Use scenarios
  • Architectural design teams

    Compare façade and shading options

    Earlier daylight-informed design decisions

  • Sustainability consultants

    Prepare certification daylight documentation

    Faster documentation cycles

Show 2 more scenarios
  • Façade engineers

    Evaluate shading performance

    Better shading decisions

    Engineers compare external shading configurations against seasonal solar exposure and interior daylight targets.

  • Real estate developers

    Assess early building concepts

    Lower early-stage design risk

    Development teams compare massing and orientation scenarios before commissioning detailed specialist studies.

Best for: Fits when design teams need fast daylight studies, visual feedback, and certification documentation from shared building models.

#3

AGi32

vertical specialist

Photometric calculation and lighting design software for interior, exterior, and roadway applications.

8.6/10
Overall
Features8.6/10
Ease of Use8.6/10
Value8.6/10
Standout feature

Radiosity method for interior illuminance prediction using lighting design grids and metric outputs.

AGi32 performs point-by-point illuminance calculation and daylight or electric lighting evaluation for lighting design work. The workflow centers on luminaire photometry import, grid or point layouts, and metrics like illuminance, uniformity ratio, and glare-related outputs.

It supports radiosity method calculations for interior bounce modeling and generates graphical deliverables such as isolux-style outputs and false-color rendering. AGi32 is most distinct for engineering-style iteration speed across scenarios using repeatable input datasets and consistent calculation settings.

Pros
  • +Point-by-point calculation workflows align with standard lighting design checks
  • +Radiosity method supports interior light bounce modeling without external renderers
  • +Produces metric-ready outputs for uniformity and glare-style assessments
  • +Consistent scenario inputs make regression comparisons practical across iterations
Cons
  • –Scene setup depends on disciplined geometry and measurement layout definitions
  • –Limited native BIM automation compared with CAD-to-calculation pipelines
  • –Does not match ray-tracing simulation granularity for complex optics workflows
  • –Automation and API access are not the primary focus versus desktop-driven runs
Use scenarios
  • lighting engineers and consultants

    produce grid and glare audit reports

    Review-ready documented performance

  • landscape lighting designers

    plan fixtures by landscape zones

    Zone-based lighting plans

Show 2 more scenarios
  • residential lighting teams

    evaluate room fixture layouts repeatably

    Repeatable residential lighting evidence

    Assess room-level layouts using photometric data and illuminance grids to support consistent decisions.

  • architectural engineers

    compare daylight and electric grids

    Comparable daylight and electric outcomes

    Analyze daylight and electric lighting on the same calculation grids for comparable room or building results.

Best for: Fits when lighting teams need repeatable point-grid calculations and interior bounce modeling.

#4

ReluxDesktop

enterprise

Lighting calculation software for indoor, outdoor, daylight, and emergency lighting projects.

8.5/10
Overall
Features8.5/10
Ease of Use8.5/10
Value8.5/10
Standout feature

Built-in isolux and false-color rendering tied to each calculation run for rapid design iteration.

ReluxDesktop is designed for iterative lighting studies where luminaire photometry feeds calculations and the user needs fast visual feedback on illuminance and luminance outputs. The software supports standard photometric input formats such as IES and EULUMDAT and can produce diagrams used for review packages. Its project-centric workflow fits teams that reuse geometry and luminaire sets across many variations.

Pros
  • +Strong luminaire photometry import for IES and EULUMDAT workflows
  • +Point-by-point outputs that support detailed spatial QA review cycles
  • +Visualization outputs like isolux and false-color renderings for stakeholder checks
  • +Project templates support repeat studies with consistent settings
Cons
  • –Automation relies on project workflow rather than a documented public API
  • –External pipeline integration needs manual handoffs in many setups
  • –Complex multi-case batch runs can be slower than headless engines
  • –Advanced governance controls for large organizations are limited
Use scenarios
  • Lighting designers

    Iterate luminaire layouts with IES photometry

    Faster design iteration cycles

  • Lighting specification engineers

    Prepare review diagrams for stakeholders

    Cleaner review packages

Show 2 more scenarios
  • Daylight and electric teams

    Compare daylight and electric lighting scenarios

    Clearer design tradeoffs

    Supports scenario-based studies that separate electric and daylight impacts in one workflow.

  • Midsize design firms

    Reuse geometry and settings across projects

    Reduced setup time

    Project templates help standardize calculation setups across recurring jobs.

Best for: Fits when lighting analysts need consistent desktop photometric studies from IES inputs.

#5

DIALux evo

enterprise

Lighting design software for calculating illuminance, glare, energy use, and documentation.

8.2/10
Overall
Features8.2/10
Ease of Use8.3/10
Value8.1/10
Standout feature

Integrated electric lighting and daylight study workflow in one environment, producing analysis visuals and standards metrics from the same model.

DIALux evo supports lighting design workflows across electric lighting calculations and daylight studies, with emphasis on point-by-point results and standard output artifacts. The tool handles luminaire photometry inputs such as EULUMDAT and IES, then generates outputs like isolux diagrams and false-color views for analysis and review.

Pros
  • +Point-by-point calculation outputs support detailed room-by-room verification.
  • +Direct support for common luminaire photometry formats like IES and EULUMDAT.
  • +Glare and uniformity metrics align with typical lighting standard checks.
  • +Daylight and electric lighting studies can share a consistent analysis workflow.
Cons
  • –Automation and API-driven provisioning are limited compared with software built for integration.
  • –Advanced geometry preparation depends on clean CAD or BIM inputs for stable results.
  • –Large project throughput can be constrained by scene size and calculation complexity.
  • –Extensibility options beyond built-in calculation types are narrower than specialist toolchains.
Use scenarios
  • road lighting planners

    calculate street lighting plans

    Calculated plan for documentation

  • landscape and outdoor lighting designers

    zone outdoors for coverage analysis

    Zone-based photometric results

Show 2 more scenarios
  • building services teams

    prepare emergency lighting handover materials

    Emergency info included in files

    Include emergency lighting layouts and outputs in project planning and handover documentation.

  • lighting engineers and architects

    review daylight versus electric lighting

    Supports daylight and electric comparison

    Model daylight conditions alongside electric lighting to review their combined effect in a space.

Best for: Fits when lighting designers need repeatable standard-based calculations from photometric data and room geometry.

#6

DM Photometrics

vertical specialist

AutoCAD-integrated photometric calculation tool using IES files for foot-candle and uniformity analysis.

7.8/10
Overall
Features7.8/10
Ease of Use7.9/10
Value7.7/10
Standout feature

Integrated workflow that ties luminaire photometry imports to both electric and daylight analysis outputs for side-by-side option comparison.

DM Photometrics performs luminaire photometry workflows by importing candela distribution data and driving point-by-point lighting calculations. The tool supports daylight analysis and electric lighting analysis workflows with diagrams and rendered outputs designed for design iterations.

Pros
  • +Point-by-point calculation workflow suited to luminaire layout iterations
  • +Supports IES and EULUMDAT file import for candela distribution inputs
  • +Daylight and electric lighting workflows in one analysis UI
  • +Output diagrams and render-style views for isolux-style review
Cons
  • –Lighting model setup requires careful input geometry and grid selection
  • –Limited automation surface for high-throughput batch runs
  • –Integration with BIM and CAD depends on manual data preparation
  • –Reporting structure stays oriented around design outputs, not data export
Use scenarios
  • Lighting designers

    Compare luminaire options against standards

    Faster option comparison for approvals

  • Facade and daylight engineers

    Model daylight analysis from photometry

    More confident daylight design decisions

Show 2 more scenarios
  • Specification engineers

    Verify candela data from IES

    Consistent photometric verification documentation

    Imports IES and EULUMDAT files to compute polar curves and produce documentation-ready outputs.

  • Project design coordinators

    Prepare compliant lighting reports

    Cleaner submissions for design reviews

    Exports configuration and reporting results for cross-option comparisons in lighting standard reviews.

Best for: Fits when lighting designers need repeatable photometric calculations with standard luminaire file inputs and visual review.

#7

Visual Lighting

enterprise

Lighting design software for photometric calculations, layouts, schedules, and documentation.

7.4/10
Overall
Features7.4/10
Ease of Use7.4/10
Value7.4/10
Standout feature

Point-by-point calculation outputs paired with false-color rendering for rapid photometric design review.

Visual Lighting focuses on photometric workflows for lighting design analysis with luminaire candela distribution inputs from common photometry file formats. It supports point-by-point illuminance workflows and scene-based rendering outputs such as false-color views and isolux-style results for design review.

Pros
  • +Works directly from luminaire photometry inputs to drive calculations
  • +Produces point-by-point lighting outputs suitable for design iteration
  • +Renders false-color results for quick visual inspection of light levels
  • +Shows isolux-style diagrams to support layout and aiming decisions
Cons
  • –Automation and API surface for external pipeline integration are not evident
  • –Daylight analysis workflows are thin compared with BIM-first tools
  • –Large scene throughput can lag when geometry complexity increases
  • –Standards compliance outputs for UGR-style workflows feel limited
Use scenarios
  • outdoor lighting engineering teams

    check exterior coverage from placed fixtures

    Photometric layouts and coverage checks

  • luminaire specialists

    compare spacing and aiming alternatives

    Faster comparisons of arrangements

Show 2 more scenarios
  • architectural lighting teams

    review lighting against imported geometry

    Decisions reviewable against the model

    Import building geometry and compare luminaire placement with illuminance results in a 3D scene.

  • lighting consultants

    present illumination maps for signoff

    More accessible visual communication

    Use rendered scenes and illumination maps to communicate proposed lighting conditions for client review.

Best for: Fits when lighting teams need repeatable photometry-based calculations with visual outputs, without heavy BIM governance.

#8

Lighting Reality

vertical specialist

Lighting calculation software for road, area, tunnel, and architectural applications.

7.1/10
Overall
Features7.1/10
Ease of Use7.2/10
Value7.0/10
Standout feature

Point-by-point illuminance reporting tied to isolux-style outputs for design review cycles.

Lighting Reality is focused on photometric calculations from luminaire candela data into usable visual and numeric lighting outputs. The workflow supports electric lighting analysis and daylight analysis with point-by-point results, including isolux-style deliverables and common lighting study metrics.

Pros
  • +Supports standard luminaire photometry inputs like IES and EULUMDAT
  • +Produces point-by-point illuminance outputs suitable for downstream review
  • +Daylight and electric lighting analysis share a single study workflow
  • +Exports practical visual artifacts like isolux-style representations
Cons
  • –Automation and API-driven provisioning are not clearly exposed for external governance
  • –Large studies can require careful scene organization to keep iteration times manageable
  • –Integrations with BIM and CAD data models appear limited in typical deployments
  • –Advanced optics evaluation breadth like UGR-style workflows is narrower than some rivals
Use scenarios
  • road and street lighting designers

    compare luminaires across road layouts

    Reviewable illuminance results

  • retrofit lighting planners

    test fixture and aiming retrofit options

    Comparable solutions for decisions

Show 2 more scenarios
  • transport infrastructure lighting teams

    plan tunnel lighting with photometric data

    Lighting plans for project review

    Model lighting for tunnels using fixture photometry and scene calculations to check targets against results.

  • lighting consultants and engineers

    assemble compliance design project packages

    Traceable documentation

    Convert calculated grids, visual outputs, and layouts into review-ready reports for client and compliance checks.

Best for: Fits when lighting designers need repeatable photometric studies from IES libraries into isolux and point results.

#9

Radiance

enterprise

Open-source validated ray-tracing lighting simulation engine for illuminance, luminance, and daylight analysis.

6.8/10
Overall
Features6.8/10
Ease of Use6.8/10
Value6.8/10
Standout feature

Point-by-point calculation that drives both quantitative illuminance mapping and visual false-color validation in one workflow.

Radiance uses the Radiance rendering toolchain style workflow where scenes, materials, geometry, and light sources produce quantitative lighting metrics for later interpretation. It supports point-by-point calculation and can generate outputs like isolux diagrams and false-color rendering to support lighting standards compliance checks. It also fits teams that manage lighting libraries and repeatedly run the same scenario with different luminaire configurations.

Pros
  • +Point-by-point illuminance and luminance outputs support metric-driven decisions
  • +Accepts luminaire photometry via IES and EULUMDAT for candela distribution inputs
  • +False-color rendering and isolux diagrams make quantitative results reviewable
  • +Daylight analysis workflows support electric and daylight mixed studies
Cons
  • –Scene and parameter setup takes more discipline than click-to-run lighting tools
  • –Limited built-in guidance for UGR evaluation compared with glare-focused niche tools
  • –Automation requires scripting comfort for repeatable batch runs
  • –Lack of native CAD authoring can add steps when starting from BIM models
Use scenarios
  • Lighting engineers and analysts

    Compare multiple luminaire layouts

    Faster layout decision cycles

  • Daylight study teams

    Validate daylight coefficient assumptions

    More defensible daylight outcomes

Show 2 more scenarios
  • Specification and compliance groups

    Support lighting standards checks

    Clear evidence for reviews

    Produce falsified-color and isolux outputs for targeted review of uniformity ratio areas.

  • BIM-to-analysis pipeline owners

    Translate IFC scene lighting

    Reduced manual rework

    Import model geometry into Radiance workflow and re-run metrics after design edits.

Best for: Fits when teams need repeatable metric outputs from controlled photometric and daylight scenes.

#10

OpenLumen

API-first

Browser-based platform for IES file analysis, photometric layout design, and illuminance heatmaps.

6.6/10
Overall
Features6.6/10
Ease of Use6.5/10
Value6.7/10
Standout feature

Scene regeneration from imported photometric data keeps point-by-point results consistent across design iterations.

OpenLumen targets lighting design and photometric calculation workflows with project-oriented modeling for luminaire photometry inputs and rendering outputs. The core work centers on point-by-point illuminance and luminance computations, plus downstream diagram and image generation for design review.

Pros
  • +Supports common luminaire photometry imports for IES and EULUMDAT workflows
  • +Point-by-point illuminance and luminance outputs for detailed review
  • +Generates diagrams and images from the same computed lighting scene
  • +Repeatable scene settings help reduce recalculation drift across iterations
Cons
  • –Daylight analysis depth is narrower than dedicated daylight-focused tools
  • –Glare and UGR evaluation features can lag specialized lighting compliance suites
  • –API and automation surface is limited compared with general engineering compute tools
  • –Large models can slow down when many points or high-resolution surfaces are used
Use scenarios
  • Lighting design engineers

    IES and EULUMDAT photometric validation

    Faster photometric review cycles

  • Facade and streetlight consultants

    Grid studies for roadway lighting

    Consistent compliance documentation

Show 2 more scenarios
  • Architectural BIM modelers

    Scene regeneration from luminaire inputs

    Reduced rework after edits

    Modelers reuse repeatable scene settings to rerun lighting outcomes after fixture changes.

  • Visual design reviewers

    Luminance outputs for design approvals

    Clearer approval decisioning

    Reviewers generate image and diagram outputs tied to photometric calculations for approvals.

Best for: Fits when lighting teams need consistent point-by-point results from imported luminaire photometry without heavy custom coding.

Conclusion

After evaluating 10 photometric software, Ladybug Tools stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
Ladybug Tools

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Photometric Software

Which photometric software tools handle point-by-point illuminance output for electric lighting and how do they differ?
Radiance generates point-by-point illuminance with both electric lighting and daylight inputs, then validates with false-color views in the same workflow. AGi32 focuses on repeatable point-grid iterations with radiosity method interior bounce modeling. Lighting Reality ties point-by-point illuminance reporting directly to isolux-style outputs for review cycles.
How does daylight analysis workflow depth differ between LightStanza and DIALux evo?
LightStanza is built for browser-based daylight analysis with interactive 3D results and standards-oriented reporting. DIALux evo runs electric lighting and daylight studies inside one environment, producing analysis visuals and standards metrics from the same model. LightStanza is less suited to a full electric-lighting design package than DIALux evo.
What breaks if a team uses Radiance for a pipeline that requires public automation via API instead of controlled study runs?
Radiance emphasizes predictable calculation control for repeatable studies across revisions rather than exposing an API-first workflow. ReluxDesktop similarly centralizes automation around project templates instead of a public interface. Teams that depend on provisioning an external automation service will need an alternative to Radiance or accept manual project regeneration.
When should an office choose ReluxDesktop over Visual Lighting for model-to-analysis iteration?
ReluxDesktop is strongest when luminaire photometry inputs arrive as file-based studies and the workstation workflow standardizes outputs like isolux and false-color views per run. Visual Lighting targets repeated geometry plus luminaire distribution recombination for design review visuals, with point-by-point outputs tied to each calculation cycle. Teams with heavy geometry iteration without strict BIM governance often find Visual Lighting aligns better with their review loop.
Which tools accept common photometric file inputs like IES and EULUMDAT, and which one is tied to a CAD host?
Radiance, Visual Lighting, and Lighting Reality support luminaire photometry inputs such as IES and EULUMDAT to drive candela distribution and point-by-point results. DIALux evo handles both IES and EULUMDAT and focuses on standards compliance reporting from the same model. Ladybug Tools is tied to SketchUp as an add-on workflow rather than acting as a standalone calculation environment.
How does data model control differ between OpenLumen and LightStanza during scenario regeneration?
OpenLumen regenerates scenes from imported luminaire photometry data using repeatable scene settings, which keeps point-by-point results consistent across design iterations. LightStanza connects imported building geometry to interactive 3D daylight result maps with standards reports generated from browser workflows. OpenLumen is oriented toward regenerating photometry-driven scenes, while LightStanza is oriented toward shared building-model daylight comparisons.
Where does AGi32 fall short compared with DIALux evo for mixed electric lighting and daylight deliverables?
AGi32 supports point-by-point illuminance and radiosity method interior bounce modeling plus daylight or electric lighting evaluation, but it centers on engineering-style scenario iteration. DIALux evo runs electric lighting and daylight studies together and produces standard-based artifacts like isolux diagrams and false-color views from one environment. Teams that need one integrated workflow for both deliverable types will find DIALux evo better aligned than AGi32.
When does an organization need tighter admin controls such as RBAC and audit logging, and how do these tools compare?
None of the listed tools are positioned as an enterprise web platform with explicit RBAC and audit log features in the same way as identity-managed SaaS systems. LightStanza is browser-based for team collaboration around daylight reporting, while ReluxDesktop is centered on desktop templates for repeatable studies. Organizations that require RBAC and audit log governance must validate administrative capabilities during pilot before standardizing.
How does DM Photometrics support side-by-side option comparison across electric and daylight analysis?
DM Photometrics connects luminaire photometry imports to both electric and daylight analysis outputs so options can be compared in a single workflow. It produces diagrams and rendered outputs aimed at design iterations, and it supports standard photometric inputs like IES and EULUMDAT. Radiance can also run electric and daylight inputs together, but DM Photometrics is more explicitly structured around option comparisons from luminaire data sets.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Photometric Software

What separates photometric software options is how faithfully they convert photometric inputs into results, how they handle measurement files and coordinate conventions, and how repeatable the workflow is for your team. Watch the criteria for input/output fidelity, validation workflow, and automation for batch runs rather than general “analysis” claims.

Photometric input and output fidelity

Why it matters

Photometric software only helps if it reads common photometric data correctly and exports results you can reuse in review. Input/output fidelity reduces silent mismatches that change distributions and reported outputs.

How to check

Bring one sample photometric file and one reference model from your workflow, then run the same case in two projects or sessions. Compare key outputs (readable summaries and exported result views) for consistency in units, coordinate orientation, and numeric ranges. If outputs include graphs, check that the plotted distribution matches the expected shape from your reference.

Calculation settings control and transparency

Why it matters

Photometric results depend on choices like mesh resolution, sampling, and performance/accuracy tradeoffs. Good calculation settings control makes reviews reproducible and lets us explain why a run differs from a prior run.

How to check

In the demo, locate where the run configuration lives and what each option does. Run a small test with two deliberate setting changes (e.g., a finer discretization versus a coarser one) and verify that the outputs shift in the expected direction. Ask the vendor to show a run log or settings report you can attach to your documentation.

Result views and metric coverage

Why it matters

Photometric software becomes practical when the results display matches what stakeholders ask for, and when metrics are easy to locate without manual stitching. Coverage matters most when you need more than a single chart view.

How to check

Create one representative scenario and check whether the product provides: numeric tables tied to the model, distribution views, and a way to filter/select points or surfaces. Confirm that the reported metrics you care about (the ones you currently use) appear in the same run. If it offers evaluation overlays, check they align with the geometry position in the scene.

Run history, versioning, and provenance

Why it matters

In photometric software, two nearly identical runs can diverge due to updated files or altered settings. Strong run history and provenance lets us audit what produced a specific outcome months later.

How to check

Perform two runs: one after changing only the settings and one after changing only the input file. Verify that the application records both changes distinctly, and that you can compare or restore prior results. Export or capture an audit-style summary (settings plus input identifiers) and confirm it’s readable without the original workspace.

Batch runs and automation/API surface

Why it matters

Teams often repeat the same photometric workflow across many luminaires, variants, or site options. Automation for batch runs and an accessible API surface reduces manual error and supports controlled throughput.

How to check

Ask for a batch workflow: import multiple photometric inputs and run the same configuration over all of them. If an API exists, request a short demo that creates a job from code or a script, then returns results to a structured output. Even without coding, verify whether the tool supports templated jobs or parameterized runs that keep settings locked.

Red flags

  • Outputs change between reruns without a visible run log or settings report.
  • Result views don’t match the model coordinates or units you imported.
  • Batch runs require manual clicking that makes repeatability hard.

Fit by situation

  • If we run many luminaire variants nightly, prioritize batch runs and automation/API surface.
  • If we need to defend specific outcomes to reviewers, prioritize run history, versioning, and provenance.
  • If we frequently reuse photometric inputs from different sources, prioritize photometric input and output fidelity.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.