Maps · head to head
CARTO vs ArcGIS Field Maps

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
- -
The short version
- Each has a real cost: CARTO no prices are published; the committed tiers are all quote-only; 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
- They diverge on capability: CARTO covers Spatial Analysis, ArcGIS Field Maps covers Offline map areas.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which CARTO and ArcGIS Field Maps actually diverge.
| Attribute | CARTO | ArcGIS Field Maps |
|---|---|---|
| Pricing model | quote | Included with an ArcGIS user type licence |
| Platforms | Web | iOS, Android, Web |
| Founded | 2012 | Unknown |
Identical on both: starting price (On request), free tier (No), 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 CARTO
- Spatial Analysis
- Interactive Maps
- Data Observatory
- Workflows
- APIs
- Snowflake
- BigQuery
- PostgreSQL
Only in ArcGIS Field Maps
- Offline map areas
- Smart forms
- High-accuracy GNSS
- Location sharing
- Assignment dispatch
- Indoor positioning
- Direct editing of authoritative data
What people use each for
The jobs each tool is most often brought in to do.
CARTO
- Spatial analysis over data already in a cloud warehousenot ArcGIS Field Maps
- Building interactive maps and location dashboardsnot ArcGIS Field Maps
- Geocoding and routing through location data servicesnot ArcGIS Field Maps
- Site selection and territory planningnot ArcGIS Field Maps
- Self-hosted geospatial analytics for regulated environmentsnot ArcGIS Field Maps
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 CARTO
- A county carrying out a sign inventory where crews work in areas without mobile coverage and need offline maps that sync laternot CARTO
- An environmental team needing sub-metre positions from an external GNSS receiver recorded directly against the authoritative datasetnot CARTO
- An organisation consolidating from Collector, Explorer, Tracker and Workforce onto a single app after Esri retired themnot CARTO
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
CARTO
- No prices are published; the committed tiers are all quote-only
- Metered on four separate axes: workflow runs, map loads, API calls and location data service operations
- API access and tokens are limited on pay-as-you-go and unlimited only from the Strategic tier
- Self-hosting is available on Enterprise and included only on the Custom tier
- The 14 day trial explicitly forbids production 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
Pricing, plan by plan
CARTO
On request- Pay As You Go$null/mo
- Metered, capped location data services
- Limited API access and tokens
- Standard support
- Enterprise$null/mo
- Limited location data services with quota
- Limited API access and tokens
- Standard or Premium support
- Strategic$null/mo
- Unlimited API access and tokens
- Premium or Elite support
- Custom branding
- Custom$null/mo
- Up to unlimited location data services
- Unlimited API access and tokens
- Elite support
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
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.
Questions people ask
- Is CARTO or ArcGIS Field Maps better?
- Neither clearly leads. CARTO starts at On request and ArcGIS Field Maps at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, CARTO or ArcGIS Field Maps?
- CARTO starts at On request and ArcGIS Field Maps at On request.
- Does CARTO or ArcGIS Field Maps run on more platforms?
- CARTO runs on Web. ArcGIS Field Maps runs on iOS, Android, Web.
- What is CARTO best used for?
- CARTO is most often used for spatial analysis over data already in a cloud warehouse, building interactive maps and location dashboards, geocoding and routing through location data services, site selection and territory planning. Of those, spatial analysis over data already in a cloud warehouse and building interactive maps and location dashboards are not what ArcGIS Field Maps is typically brought in for.
- What can CARTO do that ArcGIS Field Maps cannot?
- CARTO covers Spatial Analysis, Interactive Maps, Data Observatory, Workflows. ArcGIS Field Maps covers Offline map areas, Smart forms, High-accuracy GNSS, Location sharing.
Answered from the vendors’ own pages
CARTO: What CARTO pricing tiers are available?
CARTO offers Pay As You Go (monthly, consumption-based), Enterprise (annual commitment with limited quotas), Strategic (annual with unlimited API access), and Custom (annual with full services for large enterprises). Enterprise and higher require contacting sales.
SourceArcGIS 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.
CARTO: Does CARTO have a free version?
CARTO does not advertise a free tier. The Pay As You Go plan requires monthly payments based on consumption with capped services.
SourceArcGIS Field Maps: What replaced Collector and Workforce?
Field Maps. Esri merged Collector, Explorer, Tracker and Workforce into it and retired the separate apps.
CARTO: What is included in the CARTO Strategic plan?
Strategic tier includes unlimited API access and tokens, premium or elite support, custom branding, audit logs, and usage metrics. It requires an annual commitment and custom pricing quote.
SourceArcGIS Field Maps: Does it work offline?
Yes. Map areas are downloaded in advance and edits synchronise when connectivity returns.
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.
Related pages
More on ArcGIS Field Maps
Other head to heads
- CARTO vs Foursquare Spatial Studio
- CARTO vs Atlas.co
- CARTO vs Felt
- CARTO vs Mapbox
- CARTO vs HERE Technologies
- CARTO vs Google Maps Platform
- CARTO vs Apple Maps
- CARTO vs Leaflet
- CARTO vs Fused
- CARTO vs Lonboard
- CARTO vs Esri ArcGIS
- CARTO vs Global Mapper
- CARTO vs Navmii GPS
- CARTO vs Nominatim
- CARTO vs OpenLayers
- CARTO vs OpenRouteService
- CARTO vs OpenStreetMap
- CARTO vs OsmAnd
- CARTO vs QGIS
- CARTO vs SW Maps
- CARTO vs GRASS GIS
- CARTO vs Trailforks
- CARTO vs onX Maps
- CARTO vs Bing Maps
- CARTO vs Cesium ion
- CARTO vs Citymapper
- CARTO vs Gaia GPS
- CARTO vs GraphHopper
- ArcGIS Field Maps vs Foursquare Spatial Studio
- ArcGIS Field Maps vs Atlas.co
- ArcGIS Field Maps vs Felt
- ArcGIS Field Maps vs Mapbox
- ArcGIS Field Maps vs HERE Technologies
- ArcGIS Field Maps vs Google Maps Platform
- ArcGIS Field Maps vs Apple Maps
- ArcGIS Field Maps vs Leaflet
- ArcGIS Field Maps vs Fused
- ArcGIS Field Maps vs Lonboard
- ArcGIS Field Maps vs Esri ArcGIS
- ArcGIS Field Maps vs Global Mapper
- ArcGIS Field Maps vs Navmii GPS
- ArcGIS Field Maps vs Nominatim
- ArcGIS Field Maps vs OpenLayers
- ArcGIS Field Maps vs OpenRouteService
- ArcGIS Field Maps vs OpenStreetMap
- ArcGIS Field Maps vs OsmAnd
- ArcGIS Field Maps vs QGIS
- ArcGIS Field Maps vs SW Maps
- ArcGIS Field Maps vs GRASS GIS
- ArcGIS Field Maps vs Trailforks
- ArcGIS Field Maps vs onX Maps
- 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

