Skip to main content
v2026.11,986 entries · CC-BY 4.0

Thermo-Calc: Software, Modules and Databases Explained

Thermo-Calc is CALPHAD thermodynamics software that needs a database to run. See its built-in calculators, add-on modules, database families and SDKs.

Written and maintained by CASRAI Editorial Board

Published

On this page

Thermo-Calc is commercial computational-thermodynamics software from Thermo-Calc Software AB of Stockholm. It calculates phase equilibria, transformation temperatures, phase amounts and compositions, and related properties for multicomponent materials, and it cannot run a calculation until at least one thermodynamic database is loaded. The software and the databases are separate products, and that split is the single most useful thing to understand before you plan a project with it.

What Thermo-Calc is

The vendor describes Thermo-Calc as its flagship thermodynamics software, built on the CALPHAD approach to modelling the thermodynamics of materials. The company states that it was founded in 1997 and that the work traces back to the late 1970s, when graduate students at KTH in Stockholm developed the first version. Its headquarters are in Stockholm.

Thermo-Calc is a calculation engine and a graphical environment around it. It does not contain material data by itself. The vendor’s product page states that a thermodynamic and properties database is required to make calculations with it, which is why anyone planning to use it for metallurgy, ceramics, solder, magnets or aqueous systems starts by choosing a database that covers their chemical system. The peer-reviewed description of the software and its diffusion companion DICTRA is Andersson, Helander, Höglund, Shi and Sundman, Calphad 26(2), 273-312 (2002), doi:10.1016/S0364-5916(02)00037-8, which is the standard citation when a paper reports Thermo-Calc results.

Other thermodynamic and kinetics packages are covered elsewhere on CASRAI, such as Cantera, CoolProp and NASA CEA. Those packages address fluids, combustion and chemical equilibrium rather than multicomponent alloy phase equilibria, so they address different questions from Thermo-Calc.

What you need before the first calculation

The vendor’s own pages imply a short dependency chain, which is worth turning into a checklist before requesting a licence:

  1. The Thermo-Calc software licence. The built-in calculators listed below come with every licence.
  2. At least one thermodynamic database. The vendor’s database page states that all users must have at least one thermodynamic database.
  3. A mobility database, only if you need kinetics. Mobility databases are companion kinetic databases that pair with a specific thermodynamic database and serve the kinetic modules.
  4. The add-on module for the question you are asking. Diffusion, precipitation, additive-manufacturing and process-metallurgy work each have their own module.
  5. An SDK, only if you want to script calculations. The programming interfaces are add-ons to a Thermo-Calc licence.

A team that buys the software and then discovers that its alloy system is not covered by the database it holds has a stalled project. Matching the database to the chemical system first is the practical lesson of this dependency chain.

How a calculation works

A calculation combines three ingredients: the system definition (the elements and phases you select), the database that supplies the model parameters for those phases, and the calculator that asks a specific question. Thermo-Calc builds on the CALPHAD method, in which the thermodynamic description of each phase is stored in a database as parameters fitted to experimental and computed data. The results are therefore outputs of those models. They are only as reliable as the database’s coverage of the composition and temperature range you ask about.

The equilibrium outputs the vendor lists are phase amounts and compositions, transformation temperatures, solubility limits, driving forces, activities, and phase, potential and Pourbaix diagrams. The property-prediction tools estimate thermophysical, kinetic, mechanical, elastic and solidification properties as functions of composition and temperature. Plots can be exported as JPG, SVG or PNG, and tables as TXT, HTML or XLS.

Built-in calculators and add-on modules

The vendor distinguishes between tools included with every licence and separately licensed add-on modules. The table summarises the names the vendor uses and where each sits.

Tool Included with every licence? Note from the vendor page
Equilibrium Calculator Yes Source of the phase amount, composition, transformation temperature, solubility and diagram outputs described above
Scheil Solidification Simulations Yes Listed as a built-in calculation type
Property Model Calculator and General Model Library Yes Property prediction against composition and temperature
Material to Material Calculator Yes Listed as a built-in calculator
Aqueous Calculator Yes Listed as a built-in calculator
Pourbaix Diagram Module Yes Available in console mode only
Data Optimization Module (PARROT) Yes Listed as a built-in module
Diffusion Module (DICTRA) No, add-on Diffusion simulation
Precipitation Module (TC-PRISMA) No, add-on Precipitation simulation
Additive Manufacturing Module No, add-on Of the SDKs, only TC-Python supports it
Process Metallurgy Module No, add-on Listed as an add-on
Model libraries for steel, nickel, titanium and noble-metal alloys No, add-on Alloy-family property models

The practical reading is that a lab asking only an equilibrium question (which phases are stable at this composition and temperature) can start with the built-in set, while a lab asking how fast something happens, such as diffusion or precipitate growth, needs the kinetic modules and therefore the companion mobility databases.

Databases

