Commissioned Research
Top 10 Best Daylighting Calculation Software of 2026

GITNUXSOFTWARE ADVICE

Construction Infrastructure

Top 10 Best Daylighting Calculation Software of 2026

Ranking top daylighting calculation software for 3D daylighting analysis, covering DIALux evo, AGi32, Daysim, Relux, and DesignBuilder outputs.

29 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

Search agents gather the source set and the review record, including transcriptions of 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 rankings. Editorial policy

Daylighting calculation software tools model sunlight transport and daylight metrics inside 3D geometry to support design reviews, compliance reporting, and energy-linked performance decisions. This ranked list helps analysts compare how each platform handles import data models, simulation workflow automation, and verification-oriented outputs so teams can choose between GUI-driven tooling and API-or-scriptable pipelines.

Relux is the best fit for architectural teams that need rapid daylight iteration with mapped outputs, whereas Ladybug Tools is the smarter choice when you run parametric daylight studies in Grasshopper and want repeatable Radiance-based results.

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

Relux

Geometry-driven daylight workflow that updates mapped results during design iteration without switching tools.

Best for: Fits when architectural teams need rapid daylight iteration with mapped outputs.

2

DesignBuilder

Editor pick

Direct 3D geometry workflow that keeps daylight surfaces synced during annual climate-based runs.

Best for: Fits when daylighting and energy inputs must stay consistent across iterative BIM-based design.

3

IES Virtual Environment

Editor pick

Integrated study workflow that keeps geometry, optical definitions, and Radiance runs linked through iterative scenarios.

Best for: Fits when project teams need repeatable daylight runs with spatial maps, not only single-point checks.

Comparison Table

1
ReluxBest overall
enterprise
9.1/10
Overall
2
enterprise
8.8/10
Overall
3
8.4/10
Overall
4
enterprise
8.1/10
Overall
5
enterprise
7.8/10
Overall
6
open-source
7.4/10
Overall
7
vertical specialist
7.1/10
Overall
8
open-source
6.8/10
Overall
9
enterprise
6.5/10
Overall
10
vertical specialist
6.2/10
Overall
#1

Relux

enterprise

Daylight and artificial lighting simulation software for building design.

9.1/10
Overall
Features9.3/10
Ease of Use9.1/10
Value8.9/10
Standout feature

Geometry-driven daylight workflow that updates mapped results during design iteration without switching tools.

Relux runs daylight calculations directly against imported building geometry, then returns spatial outputs used for documentation and iteration. The workflow is built around repeated geometry preprocessing, material and opening settings, and result review on a mapped grid or view. It fits teams that want daylight analysis to stay close to the design model rather than moving through a separate command-line simulation step.

A tradeoff appears when projects require deeper custom control over simulation engines and advanced material optics beyond what Relux exposes in its UI. Relux is a good fit for iterative daylight studies where geometry and surface edits happen frequently, and teams need quick turnaround for early design checks.

Pros
  • +Interactive daylight iteration tied to geometry and surface edits
  • +Illuminance mapping outputs support spatial review and documentation
  • +Glare-focused daylight metrics support early risk screening
  • +BIM and model import reduce manual geometry reconstruction
Cons
  • –Advanced engine customization is limited compared with open simulation workflows
  • –Large models can require careful preprocessing for stable throughput
Use scenarios
  • Architects and design teams

    Window and shading iteration reviews

    Faster design decisions

  • Façade engineering reviewers

    Daylight glare screening per zone

    Reduced glare issues

Show 2 more scenarios
  • BIM coordinators

    IFC-driven daylighting studies

    Less model rework

    Model imports keep geometry aligned so daylight settings and outputs target the right spaces.

  • Sustainability analysts

    Regional daylight documentation packages

    More defensible claims

    Climate-based daylight inputs support location-specific daylight behavior for reporting.

Best for: Fits when architectural teams need rapid daylight iteration with mapped outputs.

#2

DesignBuilder

enterprise

Building performance simulation software with daylighting calculation.

8.8/10
Overall
Features8.7/10
Ease of Use8.7/10
Value9.0/10
Standout feature

Direct 3D geometry workflow that keeps daylight surfaces synced during annual climate-based runs.

