Commissioned Research
Top 9 Best Afm Analysis Software of 2026

GITNUXSOFTWARE ADVICE

Science Research

Top 9 Best Afm Analysis Software of 2026

Compare afm analysis software options like SPIP, XEI, and Gwyddion and review fit, typical workflows, and tradeoffs for lab and research teams.

19 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

Search agents gather the source set and the review record, including transcriptions of video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy

AFM analysis software matters because teams turn raw force curves, topography maps, and surface texture metrics into calibrated data products they can reproduce across instruments. This comparison helps operators and technical evaluators weigh desktop analysis depth against automation, integration, and the data model fit for their AFM control and scanning pipeline.

SPIP (spip-1) is the best pick for metrology teams that need repeatable AFM correction and measurement workflows without code because its guided pipeline folds scanner bow correction into measurement gating before analysis, while Gwyddion (gwyddion-3) suits research groups wanting scriptable batch correction, statistics, and export in one reproducible chain.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

SPIP

Scanner bow correction plus measurement gating in a single guided processing workflow before analysis.

Best for: Fits when metrology teams need repeatable AFM correction and measurement workflows without code.

2

XEI

Editor pick

Scanner bow correction and plane fitting are integrated as first-class steps for Parks AFM topography workflows.

Best for: Fits when AFM teams standardize Parks instrument measurements into consistent correction and metric reports.

3

Gwyddion

Editor pick

AFM-first measurement operations with batch automation support for correction, statistics, and export in one processing chain.

Best for: Fits when research teams need reproducible AFM correction and roughness quantification without rebuilding workflows in ImageJ.

Comparison Table

1
SPIPBest overall
enterprise
9.4/10
Overall
2
enterprise
8.9/10
Overall
3
8.6/10
Overall
4
vertical specialist
8.3/10
Overall
5
vertical specialist
8.1/10
Overall
6
vertical specialist
7.7/10
Overall
7
enterprise
7.5/10
Overall
8
vertical specialist
7.2/10
Overall
9
vertical specialist
6.8/10
Overall
#1

SPIP

enterprise

Scanning probe image processor for AFM, STM, and profilometry data.

9.4/10
Overall
Features9.4/10
Ease of Use9.4/10
Value9.4/10
Standout feature

Scanner bow correction plus measurement gating in a single guided processing workflow before analysis.

SPIP’s core strength is measurement-first image processing that stays close to AFM workflows, including flattening and bow correction that prepare images for downstream roughness and height distribution analysis. It keeps analysis operations structured around common AFM outputs, so teams can apply the same correction sequence across datasets without rebuilding pipelines. The software’s export behavior supports moving results into CSV and TIFF-based reporting and archiving for cross-tool review.

A tradeoff is that SPIP’s automation is more workflow-driven than code-driven, so highly custom registration or segmentation logic may require manual intervention or add-ons. SPIP fits teams that run routine AFM metrology on batches of similar samples, where consistent correction and measurement settings matter more than bespoke image logic.

Pros
  • +AFM-specific correction sequence built around flattening and bow removal
  • +Guided roughness and height distribution measurements with consistent settings
  • +Repeatable batch processing for large image sets
  • +Exports analysis outputs to CSV and TIFF for reporting workflows
Cons
  • –Extensibility is weaker for custom algorithms than plugin code ecosystems
  • –Registration beyond typical AFM corrections can require extra manual steps
  • –Some multidimensional AFM workflows depend on format-specific support
Use scenarios
  • Surface metrology teams

    Batch roughness reporting from AFM scans

    Consistent metrology figures

  • Materials characterization labs

    Height distribution after flattening

    Comparable distributions across samples

Show 2 more scenarios
  • Process development engineers

    Grain segmentation from AFM topography

    Stable grain metrics

    Runs segmentation-driven particle and grain measurements tied to height thresholds for repeatable feature stats.

  • Thin film research teams

    Step-height cross-section measurement

    Reduced curvature measurement error

    Measures cross-section profiles after topography correction to reduce curvature bias in step-height results.

Best for: Fits when metrology teams need repeatable AFM correction and measurement workflows without code.

#2

XEI

enterprise

Park Systems software for analyzing AFM and scanning probe microscopy data.

