Libraries · head to head
Leafmap vs Potree

Leafmap
Libraries
Python package for interactive geospatial mapping and analysis inside Jupyter notebooks
- From
- Free
- Rated
- -

Potree
Maps
Open source WebGL viewer for publishing very large point clouds in a browser
- From
- Free
- Rated
- -
The short version
- Each has a real cost: Leafmap it is a Python library rather than an application, so there is nothing to buy, nothing to install for a non-technical colleague and no interface outside a notebook environment.; Potree there is no vendor, no support contract and no service level, so anything you build on Potree is your organisation’s responsibility to maintain when a browser update breaks rendering.
- They diverge on capability: Leafmap covers Multiple mapping backends, Potree covers Octree streaming.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Leafmap and Potree actually diverge.
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 Leafmap
- Multiple mapping backends
- Notebook interactivity
- Raster and COG support
- STAC catalogue access
- Earth Engine integration
- Basemap library
- Vector data handling
- Split map comparison
Only in Potree
- Octree streaming
- Large dataset rendering
- Measurement tools
- Clipping and profiles
- Annotations
- Attribute colouring
- PotreeDesktop
- Self-hosting
What people use each for
The jobs each tool is most often brought in to do.
Leafmap
- A remote sensing course where students need interactive maps without learning JavaScript or a desktop GISnot Potree
- A researcher exploring STAC-hosted satellite imagery inside a notebook before committing to a processing pipelinenot Potree
- An analyst producing a shareable interactive map from a GeoDataFrame in a handful of linesnot Potree
- A team prototyping a geospatial visualisation before deciding whether to build it properly in a web frameworknot Potree
Potree
- A drone survey firm delivering a point cloud to a client who has no desktop software, by publishing a browser viewer link instead of a 40 GB LAZ filenot Leafmap
- A heritage or archaeology project publishing a scanned site for public access without paying per-gigabyte hosting to a commercial platformnot Leafmap
- An engineering consultancy embedding a point cloud viewer inside its own client portal without licensing a commercial web viewernot Leafmap
- A university or research group that needs measurement and profiling in a shareable viewer for a dataset too large to emailnot Leafmap
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Leafmap
- It is a Python library rather than an application, so there is nothing to buy, nothing to install for a non-technical colleague and no interface outside a notebook environment.
- Maintenance rests largely on one academic maintainer with grant funding, which makes long-term continuity a real consideration for anything beyond research use.
- The API has moved quickly across releases, so notebooks written against an older version can break on upgrade, which undermines reproducibility in exactly the research settings where it is popular.
- It abstracts over several third-party backends, so a bug or a rendering limitation is often in ipyleaflet, folium or MapLibre rather than in Leafmap, and diagnosing it means understanding the layer underneath anyway.
- Large datasets rendered through notebook widgets become slow or unresponsive, so it does not scale to the data volumes a dedicated tiling service or desktop GIS handles comfortably.
Potree
- There is no vendor, no support contract and no service level, so anything you build on Potree is your organisation’s responsibility to maintain when a browser update breaks rendering.
- Conversion is a separate manual step with PotreeConverter, and building an automated publishing pipeline around it is engineering work the project does not provide.
- Rendering quality and performance depend on the client machine and WebGL support, so a client on a locked-down corporate laptop with poor graphics may see a viewer that stutters or fails outright.
- A WebGPU rewrite, Potree-Next, is in progress and is not a drop-in upgrade, so current integrations face an eventual migration with no vendor to manage it.
- There is no access control, user management or audit layer; anyone with the URL sees the data unless you build authentication around the static files yourself, which is a real problem for confidential sites.
Pricing, plan by plan
Leafmap
Free- LeafmapFree
- MIT licence
- Installed from PyPI or conda-forge
- No usage limits
Potree
Free- PotreeFree
- BSD-style open source licence
- Unlimited datasets and viewers
- Self-hosted on any static web server
Which should you pick?
Choose Leafmap if
- You need multiple mapping backends.
- You want to start without paying.
- You work on Linux, Windows, macOS.
- You also want notebook interactivity.
Choose Potree if
- You need octree streaming.
- You want to start without paying.
- You work on Web, Windows, macOS, Linux.
- You also want large dataset rendering.
Questions people ask
- Is Leafmap or Potree better?
- Neither clearly leads. Leafmap starts at Free and Potree at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Leafmap or Potree?
- Leafmap starts at Free and Potree at Free.
- Does Leafmap or Potree run on more platforms?
- Leafmap runs on Linux, Windows, macOS. Potree runs on Web, Windows, macOS, Linux.
- Can I use Leafmap for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Leafmap best used for?
- Leafmap is most often used for a remote sensing course where students need interactive maps without learning javascript or a desktop gis, a researcher exploring stac-hosted satellite imagery inside a notebook before committing to a processing pipeline, an analyst producing a shareable interactive map from a geodataframe in a handful of lines, a team prototyping a geospatial visualisation before deciding whether to build it properly in a web framework. Of those, a remote sensing course where students need interactive maps without learning javascript or a desktop gis and a researcher exploring stac-hosted satellite imagery inside a notebook before committing to a processing pipeline are not what Potree is typically brought in for.
- What can Leafmap do that Potree cannot?
- Leafmap covers Multiple mapping backends, Notebook interactivity, Raster and COG support, STAC catalogue access. Potree covers Octree streaming, Large dataset rendering, Measurement tools, Clipping and profiles.
Answered from the vendors’ own pages
Leafmap: Is Leafmap a product?
No. It is an MIT-licensed Python package installed from PyPI or conda-forge. There is nothing to purchase.
Potree: Does Potree cost anything?
No. It is open source and free. You supply the hosting, which for a static viewer is inexpensive.
Leafmap: Who maintains it?
Primarily Qiusheng Wu at the University of Tennessee, with community contributors, funded through research grants rather than sales.
Potree: Is there commercial support?
No. There is no vendor and no support contract. Support is GitHub issues and the community.
Leafmap: Can I buy support?
No commercial support offering exists. Help comes from GitHub issues and the community.
Potree: Who maintains it?
It originated at TU Wien and is maintained principally by Markus Schütz, with community contributions.
Leafmap: Is it suitable for a production web application?
It is not designed for that. Use it for analysis and prototyping, then build production maps on MapLibre, deck.gl or a hosted service.
Potree: Can it handle very large clouds?
Yes, hundreds of millions of points, because PotreeConverter builds a multi-resolution octree that streams only what is visible.
Potree: Is my data private?
Only if you make it so. Potree serves static files with no built-in authentication, so access control is entirely your responsibility.
Related pages
Other head to heads
- Leafmap vs PDAL
- Leafmap vs Libby
- Leafmap vs Hoopla
- Leafmap vs DSpace
- Leafmap vs Ant Design
- Leafmap vs daisyUI
- Leafmap vs Mantine
- Leafmap vs ArchivesSpace
- Leafmap vs CONTENTdm
- Leafmap vs Omeka
- Leafmap vs VuFind
- Leafmap vs CollectiveAccess
- Leafmap vs SirsiDynix Symphony
- Leafmap vs Vuetify
- Leafmap vs Archivematica
- Leafmap vs Axiell Collections
- Leafmap vs Base UI
- Leafmap vs WhiteboxTools
- Leafmap vs QGIS
- Leafmap vs Global Mapper
- Leafmap vs Agisoft Metashape
- Leafmap vs Lonboard
- Leafmap vs SAGA GIS
- Leafmap vs GRASS GIS
- Leafmap vs Leica Infinity
- Leafmap vs deck.gl
- Leafmap vs Felt
- Leafmap vs Ride with GPS
- Leafmap vs Kepler.gl
- Leafmap vs Trailforks
- Leafmap vs AllTrails
- Leafmap vs Bing Maps
- Leafmap vs Cesium ion
- Leafmap vs Citymapper
- Potree vs PDAL
- Potree vs Libby
- Potree vs Hoopla
- Potree vs DSpace
- Potree vs Ant Design
- Potree vs daisyUI
- Potree vs Mantine
- Potree vs ArchivesSpace
- Potree vs CONTENTdm
- Potree vs Omeka
- Potree vs VuFind
- Potree vs CollectiveAccess
- Potree vs SirsiDynix Symphony
- Potree vs Vuetify
- Potree vs Archivematica
- Potree vs Axiell Collections
- Potree vs Base UI
- Potree vs WhiteboxTools
- Potree vs QGIS
- Potree vs Global Mapper
- Potree vs Agisoft Metashape
- Potree vs Lonboard
- Potree vs SAGA GIS
- Potree vs GRASS GIS
- Potree vs Leica Infinity
- Potree vs deck.gl
- Potree vs Felt
- Potree vs Ride with GPS
- Potree vs Kepler.gl
- Potree vs Trailforks
- Potree vs AllTrails
- Potree vs Bing Maps
- Potree vs Cesium ion
- Potree vs Citymapper