DesignBuilder is a practical daylighting tool for teams that already model buildings in 3D and need daylight outputs tied to those same surfaces. It supports annual simulation runs using weather data and workflows that generate illuminance mapping and related metrics for zones and specific points. The ray-tracing workflow is suited to questions like window layout impacts, shading changes, and interior lighting outcomes that depend on geometry and material reflectance. The strongest fit shows up when daylight and energy analysis need shared inputs for consistent design decisions.

A tradeoff is that automation and repeatability depend on the quality of the geometry preprocessing and the discipline of parametric inputs, since downstream lighting results follow surface definitions. Detailed glare and luminance-style assessments require the appropriate calculation setup and longer run times than simplified daylight factor style checks. DesignBuilder works best when a project benefits from iterative daylight runs across options, such as façade changes or interior layout revisions that must remain spatially coherent.

Pros
  • +Radiance-based daylight calculations with spatial outputs for design iteration
  • +3D model workflow keeps daylight surfaces aligned with building geometry
  • +Annual climate runs support option comparison across time-relevant weather
  • +Daylight results integrate with building energy modeling inputs
Cons
  • –Parametric option runs require disciplined geometry and material definitions
  • –High-detail daylight runs can increase turnaround time versus simpler checks
Use scenarios
  • Architectural engineering teams

    Iterate façade and interior layout

    Faster, consistent option decisions

  • Sustainability analysts

    Zone-level daylight credit documentation

    Cleaner compliance evidence

Show 1 more scenario
  • BIM coordinators

    Prepare analysis-ready building models

    Reduced rework from mismatches

    Import building geometry and map materials so daylight calculations target the intended surfaces.

Best for: Fits when daylighting and energy inputs must stay consistent across iterative BIM-based design.

#3

IES Virtual Environment

enterprise

Integrated building performance simulation suite with daylighting modules.

8.4/10
Overall
Features8.1/10
Ease of Use8.7/10
Value8.6/10
Standout feature

Integrated study workflow that keeps geometry, optical definitions, and Radiance runs linked through iterative scenarios.

IES Virtual Environment supports end-to-end daylighting runs where geometry preprocessing, material reflectance assignment, and window and shading definitions feed into Radiance ray-tracing calculations. Output is delivered as visualization layers for daylight illuminance and luminance, and it can produce glare-oriented views used during review and iteration. The workflow fits teams that need repeatable study setups across many design variants rather than one-off sanity checks.

A practical tradeoff is that geometry and material correctness drive run quality, so incomplete or inconsistent BIM-to-analysis mappings can cause misleading lighting distributions. It is most suitable for daylight autonomy and useful daylight illuminance style evaluation workflows where outputs must be spatially located on the room or floor model.

Pros
  • +Radiance-based ray tracing outputs with luminance and illuminance visual layers
  • +Workflow-oriented study setup for repeating geometry and control definitions
  • +Climate-based weather file runs designed for spatial daylight evaluations
  • +Glare-related outputs usable during iterative façade and shading changes
Cons
  • –Geometry and material inputs must be consistent to avoid misleading results
  • –Complex study setup can require setup discipline across many variants
  • –Large scenes can increase turnaround time during iterative radiance runs
Use scenarios
  • BIM daylighting analysts

    BIM-to-daylight variant study iterations

    Fewer rework loops

  • Façade design teams

    Shading and window configuration comparisons

    Clearer design tradeoffs

Show 1 more scenario
  • Compliance documentation teams

    Daylight metrics for project deliverables

    More defensible documentation

    Generate spatial daylight outputs from climate-based weather runs for stakeholder review and reporting.

Best for: Fits when project teams need repeatable daylight runs with spatial maps, not only single-point checks.

#4

DIALux

enterprise

Lighting design software with daylighting calculation and 3D visualization.

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

Tightly guided daylighting calculation setup that produces illuminance mapping and daylight factor outputs from architect-focused inputs.

DIALux focuses on daylighting calculation workflows that start from architectural geometry and produce detailed illuminance results for design and compliance documentation. It supports climate-based daylight modeling with weather data files, and it can generate daylight factor outputs and metrics used in daylight studies.

