When should I use the batch packer instead of the single packer?
Use batch mode when many texture sets follow similar naming rules and you want to reduce repetitive manual packing work.
Select files or a folder, check auto grouping results, then export one ZIP report.
Supported vars: {source}/{group}, {channel}/{mode}, {index}, {date} (YYYYMMDD).
Preview: robot_arm_packed_orm
Rules support comma-separated keywords and /regex/. Click "Apply Rules" after edits.
Case 1: robot_arm_ao.png + robot_arm_roughness.png + robot_arm_metallic.png => group=robot_arm
Case 2: /_(ao|rough|metal)$/ can match robot_01_metal.png
No groups yet. Please load files first.
Batch build ORM/RMO textures from AO, Roughness and Metallic maps with auto grouping and manual corrections.
This batch page is for teams that need repeatable texture packing across multiple assets. It focuses on grouping AO, roughness, and metallic maps, applying rule-based matching, and exporting a structured result set without manually rebuilding each packed texture one by one.
Use the single-file packer to validate one material set before scaling to batch mode.
Generate baseline PBR maps from one diffuse texture, then scale the packing workflow in batch mode.
Pair batch extraction with batch packing when source textures need to be split before regrouping.
Open the extractor when you need to inspect or isolate channels before building packed outputs.
Use this guide to align the batch export layout with the exact channel order your shader expects.
Use this guide to bridge single-image PBR map generation with repeatable batch packing rules.
Use batch mode when many texture sets follow similar naming rules and you want to reduce repetitive manual packing work.
Yes. The batch workflow is designed around automatic grouping plus manual correction before the final ZIP is generated.
This page is best suited to production pipelines that receive many AO, roughness, and metallic maps and need consistent packed outputs.