Mapbox Pricing: Cost Structure and Pricing Update 2025

The 2025 cost framework reports a usage-based model across mobile MAU, web map loads, API requests, and tileset hosting. It specifies clear monthly tier breakpoints for active users, web map loads, image and query APIs, and specialized tilesets to aid procurement and financial planning.

This analysis presents concise information for business teams evaluating maps and data services. It outlines tier thresholds for MAU and web loads, API request families, and tileset processing and hosting metrics.

Support commitments and commercial licenses are summarized so stakeholders can match response SLAs and seat-based fees with operational risk tolerance. The section equips decision-makers with actionable facts to forecast costs and align user and map demand with appropriate tiers.

Key Takeaways

2025 billing is usage-metered across mobile, web, and API volumes.
Tiers define clear thresholds for MAU, map loads, API calls, and tilesets.
Support plans differ by response times and escalation paths.
Commercial licenses add annual and per-seat costs for regulated use cases.
Accurate data on map loads and users is essential for cost control.

2025 overview: how Mapbox pricing works for apps, APIs, and services

Chargeable events in 2025 are tied directly to active users, web map loads, and individual api requests. The model separates mobile SDK billing by MAU tiers and web billing by map loads and seats.

Usage-based model across web, mobile, and data services

The system meters four core vectors: mobile monthly active users, web map loads, api request volume, and tileset processing/hosting. Each MAU and map load includes unlimited vector and raster tile retrieval, which reduces incremental tile costs.

Key terms: monthly active users, map loads, requests, tiles, and seats

Monthly active users refer to unique mobile devices in a 30-day window. A map load captures an initial web map render. Requests apply to endpoints like Static Images or Feature Query.

Meter	Primary unit	Typical breakpoints
Mobile SDKs	MAU	25k, 125k, 250k, 1.25M
Web maps	Map loads / Seats	50k, 100k, 200k, 1M
APIs	Per request	Static Images, Feature Query, Vector/Raster tiles
Tilesets	Processed MB / CUs / Hosting days	Per MB & 0.3–5 CUs; hosted per day

Support tiers set response SLAs and escalation paths for incidents.
Documentation and account setup affect implementation speed and cost control.
Address- and location-heavy applications should forecast geocoding alongside map demand.

Mapbox pricing

Free access tiers permit technical validation of maps and core data flows before committing to paid plans. These tiers cover web map loads, mobile MAU, and API request families so teams can test typical interactions.

Free tier considerations and forecasting paid use

Free tier access helps customers simulate traffic and confirm feature fit. Forecasts must include expected user growth, burst patterns, and requests per session.

Model per-user behavior: initial loads, pans/zooms, and downstream API calls that generate requests and tile retrieval.
Attribute consumption by feature: geocoding for address and addresses lookups, static images, feature queries, and tiles.
Consolidate accounts for clear billing, but avoid shared credentials that hide per-application usage.
Use caching or permanent storage where allowed to lower repeated requests and smooth costs beyond free tier limits.
Set internal alerts for tier thresholds to prevent surprise escalations mid-month. Without a paid support plan, only Accounts & Billing tickets may be opened via the designated form; technical support requires a plan or self-serve resources.

Scope	Free tier role	Forecast focus
Mobile MAU	Test device counts and session patterns	Growth, churn, peak-day bursts
Web maps	Validate map loads and seating	Loads per user, styling complexity
APIs & Data	Exercise geocoding and image requests	Requests per workflow, cacheability

Mobile SDKs pricing by Monthly Active Users (MAU)

Mobile license tiers are based on active users and simplify cost modeling for in-app maps. The model charges by unique devices that use the SDK during a 30-day billing window. This approach converts ephemeral request counts into a predictable subscription metric for procurement.

Definition and included tile access

A monthly active user is recorded when any mobile app call reaches the service within the billing period. Each counted user may request unlimited vector and raster tile resources, so rendering frequency does not raise per-user fees.

MAU breakpoints and operational notes

