Frequently Asked Questions


What is the Mapbox Vision SDK?

The Mapbox Vision SDK is tool for developers that brings visual context to the navigation experience. It uses efficient neural networks to process imagery directly on mobile or embedded devices, turning any connected camera into a second set of eyes for your car. Situational context is interpreted with AI-powered image processing that is fast enough to run in real-time, yet efficient enough to run locally on today’s smartphones. Live interpretation of road conditions with connectivity to the rest of the Mapbox ecosystem gives drivers access to fresher, more granular driving information that can help make real-time recommendations, improving safety, user experience and efficiency for drivers.

What can I do with the Vision SDK?

The Vision SDK is a lightweight, multi-platform solution for live location, connecting augmented reality and artificial intelligence to a reimagined navigation experience. The Vision SDK brings the developer into the driver’s seat with a comprehensive set of real-time navigation and mapping features that fit into a single mobile or embedded application. In doing so, the Vision SDK enables customizable augmented reality navigation experiences, classification and display of regulatory and warning signs, driver alerts for nearby vehicles, cyclists, and pedestrians, and more.

How does the Vision SDK tie into the rest of Mapbox’s products and services?

Mapbox’s live location platform incorporates dozens of different data sources to power our maps. Map data originates from sensors as far away as satellites and as close up as street level imagery. Conventionally, collected imagery requires extensive processing before a map can be created or updated. The innovation of the Vision SDK is its ability to process live data with distributed sensors, keeping up with our rapidly changing world. Developers will be able to use this new ability to create richer, more immersive experiences with Mapbox maps, navigation, and search.

Installing Vision

What is the installation process for the Vision SDK?

To download the SDKs, developers will need to first create a free account on After logging in to with valid credentials, developers will be able to access download and installation instructions at

What platforms are supported by the Vision SDK?

Embedded Linux

How do I get started with the Vision SDK?

Developing with Vision

What are the main changes since Private Beta?

Mapbox Vision now has a more modular architecture; consisting of multiple “building blocks.” Developers will be able to import only the pieces they need, enabling smaller application size and better performance. There is a single “VisionCore” block that contains all of the neural networks and directly ingests sensor data. The output of “VisionCore” is passed to a common C++ API layer called “Vision” from which developers can access all Vision data types. Vision is wrapped with native bindings for use with mobile platform SDKs.

What development platforms are supported by this new architecture?

One of the benefits of this new architecture is that every new iteration of our modules and core algorithms needs to be built only once in C++ and will be simultaneously deployed to platform language SDKs for iOS and Android platforms. Additionally, we will be supporting embedded Linux platforms beginning with this launch.

What are the components of the Vision SDK?

For each supported platform for Mapbox Vision, there are four modules: Vision, VisionAR, VisionSafety, and VisionCore:

How do I set up AR Navigation?

Creating an augmented reality navigation experience requires the modules Vision, VisionAR, and Mapbox’s Navigation SDK.

What is the purpose of the VisionSafety Module?

Developers can create features to notify and alert drivers about road conditions and potential hazards with the VisionSafety SDK, an add-on module that uses segmentation, detection, and classification information passed from the Vision SDK. For example, developers can monitor speed limits and other critical signage using sign classification and track the most recently observed speed limit. When the detected speed of the vehicle is in excess of the last observed speed limit, programmable alerts can be set. VisionSafety can also send programmable alerts with pedestrians or cyclists are in the vehicle’s path. Finally, Safety Mode can send programmable alerts when a driver is closing too quickly on a lead vehicle.

How can Mapbox Vision enable triggered actions?

Programmable alerts are available in the VisionSafety module that allow extra actions to be taken based on events recognized by the Vision SDK. For example, developers can automatically capture a video clip or an image frame when a collision or hard braking event is detected. The Vision SDK exposes various events from the driving scene to enable this functionality.

What kind of lane information is exposed by Vision?

The Vision SDK's segmentation provides developers with the following pieces of lane information: number of lanes, lane widths, lane edge types, and directions of travel for each lane. A set of points describing each lane edge is also available.

