Quantum ESPRESSO vs VASP (2026): How to Choose

Quantum ESPRESSO and VASP are two of the most widely used plane-wave density functional theory codes in materials science, and researchers routinely ask which one to build a workflow around. Both are mature, well-validated, and capable of producing publication-quality results across an enormous range of materials. The right choice depends less on raw capability and more on licensing, ecosystem, and the specific features your work demands.

This post compares the two codes fairly on the axes that matter — licensing and cost, pseudopotential and PAW libraries, features, performance, and community — without claiming a winner. Both are excellent tools; the goal is to help you match one to your situation.

Shared Foundations

It is worth starting with how similar the two codes are under the hood, because it explains why results from both generally agree closely.

Both are plane-wave codes: they expand Kohn–Sham orbitals in a basis of plane waves

controlled by a single kinetic-energy cutoff \(E_{\mathrm{cut}}\), which makes basis-set convergence systematic and easy to check. Both support the projector augmented-wave (PAW) method, the modern standard for treating core electrons accurately, as well as norm-conserving and ultrasoft pseudopotentials. Both use iterative diagonalization, \(\mathbf{k}\)-point sampling of the Brillouin zone, and the same broad menu of exchange-correlation functionals from LDA and PBE through hybrids like HSE06.

A landmark 2016 reproducibility study (“Reproducibility in density functional theory calculations of solids”, Science) compared many DFT codes, including both, and found that well-converged plane-wave PAW calculations agree to within a small fraction of a meV/atom. When set up equivalently, the two codes give the same physics. The differences are practical, not fundamental.

Licensing and Cost

This is the most consequential difference for most groups.

Quantum ESPRESSO is free and open source, distributed under the GNU General Public License (GPL). Anyone can download, read, modify, and redistribute the source. There is no per-seat fee, no license server, and no restriction on how many cores or nodes you run it on. For cloud and HPC deployment this matters: you can scale to thousands of cores without multiplying license costs.

VASP is commercial, proprietary software. It requires a paid license, negotiated per research group, with source access under strict terms. The license fee is modest relative to a research budget for a single group but becomes a real consideration for large deployments, teaching environments, or cloud bursting, where seat counts and node counts drive cost.

Neither model is inherently better. Commercial licensing funds dedicated development and support; open-source licensing removes cost barriers and enables full transparency and reproducibility. Groups that value auditable, modifiable code or that deploy at cloud scale often lean to Quantum ESPRESSO; groups that value a polished, heavily documented commercial package with a long track record often stay with VASP.

Pseudopotential and PAW Libraries

Both codes are only as accurate as the pseudopotentials or PAW datasets you feed them.

VASP ships a curated, well-tested PAW dataset library covering essentially the whole periodic table, maintained by the developers and versioned with the code. This tight integration is a genuine convenience: the recommended potentials are known-good and consistent.

Quantum ESPRESSO draws on multiple open libraries. The Standard Solid-State Pseudopotentials (SSSP) library curates and benchmarks pseudopotentials for accuracy and efficiency; PSlibrary provides PAW and ultrasoft sets; and norm-conserving sets like those from PseudoDojo are widely used. This gives flexibility and transparency — you can inspect and regenerate any potential — at the cost of having to choose, since the ecosystem is decentralized rather than a single vendor-blessed set.

QE pseudopotential ecosystem (common choices):
  SSSP efficiency / SSSP precision   - benchmarked, recommended defaults
  PSlibrary (PAW, USPP)              - full periodic table
  PseudoDojo (norm-conserving)       - ONCV, tested for GW-quality work

Feature Comparison

Both codes cover the core DFT workload — SCF, geometry relaxation, band structures, densities of states, and phonons — but their strengths and packaging differ.

A few specifics worth noting:

• Phonons and DFPT: Quantum ESPRESSO has a long-standing, native density functional perturbation theory implementation (ph.x) that is a reference for phonon and electron-phonon work. VASP typically computes phonons by finite displacements, often paired with external tools like Phonopy.
• Excited states and many-body methods: both support hybrids and GW; VASP’s implementations are tightly integrated and widely used, while Quantum ESPRESSO relies on companion packages and modules.
• Extensibility: because Quantum ESPRESSO is open, method developers frequently prototype new functionals and techniques in it first.

Performance and Parallelization

Head-to-head performance depends heavily on the system, the pseudopotentials, and how well each run is parallelized, so blanket claims are unreliable.

Both codes parallelize over k-points, plane waves, and bands using MPI, with OpenMP threading on top. VASP has a reputation for strong single-node efficiency and mature GPU acceleration, refined over many years of commercial development. Quantum ESPRESSO scales well across many nodes and has increasingly capable GPU support, particularly for the SCF and band-structure workloads that dominate most projects.