Breakpoints align to adoption phases: 25k, 125k, 250k, and 1.25M MAU tiers. Teams move between tiers as cohorts grow.

“MAU billing favors applications with frequent sessions per user, since additional map renders do not change the billed user count.”

Instrumentation must tie device identifiers to account usage to avoid double-counting across apps.
Performance relies on on-device rendering and efficient network usage; tile calls do not affect the MAU fee.
Plan implementation with tier migration paths and content delivery strategies like preloading to control user experience without adding request costs.

Metric	Definition	Key breakpoints
MAU	Unique mobile devices active in 30 days	25k / 125k / 250k / 1.25M
Tile access	Vector & raster per MAU	Unlimited per counted user
Implementation focus	Instrumentation, rendering, CDN	Accurate counts & performance

Web maps pricing: Map Loads and Map Seats for web applications

Web map billing is driven by initialization events in client pages. A map load is recorded each time the Map object initializes in GL JS. That load grants unlimited access to Vector Tiles and Raster Tiles APIs for the session.

What counts as a map load in GL JS

A web map load occurs when the Map object is created on a page or in a single-page app. Each initialization is one counted load, regardless of pan, zoom, or tile intensity during that session.

Monthly load tiers and operational notes

Monthly tiers scale at 50k, 100k, 200k, and 1M loads. Teams should model sessions and multi-map pages to avoid unexpected tier migration.

Metric	Definition	Implication
Map load	GL JS Map initialization	Counts versus monthly tier
Tile access	Vector & raster included per load	No per-tile charge within session
Other requests	Feature query, geocoding, Static Images	Billed separately; include in cost models

Performance and styling considerations

Optimize style weight, sprite use, and data-driven rules to improve perceived performance and reduce initialization delay. Use lazy initialization on multi-map pages and edge CDN caching for static assets.

Static Images API pricing

Prerendered map images are a cost-effective way to show location data on web pages and reports. A single Static Images API request returns a PNG rendered from a GL style at specified width and height.

Request definition and size parameters for PNG generation

Each request is billed per image. The caller specifies style, center or bounds, and pixel dimensions. Larger images increase bandwidth and cache impact but do not change the per-request charge.

Best practice: precompute coordinates for address or POI overlays to avoid extra geocoding at render time.

Monthly request tiers and use cases

Monthly tiers scale at 50k, 500k, 1M, and 5M requests. These breakpoints suit marketing pages, automated reports, and application previews where an interactive map is unnecessary.

Embed static PNGs in web or mobile layouts to control runtime costs and keep brand styling consistent.
Reuse templates and leverage CDN caching to reduce duplicate image generation.
For map-heavy pages, replace multiple live maps with a small set of images to lower map load counts.

“Static images offer predictable per-request costing and simplify scaling for report-driven workflows.”

Metric	Definition	Typical tiers
Per-request	PNG generated from GL style and dimensions	50k / 500k / 1M / 5M requests
Image size	Width × height in pixels; affects bandwidth and cache	Small (≤800px), Medium (800–1600px), Large (>1600px)
Embedding use	Marketing, reports, previews	Single images or templated batches for reuse

Feature querying and data access costs

Feature queries retrieve geographic features at a specific latitude and longitude from hosted vector tilesets. Each call returns targeted attributes and geometry for a single coordinate, which keeps transfer and compute minimal compared with full dataset downloads.

Feature query requests: definition and monthly tiers

A feature query request is billed per API call that queries one or more vector tilesets at a point. Monthly tiers are set at 100k, 500k, 1M, and 5M requests to match lightweight, high-frequency lookups.

Feature queries bill per request against hosted vector tilesets at a coordinate.
Tiers (100k–5M) suit applications needing targeted information without loading full datasets.
Provide bounding parameters and attribute filters to limit returned information and reduce latency.
Combine query calls with map state to avoid redundant requests during simple pans and zooms.
Address-heavy flows should batch geocoding then call feature queries for precise addresses and proximity checks.
Debounce interaction events and cache responses to lower per-request cost and improve user experience.