8.9/10
Overall
Features8.9/10
Ease of Use8.9/10
Value8.9/10
Standout feature

Scanner bow correction and plane fitting are integrated as first-class steps for Parks AFM topography workflows.

XEI from parksystems.com supports AFM image analysis tied to Parks AFM acquisition workflows through XEI software modules. Core capabilities focus on topography correction steps like plane fitting and scanner bow correction, then quantitative roughness and height distribution outputs for surface characterization.

The analysis toolchain supports line-by-line processing and batch-style workflows for repeat measurements across similar datasets. Export-oriented reporting targets common microscopy exchange formats and measurement outputs needed for downstream spreadsheets and figure generation.

Pros
  • +AFM-specific correction steps align with common Parks topography workflows
  • +Quantitative outputs include roughness and height distribution metrics
  • +Supports repeat analysis patterns for datasets with consistent acquisition settings
  • +Measurement results export cleanly for figure and spreadsheet use
Cons
  • –Tooling is strongest for Parks data paths and workflows
  • –Some specialized analysis often needs manual parameter tuning per dataset
  • –Automation surface is narrower than research-first analysis stacks
  • –Fewer open-format analysis pipelines than script-driven alternatives
Use scenarios
  • Materials surface metrology teams

    Batch roughness analysis for wafer coupons

    Comparable roughness across batches

  • Microscopy workflow operators

    Line-by-line corrections on single scans

    Cleaner height maps

Show 1 more scenario
  • Research groups making figures

    Export height distributions to spreadsheets

    Faster figure generation

    Generates quantitative height distribution outputs and exports them for downstream plotting and tabulation.

Best for: Fits when AFM teams standardize Parks instrument measurements into consistent correction and metric reports.

#3

Gwyddion

SMB

Free software for processing and analyzing scanning probe microscopy data.

8.6/10
Overall
Features8.6/10
Ease of Use8.6/10
Value8.6/10
Standout feature

AFM-first measurement operations with batch automation support for correction, statistics, and export in one processing chain.

Gwyddion is an AFM analysis tool that emphasizes scriptable, reproducible image processing for research-grade surface measurements. Core workflows include leveling and flattening, drift correction, noise handling, and quantitative roughness outputs such as RMS roughness and height statistics.

It also supports batch processing across files and exports common results for downstream analysis in ImageJ, Fiji, or custom scripts. Compared with ImageJ and Fiji, Gwyddion’s differentiation is its AFM-first processing chain and tight integration with its measurement-oriented operations and automation hooks.

Pros
  • +AFM-focused processing chain for leveling, flattening, and correction
  • +Scriptable batch workflows for repeatable roughness and statistics
  • +Good quantitative outputs like RMS roughness and height distribution
  • +Exports analysis results to common formats for further work
Cons
  • –Automation surface relies on Gwyddion scripting rather than external APIs
  • –Some spectroscopy-style workflows need add-on components or custom steps
  • –Large multidimensional datasets can be slower than dedicated analysis tools
  • –GUI operations can be less discoverable than in ImageJ-based pipelines
Use scenarios
  • AFM researchers

    Reproducible roughness pipelines with scripts

    Repeatable analysis runs

  • Imaging method engineers

    Batch flattening across experiment folders

    Lower manual processing time

Show 1 more scenario
  • Microscopy data analysts

    Export roughness stats to Fiji

    Consistent cross-tool workflows

    Exports quantitative results so ImageJ or Fiji can handle downstream visualization and additional processing.

Best for: Fits when research teams need reproducible AFM correction and roughness quantification without rebuilding workflows in ImageJ.

#4

Nanosurf C3000

vertical specialist

Nanosurf control and analysis software for AFM measurement workflows.

8.3/10
Overall
Features8.3/10
Ease of Use8.3/10
Value8.3/10
Standout feature

Recipe-based analysis that keeps flattening and measurement parameters reusable for batch AFM runs.

Nanosurf C3000 processes AFM datasets exported from Nanosurf scanners and focuses on automated topography corrections, measurements, and batch workflows for repeatable analysis. Core capabilities include plane fitting for flattening, configurable image preprocessing, and metric extraction such as roughness and height distribution outputs.

