Bakery: Lightmapping Solution for Unity3D

Bakery is a third-party GPU lightmapper for Unity. Creators often use it when baked lighting quality, iteration speed, or advanced lightmap control matters more than keeping the project on Unity's built-in lighting path.

It can be excellent for VRChat worlds, but it is still a production tool. Bakery will not fix poor light placement, broken UVs, messy static flags, or a scene that is changing every hour.

Recommended Bakery Test

Prove Bakery on one representative scene before committing your whole world to the workflow.

  1. Mark the right geometry Static and confirm lightmap UVs are valid.
  2. Add Bakery light components to the lights you want Bakery to bake.
  3. Bake a small test area, then inspect lightmaps, file size, and VRChat build behavior.
VRChat note

For VRChat worlds, baked lighting is usually a performance-friendly path, but you still need to test the uploaded world. Confirm that lightmaps are included, materials respond as expected, and Android or Quest targets stay within your performance budget.

Playlist Companion

This companion video focuses the page back on Bakery-specific workflow, so use it alongside the setup and evaluation checklist below.

Bakery lightmapping workflow

Quick follow-up reference

When Bakery Is Worth Considering

Bakery is usually worth a serious test when:

  • the scene depends heavily on baked lighting quality
  • Unity's built-in lightmapper is too slow for your iteration loop
  • you need more control over lightmap groups, bake settings, or output
  • the world has a stable layout and is ready for lighting polish
  • the team understands how to maintain a third-party lighting workflow

It is less useful during early blockout, when walls, rooms, and major assets are still moving around. Bake workflow decisions are much easier after the world structure settles.

Bakery Vs Unity Built-In Baking

Choice Good fit Watch out for
Unity built-in lightmapping Beginner projects, simple worlds, teams avoiding extra tools Bake times or quality controls may feel limiting on larger scenes
Bakery Production worlds, frequent bake iteration, creators comfortable with a custom baker Requires setup discipline, correct components, and tool-specific troubleshooting
No baked lighting yet Early layout, greybox, fast iteration The scene may not reveal final mood or VRChat performance until later

Do not choose Bakery just because it sounds advanced. Choose it because it improves the real scene you are making.

Scene Setup Checklist

Before baking with Bakery, check the basics:

  1. Static world geometry is marked Static or otherwise configured for lightmapping.
  2. Meshes have usable, non-overlapping lightmap UVs.
  3. Imported models have Generate Lightmap UVs enabled when needed.
  4. Lights intended for Bakery have Bakery light components, such as Bakery Direct Light where appropriate.
  5. Materials and shaders are compatible with the lighting result you expect.
  6. The scene is saved and source-controlled before the first major bake.

Bakery and Unity light components are not the same thing. If you only configure a normal Unity light, Bakery may not bake it the way you expect.

Lightmap UVs Matter

Lightmaps need clean UV space. If UVs overlap or are compressed badly, the bake can show:

  • dark patches
  • bright seams
  • shadow leaks
  • blurry baked detail
  • tiny objects wasting lightmap space
  • different meshes receiving inconsistent lighting

For imported assets, check the model import settings and generate lightmap UVs if the asset does not already include a proper lightmap UV channel. For custom models, unwrap deliberately instead of hoping the bake will hide the problem.

Lightmap Groups And Resolution

Bakery lightmap groups let you control how objects are grouped and baked. This can be useful when a VRChat world has different areas with different lighting needs.

Use groups to think about:

  • high-detail rooms that deserve more lightmap resolution
  • background areas that can use less resolution
  • large floors or walls that need consistent texel density
  • props that can share simpler settings
  • memory and build-size impact from too many high-resolution lightmaps

More resolution is not always better. Oversized lightmaps can increase download size, memory use, and platform pressure.

VRChat Build Checks

After a Bakery bake, test the result as a VRChat world workflow, not just as a Unity editor screenshot.

Check:

  • lightmaps are present after upload or local build testing
  • the world is not unexpectedly dark in VRChat
  • mirrors and reflective areas still read correctly
  • baked lighting works on the target platform
  • Android or Quest builds do not rely on unsupported shader behavior
  • file size and texture memory are still reasonable