Metric	Definition	Typical tiers	Operational tip
Feature query	Single coordinate query of vector tiles	100k / 500k / 1M / 5M	Filter attributes; limit radius
Use cases	Address lookup, POI, proximity	Interactive apps, routing aids	Batch addresses, then query features
Cost control	Per-request billing	Scaled by tier	Debounce & cache on client

Vector and raster tiles pricing for maps

Tile requests form the backbone of rendered maps and drive much of monthly metering for client and server workflows. This section summarizes tiered meter points for vector, raster, and satellite imagery used in production map deployments.

Vector and raster tile tiers

Vector Tiles API monthly tile request tiers are 200k, 2M, 4M, and 20M. These tiers suit interactive clients that render styled vector layers on the fly.

Raster Tiles API follows the same breakpoints: 200k, 2M, 4M, and 20M. Raster tiles are appropriate where WebGL or complex styling is unavailable.

Satellite and imagery

Satellite and other raster tilesets use distinct tiers starting at 750k, then 2M, 4M, and 20M. Imagery bandwidth and cache behavior justify higher baseline thresholds.

“Each tile request is one element in a sequence required to render a slippy map; accurate modeling of those sequences reduces surprise costs.”

Each tile request counts as a unit toward the monthly tier; multiple tiles combine to render a single view.
When MAUs or loads include unlimited tile access, route workloads through the correct access paths to avoid double-counting.
Consolidate styles and sources to reduce duplicate tile pulls across similar views.
Model api request volumes for server-side rendering separately from client-driven tile fetches.

Tile type	Monthly tiers (requests)	Typical use
Vector tiles	200k / 2M / 4M / 20M	Interactive web and mobile maps; dynamic styling
Raster tiles	200k / 2M / 4M / 20M	Non-WebGL clients, static map layers
Satellite / imagery	750k / 2M / 4M / 20M	High-bandwidth imagery with CDN caching considerations

Weather layers and regional data pricing

Weather tiles influence map render workflows and peak demand during events like storms or heat waves. Japan weather layers are available as raster or vector tiles sourced from the Japan Meteorological Agency. Teams should treat these layers as an additive metered resource when forecasting costs.

Japan weather layers: monthly tile tiers

Monthly tiers for Japan weather tilesets are set at 100k, 4M, and 20M tile requests. These tiers apply whether tiles are delivered as raster imagery or vector overlays.

Weather tilesets support location-specific overlays for precipitation, temperature, and official alerts within maps.
Evaluate weather pricing alongside baseline map tiles to avoid budget drift when layers are enabled.
Plan api usage for route overlays where weather context alters ETAs and safety constraints.
Align caching strategy to expected demand peaks (for example, storm events) to mitigate sudden request spikes.
Segment rendering pipelines so general map tiles and weather layers are requested and cached separately to control scale.

Scope	Format	Monthly tiers (requests)	Operational note
Japan weather tiles	Raster / Vector	100k / 4M / 20M	Use CDN + cache for storm peaks
Overlay types	Precipitation, temp, alerts	Per-tile request	Prefer vector for styling, raster for imagery
Routing overlays	API calls	Billed per request	Batch and debounce for route recalculations

“Treat weather layers as distinct metered assets and architect caches to absorb short-lived spikes.”

Geofencing MAU-based pricing for mobile implementations

For mobile implementations, geofencing charges are based on unique monthly devices rather than per-event billing. This MAU model mirrors the mobile SDK bands and reduces volatility when many geofence events occur.

MAU tiers and operational guidance

Tiers: 25k, 125k, 250k, and 1.25M MAU align with core mobile SDK usage. Planners can consolidate budgets across location capabilities using the same bands.

Event aggregation: Each user may trigger multiple geofence events in the month without extra per-event fee.
Battery & performance: Applications that monitor location continuously should validate optimizations; MAU billing is unaffected by polling frequency.
Common features: Entry/exit and dwell detection map to notification workflows and business logic.
Response tuning: Client-side handling should debounce callbacks to avoid unnecessary network traffic and preserve UX.
Ancillary costs: Pair geofencing selectively with address and POI enrichment to control api usage.
Governance: Use api integrations for synchronized geofence definitions and audits when rules update at scale.
Visualization: Map overlays can show active zones without incurring incremental per-event charges.

