Why Is My Emission Map Not Glowing?

The map, HDR signal, bloom, exposure, and GI are five different layers

The emission texture answers a spatial question: which texels emit, and what color do they contribute? The material answers a radiometric question: how strongly should that signal enter the renderer? Bloom answers an image-processing question: which bright pixels should spread into a halo? Exposure answers a camera question: how should the HDR scene map to the display? Lights, baking, or global illumination answer a transport question: what energy reaches other surfaces?

Diagnose in that dependency order. A later layer can hide an earlier mistake, but it cannot make the asset contract correct. A low bloom threshold can make ordinary white surfaces glow; a high exposure can make a dark map look usable; a painted halo can look convincing in one thumbnail. Each shortcut breaks as soon as the lighting, camera, distance, or platform changes.

Keep color in the texture and open-range brightness in the renderer

A conventional PNG emission map is useful for authored RGB color and coverage. In a color-managed Three.js r185 workflow, typical PNG or JPEG emissiveMap textures are annotated as sRGB and converted into the linear working space for rendering. The shader-side emissiveIntensity then creates values beyond the closed display range that tone mapping and bloom can use.

This split keeps the source portable. It also avoids destructive edits made only to satisfy one camera. If the target workflow genuinely stores HDR emission in an EXR or another open-range format, document that contract explicitly; do not assume an 8-bit PNG contains the same numeric range.

Exposure can hide a correct result

Auto exposure reacts to the whole view. A sign that blooms in a dark corridor can appear modest when the camera sees daylight, even though its material values never changed. Freeze exposure while comparing renderer states, then restore the camera behavior and validate the asset at the minimum and maximum production exposure you support.

A known-good test needs the same mesh, texture, lights, camera, tone mapper, and viewport. Change one variable and record it. The captures on this page follow that method so the visible difference can be attributed to intensity, bloom, or exposure rather than to an undocumented scene change.

Visible glow is not automatically light transport

Bloom is a screen-space halo. It does not illuminate a wall, cast a shadow, or bounce colored light through the scene. Unreal Engine and Unity can connect emissive materials to supported baked or real-time lighting paths under specific settings, while many lightweight and web renderers require explicit lights or custom GI. Treat those as engine features with their own cost, quality, and mobility limits.

The PLAYTEX AI funnel keeps those jobs separate: use Emission Map Generator for the focused mask, PBR Map Generator when the whole material needs aligned maps, and PBR Engine Converter for target naming and packing. This guide remains the owner of the not-glowing symptom; the texture troubleshooting field guide remains the broader multi-symptom reference.

Which setting controls each kind of glow?

Texture and material binding

These checks decide whether the shader receives a usable emission signal at all.

• Emission / emissive slot: Binds the texture that identifies self-lit RGB regions. Black contributes no emitted color; brighter colored pixels contribute more before the material multiplier. Check it first when the surface is completely black, the wrong regions emit, or changing the texture has no visible effect.
• Emissive color or factor: Multiplies the sampled emission texture. In Three.js r185, emissiveMap is modulated by both emissive and emissiveIntensity. Set it to white to preserve the map color, or use a deliberate tint. Never leave it black when a texture should show.
• Color-space annotation: Tells the renderer how to decode RGB emission color before lighting math. Three.js documents typical PNG or JPEG emissiveMap textures as sRGB color data. Inspect it when the hue, edge brightness, or threshold behavior changes after import. A deliberately linear or HDR source must be labeled according to how it was authored, not by filename alone.
• Compression, mipmaps, and alpha: Filtering and compression can smear thin bright marks, darken small mips, or alter an alpha-carried mask even when the full-size source looks correct. Compare the uncompressed source, a close camera view, and distant mips when small emissive details vanish or develop dark fringes.

HDR signal, bloom, and exposure

These renderer controls turn a self-lit surface into a perceptible glow while preserving a stable image.

• Material emissive intensity: Scales emitted radiance after the texture and emissive color are combined. Values above the display range can feed HDR tone mapping and bloom. Raise it when the surface is mapped correctly but never exceeds the bloom threshold. Reduce it when the core clips to featureless white.
• Bloom threshold: Limits which bright rendered pixels contribute to bloom. In Three.js UnrealBloomPass, luminance must clear this threshold before the blur chain contributes. Lower it only after confirming HDR intensity. A threshold that is too low makes ordinary highlights and UI-like whites glow.
• Bloom strength and radius: Strength controls the added bloom contribution; radius controls its spread. Neither setting makes a missing emissive texture valid. Tune strength after threshold isolates the intended emitter, then use radius to match the apparent lens or art direction.
• Tone-mapping exposure: Maps scene-referred HDR values toward the display. Auto exposure or a changed manual value can make the same material look much dimmer or brighter. Lock exposure while diagnosing, then retest across the supported production exposure range instead of optimizing for one dark frame.

Nearby illumination and runtime delivery

A visible glow and light received by another object are separate renderer features.

• Real lights: Point, spot, area, or custom lights directly illuminate nearby geometry and can cast supported shadows. Use them for dynamic signs, weapons, characters, or effects when the surrounding scene must respond predictably at runtime.
• Baked or global illumination: Transfers emissive energy to other surfaces only when the chosen engine, renderer, and bake or GI mode support that path. Use it for static or supported dynamic scenes after verifying platform cost and update rules. Do not assume a self-lit shader automatically participates.
• Engine export convention: Preserves filenames, color roles, and channel assignments expected by the destination material workflow. Use PBR Map Generator for the aligned set, then PBR Engine Converter when the target expects different names, packing, or normal conventions.