Pros
  • +Daylight factor and illuminance mapping workflows fit standard compliance studies
  • +Weather data file based runs support consistent climate-based daylight modeling
  • +Fast iteration for window and shading changes supports design-option comparisons
  • +Clear calculation setup for typical architectural daylight use cases
Cons
  • –Advanced annual sunlight exposure and glare probability workflows need careful setup
  • –Automation and external integration options are limited compared to API-first tools

Best for: Fits when teams need repeatable daylight factor and illuminance mapping outputs for architectural design iterations.

#5

AGi32

enterprise

Lighting calculation software with daylighting analysis capabilities.

7.8/10
Overall
Features7.4/10
Ease of Use8.1/10
Value8.0/10
Standout feature

Daylight factor driven runs with straightforward grid-based illuminance mapping for iterative design checks.

AGi32 performs daylighting calculations by converting geometry into a radiosity-style workflow focused on sky and sun contributions. It supports window and shading representation with material reflectance inputs that drive point-in-space and grid-based illuminance outputs.

Pros
  • +Fast daylight factor style calculations with predictable grid outputs
  • +Strong handling of window, shading, and material reflectance inputs
  • +Clear project settings for sky and calculation options
  • +Well-suited for iterative massing studies with consistent geometry
Cons
  • –Limited depth for luminance-based glare probability versus Radiance workflows
  • –Less suited for complex sensor-by-sensor daylight autonomy studies than Daysim-style tools
  • –More effort needed to keep BIM-to-analysis geometry consistent across iterations
  • –Automation and extensibility are weaker than dedicated API-driven pipelines

Best for: Fits when teams need repeatable illuminance and daylight factor outputs for early design reviews.

#6

Ladybug Tools

open-source

Environmental analysis plugins for Rhino and Grasshopper including daylighting.

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

Grasshopper components that generate skies, drive Radiance runs, and package metric results tightly with geometry changes.

Ladybug Tools centers daylighting workflows around Grasshopper, where scripts and components generate and post-process Radiance-based results for architectural models. It distinguishes itself with a workflow-first toolchain for climate data handling, sky and sun generation, and daylight metrics output tied to geometry updates.

Pros
  • +Grasshopper-driven parametric reruns keep geometry and analysis in sync
  • +Radiance-based pipeline produces metric-ready outputs for common daylight checks
  • +Climate and sky setup supports reproducible weather-driven simulations
  • +Component composition enables reusable study templates across projects
Cons
  • –Deep setup is needed to tune geometry preprocessing and material inputs
  • –Automation depends on Grasshopper graph management rather than a standalone API

Best for: Fits when teams run parametric daylight studies in Grasshopper and need repeatable Radiance-based outputs.

#7

LightStanza

vertical specialist

Cloud-based daylighting analysis software for building design.

7.1/10
Overall
Features7.3/10
Ease of Use6.8/10
Value7.2/10
Standout feature

Geometry-to-analysis reuse built around Radiance calculations lets teams rerun daylighting outputs efficiently after design changes.

LightStanza centers on building a daylighting analysis workflow from IFC or gbXML geometry through Radiance-based calculations and mapped outputs. The software focuses on automating climate-based daylight modeling inputs from weather files and producing spatial illuminance and sun-related results.

Pros
  • +Radiance-driven daylight calculations with spatial results suited for design review
  • +IFC and gbXML intake supports common BIM-to-analysis exchange paths
  • +Repeat runs benefit from geometry reuse during parametric iterations
  • +Weather-file workflows support climate-based modeling for multi-scenario studies
Cons
  • –Less suitable for teams needing deep, native EnergyPlus coupled workflows
  • –Setup requires careful daylighting parameters to avoid misleading glare and illuminance maps
  • –Automation depth is limited when compared with tools that expose extensive scripting or API control
  • –Material reflectance and window properties must be modeled consistently to maintain accuracy

Best for: Fits when daylighting teams need BIM-driven Radiance calculations with repeatable geometry handling for iterative design reviews.

#8

OpenStudio

open-source

Building energy modeling platform with Radiance-based daylighting.

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

Scene-driven daylight simulation workflow built around Radiance-style ray-tracing calculations for photometric outputs.

OpenStudio targets daylighting calculations by building a lighting scene and running photometric simulations for downstream evaluation.

