Skip to main content

Best Open Source Software for Fire Simulation in Buildings — FDS in 2026

Most fire deaths are caused not by flames, but by smoke. Toxic gases and loss of visibility disable occupants long before fire reaches them — which is exactly why predicting how smoke and heat move through a building is one of the most valuable things a fire safety engineer can do. The best tool for that job is free, open source, and built by the US government: FDS — the Fire Dynamics Simulator. This guide explains what FDS is, its capabilities and application areas, how any user can get started, and how it helps prevent fire disasters in buildings.

FDS fire and smoke simulation in a multi-storey building with occupant egress

Figure 1. What FDS models: a fire generates a rising thermal plume, hot smoke banks down under each ceiling, and occupants must escape before visibility and temperature become untenable. FDS predicts these smoke and heat flows hour by second across the whole building.

What Is FDS (Fire Dynamics Simulator)?

Fire Dynamics Simulator (FDS) is a computational fluid dynamics (CFD) model of fire-driven fluid flow, developed and maintained by the US National Institute of Standards and Technology (NIST). First released publicly in February 2000, it has become the global standard tool in fire safety science.

Technically, FDS solves a large-eddy simulation (LES) form of the Navier–Stokes equations appropriate for low-speed, thermally driven flow (Mach number below 0.3), with an emphasis on smoke and heat transport from fires. In plain terms: it divides a building into a 3D grid of small cells and, time step by time step, calculates how hot gases, smoke, oxygen and combustion products move through every cell — reproducing the physics of a real fire.

Because it is US government software, FDS is in the public domain — completely free and open source, with full source code on GitHub. As of 2026 the current stable release is FDS 6.10.1 (with Smokeview 6.10.1), and a beta branch of FDS 7 is being evaluated at NIST's Sandia FLAME facility. It runs on Windows, Linux and macOS.

In one sentence: FDS is a free, physics-based CFD engine from NIST that predicts how fire, smoke and heat spread through a building — the foundation of modern performance-based fire safety design.

Capabilities of FDS

FDS is far more than a "flame animation." It resolves the coupled physics that govern life safety in a fire:

  • Smoke and heat transport — the movement of hot, toxic smoke through corridors, stairwells, atria and shafts, including the smoke layer that banks down under ceilings.
  • Combustion and pyrolysis — energy release from burning fuels, with a heat-flux-scaling pyrolysis model (added in recent versions) for more accurate burning-rate prediction of solid fuels.
  • Heat transfer — convection, radiation and, in recent releases, full three-dimensional heat conduction through solid boundaries.
  • Temperature and gas concentrations — spatial and time histories of temperature, carbon monoxide (CO), carbon dioxide (CO₂), oxygen (O₂) and visibility.
  • Ventilation and HVAC — natural and mechanical airflow, smoke exhaust systems and pressurisation.
  • Sprinklers and detectors — activation of sprinklers, heat detectors and smoke detectors, and the effect of sprinkler sprays on the fire.
  • Devices and controls — virtual sensors (thermocouples, gas sensors) and logic to model fire-protection system responses.

All of this is validated against real fire-test data through NIST's extensive FDS Validation Guide, which is why FDS results are accepted by authorities having jurisdiction around the world.

Application Areas

FDS is used wherever fire and smoke behaviour must be understood or proven. The main application areas include:

  • Performance-based fire safety design of complex buildings — atria, malls, airports, stadiums and transit stations where prescriptive codes don't fit.
  • Smoke control and management system design — sizing exhaust fans, verifying that smoke stays above head height on escape routes.
  • Tunnel and underground fire safety — road tunnels, metros and car parks, where ventilation strategy is critical.
  • Egress and life-safety verification — coupling fire results with evacuation models to prove occupants can escape safely.
  • Industrial fire hazard analysis — warehouses, process plants and energy facilities.
  • Forensic fire investigation — reconstructing how a real fire developed to determine cause and spread.
  • Fire code development and research — the purpose for which NIST originally built it, and fundamental combustion research.

Smokeview, BlenderFDS & Companion Tools

FDS is an engine, not a complete package — so it is used alongside a small ecosystem of tools:

Smokeview (SMV) — the official NIST visualisation program. It reads FDS output and produces 3D animations of smoke, flame, temperature slices and vectors, with a simple menu-driven interface. It is how you actually see your simulation results. Free from NIST.
BlenderFDS — the leading free and open source graphical interface for building FDS models, developed by Emanuele Gissi as an add-on to Blender. It lets you draw complex geometry with powerful 3D tools and export a ready FDS input file, while keeping you in full control of every parameter. blenderfds project.
PyroSim — a polished commercial graphical front end for FDS (by Thunderhead Engineering). Not open source, but widely used in industry for faster model building and professional support.
Pathfinder — an agent-based evacuation (egress) simulator that can read FDS/Smokeview results, letting engineers model how occupants respond to smoke, and calculate the Fractional Effective Dose (FED) of toxic gases along escape routes.
CFAST — NIST's free two-zone fire model, useful for faster, simpler multi-room smoke-transport analysis where full CFD is not required. Smokeview can visualise CFAST results too.

