Overview
ZBrush handles polygon counts that other applications will not attempt. Sculpting at tens of millions of polygons is normal here, which is why character, creature and collectable work runs through it, and why the detail passes for film and games are almost always done in this application before anything is retopologised and baked.
The toolset is unusual and takes a while to learn, but the reason people stay is that it removes the modelling stage from sculpting. DynaMesh reconstructs topology on the fly as a form is pushed around, sculptris style dynamic subdivision adds density only where it is needed, and ZRemesher produces a usable animation ready mesh from a sculpt without hand retopologising it.
Around the sculpting sit the pieces that finish a job. Polypainting applies colour directly to vertices with no UV work, the boolean system builds hard surface parts cleanly, insert brushes and array systems generate repeated detail, UV master unwraps automatically, and the decimation and export tools produce a mesh at whatever budget the target pipeline needs.
What it does well
Sculpting at scale
Tens of millions of polygons handled interactively, with a brush engine that stays responsive at full density.
Dynamic topology
DynaMesh rebuilds a mesh as it is deformed, and dynamic subdivision adds density only where the sculpt needs it.
Automatic retopology
ZRemesher produces clean quad topology from a sculpt, with guide curves and density painting for control.
Hard surface tools
Live booleans that preview before committing, plus panel loops, deformers and insert meshes for mechanical work.
Polypaint and export
Colour painted directly on vertices with no UVs needed, automatic unwrapping, decimation and map generation for export.
Changes in this build
- Brush engine performance improved at very high polygon counts.
- ZRemesher updated with better edge flow around creases and hard edges.
- New deformer set for symmetrical and radial shaping.
- Live boolean preview made faster on dense meshes.
- Interface layout presets reorganised with a searchable menu.
What is in the package
- ZBrush offline installer, 64-bit
- Full brush, alpha and material library
- Retopology and UV modules
- Starter project and mesh library
- Multilingual interface files, 5 languages
System requirements
| Processor | Intel or AMD 64-bit, 6 cores or more recommended |
| Memory | 16 GB minimum, 32 GB or more for dense sculpts |
| Graphics | Any GPU with a current driver, the sculpting engine is CPU bound |
| Storage | 12 GB free plus project space |
| Display | 1920 x 1080 minimum, tablet strongly recommended |
| System | Windows 10 or Windows 11, 64-bit only |
Installation
- Extract the archive to a local drive.
- Install the tablet driver first if you are using one.
- Run setup and choose the interface language.
- Set the scratch and project folders on a fast drive at first launch.
- Load a sample project once so the brush and material caches build.
Before you start
Memory is the practical ceiling on sculpt density, not the GPU. This one wants RAM.
Save incremental versions, a dense sculpt is not something to lose to a single overwritten file.
Turn off the update check to keep the build fixed alongside any plug-ins.
Questions about this title
How dense can a sculpt get?
Tens of millions of polygons on a machine with enough memory, and the brush engine stays usable at that level.
Does it retopologise automatically?
Yes, ZRemesher produces quad topology from a sculpt with guide and density control.
Can it paint without UVs?
Yes, polypainting works on vertex colour and UVs are only needed at export.
Does it export for game engines?
Yes, decimation and map generation produce meshes at whatever budget the target needs.
About this listing
This entry was checked on a clean install of Windows 10 / 11 (64-bit) before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.