Run the emission diagnosis in this order

An emission map makes selected pixels self-lit, but it does not create a visible halo or light nearby objects by itself. Assign the map, use a non-black emissive color, raise material intensity into HDR when the renderer requires it, enable bloom, then hold exposure steady while you test.

Step 1: Confirm the emission texture is assigned

Open the material actually used by the visible mesh. Bind the exported PNG to its emission or emissive-color input, confirm the intended UV set, and make sure a material instance or runtime override is not replacing the slot. A correct file cannot affect a shader that never samples it.

Create or inspect the mask first

Step 2: Set a non-black emissive color

Many shaders multiply the texture by an emissive color or factor. Black multiplied by any map remains black. In Three.js MeshStandardMaterial, emissiveMap is multiplied by emissive and emissiveIntensity, so set emissive to white or the intended tint before judging the texture.

Step 3: Prove self-illumination before adding bloom

Disable bloom temporarily and darken the ordinary scene light. The mapped pixels should stay visible while non-emissive parts of the material become dark. If that test fails, remain in the material and texture layer; post-processing cannot repair a missing shader signal.

Step 4: Raise shader intensity into HDR

An 8-bit PNG usually stores closed-range display color, not the open-range brightness that drives HDR bloom. Keep the texture readable and raise the renderer-side emissive multiplier. In the PLAYTEX AI reference, emissiveIntensity 4.0 crosses a bloom threshold of 1.0 without baking a halo into the source image.

Step 5: Enable bloom and tune its threshold

Bloom is a post-process that spreads sufficiently bright pixels after material shading. Enable the post stack, confirm it renders to the final camera, then adjust threshold, strength, and radius in that order. A threshold above the emissive luminance produces no halo even when the surface itself is bright.

Step 6: Lock exposure and decide whether you need real light

Hold tone-mapping exposure at one known value while comparing states. After the halo works, restore the production exposure. If the requirement is light on nearby geometry, add a light, bake emissive lighting, or use a supported GI solution; PBR Engine Converter can then package the completed map set for the target convention.

Check the engine handoff

Fixes that hide the real failure

• Do not paint a soft halo into the emission PNG; the blur will stick to the UVs, mip poorly, and ignore the camera response.
• Do not judge bloom before proving the surface is self-lit with post-processing disabled.
• Do not leave the emissive color black when the shader multiplies that factor by the texture.
• Do not brighten base color to imitate emission; it remains dependent on scene lighting and contaminates material response.
• Do not assume bloom casts light on other objects. It is a post-process, not a light-transport solution.
• Do not compare captures with different exposure, light, camera, or tone mapping and call the difference an emission-map fix.
• Do not mark a color emission PNG as non-color data merely because other PBR masks are scalar; follow the target shader and the way the file was authored.
• Do not turn off mipmaps as the default answer to disappearing distant details; inspect coverage, compression, and edge energy first.

Why is my emission map visible but not glowing?

The self-lit material layer is working, but the halo layer is not. Enable the camera or renderer bloom pass, make sure the emissive result exceeds its threshold, and hold exposure steady while you compare. Do not blur the emission texture itself.

Should an emission map be sRGB or linear?

It depends on how the file was authored and what the shader expects. A typical RGB PNG or JPEG emissiveMap containing display-referred color is sRGB; Three.js r185 documents that common case. A scalar mask, deliberately linear texture, or HDR EXR has a different contract. Label the actual data meaning instead of applying one rule to every filename.

What values make emission bloom?

There is no portable universal number. The rendered luminance must exceed the configured bloom threshold after texture, emissive color, material intensity, lighting-model behavior, tone mapping, and exposure interact. The reproducible Three.js r185 sample on this page uses emissiveIntensity 4.0, threshold 1.0, strength 1.1, radius 0.55, and exposure 1.0 as a test—not as a cross-engine preset.

Does an emission map light nearby objects?

Not by itself. It makes the material self-lit. Nearby illumination needs an explicit light, a bake, or a supported real-time global-illumination path. Bloom only spreads bright pixels in the final image.

Why does the glow disappear when I enter a bright scene?

Exposure adaptation can map the same HDR emission to a dimmer display value when the wider scene becomes bright. Lock exposure during diagnosis, then test the intended material across the supported production exposure range.

Can I use a grayscale mask instead of a colored emission map?

Yes when the shader multiplies that mask by a separate emissive color. Confirm which channel is sampled and whether the texture is treated as scalar data. If the file already stores the intended RGB glow color, preserve that color and use a neutral emissive factor.

Why do thin emissive lines disappear at a distance?

Mip filtering and compression can average a thin bright feature with surrounding black texels until it falls below the bloom threshold. Inspect runtime mips, padding, texture format, and minimum screen coverage before disabling mipmaps or over-brightening the full-resolution source.

What can PLAYTEX AI Emission Map Generator fix?

It can create and refine the emission texture: threshold, edge softness, color, source-color preservation, map intensity, dark preview, and PNG export. It cannot enable an engine material slot, camera bloom, exposure, or GI. Those remain destination-renderer settings.