Pros
  • +Radiance-oriented calculation workflow fits advanced daylight analysis projects
  • +Repeatable scene runs support iterative studies across design options
  • +Explicit lighting inputs make assumptions easier to track in outputs
  • +Works well for teams that already standardize lighting model preparation
Cons
  • –BIM-to-analysis automation depth is limited compared with BIM-native tools
  • –Automation and API surface are not central to the product workflow
  • –Scene setup can become time-intensive for complex building envelopes
  • –Governance controls like audit logs and RBAC are not a highlighted capability

Best for: Fits when daylight studies require Radiance-grade scene control and iterative model runs.

#9

IDA ICE

enterprise

Building simulation software with daylighting and thermal analysis.

6.5/10
Overall
Features6.5/10
Ease of Use6.7/10
Value6.2/10
Standout feature

Single-model workflow that couples daylight calculations with the same envelope, glazing, and operational assumptions used for energy studies.

IDA ICE runs climate-based daylight modeling directly from building geometry and material inputs, then reports indoor daylight metrics for analysis and documentation. The workflow centers on importing or building 3D models for lighting, shading, and envelope effects before running calculations and reviewing results in context.

Pros
  • +Daylight results stay tied to the same 3D model used for energy workflows
  • +Automates parametric room and facade variants through its simulation project structure
  • +Supports common BIM-to-analysis geometry inputs for faster model readiness
  • +Handles glazing, shading, and envelope properties used by both daylight and thermal studies
Cons
  • –Less aligned to render-style outputs like ray-traced luminance maps
  • –Daylight outcome granularity depends on how interior surfaces and fenestration are defined
  • –Advanced daylight reporting requires careful model hygiene and consistent material assignments
  • –Complex daylight automation can require more workflow discipline than standalone daylight tools

Best for: Fits when teams must coordinate daylight assessment with thermal and energy assumptions in one maintained model.

#10

Solemma DIVA

vertical specialist

Rhino and Grasshopper daylighting plugin using Radiance and EnergyPlus engines.

6.2/10
Overall
Features6.0/10
Ease of Use6.3/10
Value6.3/10
Standout feature

DIVA’s Rhino-centered daylight workflow keeps parametric design changes in the same modeling loop.

Solemma DIVA is a daylighting calculation tool built around DIVA for Rhino workflows, with a focus on fast geometry iteration and lighting result export for review and documentation. It supports climate-based daylight modeling using standard weather files and generates common metrics such as daylight factor and daylight autonomy style outputs via its annual and sensor-based calculation modes.

Pros
  • +Rhino-first workflow makes rapid daylight iteration practical
  • +Weather-file driven annual calculations support climate-based comparisons
  • +Sensor grids and result maps make metric reporting straightforward
  • +Material and glazing parameters map cleanly into the calculation setup
Cons
  • –IFC import is not the center of the workflow and can require rework
  • –Large scenes can become slow without careful geometry management

Best for: Fits when Rhino-based teams need repeatable climate-based daylight modeling during concept iteration.

Conclusion

After evaluating 10 daylighting calculation software, Relux 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
Relux

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

How to Choose the Right Daylighting Calculation Software

Daylighting calculation software turns 3D building geometry plus climate and optical inputs into metrics like illuminance mapping, daylight factor outputs, and annual sunlight behavior used for daylight autonomy, glare probability, and compliance documentation. This buyer’s guide covers Relux, DesignBuilder, IES Virtual Environment, DIALux, AGi32, Ladybug Tools, LightStanza, OpenStudio, IDA ICE, and Solemma DIVA.

The ranking favors tools that keep daylight surfaces synchronized with design edits and that support iterative simulation at a usable throughput. The strongest category differentiators in these tools show up in how mapped results stay linked to geometry and how workflow automation is handled across scenarios and variants.

Daylighting Calculation Software for 3D Illuminance Mapping, Daylight Factor, and Annual Climate Runs

Daylighting calculation software calculates indoor daylight performance from 3D geometry, materials, glazing and shading definitions, and weather data files like EPW. Many workflows generate illuminance mapping and spatial visual layers used for design iteration, while others focus on daylight factor runs and architect-focused study setups.

