Apply WebGL shaders to your LeafletJS tile layers

Name Last Update
demo Loading commit data...
src Loading commit data...
.eslintrc.js Loading commit data...
.gitignore Loading commit data...
.gitlab-ci.yml Loading commit data...
CHANGELOG Loading commit data...
LICENSE Loading commit data...
README.md Loading commit data...
package.json Loading commit data...
yarn.lock Loading commit data...


A LeafletJS plugin to appy WebGL shaders to your tiles.

With this plugin, you can apply colour transforms to your tiles, merge two or more tiles with a custom function, perform on-the-fly hillshading, or create synthetic tile layers based only on the map coordinates.


On-the-fly colouring

This demo loads the "toner" map style by Stamen and changes the colours on-the-fly:


Conditional colouring

This demo loads the "toner" map style by Stamen and changes the colours on-the-fly, depending on the latitude of each pixel. This highlights the tropics and arctic circles:


Mandelbrot set

This demo loads no tiles and uses the map coordinates alone to draw a fractal set:


Flood & height

This demo uses MapBox's "Terrain-RGB" tiles to play with the elevation: areas are coloured depending to the elevation (below 0 meters, between 0 and 5 meters, between 5 and 10 meters, above 10 meters).


Hypsometric tint

This demo uses MapBox's "Terrain-RGB" tiles and applies a basic hypsometric tint colour ramp.



Leaflet has been lagging behind when it comes to WebGL technology. Other map libraries (such as OpenLayers 3 and most notably Tangram) can already use WebGL shaders to apply transformations to map tiles and do fancy stuff.

The inflexion point are MapBox's "Terrain-RGB" tiles. WebGL manipulation of these tiles can provide real-time terrain relief and hill shading.

This takes some inspiration from shadertoy.com, in the sense that the shaders work on two triangles with some predefined attributes and uniforms.


Leaflet 1.0.1 (or newer), and a web browser that supports both WebGL and ES6 Promises. You can also use a Promise polyfill for IE11.


Include Leaflet and Leaflet.TileLayer.GL in your HTML:

<link rel="stylesheet" href="https://unpkg.com/leaflet@1.0.1/dist/leaflet.css" />
<script src="https://unpkg.com/leaflet@1.0.1/dist/leaflet.js"></script>
<script src='https://unpkg.com/leaflet.tilelayer.gl@latest/src/Leaflet.TileLayer.GL'></script>

Alternatively, fetch a local copy of Leaflet and Leaflet.TileLayer.GL with npm install --save leaflet; npm install --save leaflet.tilelayer.gl or yarn add leaflet; yarn add leaflet.tilelayer.gl

You can create instances of L.TileLayer.GL in your code. These take three new options: vertexShader, fragmentShader and tileUrls, e.g.:

    var antitoner = L.tileLayer.gl({
        vertexShader: "// String with GLSL vertex shader code",
        fragmentShader: "// String with GLSL fragment shader code",
        tileUrls: ['http://{s}.tile.stamen.com/toner/{z}/{x}/{y}.png']

Using this plugin requires some knowledge of WebGL and GLSL shaders. If you've never heard the terms "vertex shader" or "fragment shader", read this WebGL tutorial to become acquinted, or The Book Of Shaders to learn to do cool shaders, or WebGL Fundamentals to see some WebGL image processing techniques.

The vertexShader and fragmentShader options contain shader code, in strings. For every map tile, the shaders will run once, on two triangles. This plugin does not allow you to create more triangles.

The vertex shader receives the following attributes:

  • aLatLngCoords: a vec2 containing the map data coordinates for the vertices (with values like LatLngs).
  • aCRSCoords: a vec2 containing the map display coordinates for the vertices (with values for the map CRS).
  • aVertexCoords: a vec2 containing the viewport coordinates for the vertices (with values from -1.0 to +1.0). These make the two triangles span a whole tile. Make sure to use these as gl_Position in the vertex shader.
  • aTextureCoords: a vec2 containing the texture coordinates for the vertices. Use this for fetching texels.

The shaders receive the following uniforms:

  • uTexture0: a sampler2D referring to the first loaded tile image. This exists only if the tileUrls option is not empty.
  • uTexture1..uTexture7: texture samplers for the 2nd through 8th image.

Demo shaders

This is the code used in the "antitoner" demo, commented and explained:

// Create the vertex shader as a multi-line string. Note the "`" character, valid only in ES6 JavaScript.
// Shaders can be defined elsewhere, or loaded from other files or from the network,
// but they must be strings when used in a TileLayer.GL.
var antiTonerVertexShader = `
    // Define which attribs we want. In this case, aCRSCoords is not needed.
    attribute vec2 aVertexCoords;
    attribute vec2 aTextureCoords;

    // We need a varying so the fragment shader can use the interpolated aTextureCoords
    varying vec2 vTextureCoords;

    void main(void) {
        gl_Position = vec4(aVertexCoords , 1.0, 1.0);   // Use the vertex coords as given
        vTextureCoords = aTextureCoords;    // Pass the texture coords to the frag shader

var antiTonerFragmentShader = `
    // The fragment shader runs once per fragment (AKA "once per screen pixel")
    precision highp float;
    uniform sampler2D uTexture0;    // This contains a reference to the tile image loaded from the network
    varying vec2 vTextureCoords;    // This is the interpolated texel coords for this fragment

    void main(void) {
        // Classic texel look-up (fetch the texture "pixel" color for this fragment)
        vec4 texelColour = texture2D(uTexture0, vec2(vTextureCoords.s, vTextureCoords.t));

        // If uncommented, this would output the image "as is"
        // gl_FragColor = texelColour;

        // Let's mix the colours a little bit, inverting the red and green channels.
        gl_FragColor = vec4(1.0 - texelColour.rg, texelColour.b, 1.0);

// Instantiate our L.TileLayer.GL...
var antitoner = L.tileLayer.gl({
    // ... with the shaders we just wrote above...
    vertexShader: antiTonerVertexShader,
    fragmentShader: antiTonerFragmentShader,

    // ...and loading tile images from Stamen Toner as "uTexture0".
    // If this array contained more than one tile template string,
    // there would be "uTexture1", "uTexture2" and so on.
    tileUrls: ['http://{s}.tile.stamen.com/toner/{z}/{x}/{y}.png']

Cool things that should be doable, but nobody has yet shown interest in asking about, much less in implementing them

  • Updating the shaders
  • Reusing the same WebGL context for more than one TileLayer.GL (as the render calls are sync)
  • Custom uniforms
  • Time uniform(s)
  • Some kind of animations (keep the loaded images in memory, implement a rendering loop)
  • A playground, something in-between playground-leaflet.rhcloud.com and https://gitlab.com/IvanSanchez/Leaflet.TileLayer.GL


"THE BEER-WARE LICENSE": ivan@sanchezortega.es wrote this file. As long as you retain this notice you can do whatever you want with this stuff. If we meet some day, and you think this stuff is worth it, you can buy me a beer in return.