Unity Lighting Search - First Indie Complex Scene Keep Hold 2026

If you searched unity lighting search after Unity 6.5 landed, the useful question is not “does Unity finally have a better Light Explorer?” You need a keep/hold: can a small team open Lighting Search tonight, run one pre-built query, bulk-edit a shared light property, peek at the Lightmaps provider, save a project query asset, and decide whether Lighting Search becomes the gold path for complex scenes while Light Explorer stays available as a hold?

This URL owns that evening. It is not the Unity 6.5 BIRP deprecation keep/hold (pipeline clock). It is not Unity Mesh LOD (import LODs). It is the Search-powered lighting table keep/hold for busy scenes.

Why this matters now

Unity’s Introducing Lighting Search announcement (May 12, 2026; ships with Unity 6.5) describes a table-based window built on the Search framework: find lights, mesh renderer GI flags, reflection probes, Adaptive Probe Volumes, baking sets, emissive materials, and lighting settings — then edit cells with multi-select. The Unity Manual - New in Unity 6.5 confirms the window accelerates lighting workflows and states that Light Explorer remains available. Mid-August studios still hunting “which lights cast shadows in additive scene B?” are the audience.

Why August 17, 2026 still needs this:

1. 6.5 upgrade threads fixate on BIRP deprecation — Lighting Search gets buried.
2. Light Explorer habits die slowly; teams need a one-evening proof, not a feature list.
3. Complex multi-scene projects need an honest multi-scene note from day one.
4. Catalog already owns BIRP and Mesh LOD; this URL owns Lighting Search vs Light Explorer.

Who this is for

Time: 45–75 minutes on a disposable or branch scene.
Prerequisites: Unity 6.5 (6000.5.x) or newer with Lighting Search present, a scene with more than a handful of lights, and permission to edit intensity on a throwaway set of lights. If your production pin is still 6.4, run this evening only after a disposable 6.5 project opens the menu — do not mix version FOMO into a live ship branch.

Plain vocabulary

Lighting Search

Editor window at Window → Rendering → Lighting Search. Search-framework table for lighting-related objects and data with editable cells and bulk multi-edit.

Light Explorer

Older lighting management window. Still available in 6.5 per the Manual. Use as comparison baseline tonight — do not uninstall muscle memory until G6.

Pre-built queries

Tree panel entries (100+ covered in the announcement) for lights, mesh renderers, probes, APV, baking sets, emissive materials, lighting settings. Start from a query; tweak; save.

Lightmaps provider

Search provider added with Lighting Search: tabulated lightmaps with thumbnails, metadata, exposure slider (−16 to +16 EV), and preview actions.

Query assets

Saved Search Query assets — user (preferences) or project (version-controllable). Project queries are the keep/hold artifact leads care about.

Lighting Search vs Light Explorer (decision table)

KEEP Lighting Search means: it becomes the default for complex-scene lighting audits.
HOLD Light Explorer gold means: do not force a studio rewrite of docs until G2–G4 pass and a lead signs the Discord brief.

Beginner path - one evening (G1–G6)

G1 - Confirm Unity 6.5 and open the window (10 min)

1. Help → About Unity — confirm 6000.5.x (or newer that includes the window).
2. Open Window → Rendering → Lighting Search.
3. Screenshot the empty/default state for the receipt.

PASS: Window opens.
FAIL: Menu missing — wrong Editor version; stop and upgrade a disposable project first (do not mix with production BIRP panic).

G2 - Run one pre-built Lights query (10 min)

1. In the left tree, open a Lights pre-built query.
2. Confirm your scene lights appear in the table.
3. Note columns you care about (intensity, mode, shadows, rendering layers — exact columns depend on pipeline/HDRP vs URP).

PASS: At least one expected light row visible.
FAIL: Empty table — wrong active scene, lighting data not loaded, or query filter too narrow; fix scene context before bulk edit.

G3 - Bulk intensity smoke (15 min)

1. Multi-select two or three disposable lights (never production hero keys without a branch).
2. Edit a shared cell (e.g. intensity) once.
3. Confirm Scene view / Game view update.
4. Undo or restore known-good values after the smoke if needed.

PASS: One edit touched multiple selected rows as expected.
FAIL: Only one row changed, or Editor hiccup — note version + query name; file as PARTIAL, do not declare KEEP gold.

G4 - Lightmaps provider peek (10 min)

1. Switch to a Lightmaps query / provider view.
2. Confirm thumbnails and metadata columns appear if lightmaps exist.
3. Nudge the exposure slider; open preview if available.

PASS: Provider usable or honest SKIP (“no baked lightmaps in this scene”).
FAIL: Crash / unusable — HOLD Lighting Search as gold; keep Light Explorer; file bug notes.

G5 - Save a project query asset (10 min)

1. Tweak the Lights query filter to something studio-useful (e.g. “shadows on” / directional only — use UI as shown).
2. Save as a project Search Query asset under Assets/Editor/LightingSearch/ (or your studio convention).
3. Commit path on the smoke branch.