“Geofencing on MAU terms converts event-heavy location workflows into predictable user-tier spend.”

Tilesets pricing: processing, compute units, and hosting days

Processing tilesets generates two separate cost vectors on invoices: processed megabytes and processed compute units (CUs). Teams should plan builds to control both line items and avoid unexpected month-end spikes.

Processing costs by megabytes and compute units

Tileset jobs charge by the volume of source data processed (MB) and by compute consumed (CUs). Monthly MB tiers are 10k, 50k, 100k, and 1M to match dataset growth.

Typical CU ranges and billing impact

Vector tileset jobs commonly consume between 0.3 and 5 CUs per job. Monthly CU tiers are 20, 1k, 5k, and 10k, which helps forecast compute time and monthly spend.

“Estimate both MB and CU usage for each build; small increases in CU per job compound across frequent pipelines.”

Hosting days metering: tilesets hosted per day across the month

Hosting is measured as Tileset Hosting Days: number of tilesets hosted multiplied by days hosted. For example, 3 tilesets hosted for 15 days equals 45 hosting days.

Hosting tiers: 25, 100, 1k, 10k, 20k hosted tilesets per month.
Keep unnecessary tilesets unpublished to limit accrual of hosting days.
Schedule build windows and promote artifacts to production to avoid parallel hosts across environments.
Include api gating in CI/CD and add code checks to prevent accidental reprocessing loops.
Optimize address-rich datasets via generalization to reduce compute and data transfer.

Meter	Units	Typical tiers
Processed data	Megabytes	10k / 50k / 100k / 1M
Compute	Compute Units (CUs)	20 / 1k / 5k / 10k
Hosting	Tileset hosting days	25 / 100 / 1k / 10k / 20k

Operational note: Product teams that publish many custom layers should enforce access controls and automation. Doing so reduces hosting day accrual and keeps product costs aligned with expected maps and data demand.

Commercial application licensing and enterprise considerations

Regulated use cases typically need a commercial application license with an annual fee plus monthly seats. This model applies when deployments require enhanced compliance, contractual SLAs, or embedded in-vehicle systems.

Required applications include in-vehicle software (ground, aerial, manned or unmanned), business intelligence and analytics products, sales performance management, cloud database integrations, and real estate systems. Customers should review whether their account workloads meet commercial triggers before procurement.

Annual fee plus monthly seat costs

The license combines a baseline annual commitment with per-seat monthly charges. This structure aligns vendor engagement with the deployment scale and compliance demands of the company’s products.

Scope: Seat counts, deployment model, and regulatory needs dictate final charges.
Engagement: Enterprise deals frequently include partner coordination and security reviews.
Procurement tips: Route legal and security questionnaires early to avoid delays.
Enablement: Plan SSO, environment segregation, and team access at contract setup.

When to contact Sales

Contact Sales for tailored product and partner solutions, custom SLAs, or core integration planning. Sales-led engagements help align commercial terms to business goals and technical constraints.

Use case	License element	Operational note
In-vehicle systems	Annual fee + monthly seats	Regulatory review; firmware integration
Analytics & BI	Annual fee + monthly seats	Data governance and deployment scale
Enterprise SaaS products	Annual fee + monthly seats	Partner coordination and contractual SLAs

Support plan pricing, SLAs, and response times

Support tiers translate operational risk into measurable response targets and access rights for customers. Teams should align incident handling and procurement to a chosen plan before production rollout.

Individual plan

The Individual plan costs $50/month. Technical tickets use the support portal while signed in with the subscribed account email.

First response: 3 business days for typical technical inquiries.

Business plan

The Business plan is $6,000/year. It offers measured SLAs for severity tiers and faster interventions.

P2 first response within 1 business day.
P3 first response within 3 business days.
4-hour emergency response during business hours (Mon–Fri, 6:00 a.m.–6:00 p.m. PT).
Includes tailored best practices and code review guidance for integrations with maps and api workflows.

