This tutorial is going to talk about the particle system in BabylonJS. Particles are often small sprites used to simulate hard-to-reproduce phenomena like fire, smoke, water, or abstract visual effects like magic glitter and faery dust.


A picture of the playground's ParticleSystem demo

How can I do this ?

To perform this magic trick, the first thing to do is to create a new object, which will be the particle emitter. In our case, a box will be our emitting object, representing a particle fountain.

var fountain = BABYLON.Mesh.CreateBox("fountain", 1.0, scene);

The emitter acts as the source of the particles, and its location in 3D space determines where they are generated and how they move. So pay attention to the location/rotation of this object. In our case, the emitter is our fountain, but if you wish, you can use only a vector (BABYLON.Vector3) as an emitter.

Now, we must create a new (not-rendered) ParticleSystem object:

var particleSystem = new BABYLON.ParticleSystem("particles", 2000, scene, customEffect);

Simple. The first parameter is the name, he second parameter is the maximum number of particles, the third parameter is the scene, and the optional fourth parameter is a reference to a shader effect for the particles, overriding the default shader. I will talk about the fourth parameter further below.

An important part is to define the texture of each particle. Each one will have the same pattern, so choose carefully which one you want. But keep in mind that a single scene can contain multiple particleSystems, and each one can emit particles with unique texture patterns. Also keep in mind that multiple particle systems can use the same emitter object. Our particle texture is going to be this one:


To define the particle’s texture, add a line like this:

particleSystem.particleTexture = new BABYLON.Texture("Flare.png", scene);

(in the playground demo, we used /textures/flare.png)

For this texture, you can use an optional mask to filter some colors, or filter a part of the alpha channel.

particleSystem.textureMask = new BABYLON.Color4(0.1, 0.8, 0.8, 1.0);

This is the output of this configuration:


The last main thing to do is to define our emitter that we talked about earlier:

// Where the particles comes from
particleSystem.emitter = fountain; // the starting object, the emitter, a box in this case.

Now you should see your particle system working. But it might not be our final result. We can refine some parameters:

  • Box around our emitter. Our emitter is the center of particles source, but if you want your particles to emit from more than one point, then you can tell it to do so:
    particleSystem.minEmitBox = new BABYLON.Vector3(-1, 0, 0); // Starting all From
      particleSystem.maxEmitBox = new BABYLON.Vector3(1, 0, 0); // To...

As you can see, particles are emitted from different positions along the X-axis:


  • Now you can give some colors to your particles. Color one and two are combined, and “colorDead” is the color that the particle takes-on just before it disappears.

    // Colors of all particles (splited in 2 + specific color before dispose)
    particleSystem.color1 = new BABYLON.Color4(0.7, 0.8, 1.0, 1.0);
    particleSystem.color2 = new BABYLON.Color4(0.2, 0.5, 1.0, 1.0);
    particleSystem.colorDead = new BABYLON.Color4(0, 0, 0.2, 0.0);
  • Size of particles:

    // Size of each particle (random between...)
    particleSystem.minSize = 0.1;
    particleSystem.maxSize = 0.5;
  • LifeTime of particles:

    // Life time of each particle (random between...)
    particleSystem.minLifeTime = 0.3;
    particleSystem.maxLifeTime = 1.5;
  • Emit rate. This is the density of particles, the rate of particle flow:

    particleSystem.emitRate = 1000;


If you want to launch only a few particles at once, that can be done, as well. For example, if you want to emit only 300 particles:

particleSystem.manualEmitCount = 300;

