# Batch packer mode

**Batch Packer** window is designed to process large numbers of textures simultaneously. It uses a rule-based matching system to identify textures by their filenames and automatically group them into packing sets.

Batch Packer UI processes one output configuration at a time. If you need to pack different texture workflows at once or unpack existing packed textures, navigate to the [**Repack Textures**](/asset-actions/repack-textures.md) section.

<figure><img src="/files/qgJLgxih632QdnPrxKj5" alt=""><figcaption></figcaption></figure>

<sup>*(Example workflow for packing ORM from textures with different naming and format)*</sup>

### Presets

The Presets section contains two buttons:

* **Load Preset** opens a context menu with available presets. Selecting a preset replaces all current Batch Packer settings.
* **Save Preset** saves the current configuration as a reusable Data Asset preset.

To learn more about presets, see the [**Batch Packing Presets**](/presets-and-database/batch-packing-presets.md) section.

### Input List

The Input List acts as a Drop Zone. Select textures in the Content Browser and drag them into this section.&#x20;

Textures in the input list can have two statuses:

* ✓ The texture name was successfully recognized and the texture will be used during packing.
* ⚠ The texture name did not match any rule and the texture will be ignored.

### Channel Rules

This column defines how textures are identified and assigned to each output channel. It contains four independent rule blocks - one for each output channel.

**Semantic Mapping** allows you to select a specific texture semantic for this channel. Texture names will then be resolved automatically using the Semantic Databases configured in Project Settings. TexPacker includes a default database with common PBR texture naming conventions. To learn how to add custom texture semantics, see the [**Semantic Databases**](/presets-and-database/semantic-databases.md) section.

**Manual Mappings** allow you to manually define filename matching patterns for this channel. Wildcards are supported, meaning `*_ORM` matches suffixes only, while `*_ORM*` matches the pattern anywhere in the filename, such as `T_Name_ORM_v1` or `T_Name_ORM2`.

If no wildcard (`*`) is present, the pattern is automatically treated as a suffix match. For example, entering `ORM` is treated as `*_ORM`.

**Adjustments** apply mathematical operations to the extracted channel data before packing.

**Fallback Texture** defines which texture should be used if no matching texture is found for this channel. This is especially useful for channels such as Ambient Occlusion or Roughness, where the default value is typically white instead of black.

Texture groups are determined using the shared base name of matching textures. The base name is the filename with the matched pattern removed. For example, with the patterns `*_R` and `*_AO`, the textures `T_Wood_R` and `T_Wood_AO` both belong to the `T_Wood*` group, while `T_Wood_R_v01` belongs to a separate `T_Wood*v01` group.

When resolving textures for a channel, TexPacker uses the following priority order: \
`Manual Mappings → Semantic Mapping → Fallback Texture`.

### Output

This column displays all generated packing groups, including previews and the textures assigned to each channel.

It also contains the output texture settings. To learn more, see the [**Output Settings**](/output-settings.md) section.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nautilusgs.com/ui-modes/batch-packer-mode.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.