Premium plan

Premium provides a dedicated Support Engineer, private collaboration spaces, and a 30-minute emergency response. Phone and video calls are available for critical incidents.

“Without a paid plan, only Accounts & Billing tickets can be opened via the Accounts & Billing form; technical questions should use documentation and community channels.”

Plan	Price	Key response targets
Individual	$50/month	3 business days first response; portal access via account email
Business	$6,000/year	P2: 1 business day; P3: 3 business days; 4-hour emergencies (business hours)
Premium	Custom	30-minute emergency response; dedicated engineer; private collaboration

Access methods vary by plan: portal login for Individual, portal or authorized email domains for Business and Premium. Companies should map severity to expected response times to meet user SLAs and reduce operational risk.

Geocoding pricing in 2025: temporary vs. permanent storage

Choosing between transient and persistent geocoding changes unit economics for address-heavy apps. The two models target different operational needs and cost profiles.

Cost tiers and when to use each

Temporary geocoding is priced at roughly $0.75–$0.45 per 1,000 requests. It suits one-off lookups and short-lived workflows where results are not stored.

Permanent geocoding runs about $5–$4 per 1,000 requests. That higher unit cost permits indefinite storage and reduces repeat-call volume for the same addresses.

“Investing in permanent storage often pays back when the same addresses are queried repeatedly across customer journeys.”

Features and implementation guidance

Autocomplete and proximity bias improve form completion and navigation flows.
Batch geocoding and structured input lower per-address overhead for large imports.
Use reverse geocoding for route confirmation and delivery validation.
Partition hot vs. cold address datasets and cache hot results to avoid repeated requests.
Employ confidence scoring and match codes to gate acceptance for delivery and KYC checks.

Model	Approx CPM	Best use
Temporary	$0.75–$0.45 / 1,000	Transient lookups, trial, free tier validation
Permanent	$5–$4 / 1,000	Stored address datasets, repeat queries, blended stacks
Implementation tips	—	Batch, cache, deduplicate, error-handle

How to estimate total cost: requests, users, and performance trade-offs

Estimating total cost requires combining measurable usage signals with performance assumptions. A concise forecast ties expected monthly active users and web map loads to per-session api requests and tileset operations. This approach reveals which vectors drive spend and where optimizations yield the largest savings.

Forecasting model: combine map loads, MAUs, and API request volumes

Build a model that multiplies platform users by session behavior. For example, multiply MAUs by average map loads per user, then add expected Static Images, Feature Query, and geocoding requests per session.

Segment by platform: mobile MAU vs. web map loads to isolate drivers.
Project growth curves and include seasonality or campaign spikes.
Include tilesets: processing MB, CUs per build (0.3–5 CUs typical), and hosting days as separate cost lines.
Budget for retries and error rates to provide 10–20% contingency on request volumes.

Optimization levers: caching, batch geocoding, tile reuse, and permanent storage

Performance and user experience directly affect request counts. Apply targeted optimizations to lower unit costs while preserving quality.

Use CDN and client caching to reduce repeated tile and image requests.
Batch geocoding or use permanent storage for hot address sets to cut repeated lookups.
Reuse tiles and consolidate styles to minimize duplicate pulls across views.
Time-phase feature rollouts so high-cost capabilities only deploy after cohort validation.

Validate forecasts against invoices. Reconcile modeled totals with actual line items—MAU, map loads, per-request APIs, tileset CUs and hosting days—to refine assumptions and governance controls.

Conclusion

Key action: A disciplined approach to metering and support alignment reduces operational risk when deploying map and location services at scale.

Mapbox’s 2025 pricing model ties costs to MAU, map loads, API requests, and tileset processing. Enterprises should pair forecasts with account governance, budget guards, and realtime observability to prevent surprises.

Choose a support plan that matches required response targets and escalation paths. Use permanent geocoding, caching, and phased rollouts for navigation and search-centric products to balance cost and reliability.

