Last reviewed 7 May 2026

Applies to

Unity baked-lighting workflow Faster lighting iteration GPU lightmapping decisions

Difficulty Intermediate

Switching your baking to GPU in Unity for faster baking times

If your light baking takes too long, switching Unity to GPU lightmapping can speed up iteration a lot. This is most useful when you are repeatedly adjusting lighting, reflection probes, emissive materials, or baked shadows and do not want to wait on full CPU bakes every time.

GPU baking is not always available in every project or on every machine, so the first step is confirming that your Unity version, render pipeline, graphics drivers, and hardware support it properly.

Recommended Setup

Use Progressive GPU to shorten lighting iteration, then still review the final bake for quality, artifacts, and platform cost.

Save the scene and confirm the project has a Lighting Settings asset.
Switch the Lightmapper to Progressive GPU only if the option is available and stable.
Run a low-quality test bake before committing to a full production bake.

VRChat note

For VRChat worlds, GPU baking changes how quickly you generate lightmaps in Unity. It does not make the uploaded world faster by itself; final lightmap size, realtime lights, shaders, mirrors, and Android or Quest targets still need review.

Playlist Companion

This video fits here because it shows the broader lighting workflow that GPU baking is trying to speed up: repeated scene-lighting iteration rather than a one-off final bake.

Lighting - Create Your First VRChat World

Open the video on YouTube

Quick lighting follow-up: Light Your World in Unity - 1 Minute Tutorial

What GPU Lightmapping Actually Changes

Unity's Progressive Lightmapper can run on the CPU or GPU. The end goal is the same: generating baked lighting data for your scene. The difference is where that work happens.

CPU baking is usually more broadly compatible and predictable.
GPU baking is often much faster for iteration.
GPU baking is especially helpful when testing many small lighting changes.
Large or complex scenes can still take time even on the GPU.
If the GPU path runs out of memory or hits a driver issue, CPU baking can still be the safer fallback.

Faster baking does not automatically mean better lighting. It just reduces the time between lighting changes and results.

Quick Decision Table

Situation	Best Move
You are tuning lights repeatedly	Try Progressive GPU for faster preview bakes.
The GPU option is missing	Check Unity version, graphics drivers, hardware support, and project settings before forcing the workflow.
The bake crashes or falls back	Lower bake settings, test a smaller scene, update drivers, or switch back to Progressive CPU.
The lighting has seams or artifacts	Review UVs, lightmap resolution, texel density, samples, filtering, and overlapping geometry.
You are preparing the final build	Compare the final GPU bake visually and keep CPU fallback available if the result is unstable.

Before You Switch

Check these basics first:

Make sure your Unity version supports GPU lightmapping in the way your project needs.
Update your graphics drivers if the option is missing or unstable.
Save a backup or commit your project before changing lighting settings.
Test in a duplicate scene first if your production scene is already heavily tuned.
Close other GPU-heavy apps if your bake is close to the machine's memory limits.
Disable Auto Generate while you are making many lighting changes so Unity does not rebake at inconvenient times.

If your project already has lighting issues, switching to GPU baking will not fix those by itself. It is only changing the baking backend.

How To Enable GPU Baking

In most Unity versions, you can find this in the lighting settings for the scene.

Open Window > Rendering > Lighting.
Find the lightmapping settings section.
Set the lightmapper to Progressive GPU if that option is available.
Disable auto-generate if you want tighter control over when bakes happen.
Start with a small test bake before committing to a full production bake.
Watch the Console for fallback, memory, driver, or lightmap UV warnings.

Unity Lighting window Scene tab showing Progressive GPU as the lightmapper option among other bake settings. — The Scene tab is where you confirm whether the project is baking with the CPU or with **Progressive GPU** for faster iteration.

If you do not see a GPU option, common reasons include:

unsupported Unity version
unsupported GPU or outdated driver
render pipeline or project setup mismatch
running on hardware that does not expose the required features

Best Workflow For Faster Iteration

Do not immediately run your full-quality bake. Use a staged workflow instead.

During setup and testing

