Palette Index Remapping Tool
Remap indexed palette data through an explicit old-to-new index table; many-to-one mappings are allowed and destinations are caller-defined.
Description
Remap indexed palette data through an explicit old-to-new index table; many-to-one mappings are allowed and destinations are caller-defined.
A palette index map can represent reordering or many-to-one merging. It need not be a permutation.
When to use this tool
Remap indexed palette data through an explicit old-to-new index table; many-to-one mappings are allowed and destinations are caller-defined.
- Prepare the supplied indexes, mapping fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter indexes, mapping. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.indexes. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require mapping values from 0 to 127 and every input index inside mapping length. Return mapping[index] for each occurrence, preserving sequence order.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| indexes | indexes. | List of finite numbers; at most 128 entries |
| mapping | mapping. | List of finite numbers; at most 128 entries |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.indexes | The indexes list in the ordering and representation described above. |
{
"input": {
"indexes": [
0,
1,
0
],
"mapping": [
2,
0
]
},
"output": {
"result": {
"indexes": [
2,
0,
2
]
}
}
}Limitations and assumptions
- The tool does not inspect a destination palette or prove mapped indexes fit its size. Duplicate mapping targets are allowed.
- Palette records contain string id/name and exactly four RGBA bytes from zero through 255; at most 128 records are accepted. Duplicate IDs or names remain allowed unless this operation explicitly audits or rejects them.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Use actual rendering or a color-managed workflow when comparing perceived color and transparency. Index changes need corresponding updates to their consumers; name and role checks do not establish visual accessibility.
References
Similar or alternative tools
- Palette Adjacent Repeat Audit
Audit adjacent exact RGBA palette repeats, excluding RGB-only matches whose alpha differs; caller ordering is preserved.
- Palette Alpha Presence Summary
Count transparent, opaque and partially transparent RGBA palette byte entries; no compositing or color-space conversion.