Finalize procurement assumptions around tileset hosting days and form-based billing contacts. Align product teams, partners, and company stakeholders on launch times and day-level SLAs to protect user experience and budgets.

FAQ

What is the overall cost structure and pricing update for 2025?

The 2025 cost structure uses a usage-based model across web, mobile, APIs, and data services. Charges are driven by metrics such as monthly active users (MAU), map loads, API requests, tiles served, geocoding requests, and hosting/compute for tilesets. Commercial licensing and enterprise agreements can add fixed annual fees and per-seat charges for in-vehicle or analytics deployments. Organizations should forecast by combining projected MAUs, map loads, and API volumes to estimate monthly spend.

How does the free tier work and how should a team forecast when they will pay?

The free tier covers low-volume development and proofs of concept, typically including a fixed number of map loads, MAUs, and API requests per month. To forecast transition to paid usage, track real traffic, feature usage (geocoding, tiles, static images), and growth rates. Apply optimization levers—caching, tile reuse, batch geocoding, and permanent storage—to delay or reduce paid consumption.

How are mobile SDKs billed by Monthly Active Users (MAU)?

Mobile SDK billing is MAU-based: a unique end user who opens the app and triggers map or location services within a 30-day window counts as one MAU. Each tier includes vector and raster tile access according to defined breakpoints (example tiers: 25k, 125k, 250k, 1.25M). Geofencing and location features billed by MAU align with these tiers.

What counts as a map load for web applications and how do map seats work?

A map load occurs when a map instance initializes and requests tiles or styles in a web session. Single-page app navigations that reinitialize the map may count as additional loads. Map seats provide licensed concurrent or named user access for administrative tools and customization; seat pricing is separate from loads and typically applies to web dashboards and team accounts.

How are web map monthly load tiers structured and what affects performance?

Monthly load tiers commonly include thresholds such as 50k, 100k, 200k, and 1M loads. Performance and user experience depend on real-time styling, vector tile complexity, request concurrency, and CDN/cache configuration. Optimizing style layers, reducing overdraw, and using tile prefetching improves responsiveness while lowering request volume.

How does the Static Images API get billed and what defines a request?

Static image billing is per request; request cost scales with image size and parameters (format, scale, overlays). Typical monthly tiers are 50k, 500k, 1M, and 5M requests. Use caching for frequently requested views and generate appropriately sized assets to contain costs.

What are feature query request costs and when should they be used?

Feature queries (vector feature lookups, reverse geocoding, proximity searches) are metered per request with tiers such as 100k, 500k, 1M, and 5M. Use cases include address lookup, proximity-based routing, and application data enrichment. Batch queries and local caching can reduce per-request charges for high-volume scenarios.

How are vector and raster tiles priced for maps and satellite layers?

Vector and raster tile APIs use request-tier pricing with example breakpoints at 200k, 2M, 4M, and 20M requests. Satellite and specialized raster tilesets may have dedicated tiers (for instance 750k, 2M, 4M, 20M) reflecting higher data costs. Tile compression, appropriate zoom-range limiting, and CDN configuration reduce total tile requests.

What are the billing considerations for weather layers and regional tilesets?

Weather and regional data (for example, Japan weather tilesets) are metered by tile requests with specific monthly tiers—sample thresholds include 100k, 4M, and 20M tiles. These layers can incur additional licensing or data-access surcharges depending on the provider and update cadence; evaluate the trade-off between regional fidelity and request volume.

How is geofencing charged for mobile implementations?

Geofencing often follows MAU-aligned tiers used by mobile SDKs (25k up to 1.25M). Charges reflect the number of active users whose devices participate in geofence evaluation. Reduce cost by offloading simple geofence checks to the client, using coarser geographies, or batching updates.

What costs are associated with tileset processing, compute units, and hosting days?

Tileset handling includes processing fees based on uploaded megabytes and compute units (CUs). Typical CU ranges depend on dataset complexity; higher CUs increase one-time processing and recurring billing. Hosting days meter tilesets hosted per day across the month; deleting unused tilesets reduces hosting charges. Monitor processing job size and run incremental updates to control compute usage.