Is there a way to use Vision with exogenous inputs (e.g. vehicle signals)

Yes. We now support interfaces to arbitrary exogenous sensors (e.g. differential GPS, vehicle speed, vehicle IMU). This will be especially helpful for developers using embedded platforms.

What is the minimum configuration for Mapbox Vision?

To work with only the foundational components of Vision (segmentation, detection, and classification layers), developers need only import the Vision SDK for their desired platform (iOS, Android, or Embedded Linux). Importing Vision SDK will automatically assemble the requisite VisionCore.

What can’t I do with the Vision SDK?

An enterprise license for the Vision SDK is required for developers that wish to save, download, or otherwise store any content, data, or other information generated by the Vision SDK. Contact sales to find out more. Vision SDK is meant to help you better navigate and manage fleets, not to create map databases. So please don’t use the Vision SDK for the purpose of creating a general database of locations, road features or any other map data. Full details on Vision SDK restrictions are posted in our Terms of Service.

Using Vision

In which regions is the Vision SDK supported?

Semantic segmentation, object detection, and following distance detection will work on virtually any road. The core functionality of the augmented reality navigation with turn-by-turn directions is supported globally. AR navigation with live traffic is supported in over 50 countries, covering all of North America, most of Europe, Japan, South Korea, and several other markets. Sign classification is currently optimized for North America, with some limited support in other regions. Sign classification for additional regions is under development.

Can the Vision SDK read all road signs?

The latest version of the Vision SDK recognizes over 200 of the most common road signs today, including speed limits (5 - 120 mph or kph), regulatory signs (merges, turn restrictions, no passing, etc.), warning signs (traffic signal ahead, bicycle crossing, narrow road, etc.), and many others. The Vision SDK does not read individual letters or words on signs, but rather learns to recognize each sign type holistically. As a result, it generally cannot interpret guide signs (e.g. “Mariposa St. Next Exit”). We’re exploring Optical Character Recognition (OCR) as a future release.

What are the requirements for calibration?

AR navigation and Safety mode require calibration, which takes 20-30 seconds of normal driving. (Your device will not be able to calibrate without being mounted.) Because the Vision SDK is designed to work with an arbitrary mounting position, it needs this short period of calibration when it’s initialized to be able to accurately gauge the locations of other objects in the driving scene. Once calibration is complete, the Vision SDK will automatically adjust to vibrations and changes in orientation while driving.

What is the best way for users to mount their devices when using the Vision SDK?

The Vision SDK works best when your device is mounted either to the windshield or the dashboard of your vehicle with a good view of the road. We’ve tested a lot of mounts; here are a few of our favorites:
Some things to consider when choosing and setting up a mount:

Can I use the Vision SDK with an external camera?

Yes. Beginning with public beta, developers will be able to connect Vision-enabled devices to remote cameras. Image frames from external cameras can be transmitted over WiFi or via a wired connection.

Will the Vision SDK drain my battery?

The Vision SDK consumes CPU, GPU and other resources to process road imagery on-the-fly. Just as with any other navigation or video application, we recommend having your device plugged in if you are going to use it for extended periods of time.

Can I rely on the Vision SDK to make driving decisions?

No. The Vision SDK is designed to provide context to aid driving, but does not replace any part of the driving task. During beta, feature detection is still being tested, and may not detect all hazards.

Can I use the Vision SDK to make my car drive itself?

No. The Vision SDK can be used to issue safety alerts and provide augmented reality navigation instructions and other features, but does not make any driving decisions.

Will my device get hot if I run the Vision SDK for a long time?

Phones and other IoT devices will get warmer over time as the onboard AI consumes a decent amount of resources. However, we have not run into any heat issues with moderate-to-heavy use.

Will the Vision SDK work in countries that drive on the left?


Does the Vision SDK work at night?

The Vision SDK works best under good lighting conditions. However, it does function at night, depending on how well the road is illuminated. In cities with ample street lighting, for example, the Vision SDK still performs quite well.

