Tutorials•October 7, 2026•5 min read

Roblox Dust Particles: Build a Small Burst Effect

Create a dust ParticleEmitter on an Attachment, tune a short burst, and check texture transparency, placement, lifetime, and repeated triggers in Studio.

Build a dust burst with a ParticleEmitter inside an Attachment on a Part. Use a transparent dust texture, a short lifetime, and a small manual burst. Start with one fixed test location before attaching the effect to footsteps, landings, or moving objects.

Dust effect hierarchy: Part contains an Attachment, which contains a ParticleEmitter
Original placement diagram, not a screenshot of a rendered particle effect.

Build a visible test location

Create an anchored Part named DustDemo near the spawn and insert an Attachment named DustOrigin. Put a ParticleEmitter named DustBurst inside that Attachment. Place the origin where you want the burst to start, just above the surface for this exercise.

The ParticleEmitter reference distinguishes a Part’s emission volume from an Attachment’s emission point. Use the Attachment when you need a recognizable origin. Rotate it deliberately if the emission direction is wrong.

Use a texture with a transparent background

Assign an image you own or have permission to use as the emitter’s Texture. A soft, pale dust shape is a useful starting design. Check the exported image itself: a checkerboard drawn into the artwork will appear in the particle, while an actual transparent background allows the scene to show through.

Keep the texture simple for your first test. You should be able to recognize a single particle before adding more. Use the image import guide for asset preparation, then confirm the correct image reference is assigned to the emitter.

Set a small starting recipe

Example tuning values, not a universal preset
PropertyStart withCheck
Enabled / RateFalse / 0Manual burst only
Lifetime0.4 to 0.8 secondsCue ends promptly
Speed1 to 3Small outward movement
SpreadAngle30, 30Compact spread
ColorMuted tanFits the floor and lighting
Size / TransparencySmall start, gentle expansion, fade to invisibleSoft ending rather than a sudden disappearance

Lifetime and Speed use ranges; Size and Transparency can vary across particle age. Configure their editors in Properties. Try one change at a time and compare from the same camera position.

Trigger the burst with a test prompt

Add a ProximityPrompt directly beneath DustDemo. Put a regular Script beneath the same Part, then use this exercise code. Confirm the names in Explorer match. The prompt gives you a repeatable test trigger before you connect real gameplay.

local part = script.Parent
local prompt = part:WaitForChild("ProximityPrompt")
local origin = part:WaitForChild("DustOrigin")
local emitter = origin:WaitForChild("DustBurst")
local lastBurst = -math.huge

emitter.Enabled = false
emitter.Rate = 0
prompt.Triggered:Connect(function()
    local now = os.clock()
    if now - lastBurst < 1 then return end
    lastBurst = now
    emitter:Emit(12)
end)

Emit produces the requested burst even when continuous emission is disabled. The one-second gate is shared for this test object and prevents overlapping bursts from repeated prompt activations. This is a visual test, not a player reward or damage system.

Check the official burst-effect tutorial for another practical action-effect workflow.

Check the effect in three views

  1. Stand close enough to inspect the texture and origin.
  2. Move to normal gameplay distance and trigger again.
  3. View it against both a light and a dark surface.

Look for a readable cue that ends quickly. If the dust fills the whole screen, reduce size or count before adding more effects. If it disappears against the background, compare its color and transparency in that scene’s lighting.

Keep repeated effects affordable

Test several activations, then repeat on your intended devices and lower rendering quality. Shorter lifetimes and fewer simultaneous particles are useful starting levers, but measure the actual scene. Texture coverage and overlapping transparent effects can matter even when a particle count seems small.

Use the lighting comparison guide to keep the scene readable. Capture a fixed view with creator freecam, then return to the player camera to test the effect during movement.

Diagnose a missing burst

  • No visible particle: check Texture, Lifetime, Transparency, and the emitter’s parent.
  • Wrong location: inspect DustOrigin’s position and orientation.
  • Prompt does nothing: inspect the Script path and Output messages.
  • Particles continue afterward: confirm Enabled is false and Rate is zero.
  • Squares around the dust: inspect the source image’s alpha background.

Disabling continuous emission does not remove particles already alive. Let the short burst expire, or use Clear when you deliberately need to remove existing particles. Record the setting and observed result before making another change. Documentation checked October 7, 2026.

Frequently Asked Questions

Where should a dust ParticleEmitter go?▾

For a precise test origin, place it inside an Attachment beneath a Part. Confirm the origin’s position and orientation in Studio.

Can I emit a burst with Enabled set to false?▾

Yes. Emit produces a manual burst; Enabled and Rate control continuous emission. This guide uses a small prompt-triggered burst.

Why do dust particles look like squares?▾

Inspect the texture’s transparent background. A baked background or checkerboard is part of the artwork and will render with the particle.

Ready to build your Roblox game?

Describe a small prototype, review the generated project, and test it in Roblox Studio before publishing.

Try Obby Free →