In practice, the biggest performance lever is not the code but the setup: pseudopotential hardness (norm-conserving vs ultrasoft vs PAW), plane-wave cutoff, k-point density, and parallelization layout usually matter more than which of the two codes you picked. A poorly converged run in either code is slower and less accurate than a well-tuned run in the other.

Community, Documentation, and Ecosystem

VASP benefits from extensive official documentation, a long institutional history, and a large user base in both academia and industry. Its consistency and support are frequently cited strengths.

Quantum ESPRESSO has an active open-source community, public mailing lists, open issue tracking, and deep integration with high-throughput and workflow frameworks such as AiiDA and ASE. Because the source is open, answers to “why did it do that?” are ultimately verifiable by reading the code. Its documentation and tutorials are maintained at quantum-espresso.org.

Both integrate with common analysis and workflow tools, so migrating a conceptual workflow between them is usually straightforward — the input formats differ, but the underlying physics choices (cutoff, k-points, functional) map directly.

Input Files and Workflow Style

The two codes organize a calculation differently, and the day-to-day feel reflects that.

VASP splits a job across several fixed-name files: INCAR for calculation parameters, POSCAR for the structure, KPOINTS for the Brillouin-zone mesh, and POTCAR for the concatenated PAW potentials. This separation is rigid but predictable — every VASP job has the same four files in the same roles, which makes scripting and teaching straightforward.

Quantum ESPRESSO uses a single namelist-based input file per executable (pw.x for SCF and relaxation, ph.x for phonons, bands.x for band structures, and so on), with Fortran-style &CONTROL, &SYSTEM, and &ELECTRONS namelists. The modular executables mean a full study is often a pipeline of separate runs, which pairs naturally with workflow managers.

VASP:  INCAR + POSCAR + KPOINTS + POTCAR  ->  single vasp run
QE:    pw.x (scf) -> pw.x (nscf) -> bands.x / dos.x / ph.x ...

Neither style is objectively better; they reflect different design philosophies. Groups running large automated high-throughput screens often appreciate Quantum ESPRESSO’s modular executables and open format, while groups that value a single consistent job template appreciate VASP’s fixed layout.

Reproducibility and Provenance

A practical consideration that is easy to overlook is reproducibility. Because Quantum ESPRESSO is open source, a published result can in principle be reproduced exactly by anyone: the source, the pseudopotentials (from open libraries), and the input are all freely available. This transparency is increasingly valued by journals and funding agencies that emphasize open science.

VASP results are equally valid and reproducible within the licensed community, and the curated PAW datasets aid consistency, but full reproduction requires access to the licensed code. For collaborations that span institutions with different licensing situations, or for work intended to be reproduced by the broadest possible audience, open-source availability can be a deciding factor. Both codes, it should be stressed, produce trustworthy science — the difference is who can independently verify it.

How to Choose

There is no universally correct answer, but the decision usually comes down to a few questions:

flowchart TD
  A[Choose a DFT code] --> B{Need free / open source<br/>or cloud scale without<br/>license cost?}
  B -->|Yes| C[Quantum ESPRESSO]
  B -->|No / flexible| D{Need vendor-curated PAW<br/>+ commercial support?}
  D -->|Yes| E[VASP]
  D -->|No| F{Native DFPT phonons<br/>or full source access?}
  F -->|Yes| C
  F -->|Existing VASP expertise| E
  C --> G[GPL, SSSP/PSlibrary,<br/>ph.x DFPT]
  E --> H[Licensed, in-house PAW,<br/>finite-diff phonons]

• Do you need to deploy at cloud or large HPC scale without per-node license cost? Quantum ESPRESSO’s open license removes that barrier entirely.
• Do you need native, reference-quality DFPT phonons? Quantum ESPRESSO’s ph.x is a strong reason to prefer it.
• Do you value a single vendor-curated PAW library and integrated commercial support? VASP delivers that polish.
• Is full source transparency and modifiability important for your method development or reproducibility requirements? That favors open-source Quantum ESPRESSO.
• Does your group already have deep expertise and existing workflows in one code? Institutional knowledge is a legitimate and often decisive factor.

For a deeper look at how DFT engines differ in architecture and hardware targeting, see our overview of computational engines.

Run it on Simatra

Both Quantum ESPRESSO and VASP are compute-bound: the accurate, large-scale calculations you care about are limited by the hardware you can throw at them. Simatra runs DFT on GPU-accelerated clusters (instance GPU-Opt-V2) with up to 5x faster convergence, handling supercells up to ~2,000 atoms across two computational engines: the open-source Quantum ESPRESSO and Simatra’s native KRONOS. Run production plane-wave DFT without provisioning or maintaining a cluster, and start with a free trial and $100 in credits at app.simatra.io.