VFXIntermediate

Bloom Pulse

A surge of glow that breathes through a pickup or a charged weapon — light leaking is the universal word for 'special'.

vfxpost-processingglowreward

Examples

Captured from this page's own interactive demo below.

Overview

Bloom is the halo that bright pixels bleed into their surroundings, and games use it as a value marker: the legendary sword glows, the charged shot glows, the portal glows. A bloom PULSE puts that marker on a timeline — a surge of glow that swells and settles on a pickup spawn, a power-up, a heal — so the light itself performs the event instead of just labeling the object.

Two shapes cover almost every use. The breath: a slow sine loop (one to two seconds per cycle) for objects waiting to be noticed — loot on the ground, an interactable in a dark room. The surge: a fast spike-and-decay, same grammar as a flash but softer, for the moment something gains power. Both should modulate emission intensity or a bloom-contributing color, not the post-process threshold — pulsing the global threshold makes the whole frame throb.

Glow inflation is the genre's chronic disease: when everything blooms, nothing is special, and the frame turns to soup. Budget the channel — one breathing object per scene view is plenty — and keep the resting state visibly dimmer than the pulse peak, because contrast over time, not absolute brightness, is what the eye reads as an event.

Interactive Demo

the breath says “notice me” — Power Up surges on toprare (pulses)common (resting glow)

Peak Glow2×

Pulse Time900ms

Use Cases

Loot rarity and pickup spawnsCharged weapons and abilitiesInteractables in dark scenesHeals, buffs and shrine activations

Best Practices

Do

✓Pulse per-object emission, not the global bloom threshold — the frame shouldn't throb with the sword.
✓Use the slow breath for 'notice me' and the fast surge for 'I just gained power'; they're different words.
✓Keep the resting glow visibly dimmer than the peak — contrast over time is what reads as an event.

Don't

✕Don't let every item bloom; one breathing object per scene view keeps the word meaningful.
✕Don't pulse faster than ~2 Hz on a loop — fast rhythmic glow reads as an alarm, not an invitation.
✕Don't rely on bloom alone for colorblind-critical signals; pair the glow with shape or motion.

Common Mistakes

⚠Animating the post-process threshold and making the entire frame breathe along with one pickup.
⚠A pulse identical for a common coin and an exotic drop, spending the rarity channel on nothing.
⚠HDR emission values tuned on one monitor that blow out to pure white on another — check on both.

Implementation

Paste this into your AI assistant (Cursor, Copilot, Claude) to add the effect to your project.

Prompt

Add the "Bloom Pulse" game-feel effect to my project: A surge of glow that breathes through a pickup or a charged weapon — light leaking is the universal word for 'special'.

How it works: Bloom is the halo that bright pixels bleed into their surroundings, and games use it as a value marker: the legendary sword glows, the charged shot glows, the portal glows. A bloom PULSE puts that marker on a timeline — a surge of glow that swells and settles on a pickup spawn, a power-up, a heal — so the light itself performs the event instead of just labeling the object.

Guidelines:
- Pulse per-object emission, not the global bloom threshold — the frame shouldn't throb with the sword.
- Use the slow breath for 'notice me' and the fast surge for 'I just gained power'; they're different words.
- Keep the resting glow visibly dimmer than the peak — contrast over time is what reads as an event.

Avoid:
- Don't let every item bloom; one breathing object per scene view keeps the word meaningful.
- Don't pulse faster than ~2 Hz on a loop — fast rhythmic glow reads as an alarm, not an invitation.
- Don't rely on bloom alone for colorblind-critical signals; pair the glow with shape or motion.

Implement the effect in whatever engine/stack the project already uses and follow its existing code style. Wire it up where it makes sense.