Map providers
DropAFinder supports four map providers: TomTom, Mapbox, HERE, and OpenStreetMap. Each renders the same finder data on a different tile service, so swapping providers changes how the map looks and who manages the underlying API costs — not what your locations show or how the finder behaves.
This page helps you choose the right provider for your workspace and explains how to switch at any time.
Quick comparison
| TomTom | Mapbox | HERE | OpenStreetMap | |
|---|---|---|---|---|
| API key required | Yes (managed key included; BYOK optional) | Yes | Yes | No |
| Managed key available | Yes (default) | No | No | N/A |
| Style variants | Standard, Dark, Satellite, Hybrid | Standard, Dark, Satellite, Hybrid | Standard, Dark, Satellite, Hybrid | Standard only |
| Attribution shown | © TomTom | © Mapbox © OpenStreetMap | © HERE | © OpenStreetMap contributors |
| Best for | Most workspaces — balanced coverage and visual quality | Strong design control, rich basemap detail | Enterprise / regional Europe coverage | Cost-zero, open-data purists |
Understanding “managed key” vs. “bring your own key”
When you create a finder, DropAFinder needs a tile API key to fetch map images. There are two ways it gets one:
- Managed key (TomTom only by default): DropAFinder supplies a shared TomTom key on your behalf. You pay nothing extra — map tile usage is included in your plan. This is the default for new finders.
- Bring your own key (BYOK): You register with the provider directly, generate a key in their developer dashboard, and paste it into the Finder Builder. Your account with that provider is billed directly for tile loads.
OpenStreetMap tiles are served from the public OSM tile servers with no key at all. For low-traffic finders this is fine; for high-traffic production finders, the OSM foundation asks that heavy consumers self-host or use a commercial OSM tile host.
💡 Tip: If you are unsure, start with TomTom using the managed key. You can always switch providers and add a BYOK key later — the change takes effect immediately without redeploying your embed code.
Provider details
TomTom
TomTom is the default provider and the only one that works without any configuration. When no API key is entered, DropAFinder falls back to a managed shared key so your finder renders out of the box.
Style variants supported: Standard, Dark, Satellite, Hybrid
| Variant | What it looks like |
|---|---|
| Standard | Clean light basemap with roads, labels, and points of interest |
| Dark | Inverted color scheme — works well on dark-themed sites |
| Satellite | Aerial photography with no overlay labels |
| Hybrid | Aerial photography with road and label overlay |
Attribution: © TomTom (shown automatically in the map corner)
When to use TomTom:
- You want the fastest setup with no extra accounts to create
- Your audience is primarily in North America, Europe, or major metro areas worldwide
- You want all four style variants without extra work
Getting a TomTom key: If you outgrow the managed key (high-traffic or white-label requirements), generate your own at the TomTom Developer Portal .
Mapbox
Mapbox is a popular choice for teams that want strong visual customization. The Mapbox basemaps have a polished, design-forward look that complements brand-heavy sites.
Style variants supported: Standard, Dark, Satellite, Hybrid
| Variant | Mapbox style (at time of writing) |
|---|---|
| Standard | streets-v12 |
| Dark | dark-v11 |
| Satellite | satellite-v9 |
| Hybrid | satellite-streets-v12 |
Attribution: © Mapbox © OpenStreetMap (shown automatically)
When to use Mapbox:
- You already have a Mapbox account and want to consolidate tile usage there
- Your designer prefers the Mapbox visual style
- You need global coverage with consistently rendered labels
Getting a Mapbox key: Create an access token in your Mapbox account at docs.mapbox.com/help/dive-deeper/access-tokens .
⚠️ Warning: Mapbox access tokens should be scoped to the domains where your finder is embedded. A token with full permissions embedded in a public page can accumulate unexpected tile load charges if scraped.
HERE
HERE is a strong option for enterprise customers, particularly those with a European audience or existing relationships with HERE Technologies.
Style variants supported: Standard, Dark, Satellite, Hybrid
| Variant | HERE path / style |
|---|---|
| Standard | base / lite.day |
| Dark | base / lite.night |
| Satellite | aerial / satellite.day |
| Hybrid | aerial / hybrid.day |
Attribution: © HERE (shown automatically)
When to use HERE:
- You have an existing HERE developer account or enterprise contract
- Your locations are concentrated in Europe, where HERE’s map data is particularly strong
- Your compliance requirements specify HERE as a vendor
Getting a HERE API key: Create a project and generate credentials at developer.here.com/projects .
🔴 [NEEDS CLARIFICATION: Does DropAFinder support both HERE REST API keys and OAuth 2.0 app credentials, or only the REST API key format?]
OpenStreetMap
OpenStreetMap (OSM) uses free, community-maintained tile servers. No account or API key is required.
Style variants supported: Standard only
Dark, Satellite, and Hybrid are not available for OpenStreetMap. If you switch to OSM while a dark or satellite variant is selected, the variant resets to Standard automatically.
Attribution: © OpenStreetMap contributors (shown automatically)
When to use OpenStreetMap:
- Budget is the primary concern and tile load volumes are low to moderate
- You want to use open-data map tiles for ideological or procurement reasons
- You are building a prototype or internal tool without production SLA requirements
⚠️ Warning: The public OSM tile servers have a usage policy that limits high-volume access. For finders embedded on high-traffic public pages, consider a commercial OSM provider or switch to TomTom / Mapbox / HERE with a BYOK key.
Style variants at a glance
🟡 [SCREENSHOT: 2x4 grid showing the same finder rendered in each of the four style variants (Standard, Dark, Satellite, Hybrid) across TomTom and Mapbox, with OSM shown separately in Standard only]
All providers except OpenStreetMap support the same four named variants. The visual results differ because each provider has its own tile rendering pipeline, but the intent is consistent:
- Standard — light basemap, suited to most site designs
- Dark — dark basemap, suited to dark-themed sites or nighttime aesthetics
- Satellite — aerial photography with no road/label overlay
- Hybrid — aerial photography with a semi-transparent road and label overlay
The style variant is set in the Finder Builder under Map > Style. It can be changed at any time and takes effect immediately on publish.
Cost considerations
| Scenario | What you pay |
|---|---|
| TomTom, managed key | Included in your DropAFinder plan — no external account needed |
| TomTom, BYOK | Charged to your TomTom developer account per tile load |
| Mapbox, BYOK | Charged to your Mapbox account per tile load |
| HERE, BYOK | Charged to your HERE account per tile load or per plan |
| OpenStreetMap | Free (subject to OSM fair-use policy) |
Tile load volume depends on how many visitors open your finder and how much they pan and zoom. A visitor who opens the finder once without moving the map loads a relatively small number of tiles; an interactive session with heavy panning loads significantly more.
If you are on the TomTom managed key and your finder is experiencing very high traffic, contact DropAFinder support to discuss dedicated key options.
How to change your map provider
- Open the Finder Builder for the finder you want to update.
- Navigate to the Map section in the left panel.
- Select the new provider from the Provider dropdown.
- If the new provider requires an API key (Mapbox, HERE, or TomTom BYOK), paste your key into the API key field.
- Select a style variant. If you were using Dark, Satellite, or Hybrid and switch to OpenStreetMap, the variant resets to Standard automatically.
- Click Publish to push the change live.
🟡 [SCREENSHOT: The Map section of the Finder Builder showing the Provider dropdown open with TomTom, Mapbox, HERE, and OpenStreetMap as options, and the API key field below it]
Your embed code does not change when you swap providers. The finder key stays the same — only the published configuration updates.
⚠️ Warning: If you remove a BYOK API key without replacing it and the provider is not OpenStreetMap, your map will stop rendering for visitors until you supply a valid key or switch back to TomTom with the managed key.
Attribution requirements
Each provider’s attribution string appears automatically in the bottom corner of every rendered map. You cannot remove these attributions — they are required by each provider’s terms of service, and DropAFinder enforces them at the tile layer level.
| Provider | Attribution text |
|---|---|
| TomTom | © TomTom |
| Mapbox | © Mapbox © OpenStreetMap |
| HERE | © HERE |
| OpenStreetMap | © OpenStreetMap contributors |