Relux and DesignBuilder emphasize geometry-driven iteration where daylight surfaces remain synced during runs, which supports rapid comparison across design changes. IES Virtual Environment adds a study workflow that keeps geometry, optical definitions, and Radiance runs linked across iterative scenarios, while DIALux centers guided daylighting calculation setup with daylight factor and illuminance mapping outputs from architect-oriented inputs.

Daylighting calculation feature checklist for 3D illuminance and climate runs

Daylighting calculation software must keep optical inputs and geometry locked together so mapped outputs like illuminance maps and daylight factor results stay meaningful during iteration. Tools that tie results to design edits reduce rework when glazing, shading devices, or surface definitions change across scenarios.

The differentiators show up in where geometry syncing happens, how Radiance-style ray-tracing workflows stay linked to study definitions, and how much automation exists for repeating variants. Relux and DesignBuilder lead with geometry-driven iteration, while IES Virtual Environment and Ladybug Tools focus on workflow structures that keep repeated scenarios consistent.

  • Geometry-to-results synchronization during iteration

    Relux updates mapped daylight outputs as mapped results stay tied to geometry and surface edits. DesignBuilder keeps daylight surfaces synced during annual climate-based runs through a direct 3D workflow.

  • Radiance workflow linkage to study scenarios

    IES Virtual Environment links geometry, optical definitions, and Radiance runs through iterative scenarios so spatial maps stay consistent. Ladybug Tools drives Radiance reruns through Grasshopper graphs so parametric changes propagate to packaged metric outputs.

  • Output focus for compliance-style daylight metrics

    DIALux provides tightly guided daylight factor and illuminance mapping workflows built around architect-focused inputs. AGi32 delivers fast daylight factor driven runs with grid-based illuminance mapping for early design checks.

  • BIM exchange and model reuse paths for daylight runs

    LightStanza supports IFC and gbXML intake then reuses geometry for efficient Radiance-based daylight reruns. LightStanza differs from tools like OpenStudio that focus on scene-driven Radiance-grade scene control rather than BIM-first exchange.

  • Throughput and stability for large models

    Relux can require careful preprocessing for stable throughput when models get large. Solemma DIVA can slow on large scenes without careful geometry management in Rhino-based modeling loops.

Select by workflow mechanics, not just daylight output types

Choosing daylighting calculation software works best when workflow mechanics match how geometry and variants are managed across a project. Teams that iterate geometry frequently benefit from tools that keep daylight surfaces synchronized during runs rather than forcing full re-import cycles.

Different products also prioritize different coupling styles for optical definitions, Radiance runs, and scenario setup. Relux and DesignBuilder center geometry-driven iteration, while IES Virtual Environment and Ladybug Tools center study workflows and parametric reruns.

  • Map the iteration loop to geometry synchronization behavior

    If geometry and mapped results must stay linked while design edits happen, choose Relux because interactive daylight iteration ties mapped outputs to geometry and surface edits. If daylight surfaces must remain aligned across annual climate-based runs within a direct 3D workflow, choose DesignBuilder.

  • Pick a study structure based on repeatable scenario control

    If repeating geometry plus optical definitions across scenarios is the core need, choose IES Virtual Environment because it keeps Radiance runs linked through iterative study setup and spatial visual layers. If parametric reruns are driven inside Grasshopper, choose Ladybug Tools because geometry and Radiance outputs remain synchronized through Grasshopper component graphs.

  • Choose an output depth strategy for glare and luminance needs

    If luminance-based layers and Radiance-style visual layers matter for glare-related analysis, prioritize IES Virtual Environment or OpenStudio because both center Radiance-oriented ray-tracing workflows. If early iteration needs predictable grid outputs more than luminance-driven glare probability depth, choose AGi32.

  • Decide how BIM exchange must fit the workflow

    If IFC and gbXML intake must feed a repeatable Radiance pipeline for daylight reruns, choose LightStanza because it uses IFC and gbXML intake paths with geometry-to-analysis reuse. If the workflow stays scene-driven rather than BIM-native, choose OpenStudio because automation and API surface are not central and the workflow centers Radiance-grade scene control.

  • Pick the tool that matches the compliance style of inputs

    If guided setup for daylight factor and illuminance mapping is the expected compliance workflow, choose DIALux because it produces daylight factor and illuminance mapping outputs from architect-focused inputs. If sunrise-style climate comparisons are needed during Rhino concept iteration and the team can manage geometry carefully, choose Solemma DIVA.

  • Match daylight scope to energy-coupled modeling expectations

    If daylight assessment must stay tied to the same envelope, glazing, and operational assumptions used for energy studies, choose IDA ICE because it couples daylight calculations with the same maintained model. If that scope must remain renderer-like with photometric outputs and scene control, choose OpenStudio instead.

