A soft glowing halo surrounds bright light sources across images, videos, and games, mimicking how cameras capture intense illumination. It can come from one of two places: a real camera sensor that overloads when capturing intense light, or a rendering engine that deliberately layers glow onto bright pixels after the frame is drawn. Both paths produce a result that looks almost identical on screen, which is why the labels blur together so often.
This walkthrough explains where that halo comes from, how it differs from lens flare and eye glare, and how to control it in software you already use.
The Two Origins of a Glowing Halo
Every glowing ring around a lamp, neon sign, or streetlight in a game started somewhere. Some halos come from the physics of light hitting glass and silicon. Others come from a graphics programmer’s decision to fake that same physics with code. Knowing which origin produced the glow changes how you edit, fix, or remove it.
Optical Bloom From a Camera Sensor
When a real camera points at a light source brighter than its sensor can record, the excess photons spill into neighboring pixels. That spillover creates a soft, blurry patch of brightness around the light, and it shows up in raw photographs and live-action footage. Lenses with shorter focal lengths or wider apertures tend to produce more of this bleed because they gather more light at once.
Digital Bloom From a Rendering Pipeline
Game engines and 3D software build each frame, then run a series of post-processing passes on the finished image. One of those passes isolates the brightest pixels, blurs them, and layers the result back onto the original. The blurred bright pixels spread outward, and the frame now has a synthetic glow that did not exist in the raw geometry.
This is what most people mean by bloom in modern games, and it has almost nothing to do with how a real camera behaves.
Why the Confusion Happens
The optical version and the digital version look nearly identical because the digital version was designed to imitate the optical one. Designers wanted the warm, slightly hazy glow they saw in photography and film, so they built a filter that recreates it on demand. A photo of headlights at night and a screenshot of neon in a cyberpunk game can share the same visual signature, even though one came from a sensor and the other came from a shader.
Sorting those signatures apart starts with naming each one by what actually causes it.
Bloom, Lens Flare, and Eye Glare Separated
Three different phenomena share screen space so often that labeling them accurately takes a moment of care. Each has a different cause, a different shape, and a different fix.
| Effect | What Causes It | What It Looks Like | Where It Lives |
|---|---|---|---|
| Bloom | Bright pixels spread into neighbors | Soft, diffuse halo with no defined shape | Real cameras and rendered frames |
| Lens flare | Light bouncing between internal lens elements | Streaks, hexagons, or colored rings | Real cameras and some rendering engines |
| Eye glare | Cornea and photoreceptors struggling with brightness | Squinting, afterimages, discomfort | The human eye, not the image |
Bloom is shape-less and anchored to a light source. Lens flare is geometric and often produces visible artifacts like polygonal stars, because light bounces between the flat surfaces of lens elements and scatters in predictable patterns. Eye glare is biological and never appears in the image at all, though it can shape how you perceive brightness in the scene.
A single frame can contain bloom and lens flare at the same time, and you can also experience glare while watching it, which makes casual labeling unreliable.
Because the labels overlap so easily, it helps to follow bloom through the rendering stage where it is built.
Inside the Bloom Rendering Pipeline
The digital version of bloom follows a short, repeatable sequence of steps. Understanding the pipeline is the difference between toggling a slider and actually diagnosing why a glow looks wrong.
Threshold, Blur, Composite
First, a threshold filter scans the rendered frame and keeps only the pixels above a brightness cutoff. Anything dimmer than the cutoff is set to black, so only the sun, the lamp, the laser, and the brightest reflections survive. Second, a Gaussian blur convolution spreads those surviving bright pixels outward, softening their edges into a cloud of glow.
Third, the blurred result is additively layered onto the original frame, and the final image now carries that signature halo around its highlights.
The Sliders That Shape the Result
- Threshold: sets the brightness cutoff; lower values mean more pixels glow, higher values mean only the brightest sources glow.
- Intensity: controls how strongly the blurred layer is added back onto the frame.
- Blur radius: determines how far the glow spreads from its source.
- Iteration count: runs the blur multiple times for a softer, wider halo.
Higher iteration counts and wider blur radii cost more GPU time per frame, which is one reason bloom can drag down performance on weaker hardware. The Unreal Engine and Unity editors expose each of these parameters directly, and most shipping games reduce one or more of them when you drop the graphics preset from Ultra to High.
Reducing parameters to save performance only matters once you understand why designers reached for bloom in the first place.
Where the Effect Came From and Why It Stuck
Bloom has a documented history inside games, and that history explains why it shows up in almost every modern title by default.
Early 2000s Pioneers
Tron 2.0 in 2003 leaned heavily on a CRT-like bloom to make its neon geometry feel hot and electric. The effect became a visual signature for the era, and other studios began copying the look within a few years. By the time Unreal Engine 3 and Unity matured in the late 2000s, bloom was already a standard post-process pass baked into most rendering templates.
HDR and Tonemapping Changed the Look
Pairing bloom with HDR rendering and ACES tone mapping made highlights feel physically grounded rather than decorative. An overcast sky in an HDR pipeline can carry values brighter than white, and bloom helps translate those values into a believable glow on standard displays. Modern pipelines still rely on this pairing, which is why turning off HDR often makes bloom look weaker or out of place.
Spread Into Film, UI, and 2D
The same blur-and-add technique migrated beyond 3D. Films use bloom plugins in compositing software like DaVinci Resolve, web designers apply CSS filter blur to glowing buttons, and 2D pixel-art games now run custom shaders that fake bloom despite having no real geometry. The technique is platform-agnostic, which is part of why it feels so universal.
When Bloom Elevates an Image and When It Ruins One
Bloom is a tool, and like every post-processing effect, it makes some frames better and others worse. Reading the scene matters more than the slider value.
Scenes Where Bloom Earns Its Place
Moody corridors lit by a single lamp, neon cityscapes at midnight, sunrise vistas with strong backlighting, and dreamy cutscenes with soft focus all benefit from bloom. The effect amplifies atmosphere by softening the harsh edge between bright and dark, which mimics how human vision handles extreme contrast. Bloom also makes emissive surfaces like lava, plasma, and magic effects feel hot and dangerous.
Scenes Where Bloom Washes Everything Out
Competitive shooters and horror games often suffer from heavy bloom because it can hide enemies in the glow and turn photo highlights into featureless white blobs. A flashlight pointed at a wall should reveal texture, not erase it. Some early indie titles applied bloom to every surface by default, which buried detail under a layer of haze and earned the effect a reputation as a cliché.
Aim for bloom that highlights the brightest sources, not bloom that flattens the entire frame. Threshold discipline matters more than intensity.
Eye sensitivity adds another layer. People who experience photophobia or migraines may find heavy bloom genuinely uncomfortable, because the soft glow keeps the eye’s exposure response active longer than a sharp edge would. If a scene feels visually taxing, lowering bloom intensity is often the fastest fix.
Controlling Bloom in Games, Editors, and Cameras
Most of the tools you already use expose bloom somewhere. The trick is knowing which lever to pull for which situation.
In Games
Nearly every modern PC title ships with a graphics settings menu that includes bloom as a toggle, a slider, or a low/medium/high preset. Lowering it usually improves both clarity and frame rate, because the post-process pass costs GPU time per frame. Console games expose fewer options, but resolution and HDR toggles indirectly affect how much bloom you perceive.
In Unreal Engine and Unity
Both engines let you tune threshold, intensity, blur radius, and iteration count on a per-camera or per-volume basis. A common workflow is to keep high bloom for cinematic cameras and dial it down for gameplay cameras in the same scene. You can also drive the parameters by distance, so distant fog glows while nearby geometry stays sharp.
In Photoshop, Lightroom, and DaVinci Resolve
Adobe Photoshop and Lightroom both include a glow or diffusers filter that simulates bloom when you want to add it, and masking lets you keep the effect away from skin and faces. DaVinci Resolve has a dedicated glow module in its color page, plus a lens flare tool for the geometric cousin. If bloom was stripped during export, you can usually restore it in one of these editors without re-rendering the source.
When the Glow Suggests a Medical Question
Light bloom in an image has nothing to do with eye health. If persistent halos, glare, or afterimages show up in your actual vision rather than on a screen, that pattern is biological and worth raising with an eye doctor. Persistent glare sensitivity, sudden floaters paired with halos, or halos that worsen over days can indicate corneal, lens, or retinal changes that a clinical exam can sort out in minutes.
Bottom Line
The halo you see around a bright light in a game or photo is bloom, and bloom is almost always either a deliberate filter or a sensor artifact, not a medical problem. Treat it as a creative choice: enable it where atmosphere matters, dial it down where clarity matters, and reach for an eye doctor only when the glow appears in your vision rather than on the screen.
FAQ
Is light bloom harmful to your eyes?
No physical connection links a rendered bloom effect to your actual eyes, since it exists only within pixels on a screen. Persistent halos, glare, or afterimages in your actual vision are a different matter and should be evaluated by an eye doctor, especially if they appear suddenly or worsen over time.
Why do video games use the bloom effect?
Games use bloom to soften the transition between bright highlights and darker surroundings, which adds atmosphere and helps emissive surfaces like neon, fire, and magic feel hot and glowing without extra geometry.
How do you turn off light bloom in games?
Open the graphics settings menu, look for a bloom toggle or slider, and set it to off or low. If the option is missing, lowering overall post-processing quality often reduces bloom intensity as a side effect.
What is the difference between bloom and lens flare?
Bloom is a soft, shape-less halo anchored to a light source. Lens flare is a geometric artifact of light scattering between internal lens elements, producing visible streaks, polygons, or colored rings rather than a smooth glow.
Can light bloom cause eye strain or headaches?
Long viewing sessions of high-contrast, heavily glowing images can aggravate existing photophobia or trigger headaches, even though bloom itself does not directly cause strain. Reducing intensity or taking screen breaks typically helps.
