Quantum state tomography software reconstructs a quantum-state description from measurements made on identically prepared systems. For circuit-based qubits, Qiskit Experiments provides a framework for designing tomography circuits, collecting data, and analyzing it; QSTToolkit is a Python package centered on optical-state measurement data and comparisons between conventional and deep-learning reconstruction. Choose by experimental modality, measurement workflow, estimator, and API stability—not by an unsupported claim that one tool is universally better.
What quantum state tomography software does
Quantum state tomography (QST) infers a state description from measurement outcomes gathered across suitable measurement settings. The state is not read out directly: a researcher prepares nominally identical systems, measures them in different bases, and uses the resulting counts or other measurement data to estimate the state.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Introduction To Quantum-State Estimation | $29.00 | Buy on Amazon |
| 2 |
|
In Search of Schrödinger's Cat: Quantum Physics and Reality | $16.78 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
As the Qiskit Experiments documentation puts it, “Quantum state tomography (QST) is a method for experimentally reconstructing the quantum state from measurement data.” Software can help generate or organize measurement settings, execute experiments, store results, and fit a state estimate. Which of those tasks it handles depends on the package and on whether measurements are being planned or have already been collected.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Which software should you use for quantum state tomography?
The two packages covered here address different workflows. Qiskit Experiments is suited to circuit-based characterization within the Qiskit ecosystem, while QSTToolkit is aimed at optical quantum-state measurement data and method comparisons. Neither package is established by the cited sources as a universal solution or as superior in overall accuracy or speed.
#1 Best Overall
| Decision factor | Qiskit Experiments | QSTToolkit |
|---|---|---|
| Documented emphasis | Circuit-based quantum-computer experiments, including state and process tomography. | Optical quantum-state measurement data. |
| Experiment setup | Experiment classes construct tomography circuits using supported basis choices; the framework can store results and associate analysis. | Authors describe data-generation and reconstruction components. The cited paper does not establish it as a general hardware-backend circuit-execution framework. |
| Reconstruction approaches | Linear inversion and constrained least-squares fitters are documented. | Combines conventional maximum-likelihood estimation (MLE) with deep-learning approaches in the authors’ implementation. |
| Noise or readout handling | Mitigated state and process tomography variants characterize readout error before tomography. | Authors describe synthetic data generation with configurable noise models; this is not equivalent to hardware readout-error mitigation. |
| Data and ecosystem | Uses Qiskit Experiments’ experiment and data-analysis framework; Qiskit itself is a separate open-source SDK ecosystem. | Python library bridging QuTiP and TensorFlow, as described by its authors. |
| Stability evidence | Current stable API documentation warns that tomography fitter and basis interfaces remain under development. | The cited paper describes the package, but does not establish current maintenance or dependency compatibility. |
Use this comparison to narrow candidates, then test the workflow against data representative of your apparatus. The available sources do not provide a controlled, current cross-package benchmark.
Qiskit Experiments: tomography within a circuit workflow
Qiskit Experiments is a separate package in the broader Qiskit ecosystem, rather than a tomography feature to attribute to the core Qiskit SDK. IBM describes the Qiskit SDK as open source and its quantum-information library as working with states, operators, and channels in its Introduction to Qiskit. The package’s framework is described in the 2023 Qiskit Experiments paper: an experiment defines circuits, an ExperimentData container stores measurements, and an analysis class processes data and attaches results.
State, process, and readout-mitigated experiments
The API lists StateTomography to reconstruct a state and ProcessTomography to reconstruct a quantum channel. It also lists mitigated state and process tomography variants that characterize readout error and then perform tomography. State tomography is the relevant entry point when the target is a prepared state; process tomography instead characterizes a transformation or channel.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Basis choices and fitters
The documented basis classes include Pauli measurement and preparation bases, along with custom local tensor-product basis classes. Available fitters include linear inversion, constrained Gaussian linear least-squares, and constrained weighted linear least-squares. These choices matter: the selected measurement settings determine what information is collected, while the fitting objective and constraints determine how the software converts noisy observations into an estimate.
Check the exact version you intend to pin before building against these interfaces. The Qiskit Development Team’s tomography API reference, updated August 25, 2026, says: “The API for tomography fitters and bases is still under development so may change in a future release.”
QSTToolkit: optical measurements and reconstruction comparisons
QSTToolkit is a Python library described by its authors for optical quantum-state measurement data. Its paper presents two main components: data generation and tomography/reconstruction. The package combines MLE and deep-learning methods and bridges QuTiP and TensorFlow. That makes it a candidate to investigate for optical-state work and within-package method comparisons, not an interchangeable replacement for a circuit-oriented experiment framework.
Rank #2
The authors state that the toolkit’s standard dataset contains 7,000 quantum states. This figure describes the dataset included with the toolkit, not a field-wide benchmark or an independent evaluation. Results reported for its learned models are specific to the dataset, setup, and conditions in the authors’ paper; they do not show that deep learning generally outperforms conventional tomography. See the authors’ QSTToolkit paper, submitted March 18, 2025 for the described methods and evaluation context.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsHow to reconstruct a state from measurement data
A sound workflow starts with the experiment and its assumptions, not with a preferred algorithm name.
- Define the target and modality. Decide whether you need a state estimate or a channel estimate, and whether your experiment is circuit-based or uses optical measurement data. Select a tool whose documented workflow matches that setup.
- Choose measurement settings and bases. For circuit-based tomography, select supported measurement and, where relevant, preparation bases that suit the experiment. Ensure the settings provide the measurements needed for the state you intend to reconstruct.
- Collect or prepare the data. In a circuit framework, generate and execute the experiment circuits, then retain the resulting measurement data. For a package that expects optical measurement data, check its accepted input representation and map your acquired data accordingly; do not assume identical formats across packages.
- Select an estimator deliberately. Compare the available fitting objective and constraints against your needs. Record whether the estimate comes from linear inversion, constrained least squares, MLE, or a learned model.
- Account for measurement error. Determine whether readout mitigation or a suitable modeled noise treatment is available and appropriate. Synthetic noise settings should reflect the apparatus if they are used to evaluate a reconstruction method.
- Validate on representative data. Test with simulated or experimental data reflecting your basis choices, shot counts, and noise conditions. Report those conditions with the software version and estimator assumptions so another researcher can interpret or reproduce the result.
Linear inversion, constrained least squares, and maximum likelihood
Linear inversion solves for a state description from measured data using a linear reconstruction. It is a documented option in Qiskit Experiments, but a resulting estimate need not satisfy physical-state constraints when measurements are noisy or incomplete.
Constrained least-squares fitting instead minimizes a least-squares discrepancy subject to constraints; Qiskit Experiments documents Gaussian and weighted variants. Such constraints can enforce physical properties of the estimate, but the specific objective and weighting still matter for noisy data.
MLE chooses a state estimate by maximizing the likelihood of the observed outcomes under a measurement model. QSTToolkit’s authors include MLE alongside learned approaches. The label alone does not establish that MLE or any other estimator is more accurate for a particular experiment: compare methods using the same representative data, measurement assumptions, and validation criteria.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
What to verify before committing to a package
- Modality and bases: Confirm the package supports the experiment’s measurement or preparation settings, rather than inferring universal coverage from its stated focus.
- Input and output: Check accepted data formats, output state representation, and how results are stored or exported.
- Execution integration: If circuits must run on a quantum processor, verify the relevant backend and execution path for the Qiskit workflow and your environment.
- Noise treatment: Distinguish readout-error mitigation from simulation with configurable noise; they address different parts of a workflow.
- Reproducibility: Record shot counts, basis choices, noise model, estimator assumptions, dependencies, and pinned software versions. Reproduce paper results only under the stated conditions rather than assuming the package’s example dataset matches your apparatus.
- API stability: Pin and check the exact Qiskit Experiments version because the documented fitter and basis APIs may change. For QSTToolkit, verify current maintenance and dependency compatibility directly before relying on it in a sustained pipeline; the cited paper does not establish those details.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
