Migrating from Post Manager

LayerWise replaces Pulze Post Manager, rebuilt from scratch as a modern Photoshop plugin. It does everything Post Manager did, and your PSDs and templates keep working.

​

What’s the same

• The three render engines: V-Ray, Corona and FStorm, with the same element lists (now extended with newer passes).
• The same two workflows: Create new document (Template Builder in Post Manager) and Update renders (Element Replacer), including Merge as regions.
• The same eight built-in templates, and the same .pmt template files.
• The same multimatte nametags (#Wood#Glass#Stone) and [LUMA] masks.
• The same tools, and the same settings.
• Your cloud templates: LayerWise reads and writes the same cloud templates as Post Manager.

PSDs made with Post Manager can be updated with LayerWise as they are.

​

What’s better

• Updates keep full resolution. When it fits a larger render into an old layer’s footprint, LayerWise scales the smart object instead of baking it, so full-resolution contents, linked files, smart filters and layer styles all survive.
• Masks follow the new renders. Nametags are read from the new multimatte’s file name, so renamed tags or renamed layers no longer break mask updates.
• The mask options do exactly what they say. Update existing only updates, Create new only creates.
• Multichannel EXR splitting is built in and works the same on Windows and macOS.
• A template editor, a default template per engine, and Duplicate and edit for any template.
• Refresh merged layer leaves your clipboard alone.
• AI assistant support.
• Free, with sign-in only. No license tiers, no license server.
• Many small Post Manager bugs are fixed (for example ruler units left changed, masks switched on after a scan, stray helper layers).

​

Bring your templates along

Settings and custom render elements don’t move over automatically. Set them again in Settings and Render elements. Templates that use custom elements offer to add them on import.

​

Names that changed