Credits are the currency used across ArcGIS and are consumed for specific transactions and types of storage such as storing features, performing analytics, and using premium content. Any ArcGIS software that interacts with ArcGIS Online such as ArcGIS Enterprise, ArcGIS Pro, Insights for ArcGIS, or Collector for ArcGIS can use credits. Most of what you do in ArcGIS Online does not require credits, for example, using Living Atlas basemaps and imagery, exporting data, and performing single address or place searches. In many cases, credit-consuming activities carry a relatively low cost. For example, it costs less than 5 credits to enrich ZIP Code boundaries in Detroit, Michigan, with four variables of population and income data, or geocode 125 addresses, or store 2 GB of map tile data.
The following tools do not consume credits when run in ArcGIS Online:
Managing credit expenditures is an important component of administering your organization. ArcGIS Online provides administrators several strategies for maintaining a well-balanced credit budget. One strategy is to configure and assign custom roles with only the privileges your members need. Another strategy is to configure credit budgets that assign a flexible allocation of credits to some or all organization members or set a default allocation for new members.
Another budgeting strategy is to estimate how many credits you will need to perform a specific credit-consuming activity. To help you estimate costs, each analysis tool in Map Viewer includes a credit estimator so you can view how many credits a specific set of analytic operations will cost. You can also monitor credit usage through credit utilization dashboards on item pages and the status page. The status page provides an interactive breakdown of where credits have been used over time and which members have consumed them so you can make strategic adjustments to remove unused content or update member roles to better control access across the platform. Much like reviewing a monthly utility bill, monitoring credit usage is a way of knowing how the software is being used and predicting how many credits you will need for an extended period.
Before running an analysis tool in ArcGIS Online, you can use the credit estimator to calculate the expected number of credits that will be used. If your organization has enabled credit budgeting and the expected number of credits exceeds the number of credits allocated to you, ArcGIS Online displays an error message.
Credit consumption is based on the number of input features, except when running tools that use the Network Analysis privilege. When network analysis is performed, the estimate is based on the inputs, but credits are deducted based on the results. Therefore, the estimated credit consumption may be higher than the actual number of credits deducted when the tool is run. If you are using tools with network analysis capabilities, you may need your administrator to increase the number of credits assigned to your account before your analysis can be run. Analysis tools that use the Network Analysis privilege include the following:
- Summarize Nearby (requires the Network Analysis privilege only when travel modes are used)
- Choose Best Facilities
- Enrich Layer (requires the Network Analysis privilege only when travel modes are used)
- Create Drive-Time Areas
- Find Nearest (requires the Network Analysis privilege only when travel modes are used)
- Plan Routes
- Connect Origins to Destinations
Default administrators in the organization will be notified when 75 percent and 100 percent of their credits have been used and when a member has used 100 percent of their credit allocation limit. If your organization uses all of its credits, the subscription may be suspended or restricted, or go into a negative balance, depending on the subscription type. Subscriptions can be reactivated by purchasing additional credits. While an account is suspended, access to services and other items is temporarily unavailable, but the content is not deleted or removed from the system. With a restricted account, access to premium content and functionality is limited, but the account remains usable.
Any unused credits included with your annual subscription expire at the end of the subscription period. Additional credits that are purchased expire after two years.
Credits by capability
Use the table below to estimate how many credits you will need to perform specific transactions or store data.
|Capability||Example of where used||Credits used|
Feature storage, excluding feature attachments and feature collections
Store a hosted feature layer
2.4 credits per 10 MB stored per month, calculated hourly
Storage of all content, excluding hosted feature layers
Store published vector tile layers from ArcGIS Pro
Store scene layer packages from ArcGIS Pro
1.2 credits per 1 GB stored per month
Match addresses when publishing spreadsheets (such as CSV or Excel files) as hosted feature layers using ArcGIS World Geocoding Service or a view of this locator
40 credits per 1,000 geocodes
0.5 credits per drive-time
Closest Facility Routes
0.5 credits per closest facilities route
1 credit per vehicle route
10 credits per 1,000 attributes (data variables multiplied by total feature records)
0.005 credits per simple route
Directions with Optimize order
0.5 credits per optimized route
0.1 credit per allocated demand point
Origin Destination Cost Matrix
Generate Origin Destination Cost Matrix in ArcGIS Pro and ArcMap
0.0005 credits per input origin and destination pair
Join Features does not consume credits if you choose the option to create results as a hosted feature layer view.
Search businesses and facilities in Business Analyst Web App
10 credits per 1,000 records
Demographic Maps and Layers
Pan Living Atlas Tapestry layer in map
10 credits per 1,000 map requests (pan, zoom, and identify)
View infographic in ArcGIS Maps for Office
10 credits per 1,000 views
Generate feature reports in Survey123 for ArcGIS
2.5 credits per report
Run reports in Business Analyst Web App
10 credits per report
1 credit per 10,000 tiles generated
Scene Layer Generation From Features
1 credit per 1,000 textured multipatch features
1 credit per 5,000 untextured multipatch features or point features