When is the batch extractor better than the single extractor?
Batch mode is better when you need the same channel export logic across many files instead of inspecting each texture separately.
Import files/folder, choose channels and format, then run extraction.
Supported vars: {source}/{group}, {channel}/{mode}, {index}, {date} (YYYYMMDD).
Preview: robot_arm_red
No tasks yet. Please load files first.
Batch extract RGBA channels from multiple textures and export one structured ZIP package.
This page is designed for high-volume channel extraction. It helps teams load multiple textures, choose which channels to export, and create a repeatable output package for review, downstream automation, or re-entry into another texture processing step.
Use the single-file extractor when you want to inspect one texture before scaling up.
Switch to batch packing when extracted masks need to be regrouped into packed outputs.
Use the packer to build new ORM or custom material textures after extraction.
Open the guide when you need a conceptual explanation of alpha masks before running the batch workflow.
Batch mode is better when you need the same channel export logic across many files instead of inspecting each texture separately.
The page prepares a structured ZIP output so the extracted channels can be reviewed, archived, or passed into another texture workflow.
Yes. A common workflow is to extract channels first, validate them, and then repack them into ORM, RMA, or project-specific layouts.