Pros
  • +AFM-specific batch processing for repeated metric extraction
  • +Flattening and preprocessing steps are configurable per analysis recipe
  • +Measurement outputs stay consistent across sessions and operators
  • +Export-ready tables and images support downstream reporting
Cons
  • –Limited automation compared with Fiji scripting and plugins
  • –Less suited to non-Nanosurf microscope data formats
  • –Cross-modal workflows like correlative microscopy need manual stitching
  • –Advanced segmentation pipelines require more manual tuning
Use scenarios
  • Surface labs using Nanosurf

    Automated corrections on exported scans

    Standardized measurement outputs

  • Process engineering teams

    Recipe-based repeat analysis for parts

    Fewer analysis variations

Show 1 more scenario
  • Metrology coordinators

    Batch height distributions for reporting

    Quicker batch reports

    Extracts roughness and height distribution metrics for repeated acquisitions in one run.

Best for: Fits when Nanosurf AFM teams need consistent correction and measurement across many datasets.

#5

NanoScope Analysis

vertical specialist

Bruker's official software for processing and analyzing data from Dimension and MultiMode AFM systems.

8.1/10
Overall
Features8.1/10
Ease of Use8.1/10
Value8.1/10
Standout feature

Scanner-aware topography correction workflows tuned for Bruker AFM datasets, including plane fitting and line-by-line flattening.

NanoScope Analysis is used to convert AFM scan outputs into corrected images and quantitative results with AFM-specific correction steps. Core workflows include topography flattening, plane fitting, and profile extraction from height images. It produces standard roughness metrics and height distribution outputs used in routine materials comparisons. Relative to Gwyddion, it aligns more tightly with Bruker acquisition formats and less with tool-agnostic analysis pipelines.

Pros
  • +AFM-specific correction tools like plane fitting and line-by-line flattening
  • +Quantification outputs include RMS roughness and height distribution statistics
  • +Cross-section profiles support direct measurement from topography images
  • +Metadata-oriented workflow aligns with typical Bruker AFM data formats
Cons
  • –Batch automation depth is limited versus scripted pipelines in Fiji
  • –Automation requires workspace and parameter management inside the GUI
  • –Integration with non-Bruker datasets is weaker than ImageJ approaches
  • –Advanced segmentation workflows require extra steps compared with research toolchains
Use scenarios
  • Materials characterization teams

    Routine roughness comparisons by profile

    Consistent roughness reporting

  • AFM method validation groups

    Topography flattening with plane fitting

    Lower measurement bias

Show 1 more scenario
  • Instrumentation-focused laboratories

    Analysis aligned to Bruker acquisition formats

    Faster turnaround

    Processes data in the same format family used during acquisition, reducing conversion friction.

Best for: Fits when Bruker AFM users need instrument-native corrections and repeatable quantification without building custom scripts.

#6

AFMWorkshop Software

vertical specialist

Instrument software for AFM acquisition, visualization, and data analysis.

7.7/10
Overall
Features7.7/10
Ease of Use7.7/10
Value7.7/10
Standout feature

GUI-defined batch pipelines keep plane fitting and line-by-line flattening consistent across folders.

AFMWorkshop Software fits research groups that need repeatable preprocessing before downstream calculations, not one-off interactive scripts. Plane fitting and line-by-line flattening are available as first-class operations, and they are typically used to normalize scans before roughness and height statistics are computed. Batch processing supports running the same correction and analysis chain across many images, which reduces variation between operator sessions.

Pros
  • +Plane fitting and line-by-line flattening are built into repeatable workflows
  • +Batch processing supports consistent correction across large scan sets
  • +Export includes CSV and TIFF for measurement results and images
  • +Metadata preservation helps track analysis context across runs
Cons
  • –Workflow customization is primarily GUI-driven rather than API-driven
  • –Advanced registration and spectroscopy workflows are thinner than research-grade pipelines
  • –Force spectroscopy analysis support is limited outside basic curve handling
  • –Extensibility for bespoke measurement algorithms depends on manual setup
Use scenarios
  • Surface metrology teams

    Normalize scans before roughness reporting

    Comparable RMS and height stats

  • Materials research groups

    Process study batches for publication

    Fewer operator-to-operator differences