Who benefits from geometry-synced daylight iteration and Radiance-linked studies

Daylighting calculation software serves teams that manage many design variants and need consistent metrics across runs. The right tool depends on whether the project is driven by geometry edits, study scenario repetition, or parametric generation inside modeling tools.

Relux and DesignBuilder support teams that iterate quickly and need mapped outputs that remain stable across design edits. IES Virtual Environment and Ladybug Tools support teams that repeat daylight studies through workflow or parametric graph management.

  • Architectural teams running frequent daylight design iterations

    Relux and DesignBuilder keep daylight surfaces synchronized during edits so illuminance mapping and related outputs support rapid comparison across design changes.

  • Simulation teams building repeatable scenario libraries

    IES Virtual Environment keeps geometry, optical definitions, and Radiance runs linked so multiple scenarios produce spatial maps without drifting assumptions across iterations.

  • Parametric designers using Grasshopper for daylight generation

    Ladybug Tools packages Radiance-based metric outputs through Grasshopper component reruns so daylight studies update directly from parametric geometry changes.

  • BIM-driven teams that need IFC or gbXML daylight model intake

    LightStanza provides IFC and gbXML intake and then reuses geometry for Radiance-driven daylight reruns aligned to design review needs.

  • Teams coordinating daylight with thermal and energy assumptions

    IDA ICE couples daylight results with the same envelope, glazing, and operational assumptions used for energy studies inside one maintained simulation project structure.

Common daylighting calculation pitfalls that break comparability

Many daylighting calculation failures come from mismatched assumptions between runs rather than from missing output types. The most common errors involve geometry or optical definitions drifting across variants, which produces maps that look precise but do not compare cleanly.

Another frequent problem is choosing a tool whose workflow depth does not match glare and luminance needs, which leads to inadequate analysis for daylight glare probability style questions.

  • Letting geometry or materials drift between runs while comparing results

    Use Relux or DesignBuilder when mapped results must stay tied to geometry and surface edits. Avoid comparing scenarios in which inputs are not kept consistent because IES Virtual Environment depends on consistent geometry and material inputs for reliable Radiance outputs.

  • Using a daylight factor focused tool for luminance-driven glare questions

    Treat AGi32 daylight factor style grid outputs as early design checks rather than luminance-based glare analysis. For luminance visual layers and Radiance-centered ray tracing, use IES Virtual Environment or OpenStudio.

  • Building a parametric workflow without managing geometry preprocessing and graph stability

    Ladybug Tools supports Grasshopper-driven reruns but deep setup is needed to tune geometry preprocessing and material inputs for stable outputs. If graph management becomes inconsistent, the packaged Radiance reruns can propagate errors across many variants.

  • Assuming BIM exchange will be a one-click path into a Radiance workflow

    LightStanza supports IFC and gbXML intake, but daylighting parameters still need careful setup to avoid misleading glare and illuminance maps. Solemma DIVA keeps IFC import from being the center of the workflow, so Rhino-first geometry management matters for large scene performance.

  • Overloading large models without preprocessing, then mistaking runtime issues for analysis quality

    Relux can require careful preprocessing for stable throughput when models get large. Solemma DIVA can slow on large scenes without careful geometry management, so geometry discipline should be applied before scaling up study runs.

How We Selected and Ranked These Tools

We evaluated Relux, DesignBuilder, IES Virtual Environment, DIALux, AGi32, Ladybug Tools, LightStanza, OpenStudio, IDA ICE, and Solemma DIVA against workflow synchronization, daylight output coverage, and how iteration stays linked to geometry. Features accounted for 40% of the ranking because geometry-driven iteration support and Radiance-linked study control determine whether mapped outputs remain comparable.

