Softwr

CAD · head to head

CloudCompare vs Lonboard

CloudCompare logo

CloudCompare

CAD

Open source point cloud comparison and processing maintained largely by one person in their spare time

From
Free
Rated
-
Full reviewWebsite
Lonboard logo

Lonboard

Maps

Python map rendering in Jupyter that skips GeoJSON and moves millions of features without choking

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: CloudCompare the project is administered by its creator in his spare time while he holds a full-time job elsewhere, so an organisation building a monitoring programme on it depends on one person with no obligation to continue; Lonboard it is a notebook visualisation library, not a mapping application, so there is no editing, no layout, no map export for print and no sharing beyond distributing the notebook or an HTML file
  • They diverge on capability: CloudCompare covers Cloud to cloud distance, Lonboard covers GeoArrow binary transfer.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which CloudCompare and Lonboard actually diverge.

Attributes where CloudCompare and Lonboard differ
AttributeCloudCompareLonboard
PlatformsWindows, macOS, LinuxLinux, macOS, Windows
CategoryCADMaps

Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in CloudCompare

  • Cloud to cloud distance
  • Cloud to mesh distance
  • Registration
  • Segmentation and cleaning
  • Plugin architecture
  • Format support
  • Command line mode

Only in Lonboard

  • GeoArrow binary transfer
  • GeoPandas input
  • deck.gl layers
  • Jupyter widget
  • Large dataset handling
  • Styling by attribute
  • Open source licence

What people use each for

The jobs each tool is most often brought in to do.

CloudCompare

  • A monitoring engineer comparing quarterly laser scans of a retaining wall to quantify movement without buying a proprietary deformation packagenot Lonboard
  • A heritage team registering dozens of terrestrial scans of a building into a single cloud before meshingnot Lonboard
  • A geomorphologist measuring erosion between two drone-derived surfaces of a river banknot Lonboard
  • A survey technician cleaning and subsampling a scan before delivering it to a client whose software cannot handle the full densitynot Lonboard

Lonboard

  • An analyst exploring a national road or parcel dataset in a notebook where pydeck or ipyleaflet becomes unusable at that sizenot CloudCompare
  • A researcher publishing a reproducible analysis where the visualisation must run from the same script as the processingnot CloudCompare
  • A data scientist joining spatial data to model outputs in pandas and needing to see the result immediately without exporting to a GISnot CloudCompare
  • A team building an internal analysis pipeline on GeoParquet that wants rendering without a serialisation step in the middlenot CloudCompare

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

CloudCompare

  • The project is administered by its creator in his spare time while he holds a full-time job elsewhere, so an organisation building a monitoring programme on it depends on one person with no obligation to continue
  • There is no commercial support contract from anyone, so a defect that blocks a deliverable is resolved by a GitHub issue and community goodwill rather than by an agreement
  • Processing is single machine and memory bound, so very large aerial lidar collections must be tiled manually and large jobs are limited by the workstation rather than scaled out
  • The interface is unforgiving and organised around the underlying data structures rather than around tasks, so competent surveyors routinely take weeks to become productive
  • Plugins vary widely in maintenance, and several useful ones originated in research projects that have since ended, so a workflow built around a specific plugin can break at the next release

Lonboard

  • It is a notebook visualisation library, not a mapping application, so there is no editing, no layout, no map export for print and no sharing beyond distributing the notebook or an HTML file
  • Maintenance sits with Development Seed as an open source side output of a consultancy, so roadmap priorities follow client projects and there is no support contract to buy
  • Layer coverage is a subset of deck.gl, so an analyst needing a less common layer type has to drop to pydeck or write JavaScript rather than staying in Python
  • It expects data already in GeoPandas or Arrow form, which means the performance benefit depends on the rest of your pipeline being Arrow-friendly; reading a large Shapefile is still the slow step
  • Rendering happens in the browser, so very large datasets are ultimately limited by the client machine's memory and GPU rather than by the server, and a laptop will still fail on data a workstation handles

Pricing, plan by plan

CloudCompare

Free
  • CloudCompareFree
    • GNU General Public Licence
    • No licence fee and no usage limits
    • No commercial support contract exists

Lonboard

Free
  • LonboardFree
    • Open source, no licence fee
    • No usage limits
    • Installed from PyPI or conda

Which should you pick?

Choose CloudCompare if

  • You need cloud to cloud distance.
  • You want to start without paying.
  • You work on Windows, macOS, Linux.
  • You also want cloud to mesh distance.
CloudCompare review

Choose Lonboard if

  • You need geoarrow binary transfer.
  • You want to start without paying.
  • You work on Linux, macOS, Windows.
  • You also want geopandas input.
Lonboard review

Questions people ask

Is CloudCompare or Lonboard better?
Neither clearly leads. CloudCompare starts at Free and Lonboard at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, CloudCompare or Lonboard?
CloudCompare starts at Free and Lonboard at Free.
Does CloudCompare or Lonboard run on more platforms?
CloudCompare runs on Windows, macOS, Linux. Lonboard runs on Linux, macOS, Windows.
Can I use CloudCompare for free?
Both have a free tier, so you can try either at no cost before committing.
What is CloudCompare best used for?
CloudCompare is most often used for a monitoring engineer comparing quarterly laser scans of a retaining wall to quantify movement without buying a proprietary deformation package, a heritage team registering dozens of terrestrial scans of a building into a single cloud before meshing, a geomorphologist measuring erosion between two drone-derived surfaces of a river bank, a survey technician cleaning and subsampling a scan before delivering it to a client whose software cannot handle the full density. Of those, a monitoring engineer comparing quarterly laser scans of a retaining wall to quantify movement without buying a proprietary deformation package and a heritage team registering dozens of terrestrial scans of a building into a single cloud before meshing are not what Lonboard is typically brought in for.
What can CloudCompare do that Lonboard cannot?
CloudCompare covers Cloud to cloud distance, Cloud to mesh distance, Registration, Segmentation and cleaning. Lonboard covers GeoArrow binary transfer, GeoPandas input, deck.gl layers, Jupyter widget.

Answered from the vendors’ own pages

CloudCompare: Who maintains CloudCompare?

Daniel Girardeau-Montaut, its creator, administers it in his own time alongside a full-time engineering job, with contributions from a community of users and research groups.

Lonboard: Why not just use pydeck?

pydeck serialises geometry to GeoJSON to reach the browser. Lonboard uses a binary GeoArrow pipeline, which is the reason it handles far larger datasets in the same notebook.

CloudCompare: Can I buy support?

No. There is no vendor and no commercial support offering. Some geospatial consultancies know it well and can be hired, but they are not contracted to support the software itself.

Lonboard: Who maintains it?

Development Seed, a geospatial engineering consultancy, as an open source project. There is no commercial support offering.

CloudCompare: Is it suitable for commercial deliverables?

It is widely used for them. The licence permits it and the algorithms are well regarded. The risk is operational, not legal: no support and no roadmap commitment.

Lonboard: Does it work outside Jupyter?

It is built as a Jupyter widget. Exporting to standalone HTML is possible, but the intended environment is a notebook.

CloudCompare: Can it handle a full aerial lidar survey?

Not in one piece. It is memory bound on a single machine, so large collections need tiling or a dedicated lidar pipeline such as PDAL.

Lonboard: Is it free for commercial use?

Yes, it is open source with no licence fee.

Share

Related pages

More on CloudCompare

More on Lonboard

Keep looking

Other head to heads