Show 2 more scenarios
  • QA engineers for coatings

    Measure grain features across runs

    Repeatable feature counts

    Use segmentation and particle-like measurements on corrected topography to track surface changes.

  • Microscopy data curators

    Preserve analysis context

    Traceable analysis provenance

    Keep metadata attached to images so exported results remain traceable to processing settings.

Best for: Fits when labs process many comparable AFM images and need consistent correction and measurements without coding.

#7

MountainsSPIP

enterprise

Commercial software for AFM, SPM, and surface texture analysis.

7.5/10
Overall
Features7.5/10
Ease of Use7.5/10
Value7.5/10
Standout feature

SPIP’s guided correction chain couples fitting and flattening steps to downstream roughness and bearing area outputs without losing spatial consistency.

MountainsSPIP from Digital Surf targets AFM image processing with a workflow centered on topography correction, plane fitting, and flattening operations. The software keeps multiple analysis steps tied to a consistent image coordinate system, which helps when workflows include bearing area curve generation and surface roughness metrics. MountainsSPIP also supports batch-oriented processing for repeated acquisitions and exports processed results for downstream analysis in external tools.

Pros
  • +Plane fitting and multi-step flattening workflows for consistent topography correction
  • +Bearing area curve and roughness metric outputs derived from processed height fields
  • +Batch processing support for repeated AFM image sets and standardized reporting
  • +Export of analysis outputs for external review in common data workflows
Cons
  • –Automation depth depends on workflow construction rather than fine-grained scripting hooks
  • –Metadata preservation across complex multi-channel acquisitions can require manual checks
  • –Large multidimensional datasets can feel slower during iterative correction steps
  • –Advanced segmentation and particle analysis often needs parameter tuning per dataset
Use scenarios
  • Surface roughness analysts

    Bearing area curve plus roughness metrics

    Coherent roughness statistics

  • Research groups processing repeated runs

    Batch correction and metric extraction

    Reduced manual workflows

Show 1 more scenario
  • Downstream reporting teams

    Export processed results to external tools

    Less time rebuilding datasets

    Exports processed height and metric outputs for external analysis and figure preparation.

Best for: Fits when research teams need repeatable AFM correction and roughness workflows with consistent outputs.

#8

Asylum Research AFM Software

vertical specialist

Igor Pro-based analysis environment for Oxford Instruments Asylum AFM systems.

7.2/10
Overall
Features7.2/10
Ease of Use7.3/10
Value7.1/10
Standout feature

Scanner-aware correction and channel handling tailored to Asylum acquisition outputs inside the same workflow.

Asylum Research AFM Software controls AFM acquisition and converts raw scan outputs into analysis-ready data for downstream workflows. The software supports core AFM processing steps such as plane fitting and line-by-line flattening, plus common corrections for scanner artifacts and drift during acquisition.

Pros
  • +Direct AFM acquisition integration reduces format translation steps for Asylum datasets
  • +Plane fitting and flattening workflows support common topography correction needs
  • +Built-in measurement tools cover roughness statistics and cross-section style reads
  • +Channel-aware processing fits amplitude and phase images produced during AFM acquisition
Cons
  • –Batch processing and scripting automation are weaker than Fiji and ImageJ workflows
  • –Export and interchange with open microscopy formats can require manual step validation
  • –Advanced segmentation and grain analysis tooling is less comprehensive than Gwyddion
  • –Metadata preservation across multi-stage processing is harder to guarantee than in dedicated stacks
Use scenarios
  • AFM instrumentation teams

    Correct scans directly from Asylum acquisitions

    Reduced preprocessing overhead

  • Surface characterization analysts

    Drift and scanner artifact correction

    More reliable topography metrics

Show 1 more scenario
  • Materials QA teams

    Profile outputs for routine roughness quantification

    Consistent QA measurements

    Produces height statistics and profile outputs mapped to routine roughness and topography quantification tasks.

Best for: Fits when Asylum AFM datasets need quick in-software correction and measurement without building ImageJ pipelines.

#9

Cytosurge FluidFM Analysis

vertical specialist

Software suite for analyzing FluidFM and AFM force spectroscopy data.

6.8/10
Overall
Features6.8/10
Ease of Use6.8/10
Value6.8/10
Standout feature