PASS: Asset exists and reopens the same filter.
FAIL: Only user-preference save — note it; project assets are the KEEP signal for teams.

G6 - Keep / hold decision

Developer depth - what the announcement actually unlocks

From the official Discussions post and Manual summary, treat these as first-class smoke targets:

Lights

Search and edit light types (including HDRP shapes where applicable). Intensity with unit conversion, color temperature, rendering layers, HDRP shadow/contact/ray tracing fields when present. Indie URP scenes still benefit from intensity/shadow/layer bulk edits.

Mesh Renderers

GI contribute/receive, reflection probe usage, rendering layers — the silent killers in additive loads.

Reflection Probes / Adaptive Probe Volumes

Mode and resolution filters; APV global/scene/local and spacing. If you do not use APV, SKIP with reason.

Baking Sets / Lighting Settings

Probe spacing, renderer thresholds, backend, sample counts — bake owners should smoke once even if art only wanted “find my spots.”

Materials (emissive)

Find emissives by intensity/mode — useful before a bake when someone “temporarily” left emission at 50.

Multi-scene honesty

Forum feedback asked for additive multi-scene clarity. Unity staff noted multi-scene testing. Your receipt should still record:

• Which scenes were loaded
• Which scene was active
• Whether lighting rows matched expectations

If additive lighting depends on active scene (a known Unity footgun), Lighting Search does not erase that design — it only helps you see the data. Pair with conscious active-scene discipline.

KEEP / HOLD matrix for leads

CapEx four-liner

1. Status: Evaluated Unity 6.5 Lighting Search on branch lighting-search-smoke.
2. Evidence: G3 bulk intensity PASS (or PARTIAL) + dated screenshot of query tree.
3. Ship default: Lighting Search is KEEP for complex-scene audits; Light Explorer remains available fallback per Manual.
4. Trigger to rewrite all lighting SOPs: Two production scenes pass G2–G5 with project query assets checked in.

Paste the four-liner into diligence notes so art leads and producers share one decision sentence before rewriting lighting SOPs studio-wide.

Discord-ready brief

Unity Lighting Search (6.5) - evening receipt
Path: Window > Rendering > Lighting Search
Smoke: one Lights query + bulk intensity on disposable lights
Also: Lightmaps provider peek; save project query asset
Light Explorer still available - not deleted
KEEP Search for complex scenes / HOLD forcing SOP rewrite until lead signs
Not the BIRP night - separate receipt

Creators can drop that block into Discord without translating gate IDs. Leads should pin it beside the project query asset path.

Failure modes

Worked example - additive dungeon

Wrong plan: Upgrade to 6.5 for BIRP reasons, ignore Lighting Search, continue selecting lights one-by-one in Hierarchy for a 60-light dungeon.

Right plan:

1. Disposable duplicate of the dungeon scene on a smoke branch.
2. G1–G3: bulk-normalize temporary fill lights’ intensity.
3. G4: confirm lightmap thumbnails still make sense after intensity smoke (or SKIP if realtime-only).
4. G5: save Dungeon_ShadowCasting_Lights.query as project asset.
5. G6: KEEP Lighting Search for weekly lighting audits; update art SOP week-two.

Relation to Surface Cache / GI experiments

If your real pain is URP GI preview features, pair later with Surface Cache GI preview keep/hold. Tonight is inventory and batch edit, not a GI algorithm adopt/hold.

Format ladder

Week-two after KEEP

1. Port two more project queries (emissives; shadow-casting only).
2. Train one artist on G2–G3 without an engineer present.
3. Add Lighting Search path to onboarding doc; keep Light Explorer as fallback paragraph.
4. Re-smoke after the next 6.5.x patch if G4 was flaky.
5. Do not merge this receipt into BIRP migration CapEx language.

HDRP vs URP note (same window, different columns)

Lighting Search is pipeline-aware in the sense that HDRP-specific fields (contact shadows, some ray tracing toggles, HDRP light shapes) appear when those components exist. URP projects still get the core win: find lights, bulk intensity, layers, probe usage, emissives. Do not reject the tool because an HDRP screenshot in the announcement looked “too AAA.” Smoke your pipeline.

If a column is missing, check you selected the right query and that the component exists in the loaded scenes — empty columns are not always bugs.

Style of work - lighting lead Monday

1. Open Lighting Search before Hierarchy.
2. Run the studio’s project query asset for “ship lights.”
3. Spot-check three rows visually in Scene view.
4. File PASS/FAIL in the weekly lighting channel with a screenshot.
5. Only then touch bake settings.

This turns Lighting Search into a ritual instead of a one-off feature demo.

Before/after mental model

Before: Expand Hierarchy folders → click each Light → Inspector → hope you did not miss a child prefab instance.

After: Open Lighting Search → Lights query → filter → multi-edit → save query for the next person.

The after path still needs taste. It removes inventory blindness.

Performance honesty