The vendor lists more than 40 databases: 28 thermodynamic and properties databases and 14 companion kinetic (mobility) databases, plus customer-specific databases. The thermodynamic ones are organised by material family and application. The published categories are steel and Fe-alloys, nickel, aluminium, magnesium, copper, titanium and TiAl, noble metal, high entropy, solder, silicon, metal oxide solutions, zirconium, molybdenum, niobium, permanent magnetic, ultra-high temperature, molten salts, cemented carbides, electronic materials, aqueous, minerals, SGTE general alloys and pure substances, nuclear materials from IRSN, and ThermoTech Ltd databases.

Two points matter when scoping a project. First, a database defines which elements and phases you can model, so the category list is effectively the list of chemical systems the product can address. Second, the kinetic databases are not standalone: each mobility database pairs with a specific thermodynamic database, so a diffusion study needs both.

SDKs and automation

Thermo-Calc can be driven from code through three vendor SDKs, summarised in the data table below. All three are add-ons to a Thermo-Calc licence. TC-Python is the Python SDK, built to work with NumPy, SciPy and Jupyter, and it is the only SDK that supports the Additive Manufacturing Module. TC-Toolbox for MATLAB needs its own MATLAB licence and is currently only available on Windows. TQ-Interface provides Fortran subroutines delivered as a DLL, with C equivalents, runs on Windows and Linux, is used in MICRESS and is maintained as needed. The vendor describes a twice-yearly release cycle for TC-Python and TC-Toolbox.

Scripting matters for research practice because it makes a parameter sweep or a database comparison repeatable: the script, the software version and the database version become part of the record. Keep all three in the project’s methods note or data package so that another group can reproduce the figure.

Where it matters for materials labs

Thermo-Calc is used alongside experiments. A typical pairing is a calculated equilibrium or solidification result that guides which compositions and heat treatments a lab tests, followed by measured microstructure data that confirms or corrects the prediction. For reporting, record the software release, each database and its version, the elements and phases included, and any phases you suspended. Without that, a phase diagram in a paper cannot be reproduced. If your project also publishes or deposits computed results, the open materials science discipline hub and the lab operations hub list related practice guides, and the Computational Materials Science journal guide is relevant to where such work is published.

Worked scoping example (illustrative composite)

This is an illustrative composite, not a report of a real project. Suppose a lab wants to know which phases form in a nickel-based alloy as it cools, and then how quickly a strengthening phase coarsens during ageing. Using the dependency chain above: the first question is an equilibrium and solidification question, so it needs the software, a nickel thermodynamic database, and the built-in Equilibrium Calculator and Scheil Solidification Simulations. The second is a precipitation question, so it needs the Precipitation Module (TC-PRISMA) and, because it is a kinetic module, a mobility database paired with the chosen nickel thermodynamic database. If the lab then wants to run a hundred compositions unattended, it adds TC-Python. Each step names a specific item from the vendor pages, so the scoping conversation with the vendor or the lab’s IT team can list exactly what is needed rather than asking for ‘Thermo-Calc’ in general.

What to record in a methods note

  • The Thermo-Calc release used and any add-on modules involved
  • Each thermodynamic database and, for kinetic work, each mobility database, with its version
  • The elements and phases included in the calculation
  • For scripted work, the SDK used and the script itself
  • The citation for the software, such as the Calphad 2002 paper listed under Sources

These items are editorial guidance for reproducibility rather than a requirement stated by the vendor, but each one corresponds to something the vendor pages show can change a result: the database defines the available models, the modules define the calculation type, and the SDK defines how a run is automated.

Common misunderstandings

Thermo-Calc is not a database

The software and the databases are sold and described separately. The vendor states that a database is required, and the database page states that all users need at least one thermodynamic database.

Calculated phase diagrams are model outputs, not measurements

CALPHAD results depend on the parameters stored in the database. Outside the composition and temperature ranges those parameters were assessed for, the result is an extrapolation that should be checked experimentally.

Kinetic questions need more than the base licence

Diffusion and precipitation are handled by add-on modules, which in turn rely on mobility databases paired with a thermodynamic database.

Automation is an add-on, not part of the base product

The Python, MATLAB and Fortran/C interfaces are all add-ons to a Thermo-Calc licence, and the MATLAB toolbox additionally requires a MATLAB licence.

Sources

Data: Thermo-Calc software development kits compared

Compares the three programming interfaces Thermo-Calc Software offers, by language or environment, platform, licensing dependency and notes. Compiled from the vendor's SDK page, read on 2026-11-16.

Thermo-Calc software development kits compared
SDKLanguage or environmentPlatformExtra licence needed beyond Thermo-CalcNotes
TC-PythonPython (NumPy, SciPy, Jupyter)Not stated on the vendor pageNoOnly SDK that supports the Additive Manufacturing Module; twice-yearly release cycle
TC-Toolbox for MATLABMATLABWindows only (currently)MATLAB licenceTwice-yearly release cycle
TQ-InterfaceFortran subroutines as a DLL, with C equivalentsWindows and LinuxNoUsed in MICRESS; maintained as needed

Sources

Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Ask CASRAI · full access

Ask about Thermo-Calc: Software, Modules and Databases Explained

Full access: large monthly usage, up to 10 source passages behind each answer, and MCP and API access for Claude Code, Codex and other CLIs. Cancel any time.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →