Maps · head to head
ArcGIS Field Maps vs WhiteboxTools

ArcGIS Field Maps
Maps
Esri field data collection that cannot be bought on its own, only with an ArcGIS user type
- From
- On request
- Rated
- -

WhiteboxTools
Maps
Open source geospatial analysis engine with several hundred raster, LiDAR and hydrological tools
- From
- Free
- Rated
- -
The short version
- Only WhiteboxTools has a free tier, so it costs nothing to try first.
- Each has a real cost: ArcGIS Field Maps field Maps has no price of its own, so a project budget built from the product page misses the Creator seats, the Mobile Worker seats and the ArcGIS Online credits or Enterprise infrastructure that actually cost money; WhiteboxTools there is no vendor and no commercial support contract, so an organisation whose regulatory or client obligations require an answerable supplier cannot use it for that work no matter how good the algorithms are.
- They diverge on capability: ArcGIS Field Maps covers Offline map areas, WhiteboxTools covers Hydrological analysis.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which ArcGIS Field Maps and WhiteboxTools actually diverge.
| Attribute | ArcGIS Field Maps | WhiteboxTools |
|---|---|---|
| Starting price | On request | Free |
| Pricing model | Included with an ArcGIS user type licence | Open source, no licence fee |
| Free tier | No | Yes |
| Platforms | iOS, Android, Web | Windows, macOS, Linux |
Identical on both: user rating (Not yet rated), category (Maps).
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 ArcGIS Field Maps
- Offline map areas
- Smart forms
- High-accuracy GNSS
- Location sharing
- Assignment dispatch
- Indoor positioning
- Direct editing of authoritative data
Only in WhiteboxTools
- Hydrological analysis
- LiDAR processing
- Terrain derivatives
- Raster analysis
- Image processing
- Python and R front ends
- QGIS plugin
- MIT licence
What people use each for
The jobs each tool is most often brought in to do.
ArcGIS Field Maps
- A water utility whose inspectors update the same asset feature service the office GIS runs on, rather than filling in forms that someone re-keysnot WhiteboxTools
- A county carrying out a sign inventory where crews work in areas without mobile coverage and need offline maps that sync laternot WhiteboxTools
- An environmental team needing sub-metre positions from an external GNSS receiver recorded directly against the authoritative datasetnot WhiteboxTools
- An organisation consolidating from Collector, Explorer, Tracker and Workforce onto a single app after Esri retired themnot WhiteboxTools
WhiteboxTools
- A hydrologist who needs depression breaching rather than filling on a large DEM, because filling destroys the drainage structure the model depends onnot ArcGIS Field Maps
- A forestry or environmental team processing airborne LiDAR into canopy height and terrain models without buying a point cloud licence per analystnot ArcGIS Field Maps
- A GIS developer embedding terrain analysis into a commercial product, where the MIT licence avoids the copyleft obligations of GRASS or SAGAnot ArcGIS Field Maps
- A university teaching geomorphometry where every student needs the full toolset on their own laptop at zero costnot ArcGIS Field Maps
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
ArcGIS Field Maps
- Field Maps has no price of its own, so a project budget built from the product page misses the Creator seats, the Mobile Worker seats and the ArcGIS Online credits or Enterprise infrastructure that actually cost money
- It only works against Esri feature services, so an organisation whose data is in PostGIS or a database without an ArcGIS layer must publish through Esri first, which is a platform decision rather than an app choice
- Named user licensing means occasional or seasonal field staff still consume a full annual seat, and organisations with a large pool of infrequent collectors pay for capacity they use a few weeks a year
- As a forms tool alone it is more rigid and more expensive than dedicated mobile forms products, so its value collapses if you are not already committed to ArcGIS
- The consolidation of four apps into one changed established workflows, and organisations that had built processes around Collector or Workforce have had to rework them on Esri's timetable rather than their own
WhiteboxTools
- There is no vendor and no commercial support contract, so an organisation whose regulatory or client obligations require an answerable supplier cannot use it for that work no matter how good the algorithms are.
- Maintenance depends on a single academic research group and effectively on one professor, which is a real continuity risk for anything embedded in a production pipeline for a decade.
- It is command line first; the QGIS plugin and Python bindings help, but analysts who expect a graphical workflow with previews and undo find it unforgiving.
- Documentation is a reference manual rather than a set of worked workflows, so knowing which of 450 tools to chain for a given problem requires domain knowledge the software does not supply.
- Naming and behaviour overlap confusingly with the older Whitebox GAT, a separate GPL-licensed desktop GIS from the same group, and adopters regularly install or cite the wrong one.
Pricing, plan by plan
ArcGIS Field Maps
On request- Mobile Worker user type$undefined/year
- Field editing in Field Maps included with no additional purchase
- Cannot author maps; requires a Creator seat elsewhere in the organisation
- Priced per named user per year
- Creator user type$undefined/year
- Required to author and publish the maps that field workers use
- At least one Creator needed before Field Maps can be deployed
- Includes Field Maps editing as well as authoring
- ArcGIS Enterprise deployment$undefined/year
- Field Maps against self-hosted ArcGIS Enterprise instead of ArcGIS Online
- Server licensing and infrastructure priced separately
- Quoted through Esri or a distributor
WhiteboxTools
Free- WhiteboxTools open coreFree
- MIT licence
- Over 450 geospatial tools
- Python, R and QGIS front ends
Which should you pick?
Choose ArcGIS Field Maps if
- You need offline map areas.
- You work on iOS, Android, Web.
- You also want smart forms.
Choose WhiteboxTools if
- You need hydrological analysis.
- You want to start without paying.
- You work on Windows, macOS, Linux.
- You also want lidar processing.
Questions people ask
- Is ArcGIS Field Maps or WhiteboxTools better?
- Neither clearly leads. ArcGIS Field Maps starts at On request and WhiteboxTools at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, ArcGIS Field Maps or WhiteboxTools?
- WhiteboxTools has a free tier; the other does not. Paid plans start at On request for ArcGIS Field Maps and Free for WhiteboxTools.
- Does ArcGIS Field Maps or WhiteboxTools run on more platforms?
- ArcGIS Field Maps runs on iOS, Android, Web. WhiteboxTools runs on Windows, macOS, Linux.
- Can I use WhiteboxTools for free?
- Yes. WhiteboxTools has a free tier, so you can try it without paying. ArcGIS Field Maps starts at On request.
- What is ArcGIS Field Maps best used for?
- ArcGIS Field Maps is most often used for a water utility whose inspectors update the same asset feature service the office gis runs on, rather than filling in forms that someone re-keys, a county carrying out a sign inventory where crews work in areas without mobile coverage and need offline maps that sync later, an environmental team needing sub-metre positions from an external gnss receiver recorded directly against the authoritative dataset, an organisation consolidating from collector, explorer, tracker and workforce onto a single app after esri retired them. Of those, a water utility whose inspectors update the same asset feature service the office gis runs on, rather than filling in forms that someone re-keys and a county carrying out a sign inventory where crews work in areas without mobile coverage and need offline maps that sync later are not what WhiteboxTools is typically brought in for.
- What can ArcGIS Field Maps do that WhiteboxTools cannot?
- ArcGIS Field Maps covers Offline map areas, Smart forms, High-accuracy GNSS, Location sharing. WhiteboxTools covers Hydrological analysis, LiDAR processing, Terrain derivatives, Raster analysis.
Answered from the vendors’ own pages
ArcGIS Field Maps: Can I buy Field Maps on its own?
No. It is included with the Mobile Worker, Creator and GIS Professional user types, and you need at least one Creator in the organisation to author maps.
WhiteboxTools: Is WhiteboxTools free for commercial use?
Yes. It is MIT licensed, which permits commercial use and embedding without a copyleft obligation.
ArcGIS Field Maps: What replaced Collector and Workforce?
Field Maps. Esri merged Collector, Explorer, Tracker and Workforce into it and retired the separate apps.
WhiteboxTools: Is there paid support?
No general commercial support contract is offered. Support is GitHub issues and community forums. Budget internal expertise instead.
ArcGIS Field Maps: Does it work offline?
Yes. Map areas are downloaded in advance and edits synchronise when connectivity returns.
WhiteboxTools: Who maintains it?
Professor John Lindsay and the Geomorphometry and Hydrogeomatics Research Group at the University of Guelph, Canada.
ArcGIS Field Maps: Can it write to a non-Esri database?
Not directly. The data must be published as an ArcGIS feature service, which may sit over an enterprise geodatabase you already run.
WhiteboxTools: How is it different from Whitebox GAT?
Whitebox GAT is an older GPL-licensed desktop GIS from the same group. WhiteboxTools is the newer Rust command line engine with a permissive licence. They are not the same product.
WhiteboxTools: Can I use it from QGIS?
Yes, through a plugin, and also from Python and R.
Related pages
More on ArcGIS Field Maps
More on WhiteboxTools
Other head to heads
- ArcGIS Field Maps vs QGIS
- ArcGIS Field Maps vs SW Maps
- ArcGIS Field Maps vs Felt
- ArcGIS Field Maps vs CARTO
- ArcGIS Field Maps vs Global Mapper
- ArcGIS Field Maps vs GRASS GIS
- ArcGIS Field Maps vs Foursquare Spatial Studio
- ArcGIS Field Maps vs Trailforks
- ArcGIS Field Maps vs onX Maps
- ArcGIS Field Maps vs Mapbox
- ArcGIS Field Maps vs Google Maps Platform
- ArcGIS Field Maps vs Leaflet
- ArcGIS Field Maps vs Bing Maps
- ArcGIS Field Maps vs Cesium ion
- ArcGIS Field Maps vs Citymapper
- ArcGIS Field Maps vs Gaia GPS
- ArcGIS Field Maps vs GraphHopper
- ArcGIS Field Maps vs Potree
- ArcGIS Field Maps vs Esri ArcGIS
- ArcGIS Field Maps vs SAGA GIS
- ArcGIS Field Maps vs Lonboard
- ArcGIS Field Maps vs CesiumJS
- ArcGIS Field Maps vs Kepler.gl
- ArcGIS Field Maps vs OpenLayers
- ArcGIS Field Maps vs deck.gl
- ArcGIS Field Maps vs Mappedin
- ArcGIS Field Maps vs MapTiler
- ArcGIS Field Maps vs Agisoft Metashape
- WhiteboxTools vs QGIS
- WhiteboxTools vs SW Maps
- WhiteboxTools vs Felt
- WhiteboxTools vs CARTO
- WhiteboxTools vs Global Mapper
- WhiteboxTools vs GRASS GIS
- WhiteboxTools vs Foursquare Spatial Studio
- WhiteboxTools vs Trailforks
- WhiteboxTools vs onX Maps
- WhiteboxTools vs Mapbox
- WhiteboxTools vs Google Maps Platform
- WhiteboxTools vs Leaflet
- WhiteboxTools vs Bing Maps
- WhiteboxTools vs Cesium ion
- WhiteboxTools vs Citymapper
- WhiteboxTools vs Gaia GPS
- WhiteboxTools vs GraphHopper
- WhiteboxTools vs Potree
- WhiteboxTools vs Esri ArcGIS
- WhiteboxTools vs SAGA GIS
- WhiteboxTools vs Lonboard
- WhiteboxTools vs CesiumJS
- WhiteboxTools vs Kepler.gl
- WhiteboxTools vs OpenLayers
- WhiteboxTools vs deck.gl
- WhiteboxTools vs Mappedin
- WhiteboxTools vs MapTiler
- WhiteboxTools vs Agisoft Metashape