Does the Vision SDK work in the rain and/or snow?

Yes. Just like human eyes, however, the Vision SDK works better the better it can see. Certain features, such as lane detection, will not work when the road is covered with snow.


What is “classification”?

In computer vision, classification is the process by which an algorithm identifies the presence of a feature in an image. For example, the Vision SDK classifies whether there are certain road signs in a given image.

What is “detection”?

In computer vision, detection is similar to classification - except instead of only identifying whether a given feature is present, a detection algorithm also identifies where in the image the feature occurred. For example, the Vision SDK detects vehicles in each image, and indicates where it sees them with bounding boxes. The Vision SDK supports the following detection classes: cars (or trucks), bicycles/motorcycles, pedestrians, traffic lights, and traffic signs.

What is “segmentation”?

In computer vision, segmentation is the process by which each pixel in an image is assigned to a different category, or “class”. For example, the Vision SDK analyzes each frame of road imagery and paints the pixels different colors corresponding its the underlying class. The Vision SDK supports the following segmentation classes: buildings, cars (or trucks), curbs, roads, non-drivable flat surfaces (such as sidewalks), single lane markings, double lane markings, other road markings (such as crosswalks), bicycles/motorcycles, pedestrians, sky, and unknown.

What is the difference between detection and segmentation?

Detection identifies discrete objects (e.g., individual vehicles) and draws bounding boxes around each one that is found. The number of detections in an image changes from one image to the next, depending on what appears. Segmentation, on the other hand, goes pixel-by-pixel and assigns each to a different category. For a given segmentation model, the same number of pixels are classified and colored in every image. Features from segmentation can be any shape describable by a 2-d pixel grid, while features from object detection are indicated with boxes defined by four pixels making up the corners.

Where does calibration happen?

Calibration is handled in the VisionCore module. VisionCore uses camera, IMU, and GPS to calibrate itself for best performance of Vision features.

Data and Privacy

Do I need to use my data plan to utilize the Vision SDK?

In the standard configuration, the Vision SDK requires connectivity for initialization, road feature extraction, and augmented reality navigation (VisionAR). However, the neural networks used to run classification, detection, and segmentation all run on-device without needing cloud resources. For developers interested in running the Vision SDK offline, please contact us.

How much data does the Vision SDK use?

The Vision SDK beta uses a maximum of 30 MB of data per hour. For reference, this is less than half of what Apple Music uses on the lowest quality setting.

What type of road network data is Mapbox getting back from the Vision SDK?

The Vision SDK is sending back limited telemetry data from the device, including location data, road feature detections, and certain road imagery, at a data rate not to exceed 30 MB per hour. This data is being used to improve Mapbox products and services, including the Vision SDK. As with other Mapbox products and services, Mapbox only collects the limited personal information described in our privacy policy.

Billing and Sales

How much does the Vision SDK cost?

Beginning on Public Beta launch day (4/15/2019), developers have immediate access to the Vision SDK with a free account. Use of the Vision SDK for iOS and Android platforms is billed based on monthly active users (MAUs), with a free tier of 50 MAUs to allow our developers to get started prototyping right away at no cost. After 50 MAUs, pricing is $1.00/MAU for up to 2500 MAUs and then $0.75/MAU thereafter. As a special promotion for the beginning of our public beta, we will offer free use of the Vision SDK until billing periods beginning on or after 6/15/2019. Please note that Vision SDK pricing is subject to change during the public beta.

How does beta promotional pricing work?

Until billing periods beginning on or after 6/15/2019, developers will not be billed for use of the Vision SDK unless they exceed 50,000 MAUs. In other words, developers will only be subject to billing for Vision SDK if they exceed the free tier for Mobile SDKs on the Mapbox pricing page. Our standard beta pricing will go into effect for billing periods beginning on or after 6/15/2019.

How much does Vision cost for embedded Linux platforms?

An enterprise agreement is required for access to the embedded Linux SDKs. For more information, please contact us.