Substance Bridge

Texture palette

Getting a ZBrush sculpt into Adobe Substance 3D Painter has traditionally been a multi-step, manual process. Artists had to export separate low-poly and high-poly files, import them into Substance, configure baking settings, and run the bake, all by hand. Substance Bridge eliminates that entire workflow. You configure your settings, click Send to Painter, and Substance opens with your asset loaded, UVs mapped, and all maps baked automatically if you choose. No more manual file exports or dragging FBX files between applications.

If you have used GoZ to send models to Cinema 4D, Maya, or 3ds Max, the experience is similar: Click one button, and the model appears in the target application. The difference is that Substance Painter was built for game industry workflows and has specific requirements that GoZ was never designed to handle. Every mesh must have UV coordinates, and viewing sculpt detail requires baked texture maps. Substance Bridge manages all of that automatically.

The Auto-Bake Workflow

This is the workflow most used by artists. Auto-Bake sends both the lowest and highest subdivision levels of your model to Substance, then automatically runs all of Substance's baking algorithms, generating normal maps, ambient occlusion, curvature, and other detail maps. You end up with a low-poly model that looks like your full-resolution sculpt, ready for texturing.

1. Open the Substance Bridge sub-palette in the Texture palette.
2. Set Subdivision Level to send both the lowest and highest levels of your subdivision stack. Substance needs both: the low-poly mesh is what you actually see and paint on in Substance, and the high-poly mesh provides the sculpt detail that gets baked into maps.
3. Enable Auto-Bake Maps. Substance will automatically generate normal, ambient occlusion, curvature, and other maps when the model arrives. Without this, you would need to configure and run baking manually inside Substance, which is the exact tedious process Substance Bridge is designed to eliminate.
4. You can enable Smooth Normals if you want faceted meshes to appear smooth in Substance. Game engines smooth tangent normals so that a low-poly mesh looks smooth even though the geometry is faceted, and Substance does the same thing. With this on, your model in Substance will match how it would look in a game engine. With it off, you see the actual faceting of the geometry.
5. If your model has PolyPaint, enable Send PolyPaint to include it. ZBrush converts the PolyPaint into a texture map and applies it as a fill layer in Substance, so you can paint over the top of it and blend with it.
6. Click Send to Painter and choose which SubTools to include: All (every SubTool regardless of visibility), Visible (only SubTools with the eye icon turned on in the SubTool list), or Active (only the currently selected SubTool).
7. Substance 3D Painter launches. The model loads and baking runs.
   
8. Upon completion, your sculpt detail is mapped onto the low-poly geometry. The model is ready for texturing.

How Baking Works

When you view a sculpt in ZBrush, all the fine surface detail (wrinkles, skin texture, striation marks) is physically present in the geometry as millions of polygons. Substance Painter cannot work with that level of geometric complexity the way ZBrush can. Instead, Substance represents sculpt detail through texture maps: normal maps, ambient occlusion, curvature, and others.

Baking is the process of transferring detail from a high-poly mesh onto a low-poly mesh via these maps. Substance compares the two meshes, calculates where the surfaces differ, and writes those differences into maps that the low-poly mesh can display. The result looks like the full sculpt, but the geometry Substance is actually rendering is the lightweight low-poly version.

Before Substance Bridge, this process required artists to manually create two separate export files (one low, one high), import both into Substance, assign them correctly, configure baking parameters, and run the bake. With Auto-Bake Maps enabled and Subdivision Level set to send low and high, Substance Bridge handles all of this in a single click.

Sending Without Baking

You can also send a model without baking by leaving Auto-Bake Maps off and sending only the current subdivision level. This sends the exact mesh currently displayed in ZBrush, polygon for polygon, with no high/low comparison and no map generation.

If you’d like to transfer your raw geometry into Substance Painter for some quick early concept work without baking, you can absolutely do that! Just keep in mind that higher polygon counts may take a little longer to process, and performance will vary depending on your system specs. Starting with moderately sized meshes can help ensure a smooth experience, and you can always step up to higher counts as your workflow allows.

What to Know Before You Send

Every mesh needs UVs. Substance 3D Painter cannot work with meshes that have no UV coordinates. If your model already has good UVs, leave Force UV Auto-Unwrap off and your hand-made UVs are preserved exactly as they are.

If your model lacks UVs, enable Force UV Auto-Unwrap. This triggers Substance's own UV unwrapping algorithm on its end after the model arrives. It is not ZBrush's UV unwrapping. Substance applies its auto-unwrap to every SubTool that gets sent over. If you have invested time in quality UVs, you'll generally want to keep this off and let your existing UVs pass through untouched.

Force UV Auto-Unwrap is a global setting. When enabled, every SubTool in ZBrush, including those that already contain UVs, will have its existing UVs removed, and Substance 3D Painter’s automatic UV unwrapping will be applied to each SubTool.

If a project contains a mix of SubTools with and without UVs, it's recommended to keep Force UV Auto-Unwrap disabled. In this case, ZBrush will send SubTools that already have UVs to Substance 3D Painter with their UVs preserved, while SubTools without UVs will automatically receive Substance Painter’s auto-unwrapped UVs.

Be aware that every send is a full repackage. Each time you click Send to Painter, ZBrush repackages everything and sends it as an entirely new Substance project. If you forgot to include PolyPaint on the first send, you can enable it and send again, but this creates a new project from scratch, not an update to the existing one. There is no way to incrementally update a previously sent project.

Texture Sets control how UV space is divided. Substance Painter's entire UI is built around texture sets. Each mesh gets a texture set that maps to its UV coordinates in 0-to-1 space, and painting happens within that texture set. Per SubTool creates one texture set for each SubTool, which is the simpler option. Per PolyGroup creates one texture set per PolyGroup within each SubTool, giving you finer control over material assignments.

Export Options Reference

Quick reference for all settings in the Substance Bridge sub-palette.

Option	What it does
Send to Painter	Sends the model to Substance 3D Painter with the current settings applied. Each click creates a new Substance project from scratch.
Send PolyPaint	Converts PolyPaint into a texture map and applies it as a fill layer in Substance, where you can paint over it and blend with it.
Smooth Normals	Smooths tangent normals on export so faceted meshes appear smooth in Substance, matching how game engines render them. Turn off to see the actual faceting of the geometry.
Auto-Bake Maps	Runs Substance's baking algorithms automatically after the model arrives, generating normal maps, ambient occlusion, curvature, and other detail maps from the high/low mesh comparison.
Force UV Auto-Unwrap	Triggers Substance's UV unwrapping algorithm on every SubTool that arrives. Leave off if your model already has good UVs because this overwrites them.
Subdivision Level	Controls which subdivision levels are sent. Current sends only the displayed level. Low & High sends both the lowest and highest levels for baking and is the recommended option for most workflows.
Texture Sets	Controls how UV space is divided in Substance: Per SubTool (one texture set per SubTool) or Per PolyGroup (one texture set per PolyGroup within each SubTool).
All	Sends every SubTool regardless of visibility. Whether the eyeball is on or off, everything gets sent.
Visible	Sends only SubTools with the eye icon turned on in the SubTool list.
Active	Sends only the currently selected SubTool.