Skip to main content


The MVTLayer is a derived TileLayer that makes it possible to visualize very large datasets through MVTs (Mapbox Vector Tiles). Behaving like TileLayer, it will only load, decode and render MVTs containing features that are visible within the current viewport.

Data is loaded from URL templates in the data property.

This layer also handles feature clipping so that there are no features divided by tile divisions.

import {Deck} from '';
import {MVTLayer} from '';

const layer = new MVTLayer({
id: 'MVTLayer',
data: [
minZoom: 0,
maxZoom: 14,
getFillColor: f => {
switch ( {
case 'poi':
return [255, 0, 0];
case 'water':
return [120, 150, 180];
case 'building':
return [218, 218, 218];
return [240, 240, 240];
getLineWidth: f => {
switch ( {
case 'street':
return 6;
case 'motorway':
return 10;
return 1;
getLineColor: [192, 192, 192],
getPointRadius: 2,
pointRadiusUnits: 'pixels',
stroked: false,
picking: true

new Deck({
initialViewState: {
longitude: -122.4,
latitude: 37.74,
zoom: 11
controller: true,
getTooltip: ({object}) => object && ( ||,
layers: [layer]


To install the dependencies from NPM:

npm install
# or
npm install
import {MVTLayer} from '';
import type {MVTLayerProps, MVTLayerPickingInfo} from '';

new MVTLayer<FeaturePropertiesT>(...props: MVTLayerProps<FeaturePropertiesT>[]);

To use pre-bundled scripts:

<script src="^9.0.0/dist.min.js"></script>
<!-- or -->
<script src="^9.0.0/dist.min.js"></script>
<script src="^9.0.0/dist.min.js"></script>
<script src="^9.0.0/dist.min.js"></script>
new deck.MVTLayer({});


Inherits all properties from TileLayer and base Layer, with exceptions indicated below.

If using the default renderSubLayers, supports all GeoJSONLayer properties to style features.

data (string | string[] | object)

The remote data for the MVT layer.

  • String: Either a URL template or a TileJSON URL.
  • Array: an array of URL templates. It allows to balance the requests across different tile endpoints. For example, if you define an array with 4 urls and 16 tiles need to be loaded, each endpoint is responsible to server 16/4 tiles.
  • JSON: A valid TileJSON object.

See TileLayer's data prop documentation for the URL template syntax.

The getTileData prop from the TileLayer class will not be called.

uniqueIdProperty (string, optional)

Needed for highlighting a feature split across two or more tiles if no feature id is provided.

An string pointing to a tile attribute containing a unique identifier for features across tiles.

highlightedFeatureId (number | string, optional)

  • Default: null

When provided, a feature with ID corresponding to the supplied value will be highlighted with highlightColor.

If uniqueIdProperty is provided, value within that feature property will be used for ID comparison. If not, feature id will be used.

loadOptions (object, optional)

On top of the default options, also accepts options for the following loaders:

Note that by default, the MVTLoader parses data using web workers, with code loaded from a CDN. To change this behavior, see loaders and workers.

binary (boolean, optional)

  • Default: true

Use tile data in binary format to improve performance (2-3x faster on large datasets). It removes the need for serialization and deserialization of data transferred by the worker back to the main process. See here for details on this format.


  • It requires using GeoJsonLayer in the renderSubLayers callback.


onDataLoad (Function, optional)

Called if data is a TileJSON URL when it is successfully fetched

Receives arguments:

  • tileJSON (object) - the loaded TileJSON


getRenderedFeatures (Function)

Get the rendered features in the current viewport.

If a uniqueIdProperty is provided only unique properties are returned.

Requires pickable prop to be true.


  • maxFeatures (number, optional): Max number of features to retrieve when getRenderedFeatures is called. Default to null.


  • An array with geometries in GeoJSON format.


  • As it's an expensive operation, it's not recommended to call getRenderedFeatures every time onViewStateChange is executed, use a debounce function instead.
  • In most of the cases you probably want to use it attached to onViewStateChange and onViewportLoad.


Aside from all members of the Tile class, tile instances from the MVTLayer also include the following fields:

dataInWGS84 (Feature[])

A list of features in world coordinates (WGS84).

Usage example:

const onViewportLoad = tiles => {
tiles.forEach(tile => {
// data in world coordinates (WGS84)
const dataInWGS84 = tile.dataInWGS84;
new MVTLayer({
id: "..."
data: "..."