If the scene looks correct in Unity but wrong after upload, stop and verify that the lighting data, lightmap textures, materials, and platform-specific shader path are all included correctly.

Common Bakery Mistakes

Switching before the scene is ready

If the layout changes constantly, every lighting pass becomes disposable. Get the room shapes, major props, and sightlines stable first.

Baking without checking UVs

Bad lightmap UVs create bad lightmaps. The baker can calculate lighting, but it cannot make messy UV unwraps magically production-ready.

Forgetting Bakery-specific light components

Bakery has its own light components and workflow. Match or configure the Bakery lights intentionally instead of assuming normal Unity light settings transfer perfectly.

Raising resolution instead of fixing the scene

Higher lightmap resolution can hide some softness, but it will not fix poor light placement, bad materials, or broken UVs. It also increases memory and build size.

Not testing in VRChat

The Unity editor is not the final runtime. Always check the world through the VRChat SDK workflow before trusting the bake.

Practical Evaluation Workflow

Use this process before committing the whole project to Bakery:

  1. Pick one representative room or scene section.
  2. Bake it with Unity's built-in lightmapper.
  3. Bake the same section with Bakery.
  4. Compare bake time, visual quality, artifacts, build size, and setup friction.
  5. Upload or locally test the result through the VRChat SDK path.
  6. Keep Bakery only if it clearly improves your actual workflow.

That gives you evidence instead of a tool-choice guess.

Help! My Bakery bake has black or broken areas.

Check static flags, Bakery light components, lightmap UVs, material compatibility, and whether the affected object is assigned to a sensible lightmap group.

Help! The bake looks good but the world is too large.

Lower unnecessary lightmap resolution, simplify background areas, review texture compression, and avoid giving every surface premium bake settings.

Help! Lighting works in Unity but not after VRChat upload.

Verify that lightmap textures and lighting data are included, then test platform-specific shaders and materials. A Unity editor preview can hide upload or platform issues.

Help! I do not know whether Bakery is worth buying or learning.

First finish a small baked-lighting test with Unity's built-in tools. If bake quality or iteration speed is still the bottleneck, then Bakery is a better-informed next experiment.

Bakery Unity FAQ

What is Bakery in Unity?

Bakery is a third-party GPU lightmapper for Unity. It is used to bake lighting into textures so static scenes can look richer without relying on expensive real-time lights.

Is Bakery good for VRChat worlds?

It can be, especially for stable worlds that need polished baked lighting. It still requires clean UVs, sensible lightmap settings, platform testing, and normal VRChat optimization discipline.

Should I learn Unity lighting before Bakery?

Yes. Learn the basics of lights, static objects, UVs, lightmaps, and testing first. Bakery is easier to judge when you already know what a normal Unity bake is failing to solve.

References

Best Related Pages

Final Advice

Bakery is most valuable when your world is already stable enough for a serious lighting pass. Learn the fundamentals, prepare clean UVs and static geometry, test one representative scene, then decide whether Bakery earns its place in the project.

Related Navigation

Bake Workflow

Evaluate Bakery Before You Commit The Whole World

Bakery can be excellent for VRChat lighting, but test it on a representative area before committing the whole world to that bake workflow.

Suggested Order

  1. Prepare the scene first Fix static flags, lightmap UVs, material assignments, and major layout changes before comparing bake tools.
  2. Bake one representative area Use a small test section to compare quality, iteration time, lightmap count, and file size.
  3. Validate inside VRChat Check uploaded lighting, mirrors, avatars, Android or Quest targets, and real player visibility before scaling the workflow.

Common Questions

Should beginners start with Bakery?

Usually no. Learn Unity baked lighting first, then test Bakery when bake quality, iteration speed, or production control is a real bottleneck.

Does Bakery automatically make a VRChat world faster?

No. Baked lighting can help runtime performance, but lightmap size, UVs, materials, and uploaded behavior still need testing.