When should an organization pursue commercial application licensing or enterprise agreements?

Organizations requiring in-vehicle integration, large-scale analytics, or custom SLAs should pursue commercial or enterprise licensing. These agreements commonly combine an annual base fee with per-seat or per-device charges and include options for dedicated support, on-prem or private data routing, and partner integrations. Contact Sales to negotiate volume discounts and bespoke terms.

What are the available support plans, SLAs, and typical response times?

Support tiers range from individual to premium. Example plans include an individual option (~/month) with a three-business-day first response; a business plan (~,000/year) offering faster P2 and P3 responses and four-hour emergency handling; and a premium plan with 30-minute emergency response and a dedicated engineer. Access methods include a technical portal, authorized email channels, and collaboration spaces for enterprise customers.

How is geocoding billed in 2025 and what feature sets are included?

Geocoding uses separate temporary and permanent storage pricing. Temporary geocoding CPMs range roughly

FAQ

What is the overall cost structure and pricing update for 2025?

How does the free tier work and how should a team forecast when they will pay?

How are mobile SDKs billed by Monthly Active Users (MAU)?

What counts as a map load for web applications and how do map seats work?

How are web map monthly load tiers structured and what affects performance?

How does the Static Images API get billed and what defines a request?

What are feature query request costs and when should they be used?

How are vector and raster tiles priced for maps and satellite layers?

What are the billing considerations for weather layers and regional tilesets?

How is geofencing charged for mobile implementations?

What costs are associated with tileset processing, compute units, and hosting days?

When should an organization pursue commercial application licensing or enterprise agreements?

What are the available support plans, SLAs, and typical response times?

Support tiers range from individual to premium. Example plans include an individual option (~$50/month) with a three-business-day first response; a business plan (~$6,000/year) offering faster P2 and P3 responses and four-hour emergency handling; and a premium plan with 30-minute emergency response and a dedicated engineer. Access methods include a technical portal, authorized email channels, and collaboration spaces for enterprise customers.

How is geocoding billed in 2025 and what feature sets are included?

Geocoding uses separate temporary and permanent storage pricing. Temporary geocoding CPMs range roughly $0.75–$0.45 per 1,000 requests; permanent geocoding (stored indexes or cached results) can cost roughly $5–$4 per 1,000 requests. Key features include autocomplete, batch geocoding, proximity bias, structured input, reverse geocoding, and address autofill. Strategies such as result caching and batch processing reduce per-request expense.

How should teams estimate total cost considering requests, users, and performance?

Build a forecasting model that combines projected MAUs, map loads, and API request volumes across features (tiles, geocoding, static images, feature queries). Incorporate performance trade-offs: higher fidelity and lower latency increase requests and cost. Apply optimization levers—caching, batch geocoding, tile reuse, permanent storage—to lower consumption and stabilize monthly spend.

.75–

FAQ

What is the overall cost structure and pricing update for 2025?

How does the free tier work and how should a team forecast when they will pay?

How are mobile SDKs billed by Monthly Active Users (MAU)?

What counts as a map load for web applications and how do map seats work?

How are web map monthly load tiers structured and what affects performance?

How does the Static Images API get billed and what defines a request?

What are feature query request costs and when should they be used?

How are vector and raster tiles priced for maps and satellite layers?

What are the billing considerations for weather layers and regional tilesets?

How is geofencing charged for mobile implementations?

What costs are associated with tileset processing, compute units, and hosting days?

When should an organization pursue commercial application licensing or enterprise agreements?

What are the available support plans, SLAs, and typical response times?

How is geocoding billed in 2025 and what feature sets are included?

How should teams estimate total cost considering requests, users, and performance?

.45 per 1,000 requests; permanent geocoding (stored indexes or cached results) can cost roughly – per 1,000 requests. Key features include autocomplete, batch geocoding, proximity bias, structured input, reverse geocoding, and address autofill. Strategies such as result caching and batch processing reduce per-request expense.