Ease and value each accounted for 30% because stable throughput on larger models and repeatable setup reduce variant rework across design cycles. Relux separated from the rest by providing geometry-driven daylight workflow that updates mapped results during design iteration without switching tools.

Frequently Asked Questions About Daylighting Calculation Software

How should a BIM-to-analysis workflow be handled when geometry changes during design iteration?
Relux supports a geometry-driven daylight workflow that updates illuminance mapping outputs as surfaces, openings, and window changes are made. DesignBuilder also keeps daylight surfaces synced with iterative 3D changes and runs climate-based daylight modeling through a Radiance-based engine.
Which tool is best for producing illuminance mapping outputs tied to 3D geometry rather than single-point checks?
Relux produces lighting metrics and illuminance mapping from 3D geometry so teams can judge spatial daylight distribution. IES Virtual Environment builds map-style illuminance and luminance views in an IES-led study workflow that links geometry, optical definitions, and Radiance ray-tracing runs.
What breaks if the daylighting workflow relies on daylight factor only instead of annual climate-based metrics?
DIALux is structured around daylight factor and repeatable illuminance mapping for design iterations, so it can underspecify seasonal performance. AGi32 favors daylight factor driven runs and repeatable grid outputs, but teams using only that approach may miss annual sunlight exposure patterns captured in Ladybug Tools and DesignBuilder during climate-based runs.
When does Radiance-style ray-tracing matter more than radiosity-style approaches?
DesignBuilder uses a Radiance-based engine for ray-tracing style illuminance and luminance outputs, which helps when optical interactions need higher fidelity in complex scenes. AGi32 uses a radiosity-style workflow that focuses on sky and sun contributions, so throughput stays higher while some deep bidirectional luminance and glare probability detail is not the main emphasis.
How do parametric iteration workflows differ between Grasshopper-based and Rhino-centered tools?
Ladybug Tools operates through Grasshopper components that generate skies, drive Radiance runs, and package metric results tied to geometry updates. Solemma DIVA keeps the study inside the Rhino modeling loop by managing scene setup and computation for repeatable changes to glazing, shading, and material reflectance.
How can a team reuse model structure across multiple daylight studies with different assumptions?
LightStanza focuses on geometry-to-analysis reuse built around Radiance calculations so teams can rerun daylighting outputs efficiently after design changes. OpenStudio also supports repeatable analysis runs tied to a lighting model so scenarios can be swapped without rebuilding the entire scene.
What is the tradeoff when using a tool primarily for daylit performance inside an energy simulation environment?
IDA ICE couples daylight calculations with the same envelope, glazing, and operational assumptions used for energy studies, which keeps daylight and thermal context aligned. The tradeoff is that deep BIM-to-analysis automation and governed collaboration controls are not the product centerpiece, which is why OpenStudio can be a better fit for scene-driven Radiance control when collaboration governance is not the focus.
How do integrations and API-style automation differ across the list for repeatable study templates?
Ladybug Tools provides automation hooks through scripting and commandable components, which supports repeatable study templates driven by parametric geometry. OpenStudio focuses on Radiance-style scene control for repeatable analysis runs, while Relux targets an interactive geometry workflow that updates mapped results directly during design iteration.
Where does SSO or RBAC-style governance fit when multiple teams need controlled access to study configurations?
None of the daylighting tools in the list are positioned as a governance-first collaboration platform, so RBAC and SSO capabilities are not a primary selection criterion across Relux, AGi32, and DIALux. Teams that need audit log and permissioned configuration management often choose a separate platform for access control and then run calculations in tools like DesignBuilder or IES Virtual Environment under controlled workflows.
How should users plan data migration when moving a daylighting workflow between different simulation ecosystems?
Solemma DIVA is designed for Rhino and DIVA workflows, so migrating from a BIM-centered setup to Rhino requires rebuilding scene definitions and parameter setups in the Rhino loop. LightStanza and IES Virtual Environment better match migration efforts from IFC or geometry-centric inputs because they center around Radiance-based calculations that can reuse model structure and optical definitions during iterative scenarios.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

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.