Niagara VFX Basics · Beginner · 16 min
Build Your First Spark or Fire Effect from a Niagara Template
Start from a ready-made sprite template and tweak five settings — spawn rate, velocity, lifetime, colour and blend mode — to turn it into flying sparks or a flickering flame. Your first real effect, fast.
Before this: What Is Niagara? Spawn Your First Particle System in UE5, The Niagara Editor Tour: Emitters, Modules and the Particle Stack
- Create a Niagara System from the Fountain sprite template
- Tune spawn rate, initial velocity and particle lifetime to reshape the effect
- Recolour particles and choose an additive (glowing) blend mode for sparks and fire
- Drop the finished effect into your level and see it play
Don't build from scratch — start from a template
Here's the secret that makes VFX feel approachable: you almost never start with an empty system. Niagara — Unreal's particle and effects tool — ships with a handful of ready-made templates, and one of them, the 'Fountain', is a perfect launch pad. It already spawns little glowing dots that shoot upward, slow down, and fade. That is most of the way to a sparks effect, and a solid starting point for a fire effect too.
So instead of learning a hundred modules, you'll learn the five that actually change how an effect looks: how many particles appear (spawn rate), how fast they fly (initial velocity), how long they live (lifetime), what colour they are, and how they blend with the world (the material's blend mode). Nudge those five and the same template becomes either a shower of orange sparks or a soft, rising flame. Let's do both.
Before you start
A couple of quick checks so nothing blocks you:
- An open project with a level you can drop things into (the Third Person template is perfect)
- You've met the Niagara editor before — you know an Emitter has stacked Modules (covered in the editor-tour lesson)
- Somewhere dark in your scene to test in: glowing effects read best against a darker background
The five dials you'll be turning
Tap a card to flip it
Make the system and reshape it into sparks
Work top to bottom. Each row stays ticked even if you close the page and come back. We'll aim for sparks first, then turn it into fire afterwards.
- 1Create a Niagara System from the Fountain template
In the Content Browser, click '+ Add' (or right-click in empty space) and choose FX → Niagara System. A wizard opens.
Choose 'New system from selected emitter(s)' or the template option, find the 'Fountain' template/emitter, add it, and finish. Name the asset something like 'NS_Sparks' and double-click it to open the Niagara editor.
TipIf you see both 'System' and 'Emitter' templates, pick the Fountain to create a whole System — that's the asset you'll actually place in a level.
- 2Find the modules in the emitter stack
In the middle of the editor is the emitter — a vertical stack of grouped modules: Emitter Spawn, Emitter Update, Particle Spawn, Particle Update, and Render.
Click a module to select it; its settings appear in the Selection/Details panel on the right. This is where every dial lives. The viewport on the left shows the effect updating live as you change values.
TipIf the preview ever looks frozen, there's a small play/pause/restart bar under the viewport — give it a tap to restart the simulation.
- 3Turn down the Spawn Rate for sparse sparks
In the Emitter Update group, find the 'Spawn Rate' module and select it. Lower the rate (try something modest like 20–40) so you get individual, readable sparks rather than a solid stream.
Watch the viewport: fewer particles per second means each one stands out, which is exactly what sparks should do.
TipSpawn Rate is 'particles per second'. There's also a 'Spawn Burst Instantaneous' module if you ever want a one-shot pop of sparks instead of a constant stream.
- 4Speed them up with velocity
In Particle Spawn, look for a velocity module — often 'Add Velocity' or 'Add Velocity in Cone'. Increase the speed value so the sparks shoot out energetically.
If it's a cone, widen or narrow the cone angle to spray them outward or keep them tight. Sparks look great flying up and slightly outward, then arcing back down under gravity.
TipDon't see them fall back down? Add a 'Gravity Force' or 'Curl Noise'/'Drag' module in Particle Update, or check that a gravity module is already present — gravity is what gives sparks that satisfying arc.
- 5Shorten the Lifetime so they snap and fade
In Particle Spawn, find 'Initialize Particle' (or a 'Lifetime' setting) and reduce the Lifetime to something short, like 0.3–0.8 seconds. Short-lived particles read as quick, hot flecks.
Combined with a fast velocity and a fade-out colour, short lifetime is what separates a 'spark' from a lazy floating dot.
TipLifetime is in seconds. If your sparks vanish too abruptly, nudge it up slightly; if they linger like smoke, bring it down.
- 6Recolour them hot
Find the 'Color' module in Particle Update (or set the initial colour in Initialize Particle). Push it toward a hot palette — bright white/yellow at birth shifting to orange.
Many color modules expose a curve or gradient so the colour changes over the particle's life. Start near-white (hottest), end orange/red (cooling), which instantly sells 'spark' or 'ember'.
TipBoosting the colour values above 1.0 (e.g. an Intensity/multiplier on an additive material) makes particles bloom and glow when your scene has Bloom in post-processing.
- 7Set an additive (glowing) blend mode
Select the Render group's Sprite Renderer and find its Material. The Fountain template usually already uses an additive sprite material — confirm it, and if you swap materials, pick one whose Blend Mode is 'Additive'.
Additive blending adds the particle's light to whatever's behind it, so overlapping sparks build up into bright hot spots. That glow is the difference between 'dots on screen' and 'real sparks'.
TipIf you open the material itself, the Blend Mode lives in the material's Details under the 'Material' section. 'Additive' = glowing/fire/sparks; 'Translucent' = soft smoke/dust that can also be dark.
Same template, two effects: sparks vs fire
Low spawn rate (sparse, readable specks). Fast initial velocity, ideally in a cone, so they fling outward. Short lifetime (well under a second). Small particle size. Colour: white-hot fading to orange.
Add gravity so they arc and fall. Additive material. The vibe is energetic and sharp — like a grinder or a campfire log popping.
Higher spawn rate (a dense, continuous column). Gentle upward velocity (flames rise, they don't shoot). Slightly longer lifetime so the column holds together. Larger, softer particles, often growing over life.
Colour: bright yellow/white at the base fading to orange then a dark red at the top. Keep the additive material. The vibe is a soft, flickering, rising glow rather than flying specks.
You tuned everything for fire but it still looks like a fast spray of dots, not a soft flame. What are the two most likely culprits?
Velocity is probably too high. Flames rise gently — drop the initial/added velocity right down so particles drift upward instead of shooting out. Sparks are fast; fire is slow.
Particle size and spawn rate are likely too low. Fire reads as a connected mass, so increase the spawn rate for density and increase the particle size (and let it grow over life with a Scale/Size module) so individual sprites blur together into a single glowing column.
Put it in your level and save
An effect isn't real until it's playing in a scene. Two quick steps.
- 1Drag the system into the level
Save the Niagara System (Ctrl+S). Back in the level editor, drag your 'NS_Sparks' asset from the Content Browser straight into the viewport. It becomes a Niagara Actor and starts emitting.
Move it where you want with the transform gizmo, exactly like any other actor. Press Play (or Alt+P) to see it running in the actual game view.
TipGlowing effects can look washed out in a bright editor scene. Test near something dark, or with the level's lighting, so the additive glow actually shows.
- 2Iterate without re-placing
Leave the actor in the level and double-click the system asset to keep tweaking. Changes to the system asset show up on every placed copy of it.
That's the power of a System asset: tune once, and every spark/fire actor that uses it updates together.
TipIf a change in the editor doesn't seem to take, save the system — placed actors reflect the saved asset.
Handy shortcuts for this lesson
- Ctrl S Save the open Niagara System (do this before placing or playing)
- Alt P Play In Editor — see the effect running in the level
- Esc Stop Play In Editor and return to editing
- F Focus/frame the selected Niagara actor in the level viewport
QuizCheck yourself
1Which blend mode gives particles that hot, glowing look used for sparks and fire?
Additive adds the particle's brightness to the background, so overlapping particles build into bright glowing cores — perfect for fire and sparks.
2You want flying sparks rather than a soft flame. Compared to fire, sparks should generally have…
Sparks are fast and short-lived — they shoot out and snap away. Fire rises gently and lingers a little longer in a denser column.
3Where do you change how many particles are created per second?
Spawn Rate (particles per second) lives in the Emitter Update group. Low rate = sparse sparks; high rate = a dense flame.
Duplicate your sparks system (right-click the asset → Duplicate) and rename the copy 'NS_Fire'. Without creating anything new, retune only the five dials so the copy reads as a flickering flame instead of sparks. Then place both in the level side by side and compare.
Hint 1
Spawn Rate: raise it so the fire is dense and continuous, not sparse.
Hint 2
Velocity: lower it a lot — flames rise gently, they don't shoot.
Hint 3
Lifetime + size: lengthen lifetime slightly and increase particle size (let it grow over life) so sprites blur into one column.
Hint 4
Colour: bright yellow/white at the base fading up to orange then dark red. Keep the additive material.
Open NS_Fire. In Emitter Update, increase Spawn Rate for density. In Particle Spawn, drop the Add Velocity speed right down and keep it pointing up. Raise Lifetime a touch and increase the initial size, adding/using a Scale or Size-over-life so particles grow as they rise.
In Particle Update, set the Color curve from bright white/yellow at birth to orange and then dark red near death. Leave the additive material as-is.
Save, drag both NS_Sparks and NS_Fire into the level, and press Play. Same template, two completely different effects — proof that those five dials are where the look really comes from.
You can now
Tick these off — they're real skills you'll reuse in every effect you build:
- Create a Niagara System from the Fountain template
- Find and edit Spawn Rate, velocity, lifetime and colour in the emitter stack
- Recognise and use an additive blend mode for a glowing look
- Place a Niagara effect in a level, play it, and iterate on the asset
Mark this lesson complete
We'll remember it on your Academy page and unlock the next lesson below.
Questions beginners ask
I don't see a 'Fountain' template — where is it?
When you create a Niagara System (Content Browser → + Add → FX → Niagara System), the wizard offers templates and ready-made emitters. The Fountain is one of Epic's built-in sprite examples. If your list looks different, pick any simple sprite/'fountain'-style emitter that spawns upward-shooting dots — the workflow is identical. Exact template names can vary by engine version.
What's the difference between a Niagara System and an Emitter?
An Emitter is one effect element (one stack of modules that spawns and updates particles). A System is a container that holds one or more emitters and is the asset you actually drop into a level. For a single spark or fire effect you'll work in one emitter inside one system.
My particles are there but I can't see them glow. Why?
Two common reasons: the material isn't additive (so it isn't adding light), or your scene is too bright for the glow to stand out. Confirm the Sprite Renderer's material uses an Additive blend mode, test against a darker part of your level, and make sure your post-process has some Bloom so hot particles bloom.
Do I have to write any code for this?
No. Niagara is entirely visual — you build effects by stacking and tuning modules, no C++ or Blueprint required. You'll only reach for Blueprint later if you want to trigger an effect from gameplay, which is a separate lesson.