Batch Processing

Select files or a folder, check auto grouping results, then export one ZIP report.

Folder API unavailable, fallback to file upload.
Batch Settings

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

Auto Grouped Tasks

No groups yet. Please load files first.

Texture Batch Packer

Batch build ORM/RMO textures from AO, Roughness and Metallic maps with auto grouping and manual corrections.

What this batch packer covers

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.

Batch workflow expectations

  • Source maps: AO, roughness, metallic, and similar grayscale textures that can be grouped by filename.
  • Processing model: rule-based matching, manual correction, and ZIP export for grouped outputs.
  • Best fit: production cleanup, asset ingestion, and high-volume material preparation.

Typical batch scenarios

  • Prepare packed textures for a large material library where filenames already follow predictable patterns.
  • Normalize incoming texture sets from outsourced or scanned assets before they enter a game pipeline.
  • Run the same packing rules across many folders and export one ZIP package for review or handoff.

Related tools

Batch packing FAQ

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.

Can I review grouping results before export?

Yes. The batch workflow is designed around automatic grouping plus manual correction before the final ZIP is generated.

What kind of pipeline benefits most from this page?

This page is best suited to production pipelines that receive many AO, roughness, and metallic maps and need consistent packed outputs.