Written and maintained by CASRAI Editorial Board
Published
On this page
openEMS is a free and open-source electromagnetic field solver that uses the Finite-Difference Time-Domain (FDTD) method to solve Maxwell’s equations in three dimensions. Researchers use it for radio-frequency and microwave circuits, antennas, radar and metamaterial work, and it is unrelated to the OpenEMS “Open Source Energy Management System” that shares most of its name.
Short answer
openEMS (written with a lowercase “open” and capital “EMS”) is a 3D full-wave simulator. Its engine is written in C++, you describe a model through a Matlab/Octave or Python interface, and it solves Maxwell’s equations on a discretised grid in space and time. Its developers describe an improved formulation called Equivalent-Circuit FDTD (EC-FDTD). It is released under the GPL v3 or later and has been developed since February 2010 at the University of Duisburg-Essen. If you were looking for a Java platform for batteries, solar and energy storage, see the section on the other OpenEMS below.
What openEMS is
According to the project’s own documentation, openEMS is a “free and open source electromagnetic field solver based on the Finite-Difference Time-Domain (FDTD) method”. The documentation lists RF and microwave circuit design, antenna design, radar, metamaterial research and medical research among its applications. It was started and is maintained by Thorsten Liebig at the lab for General and Theoretical Electrical Engineering (ATE), University of Duisburg-Essen. The GitHub repository carries a copyright line of “2010-2026 Thorsten Liebig and contributors”.
The software is a small family of components rather than one program. The data table below lists the main parts and their licences. The solver engine is licensed GPL v3 or later, while the CSXCAD geometry library is licensed LGPL v3 or later. Researchers who need to know whether they may link, modify or redistribute the code should read the licence texts themselves, and our short entry on open-source software gives the general vocabulary.
How openEMS works
The FDTD idea
The openEMS numerical-method page explains that FDTD discretises Maxwell’s curl equations on a Yee grid and advances the fields explicitly in time. Because the update is explicit, there is no global system of equations to assemble or invert. A common workflow is to excite the structure with a broadband pulse such as a Gaussian and take a Fourier transform of the recorded signals. A single run then yields S-parameters, impedances and far-field patterns across the whole frequency band, rather than one frequency at a time.
Equivalent-Circuit FDTD (EC-FDTD)
openEMS uses EC-FDTD, in which each Yee cell is treated as a small lumped circuit: capacitances and conductances sit on the electric-field edges, and inductances and resistances sit on the magnetic-field faces. The documentation is explicit that this is “a reformulation, not a different physical model” and is mathematically equivalent to standard Yee-FDTD. It states that the formulation helps with lumped elements, dispersive materials (Debye, Drude and Lorentz models) and graded or cylindrical meshes, and it points to the Finite Integration Technique associated with Weiland as its lineage.
The mesh
The mesh is the set of Yee cells. Cartesian meshes are the default and can be non-uniform; a cylindrical mesh is available and, per the documentation, avoids staircasing for round structures. Coordinates are unitless, and the scripting call SetDeltaUnit sets what one unit means: the default is the metre, and a value of 1e-3 makes coordinates millimetres. Mesh lines are placed with SetLines or AddLine, and SmoothMeshLines fills in lines subject to a maximum cell size and a grading ratio (the docs give 1.5 as an example).
Two practical points come from the project FAQ. A very small time step means at least one very small cell exists in the mesh. And a zero-thickness 2D metal sheet needs exactly one mesh line at its coordinate, otherwise it is reported as unused.
Features and interfaces
- Cartesian (x, y, z) and cylindrical (rho, phi, z) coordinate systems, with fully graded meshes and subgrids in the cylindrical case.
- MUR and PML absorbing boundary conditions.
- Field dumps in vtk and hdf5 formats, in both time and frequency domain.
- A near-field-to-far-field (NF2FF) transform.
- Coordinate-dependent materials and excitations, which allows mode profiles.
- Multi-threading with SIMD (SSE) acceleration.
- Matlab/Octave and Python interfaces; the CSXCAD library handles geometry, and the AppCSXCAD GUI lets you inspect the 3D model.
The documentation includes tutorials for transmission lines, waveguides, patch antennas, horn antennas, composite right/left-handed (CRLH) structures, scattering and biomedical cases.
openEMS versus the OpenEMS energy platform
Two unrelated open-source projects are spelled almost identically. The other one describes itself as “the Open Source Energy Management System”: a modular platform with an Edge component that runs on site, a Backend in the cloud and a user interface. Its documentation states that Edge and Backend are under the Eclipse Public License 2.0 and the UI under AGPL v3, that it is driven by the OpenEMS Association e.V., and that development began at FENECON GmbH. It has nothing to do with electromagnetic simulation.
The quickest way to tell them apart: openEMS documentation lives at docs.openems.de and the source at github.com/thliebig/openEMS, and talks about meshes, boundaries and S-parameters. The energy platform lives at openems.io and talks about Edge, Backend and energy storage. When you cite or search, include “FDTD” or “electromagnetic” with the name.
When FDTD fits: strengths and limits
The openEMS numerical-method page sets out the trade-offs of FDTD itself. This is useful when deciding between a time-domain solver and a frequency-domain method such as the method of moments (MoM) or the finite element method (FEM), as used in tools like Ansys HFSS or COMSOL.
| Topic | What the openEMS documentation says |
|---|---|
| Bandwidth per run | A broadband pulse plus a Fourier transform gives S-parameters, impedances and far-fields across the whole band in one run. |
| Geometry | No surface meshing as in MoM and no unstructured volume mesh as in FEM; geometry is flexible. |
| Linear algebra | No global linear system is assembled or solved; the method parallelises well. |
| Debugging | Time-domain field dumps help to see what a structure is doing. |
| Meshing cost | All free space up to the absorbing boundary must be meshed volumetrically, so cost grows with volume measured in wavelengths cubed. |
| Accuracy artefacts | Staircasing and numerical dispersion can occur. |
| Stability | Conditionally stable: the time step is set by the smallest cell (the CFL condition). |
| Resonators | Inefficient for narrowband, high-Q resonators because many time steps are needed. |
| Scale mismatch | Low-frequency problems and very small structures are a poor match. |
The practical reading: openEMS suits broadband questions (a filter or antenna across a band) where a single time-domain run replaces many frequency sweeps. It is a weaker choice for a single high-Q resonance or for geometry with features far smaller than the wavelength. For circuit-level (rather than field-level) simulation, a different tool class such as ngspice applies.
Requirements to build it
The installation requirements page lists these minimum versions: CMake 3.0, a C++17-capable compiler (GCC 8 is given as an example) and Boost 1.55. The optional AppCSXCAD viewer additionally needs VTK 6.0 and Qt 4. A script, scripts/install_deps.sh, detects apt, dnf, apk, pacman, brew and pkg. On Unix-like systems all CPU architectures are supported (ARM, POWER, x86_64 and RISC-V are named); on Windows the documentation names x86 and x86_64 using MSVC. A 64-bit build is strongly recommended because a 32-bit build limits the problem size. The README lists CSXCAD, fparser, TinyXML, HDF5, zlib and Boost as dependencies and points to the openEMS-Project meta-repository’s update_openEMS.sh script for building.
How to cite openEMS
The documentation asks users to cite openEMS in publications. Its publications page gives a BibTeX entry: Thorsten Liebig, “openEMS – Open Electromagnetic Field Solver”, General and Theoretical Electrical Engineering (ATE), University of Duisburg-Essen, https://www.openEMS.de. The design paper is Liebig, Rennings, Held and Erni, published in the International Journal of Numerical Modelling: Electronic Networks, Devices and Fields, December 2012, DOI 10.1002/jnm.1875. For general practice on referencing code, see our entries on the FAIR4RS and software citation principles and the software citation working group. Recording the version you used, together with your mesh and boundary settings, makes a simulation easier for others to reproduce.
Common misunderstandings
- “openEMS is the energy management system.” No. These are two separate projects with different licences, languages and communities (see above).
- “EC-FDTD is a different physical model.” The documentation says it is a reformulation, mathematically equivalent to Yee-FDTD, not new physics.
- “A finer mesh is always better.” The time step is set by the smallest cell, so one tiny cell slows the whole simulation.
- “FDTD is best for everything.” The same documentation lists narrowband high-Q resonators and low-frequency or very small structures as weak cases.
- “Free means unrestricted.” The engine is GPL v3 or later and the geometry library LGPL v3 or later; those licences carry conditions.
Frequently asked questions
What does openEMS stand for?
The documentation presents openEMS as the “Open Electromagnetic Field Solver”; the BibTeX title reads “openEMS – Open Electromagnetic Field Solver”.
Is openEMS free?
Yes. openEMS is licensed GPL v3 or later and CSXCAD LGPL v3 or later, and the source is public on GitHub.
Which languages does openEMS use?
The engine is C++. You define simulations with the Matlab/Octave or Python interfaces.
Which operating systems does it run on?
The documentation names Linux, FreeBSD, macOS and Windows.
Is openEMS the same as OpenEMS from FENECON?
No. The energy management platform is a separate project governed by the OpenEMS Association e.V.
Sources
- openEMS documentation, Introduction, https://docs.openems.de/en/latest/intro.html (read 2026-11-14).
- openEMS documentation, Numerical method, https://docs.openems.de/en/latest/concepts/numerical_method.html (read 2026-11-14).
- openEMS documentation, Mesh, https://docs.openems.de/en/latest/concepts/mesh.html (read 2026-11-14).
- openEMS documentation, Requirements, https://docs.openems.de/en/latest/install/requirements.html (read 2026-11-14).
- openEMS documentation, FAQ, https://docs.openems.de/en/latest/faq.html and Publications, https://docs.openems.de/en/latest/publications.html (read 2026-11-14).
- openEMS repository README, https://github.com/thliebig/openEMS (read 2026-11-14).
- OpenEMS (Open Source Energy Management System) introduction, https://openems.github.io/openems.io/openems/latest/introduction.html (read 2026-11-14).
Data: openEMS and OpenEMS (energy): components, roles and licences
Compares the components of the openEMS electromagnetic field solver with the unrelated OpenEMS energy management platform, giving each component's role, implementation language where stated and licence. Compiled from the projects' own documentation and repository README.
| Component | Project | Role | Licence |
|---|---|---|---|
| openEMS engine | openEMS (FDTD solver) | Solves Maxwell's equations by EC-FDTD; C++ | GPL v3 or later |
| CSXCAD | openEMS (FDTD solver) | Geometry library | LGPL v3 or later |
| Edge | OpenEMS (energy management) | Runs on site | Eclipse Public License 2.0 |
| Backend | OpenEMS (energy management) | Cloud component | Eclipse Public License 2.0 |
| UI | OpenEMS (energy management) | User interface | AGPL v3 |
Sources
- openEMS documentation: Introduction (accessed 2026-11-14)
- openEMS repository README (accessed 2026-11-14)
- OpenEMS introduction (energy management system) (accessed 2026-11-14)
Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.