How Any User Can Use FDS — Step by Step

You do not need to be a NIST scientist to run a fire simulation. The workflow below is how students, engineers and researchers use FDS in practice.


Four-step FDS fire safety workflow for buildings

Figure 2. The FDS fire-safety workflow. Build the model, simulate the fire, visualise smoke and heat, then assess whether occupants can escape safely — turning physics into a safer, code-compliant building design.

The four practical steps:

Step 1 — Build the model. Define the building geometry (walls, floors, doors, vents), the fire source (location and heat release rate), fuels, ventilation and any detectors or sprinklers. Beginners use BlenderFDS (free) or PyroSim to draw this graphically; advanced users write the FDS text input file (.fds) directly.
Step 2 — Run the simulation. Download FDS free from the NIST download page and run your input file. FDS computes the numerical solution and writes output files. Larger or finer-mesh models take longer — from minutes to hours or days — and can be run in parallel across multiple CPU cores.
Step 3 — Visualise results in Smokeview. Open the output in Smokeview to watch smoke fill the space, view temperature and visibility slices, and track when and where conditions become dangerous.
Step 4 — Assess safety and iterate. Extract the numbers that matter — smoke layer height, temperature, CO, visibility at head height — and compare them against life-safety criteria. If a design fails, change the smoke exhaust, vents or layout and re-run. This loop is the heart of performance-based fire engineering.
Learning tip: Start with NIST's FDS User's Guide, run a simple single-room example first, and confirm your results look physically reasonable before modelling a whole building. Free tutorials and an active discussion forum are available online.

How FDS Helps Prevent Fire Disasters in Buildings

This is the real payoff. FDS prevents fire tragedies by letting engineers test a fire safely on a computer — before the building is built and before anyone is at risk. Concretely, it helps in these ways:

1. Verifying that people can escape in time (ASET vs RSET)

The core life-safety question is whether occupants can get out before conditions become untenable. FDS predicts the Available Safe Egress Time (ASET) — how long until smoke, heat or toxic gas make escape routes impassable. Paired with an evacuation model like Pathfinder, which gives the Required Safe Egress Time (RSET), engineers can prove that ASET comfortably exceeds RSET. If it doesn't, the design is fixed before construction.

2. Designing effective smoke control

Because smoke — not flame — kills most people, keeping escape routes clear of smoke is critical. FDS lets designers size and position smoke exhaust and pressurisation systems and prove they keep the smoke layer above head height long enough for evacuation.

3. Placing detectors and sprinklers where they work

FDS models when heat and smoke detectors activate and how sprinklers respond, helping optimise their location and sensitivity so that alarm and suppression happen as early as possible.

4. Testing "what-if" fire scenarios impossible in real life

Engineers can simulate worst-case fires — a blocked exit, a failed fan, a fast-growing fire — and see the consequences without endangering anyone. This scenario testing exposes weaknesses that a checklist-based code review would miss.

5. Justifying safe, code-compliant designs

For complex or novel buildings where prescriptive codes don't apply, FDS provides the quantitative evidence that authorities require to approve a performance-based design — enabling architecture that is both ambitious and safe.

In short, every smoke plume FDS simulates on screen is a hazard identified and engineered out before it can ever threaten real occupants. That is how simulation saves lives.

FDS vs Other Fire & Egress Tools

ToolRoleMethodOpen Source?Best For
FDSFire & smoke engineCFD (LES)Yes (NIST)Detailed smoke/heat modelling
SmokeviewVisualisation3D renderingYes (NIST)Viewing FDS results
BlenderFDSModel builder (GUI)Geometry pre-processorYes (GPL)Free graphical FDS modelling
CFASTFire & smoke engineTwo-zone modelYes (NIST)Fast multi-room analysis
PyroSimModel builder (GUI)FDS front endNo (commercial)Professional FDS workflows
PathfinderEvacuationAgent-based egressNo (commercial)Occupant escape modelling

Limitations to Know

FDS is powerful, but honest practice means understanding its limits. It is a low-speed (low-Mach) model, so it is not intended for explosions or detonations. Results depend heavily on mesh resolution — too coarse a grid gives misleading smoke behaviour, so a grid-sensitivity check is essential. Fine meshes needed to resolve turbulent flames can demand hours of computing per second of simulated fire, so large models require patience and multi-core hardware. And, as with any CFD tool, results are only as good as the input assumptions — the fire size, fuel properties and boundary conditions must be chosen carefully and, ideally, validated. FDS is a professional engineering tool, not a plug-and-play app, and competent results require understanding the underlying fire science.

Frequently Asked Questions

What is FDS software used for?

FDS (Fire Dynamics Simulator) is a CFD model used to simulate fire-driven fluid flow in buildings. It predicts smoke movement, heat transport, temperature, gas concentrations and the effect of ventilation and sprinklers, so engineers can design safer buildings, verify smoke control systems and support performance-based fire safety design.

Is FDS free to use?

Yes. FDS and Smokeview are completely free and open source, developed by the US National Institute of Standards and Technology (NIST). As US government software they are in the public domain, with no licence fee for any user, including commercial use.

Does FDS have a graphical user interface?

FDS itself does not; it reads a text input file and writes output files. Smokeview provides menu-driven visualisation. For building the model, the free open source BlenderFDS add-on and commercial front ends like PyroSim make it much easier to create geometry and generate FDS input files.

How does fire simulation help prevent fire disasters in buildings?

It lets engineers test how smoke and heat spread before a building is built, without risking lives. By comparing Available Safe Egress Time with Required Safe Egress Time, sizing smoke control systems, positioning detectors and sprinklers, and testing worst-case scenarios, designers can prove occupants will be able to escape safely — reducing the risk of fatalities in a real fire.

What is the latest version of FDS in 2026?

As of 2026 the current stable release is FDS 6.10.1 with Smokeview 6.10.1, published by NIST. Recent versions added three-dimensional heat conduction and an improved pyrolysis model, and a beta branch of FDS 7 is being evaluated at NIST's Sandia FLAME facility.

Conclusion

FDS proves that the best fire simulation software for buildings is also completely free. Backed by NIST, validated against real fire tests, and supported by open tools like Smokeview and BlenderFDS, it gives students, engineers and researchers a professional-grade way to understand and control fire and smoke — the single biggest killer in building fires.

By letting us watch a fire unfold safely on a screen, FDS turns fire safety from guesswork into engineering. Every hazard it reveals in simulation is one that never has to be discovered in a real emergency — and that is how open source software helps save lives.


For more tutorials on CFD, fire, energy and engineering simulation, explore Free CFD Tutorial. If this guide helped, please share it with your colleagues and students.

Comments

Popular posts from this blog

Ceiling Fan Simulation in a Room Using Ansys Fluent | Adding Fan Boundary Condition in CFD

Ceiling Fan Simulation in a Room Using Ansys Fluent | Adding Fan Boundary Condition in CFD Introduction In this tutorial, we will perform a CFD simulation of a ceiling fan inside a room using Ansys Fluent. We will also learn how to add a fan boundary condition to simulate airflow behavior accurately. Step 1: Setting Up the Geometry in Ansys Open Ansys Workbench and create a new Fluid Flow (Fluent) Project . Use SpaceClaim or DesignModeler to create the room and fan geometry. Ensure that the fan blades are modeled properly or import the 3D fan model. Step 2: Meshing the Model Open the Meshing Tool in Ansys. Apply a fine mesh around the fan for better resolution. Use inflation layers near walls for accurate boundary layer calculations. Step 3: Defining the Boundary Conditions Open Ansys Fluent and import the mesh. Set the room walls as no-slip boundaries. Define the fan region and apply the fan boundary condition . Set the inlet velocity and outlet pressure as per simulation r...

TUTORIAL 03: CFD ANALYSIS OF DATA CENTER USING OPEN FOAM SOFTWARE

Title : CFD analysis of data center using open foam software Figure 3.1 (a) Velocity Contour of data center with BCs Figure 3.1 (b) Meshed domain of data center Problem Identification In this problem investigation of data center using OPENFOAM is proposed for heat transfer modeling (data center cooling), in which air is flow in data center from prescribed location section from one inlet condition, which is assumed at surface of left side wall (See the following figure). Air properties are selected from literature available in digital medium. Outlet is at top of the room which is selected for cooling effect of data center system. Some assumptions are applied in this problem like initial room temperature is assumed at constant value for this problem. Air properties are also assumed constant for this problem. “ buoyantBoussinesqPimpleFoam ”  is selected as solver for this problem. Open Foam software is installed on Win 7, provided by FSD blueCAPE Lda: http://bluec...

FDS-01: SIMPLE FLUID FLOW ANALYSIS USING FDS (FIRE DYNAMICS SIMULATOR) TOOL

FDS-01: SIMPLE FLUID FLOW ANALYSIS USING FDS (FIRE DYNAMICS SIMULATOR) TOOL In this tutorial a window is created which is treated as inflow of air with velocity of 2.5 m/s having temperature of 5 C. The outflow conditions is treated at top of the office, and the boundary condition is set as open to atmosphere  The steps are followed in this tutorial are listed below::   Step I: create header syntax file to start program in FDS software.   &HEAD CHID='office'/ Note: office is user defined name of FDS function/ file.   Step II: create syntax for simulation flow time.   &TIME T_END=15.0 Note: 15 sec is simulation flow time, which is solved in FDS software.   Step III: create syntax for initial temperature of domain.   &MISC TMPA=45.0/   Note: 45 C is initial room temperature, which is provided in this tutorial. Following three syntax is must for every FDS function.   Step IV: Create syntax for geom...