ZBrush Tip: ZBrush Projects (.zpr): Bundle Work, Assets, and Session Settings

Today’s tip: use Projects (.zpr) to keep your ZBrush work, resources, and session settings bundled for reliable, portable production.

• What a .zpr actually bundles
  • All loaded Tools/SubTools with subdivision levels and PolyPaint.
  • Imported/assigned alphas, textures, and materials tied to the session.
  • Document settings (canvas size, background), lighting/LightCap, BPR render settings and filters, and scene scale/pivot state.
  • SubTool visibility, masks, polygroups, and many per-session toggles.
• Project (.zpr) vs Tool (.ztl)
  • Use .zpr to freeze the entire working environment for a shot, asset, or look-dev session.
  • Use .ztl to archive a single Tool/SubTool stack for reuse across projects.
  • Tip: Save both—.zpr as the “master context,” .ztl as a portable asset.
• Build a reusable Project template
  • Set Scene scale, Floor grid units, and a neutral MatCap for consistent perception.
  • Dial in BPR: shadows (Angle/Radius), AO, SSS, and a clean LightCap.
  • Load staple alphas/brushes, create core Polygroups, and set SubTool folders.
  • Document size: match your review/render needs to avoid resampling later.
  • Preferences > Config > Store Config for your UI; keep the .cfg with your template.
  • Save as “Studio_Template.zpr” in LightBox/Projects for one‑click starts.
• Keep file sizes healthy
  • Delete unused SubTools, hidden geo, and unneeded layers before saving.
  • Tool > Geometry: lower unnecessary subdivision levels on static pieces.
  • Externalize giant textures you don’t need embedded; reload via Spotlight when required.
  • Preferences > Undo History: consider disabling history saving for final archives.
  • Use Decimation Master for presentation-only copies; keep a full‑fidelity .ztl backup.
• Versioning that survives late changes
  • File > Save As: MyAsset_proj_v001.zpr → v002.zpr at each milestone.
  • Pair with Tool exports: MyAsset_tool_v###.ztl after key topology/detail steps.
  • Add a “_final” only when baked maps have shipped and QA is done.
• Collaboration and hand‑off
  • Keep naming/Polygroups consistent; include readme with scale notes and map settings.
  • Export FBX/OBJ for DCC use, but store the authoritative state in the .zpr.
  • Use GoZ for round‑trips and retain the .zpr as your look‑dev ground truth.
• Recovery safety nets
  • Preferences > QuickSave: set short intervals and sufficient slots.
  • Use QuickSave for WIP; graduate to a named .zpr as soon as direction locks.
  • File > Open Recent for swift reverts; avoid “Save” over your last stable version.
• Common pitfalls
  • Opening a Project replaces your session—save current work first.
  • Massive embeds (4K+ textures, many subtools) balloon save times—trim before archiving.
  • Relying only on .zpr: always keep a parallel .ztl for asset reuse and recovery.

Need licenses, team provisioning, or upgrade advice? Talk to NOVEDGE. Exploring or expanding ZBrush in your pipeline? See NOVEDGE’s ZBrush options for tailored purchasing and expert support.