Forum users reported lag in general Search on some versions. If typing freezes the Editor, note it separately from Lighting Search acceptance. Still complete G2–G3; if Lighting Search tables themselves hitch badly on your scene size, HOLD gold and attach Progress window notes (Unity staff asked about background indexing). Complex scenes are exactly when you need the tool — and also when UI cost shows up.

Sample smoke comments (docs only)

// Evening notes - not production code
// 1) Unity 6000.5.x confirmed
// 2) Window > Rendering > Lighting Search
// 3) Pre-built Lights query → multi-select fill lights → intensity 0.8
// 4) Undo after screenshot
// 5) Save project query under Assets/Editor/LightingSearch/

Onboarding card (paste into Notion)

Title: First Lighting Search evening
Goal: Bulk-edit disposable lights + save one project query
Do not: Migrate BIRP or rewrite bake pipelines tonight
Done when: G6 KEEP/HOLD written with active-scene note

Sample receipt (documentation)

{
  "receipt": "unity_lighting_search_keep_hold_v1",
  "as_of": "2026-08-17",
  "editor": "6000.5.x",
  "gates": {
    "G1_window": "PASS",
    "G2_lights_query": "PASS",
    "G3_bulk_intensity": "PASS",
    "G4_lightmaps_provider": "SKIP_no_baked_maps",
    "G5_project_query_asset": "PASS",
    "G6_decision": "KEEP_search_HOLD_explorer_as_fallback"
  },
  "project_query_path": "Assets/Editor/LightingSearch/Dungeon_ShadowCasting_Lights.asset",
  "notes": "Multi-scene: Hub + Dungeon_A loaded; Dungeon_A active."
}

Contractor script

When someone says “Lighting Search replaces Light Explorer, delete the old SOP”:

1. Ask for G3 bulk-edit evidence.
2. Ask whether Light Explorer is still in the Manual for their version.
3. Accept KEEP Search + fallback Explorer.
4. Reject SOP deletion without two production scenes smoked.

Comparison - Hierarchy hunt vs Lighting Search

Accessibility / collaboration angle

Lighting Search helps more than artists:

• Leads can verify “no accidental realtime lights” before a build
• New hires get a project query instead of a tribal Hierarchy tour
• QA can attach a query screenshot to lighting bug tickets

Still pair with human taste checks — a table does not replace looking at the frame.

Company diligence questions

1. Which Unity version first showed Window → Rendering → Lighting Search here?
2. Do we have a project query asset in VCS?
3. Is Light Explorer still documented as available — and kept as fallback?
4. Did multi-scene active-scene notes get filed?
5. Are we stacking this with BIRP migration CapEx? (Should not.)

Prefab and nested light traps

Prefab instances with nested lights are why Hierarchy hunts fail. Lighting Search should surface those rows when queries include the right objects — still verify by selecting a row and confirming the Inspector target is the instance you meant. If a prefab override fight appears after bulk edit, undo, edit the prefab asset deliberately, then re-smoke instances.

Document whether G3 touched scene instances, prefab assets, or both. Mixing those without a note creates “who changed the key light?” Slack archaeology.

Bake vs realtime scope

Lighting Search helps both bake owners and realtime lighting owners, but acceptance tests differ:

Do not call KEEP if you only stared at the table without touching Scene/Game view.

Key takeaways

• Unity Lighting Search (6.5+) is a Search-powered table for lighting data — open via Window → Rendering → Lighting Search (Discussions, Manual What’s New 6.5).
• Light Explorer remains available — KEEP Search does not mean delete Explorer.
• Smoke bulk edit, Lightmaps provider, and a project query asset before rewriting studio SOPs.
• Record active/loaded scenes on multi-scene projects.
• Do not stack with BIRP deprecation or Mesh LOD on the same night.

FAQ

Where is Lighting Search in the menu?

Window → Rendering → Lighting Search per Unity’s announcement.

Which Unity version do I need?

It landed in Unity 6.5. Confirm your Editor build includes the menu item.

Is Light Explorer removed?

No. The Manual states Light Explorer is still available. Use it as fallback until KEEP is earned.

Can I bulk-edit lights?

Yes — multi-select rows and edit shared cells. Smoke on disposable lights first.

What is the Lightmaps provider?

A Search provider for lightmap thumbnails, metadata, and exposure control added with Lighting Search.

Should we migrate BIRP the same evening?

No. Use the BIRP deprecation keep/hold on a separate receipt.

Related to Mesh LOD?

Different tool. Mesh LOD is import-time mesh LODs — see Mesh LOD keep/hold.

Related reading

• Unity Custom 2D Light - First Indie Triangle Provider Keep Hold 2026 — Light2DProvider shapes (not Search bulk edit)
• Unity 6.5 Upgrade Keep Hold - BIRP Deprecation Playbook for Indies 2026
• Unity Mesh LOD - First Indie Import Keep Hold Evening 2026
• Your First Unity Surface Cache GI Preview Evening - URP Keep Hold 2026
• Optimizing Game Performance - Complete Guide
• Unity guide