
OBS Luma Key decides which pixels become transparent from their lightness. It does not recognize a title as foreground. If white lettering and a white background occupy the same lightness range, a threshold that removes the background can also remove the lettering. Adjusting that threshold cannot establish a semantic distinction that the input image does not provide.
Key Takeaways
- Luma Key separates pixels by lightness, not by whether they belong to a word or a background.
- Upper and lower thresholds remove different lightness ranges.
- Use an asset with intentional transparency when the title must remain independent of the background's brightness.
Confirm that brightness is a useful separator
The official OBS Luma Key reference explains that the filter modifies opacity based on lightness. Inspect the source with the filter bypassed. Identify the background to remove and every title stroke that must remain.
If the source is a flattened white-on-white graphic, write down that shared brightness as the central limitation. A preview that loses both regions does not by itself indicate a damaged title or a failed import. The selected filter may be doing precisely the lightness-based operation it is designed to perform.
Diagnose the upper and lower boundaries
- Preserve the unkeyed source or an editable artwork master.
- Identify whether the unwanted background occupies the bright or dark end of the image.
- Inspect Luma Max for removal of brighter pixels and Luma Min for removal of darker pixels.
- Compare the title strokes while changing the relevant threshold.
- Evaluate smoothing only after the required strokes survive the basic separation.
The documentation states that lowering Luma Max removes pixels above it, while raising Luma Min removes pixels below it. Smoothing changes the removal edge; it does not make equal-brightness regions represent different objects. Do not approve an apparently clean background if it was achieved by erasing required parts of the title.
Use the following proposed decision branches before asking for a replacement asset.
| Source condition | Useful comparison | When to stop |
|---|---|---|
| Background is at the bright end and required strokes have a distinct range | Compare the upper boundary, Luma Max | Stop if required strokes disappear with the background |
| Background is at the dark end | Compare the lower boundary, Luma Min | Keep every required dark detail visible |
| Required strokes and unwanted background occupy the same lightness range | Return to the artwork for intentional alpha | Do not expect smoothing to identify the meaning of a letter |
A pale background and a white title are not automatically inseparable: the issue is whether their actual lightness ranges permit the required separation. No threshold numbers in this guide are recommended settings.
Return to the artwork when there is no usable separation
Consider a proposed white wordmark delivered on a pale rectangular background. If keying the rectangle also removes fine letter strokes, ask for the editable artwork or an export with a deliberate alpha channel. Use the cross-tool mask convention check to describe the desired visible and transparent regions to the designer rather than asking only for a different file extension.
A PNG can contain opaque pixels throughout, so the extension alone does not establish that transparency was delivered. Inspect the replacement on a contrasting background before using it in the composition. This is a proposed source-validation check, not a promise that every export process preserves alpha in the same way.
Review the actual title in the finished shot
Make a short candidate recording with the intended background. Inspect fine lettering and antialiased boundaries at the delivery size, including a frame where the title overlaps a lighter part of the scene. Keep a contrasting check background available to reveal any remaining unwanted rectangle.
Accept the title when every required stroke remains visible and the intended transparent area behaves correctly. If that depends on a specific background color, state the limitation in the handoff instead of describing the asset as universally transparent.
Related tasks
- Why Does Resizing an OBS Browser Overlay Crop It Instead of Reflowing Its Layout?
- Why Did Cropping an OBS Source Change Its Framing in Every Scene?
- An OBS preview artwork edit appears live: check whether scenes share the source
Sources and scope
- OBS Luma Key Filter: Luma Key changes opacity by lightness. Lowering Luma Max removes pixels above the selected value; raising Luma Min removes pixels below it. Each boundary has its own smoothing control.
The filter's documented lightness thresholds support the technical explanation. The equal-brightness title scenario and delivery checks are explicit reasoning and proposed procedures, not a claim of a completed compositing test.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.