FluidFM-specific processing workflow maps raw acquisitions into a repeatable correction and measurement sequence.

FluidFM Analysis provides a guided workflow for turning raw AFM acquisitions into corrected topography and derived quantities, which reduces manual step chaining. Batch processing is geared toward processing many scans with consistent parameters, which helps when experiments produce hundreds of similar fields. Output includes images for visual inspection and tabular exports that fit typical lab data review cycles.

Pros
  • +FluidFM-oriented import and parameter presets reduce per-dataset setup
  • +Batch processing supports consistent correction across large scan sets
  • +Export includes both inspection images and analysis tables
  • +Workflow chaining reduces manual errors in repeated AFM pipelines
Cons
  • –Custom analysis logic is limited compared with scriptable tools
  • –Less suitable when input files use non FluidFM acquisition conventions
  • –Complex multichannel spectroscopy workflows may require external handling
  • –Some advanced correction variants need careful parameter tuning
Use scenarios
  • Materials characterization teams

    Batch surface roughness metrics

    Consistent dataset metrics

  • Biointerfaces researchers

    Topography correction after fluid imaging

    Comparable corrected topography

Show 2 more scenarios
  • Core facility operators

    Automated processing for multiple users

    Lower operator intervention

    Parameterized batch workflows generate consistent outputs for shared lab datasets.

  • R&D analysts

    Review-ready exports to CSV

    Faster analysis handoff

    Tabular exports support downstream plotting and reporting without manual data reformatting.

Best for: Fits when FluidFM-style AFM batches need repeatable correction and metric export without custom scripting.

Conclusion

After evaluating 9 afm analysis software, SPIP stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
SPIP

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Afm Analysis Software

How do SPIP and Gwyddion differ in guided AFM correction versus scriptable processing?
SPIP and MountainsSPIP run guided correction chains that couple scanner bow correction with line-by-line flattening and then proceed to roughness and bearing area outputs in one workflow. Gwyddion stays measurement-first and scriptable, with leveling, flattening, drift correction, and RMS roughness calculations exposed for batch automation and reproducible reprocessing.
Which tool handles batch processing of AFM height images with consistent plane fitting across folders?
AFMWorkshop Software is designed around GUI-defined batch pipelines that keep plane fitting and line-by-line flattening consistent across directory runs. SPIP and MountainsSPIP also support batch handling, but AFMWorkshop emphasizes repeatability through batch pipeline configuration rather than relying on operator-guided measurement steps.
When does scanner bow correction matter more than generic leveling for AFM topography?
Scanner bow correction is a primary step in SPIP and MountainsSPIP workflows, which reduces bow-related distortions before roughness and grain metrics are measured. XEI also integrates scanner bow correction and plane fitting as first-class steps for Parks AFM topography workflows, which helps when comparing scans that show nonuniform curvature across the field of view.
What breaks if metadata preservation is missing when exporting analysis outputs from AFM tools?
If metadata preservation is weak, downstream comparisons in NanoScope Analysis and XEI become harder because exported measurements and coordinate interpretations can lose channel and acquisition context. AFMWorkshop Software emphasizes metadata preservation across batch runs, while Gwyddion focuses on measurement outputs and automation hooks that can require extra care to maintain consistent downstream interpretability.
How do Nanosurf C3000 and NanoScope Analysis compare for scanner-aligned processing and batch reproducibility?
Nanosurf C3000 targets Nanosurf scanner exports and keeps flattening and measurement settings as reusable analysis recipes for consistent batch runs. NanoScope Analysis targets Bruker acquisition outputs and focuses on instrument-native correction workflows with repeatable batch-style operations, including height-channel post-processing like line-by-line flattening and plane fitting.
Which tool provides AFM-first workflow automation without building ImageJ or Fiji pipelines?
Gwyddion provides an AFM-first processing chain with batch automation support for correction, statistics, and export, which reduces the need to rebuild common AFM steps in ImageJ or Fiji. SPIP and MountainsSPIP also reduce pipeline building by packaging correction and measurement steps together, but they emphasize guided processing rather than script-driven extensibility.
How does FluidFM-oriented analysis in Cytosurge FluidFM Analysis differ from general AFM preprocessing?
Cytosurge FluidFM Analysis builds a structured processing workflow for FluidFM-style experiments, mapping raw acquisitions into a repeatable correction and metric export sequence. SPIP and AFMWorkshop Software center on general AFM height-image correction steps like line-by-line leveling and plane fitting, which can support many datasets but do not encode FluidFM-specific workflow structure.
What tradeoff appears when using AFMStudio-like scanner-aligned tools versus open research stacks for spectroscopy workflows?
Asylum Research AFM Software and NanoScope Analysis provide tighter coupling to their instrument data formats and channel handling, which supports quick in-software correction and measurement. The tradeoff is narrower scripting flexibility than an open research stack, so teams that rely on custom spectroscopy curve processing may need additional workflow work outside these instrument-native tools.
When should an AFM team choose Gwyddion over a single-instrument workflow tool like XEI?
Gwyddion fits teams that need repeatable AFM correction and roughness quantification with scriptable batch automation that can adapt across different acquisition sources. XEI fits teams that must standardize Parks AFM instrument measurements into consistent correction and metric reporting, where scanner bow correction and plane fitting are integrated into the Parks-specific workflow chain.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Afm Analysis Software

Analysts distinguish afm analysis software by whether it can reproduce the same correction and output steps on your data, not just display images. The biggest swing is usually how well it handles height correction and surface metrics with a transparent workflow and repeatable exports.

Height correction workflow

Why it matters

A reliable height correction workflow matters because small choices in plane removal and flattening can shift measured heights and derived results. When results must match prior work, this criterion decides whether outputs are comparable.

How to check

Load a sample dataset that includes tilt or curvature, then run the standard flattening/correction option the demo recommends. Compare the resulting height map and any reported surface changes before/after the correction, and ask whether the method is configurable or fixed.

Line-by-line leveling controls

Why it matters

Line-by-line leveling controls matter when samples show directional drift or scan artifacts that affect profiles. Without control, two runs can produce different cross-section profiles.

How to check

Choose a demo scan that shows striping or slope, then toggle the line-by-line flattening (or equivalent) feature. Ask what options exist for its directionality and strength, and verify the change by comparing at least two cross-section profiles.

Drift handling and image registration

Why it matters

Drift handling and image registration matter because repeated acquisitions (or multi-pass data) can misalign, distorting roughness and particle-like statistics. If registration is opaque, you can’t tell what changed.

How to check

Run an analysis on a dataset with more than one frame or pass. Turn registration or drift correction on and off, then inspect whether features line up and whether the software reports the correction applied.

Surface metrics calculation

Why it matters

Surface metrics calculation matters because many decisions rely on consistent roughness descriptors and height distributions. If the software changes definitions behind the scenes, your reported numbers won’t match publications or internal baselines.

How to check

Compute the software’s default roughness metrics and height statistics on the same corrected dataset. Ask the demo to show the exact definitions used (for example, RMS roughness and arithmetic mean roughness) and confirm you can reproduce the outputs after re-running.

Export fidelity for analysis outputs

Why it matters

Export fidelity matters because downstream work often depends on preserving the corrected heights, masks, and profiles. If exports drop metadata or reshape units, you lose traceability across tools.

How to check

Export at least one result set (height map plus profiles or derived metrics) and re-import into the software or a viewer it supports. Verify that axis scaling, units, and key computed values remain the same, and request a documented description of what gets written out.

Automation and API for repeat runs

Why it matters

Automation and API matter when you process many AFM scans with the same correction and metric settings. Without an automation surface, you risk manual parameter drift between datasets.

How to check

Ask whether you can run the same workflow via scripting or API calls and whether parameters are exposed (not just hidden defaults). Then try a small batch of similar datasets and confirm the outputs match single-run results.

Red flags

  • Height correction is described vaguely, with no visible parameters or method choice
  • Drift or registration alters features but the software can’t clearly explain what it did
  • Exports change units or don’t preserve the profile and metric values you just computed

Fit by situation

  • If you must compare results across past studies, prioritize Height correction workflow to keep measurements comparable.
  • If your scans show directional striping or scan-line artifacts, prioritize Line-by-line leveling controls to stabilize profiles.
  • If you reprocess many datasets with the same settings, prioritize Automation and API for repeat runs.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.