lower indirect sample counts
reduce lightmap resolution
bake only the scene you are working on
keep test scenes small
avoid rebaking everything after every tiny edit
lower bounce count or filtering cost temporarily if you only need a rough lighting preview
keep a note of the temporary settings so you can restore final quality later

Before final publish

restore proper lightmap resolution
review shadow quality
check for seams and artifacts
test reflective and emissive surfaces again
inspect generated lightmap textures and total memory impact
verify Android or Quest versions if the world is cross-platform

This gives you fast preview iterations while still preserving a proper final bake for release.

Settings That Affect Bake Time

GPU baking helps, but the scene still determines how much work Unity has to do.

Setting or scene choice	Why it matters
Lightmap Resolution	Higher texel density creates more lighting data to calculate and store.
Max Lightmap Size	Larger lightmaps can improve packing, but they also increase memory pressure.
Samples and bounces	Higher values can improve quality while making bake iteration slower.
Static geometry count	More baked surfaces mean more lightmap work.
Lightmap UV quality	Bad UVs create artifacts that no baking backend magically fixes.
Realtime lights left in the scene	GPU baking does not remove runtime lighting costs.

Common Performance Expectations

GPU baking helps most when:

you are adjusting light positions or intensity often
you are tuning baked spotlights and area lighting
your scene has a moderate amount of baked geometry
your machine has a strong compatible GPU

You may see less benefit if:

your scene is extremely large
memory becomes the bottleneck
the bake repeatedly fails or falls back
the lighting setup itself is inefficient

Common Problems And Fixes

The GPU option is missing

Check your Unity version first. Then update GPU drivers and confirm the machine actually supports the required graphics features.

The bake starts but crashes or fails

This can point to driver issues, memory pressure, or a scene that is too heavy for the current settings. Try lowering bake quality temporarily and test with a smaller scene.

The bake works, but the lighting looks worse

The GPU is probably not the real problem. Review lightmap resolution, UVs, overlapping geometry, emissive settings, and mixed light setup.

Unity Baked Lightmaps tab showing generated lightmap textures after a bake completes. — When the bake completes, inspect the generated lightmaps too. Faster GPU baking still needs sensible resolution and clean inputs if you want good final results.

The bake is still too slow

Reduce what Unity has to calculate. Simplify baked geometry, lower test quality, reduce unnecessary lights, and avoid baking objects that do not need baked contribution.

Unity keeps rebaking at bad times

Turn off Auto Generate and start bakes manually when you are ready. This keeps lighting iteration under your control while you move objects, adjust lights, or fix materials.

Practical Tips For VRChat And VR Scenes

For VR worlds, baked lighting is usually preferred over heavy real-time lighting because it helps performance. GPU baking is useful here because VR creators often need to rebake repeatedly while dialing in ambience.

Keep in mind:

mirrors and special shaders can still affect the perceived result
poor UVs will still create bad bakes
overusing baked detail in tiny props can increase bake cost without much visual gain
final testing should always be done in the actual target platform or upload pipeline
lightmaps add texture memory and download weight, so lower resolution can be better when the visual result still holds up
baked lighting does not replace good scene readability from player eye height

Recommended Approach

Use GPU baking as an iteration tool first. If it is stable on your system, keep using it for day-to-day lighting work. If you hit compatibility problems, fall back to CPU baking for final output rather than forcing a broken workflow.

The real productivity gain comes from shortening the loop between "change a light" and "see the result". That is where GPU baking helps most.

Helpful follow-up pages

Help! I do not know what to optimize first.

Start with the bake inputs: lightmap resolution, static geometry, samples, bounces, realtime lights, lightmap UVs, and the areas players actually occupy.

Help! The scene only slows down in VRChat.

Test with realistic avatars, platform targets, and active world systems. Editor-only testing can miss the costs that appear in real multiplayer use.

Help! Progressive GPU is not available.

Use Progressive CPU for now, then check Unity version, graphics driver updates, hardware support, and whether another project on the same machine can use GPU lightmapping.

Help! GPU baking runs out of memory.

Lower temporary bake quality, reduce lightmap resolution, bake a smaller scene, close GPU-heavy apps, or switch back to CPU baking for the final pass.