Godot 4 GPU Particles Invisible on Mobile or Web - GLES Compatibility and Process Mode Fix

Problem: GPUParticles2D or GPUParticles3D look correct in the editor (often on Vulkan desktop), but on an Android or iOS build, or in a web export, nothing renders or only a subset of effects appears.

Who is affected: Godot 4 projects that author VFX on desktop, then ship to GLES-class devices or WebGL without re-validating particle settings.

Fastest safe fix: Confirm the particle node is not paused by process mode, confirm visibility and layer masks, then align particle features with what your mobile renderer and web target actually support. If GPU particles still fail, swap the worst offenders to CPUParticles2D / CPUParticles3D for that platform profile.

Direct answer: invisible GPU particles on mobile or web are usually process mode + pause-tree interaction, GLES/WebGL feature limits, or visibility/canvas layer mismatch rather than a broken shader graph.

Why GPU particles vanish on mobile or web

Common causes:

Process mode is Pausable or Inherited while your scene tree is paused during menus, cutscenes, or state machines, so simulation stops.
Rendering driver path on device does not support the same particle features you used on desktop (certain meshes, trails, collision, or high counts).
CanvasItem or VisualInstance visibility, z-index, or cull mask differs between test camera and device camera.
One-shot or explosiveness timing looks fine at 120 FPS in editor but finishes before first visible frame on a slow first paint on web.
Fixed FPS on particles is set too low or idle processing is disabled in a way that skips updates on export.

Step 1 - Confirm it is not a pause or process issue

Select the particle node and open the Inspector.
Set Process / Process Mode to Always for nodes that must emit during paused UI (menus, overlays).
Re-test on device with the same pause state you use in production (open pause menu, hit cutscene flags).
If you drive emitters from code, verify you are not calling emitting = false on scene load only on export builds.

Verification checkpoint: With the game intentionally paused, your critical VFX still simulates when you expect them to.

If particles only fail when paused, stop here and ship with the corrected process mode.

Step 2 - Validate visibility, layers, and camera masks

For GPUParticles2D:

Confirm Visible is on and the node is not under a parent with modulate.a near zero.
Check Z Index and Y Sort against your gameplay layers.
Match CanvasLayer to the layer your gameplay camera draws.
Confirm Light Mask and Visibility Layer on the camera still include the particle layer on the export preset.

For GPUParticles3D:

Confirm the particles sit in the same world layer your Camera3D cull mask includes.
Check Global Coordinates vs local if the parent moves differently on device.

Verification checkpoint: A single solid ColorRect or mesh at the same transform is visible on device; only the particle node is missing.

Step 3 - Reduce GLES and WebGL-unfriendly features

On Android / iOS, test with the same renderer your export preset uses (Vulkan vs GLES compatibility classes depending on Godot minor and project settings). Then simplify:

Lower Amount to a conservative cap and test.
Disable Trails, Collision, and heavy Subemitters temporarily.
Replace custom mesh particles with simple quads for one build.
For web, assume stricter fragment limits; strip expensive material features on the particle material.

Verification checkpoint: A minimal particle (default material, low amount, no trails) renders on device.

If minimal particles work, reintroduce features one at a time until the culprit is identified.

Step 4 - Align timing for web and low-end first frame

If you use One Shot, increase lifetime margin so the burst is not missed during slow first frames.
Avoid relying on a single-frame emit right after scene change on web; defer one physics frame or use a short await get_tree().process_frame.
Confirm Fixed FPS on the particle node is not starving simulation on low refresh devices.

Verification checkpoint: Recording a slow-motion screen capture on device still shows at least one visible frame of the effect.

Step 5 - Platform fallback with CPUParticles

If GPU particles remain unreliable on a specific export:

Duplicate the effect as CPUParticles2D or CPUParticles3D.
Match amount, lifetime, and texture closely enough for gameplay readability.
Use a feature flag or export-feature tag so mobile or web builds instantiate CPU variants automatically.

This is a supported production pattern when GPU particle limits or driver variance would otherwise block shipping.

Verification checklist

[ ] Particle process mode allows simulation during real pause states.
[ ] Layer, mask, and camera culling match on export preset.
[ ] Minimal particle preset renders on target hardware or browser.
[ ] Heavy features re-enabled with known-safe caps per platform.
[ ] Optional CPU fallback path tested on worst device in your matrix.

Alternative fixes

Convert only hero effects to CPUParticles and keep ambient GPU particles desktop-only.
Split scenes so mobile uses a simplified VFX container scene.
Pre-bake flipbook-style animated sprites for ultra-low-end web if particle count is still unstable.

Prevention tips

Add one GLES / mobile VFX scene to your CI or weekly build smoke that only asserts "particles visible" on a reference device or emulator.
Document per-platform max particle amount in your art guidelines.
When upgrading Godot minors, re-run mobile particle smoke because renderer defaults and GLES paths change.

FAQ

Should I default new particles to process mode Always?

No. Use Always only when effects must run while the tree is paused. Overusing it hides real pause bugs elsewhere.

Do GPUParticles3D and GPUParticles2D fail for the same reasons?

Often process mode and masks behave similarly, but 3D adds camera cull mask and directional light interactions 2D does not share.

Why would editor Vulkan match GLES if I never change settings?

Desktop editor preview does not prove GLES feature parity. Treat device GPU as the source of truth.