Be aware that the stream is no longer continuous. This is a one-shot particle emission, so this function overrides the previous “emitRate” parameter.

  • The selected mode for particles. You can choose between “BLENDMODE_ONEONE” (default choice: source color is added to the destination color without alpha affecting the result), and “BLENDMODE_STANDARD” (to blend current color and particle color using particle’s alpha).

    particleSystem.blendMode = BABYLON.ParticleSystem.BLENDMODE_ONEONE;
  • Gravity. You can use gravity if you want to give an orientation to your particles (e.g.: fire particles travel upward on the Y-axis)

    //Set the gravity of all particles (not necessarily down)
    particleSystem.gravity = new BABYLON.Vector3(0, -9.81, 0);
  • Direction. Random direction of each particle after it has been emitted, between direction1 and direction2 vectors.

    particleSystem.direction1 = new BABYLON.Vector3(-7, 8, 3);
    particleSystem.direction2 = new BABYLON.Vector3(7, 8, -3);


  • AngularSpeed. You can define a Z-axis rotation for each particle (in radian):

    particleSystem.minAngularSpeed = 0;
    particleSystem.maxAngularSpeed = Math.PI;
  • Speed/Strength. You can define the power of emitting particles, and the overall motion speed (0.01 is default update speed, faster updates = faster animation). ```javascript particleSystem.minEmitPower = 1; particleSystem.maxEmitPower = 3;

particleSystem.updateSpeed = 0.005;

* Duration. You can set the amount of time the particle system is running (depends of the overall speed above).
particleSystem.targetStopDuration = 5;
  • Dispose. Disposes (or not) the particle system on stop (very useful if you want to create a one shot particle system with a specific targetStopDuration):
    particleSystem.disposeOnStop = true;

Finally, you can start this particle system whenever you want in your code with:


And naturally stop it:


Feel free to play with this scene... at our online playground.

customEffect (the fourth parameter in the constructor)

var ps = new BABYLON.ParticleSystem("particles", 2000, scene, customEffect);

The customEffect is a type of BABYLON.Effect used to target a valid shader program.

The primary author of Babylon.js was kind enough to make us a fantastic playground demo of a particle system using a fragment shader effect -

. Visit that link, and you can see a fragment shader program that has been stored in a shader store. Notice the line:

BABYLON.Effect.ShadersStore["myParticleFragmentShader"] = [...]

A bit below that, you will see:

var effect = engine.createEffectForParticles("myParticle", ["time"]);

.createEffectForParticles accepts the following parameters:

  • fragment name (can be in the shaders store or the id of a DOM element)
  • array of additional parameters (uniforms)
  • array of additional samplers (for additional textures!)

The particle Effect Object is a slightly-modified Babylon Effect Object. Also notice that the ShadersStore is a namespace upon this special Effect Object.

The Effect Object has many 'setter' methods on it, one of which is .setFloat. Notice how it is used in the registerBeforeRender function. This causes the speed of the effect to cycle across about a 20 second time span. We are (the demo author is) varying the time parameter of the fragment shader program... from within the scene's render loop! WE LOVE IT!

Here is a short comment from Deltakosh... regarding that playground demo linked above:

By default Babylon.js will give you a vUV and a vColor varying parameter. It will also transmit you the particle texture. But you can feel free to add any new parameter, like I did, with 'time'.

This section of the tutorial is under construction. We will have much more to say, soon.

Custom functions

You can get even more control over particles by using custom functions: startDirectionFunction: (emitPower: number, worldMatrix: Matrix, directionToUpdate: Vector3): This function can be defined to specify initial direction for every new particle. By default, this function is defined with the following code:

startDirectionFunction = (emitPower: number, worldMatrix: Matrix, directionToUpdate: Vector3): void => {
    var randX = randomNumber(this.direction1.x, this.direction2.x);
    var randY = randomNumber(this.direction1.y, this.direction2.y);
    var randZ = randomNumber(this.direction1.z, this.direction2.z);

    Vector3.TransformNormalFromFloatsToRef(randX * emitPower, randY * emitPower, randZ * emitPower, worldMatrix, directionToUpdate);

startPositionFunction = (worldMatrix: Matrix, positionToUpdate: Vector3): This function can be defined to specify initial position for every new particle. By default, this function is defined with the following code:

startPositionFunction = (worldMatrix: Matrix, positionToUpdate: Vector3): void => {
    var randX = randomNumber(this.minEmitBox.x, this.maxEmitBox.x);
    var randY = randomNumber(this.minEmitBox.y, this.maxEmitBox.y);
    var randZ = randomNumber(this.minEmitBox.z, this.maxEmitBox.z);

    Vector3.TransformCoordinatesFromFloatsToRef(randX, randY, randZ, worldMatrix, positionToUpdate);

updateFunction: (particles: Particle[]): This function can be defined to provide custom update for active particles. This function will be called instead of regular update (age, position, color, etc.). Do not forget that this function will be called on every frame so try to keep it simple and fast :). By default the following code is used:

updateFunction = function(particles) {
     for (var index = 0; index < particles.length; index++) {
           var particle = particles[index];
           particle.age += this._scaledUpdateSpeed;

           if (particle.age >= particle.lifeTime) { // Recycle
                particles.splice(index, 1);
           else {
                particle.colorStep.scaleToRef(this._scaledUpdateSpeed, this._scaledColorStep);

                if (particle.color.a < 0)
                             particle.color.a = 0;

                particle.angle += particle.angularSpeed * this._scaledUpdateSpeed;

                particle.direction.scaleToRef(this._scaledUpdateSpeed, this._scaledDirection);

                this.gravity.scaleToRef(this._scaledUpdateSpeed, this._scaledGravity);

Next step

ParticleSystems are very powerful and versatile tools that can help bring realness and movement to your scenes. Don’t hesitate to use them as they are not resource-intensive.

Stay with us, because we are going to learn a new, very interesting thing: Configuring your environment.