Palette Used Entry Compactor

Compact a palette to explicitly used entries in original palette order and remap all indexes, retaining old-index provenance.

Description

Compact a palette to explicitly used entries in original palette order and remap all indexes, retaining old-index provenance.

An indexed palette can be compacted to the entries actually referenced, provided the pixel indexes are remapped consistently.

When to use this tool

Compact a palette to explicitly used entries in original palette order and remap all indexes, retaining old-index provenance.

  • Prepare the supplied paletteJson, indexes 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

  1. Enter paletteJson, indexes. Use the exact text syntax, units and index conventions explained below.
  2. Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
  3. Read result.palette, result.indexes, result.oldIndexes. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Validate all indexes against palette size. Sort distinct used source indexes ascending, keep those entries, map each reference into the compact list and return oldIndexes.1

Input fieldMeaning and representationAccepted input
paletteJsonJSON text, entered as one text field. The decoded structure is illustrated below; it is not a separate file.Text
indexesindexes.List of finite numbers; at most 128 entries

For the JSON text fields, the following decoded structures show the example records before they are serialized into input strings. Keep field names, list nesting and value types as shown.

json
[
  {
    "field": "paletteJson",
    "decoded": [
      {
        "id": "a",
        "name": "Red",
        "rgba": [
          255,
          0,
          0,
          255
        ]
      },
      {
        "id": "b",
        "name": "red",
        "rgba": [
          255,
          0,
          0,
          0
        ]
      }
    ]
  }
]
Output fieldInterpretation
resultObject containing the named outputs below.
result.paletteThe palette list in the ordering and representation described above.
result.indexesThe indexes list in the ordering and representation described above.
result.oldIndexesThe old indexes list in the ordering and representation described above.
json
{
  "input": {
    "paletteJson": "[{\"id\":\"a\",\"name\":\"Red\",\"rgba\":[255,0,0,255]},{\"id\":\"b\",\"name\":\"red\",\"rgba\":[255,0,0,0]}]",
    "indexes": [
      1,
      1
    ]
  },
  "output": {
    "result": {
      "palette": [
        {
          "id": "b",
          "name": "red",
          "rgba": [
            255,
            0,
            0,
            0
          ]
        }
      ],
      "indexes": [
        0,
        0
      ],
      "oldIndexes": [
        1
      ]
    }
  }
}

Limitations and assumptions

  • No visually identical entries are merged. Used entries follow old palette order rather than first pixel use, and an empty usage list gives an empty palette.
  • 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

  1. Tool behavior and example: Palette Used Entry Compactor — tool.io

Similar or alternative tools

  • Palette Entry Permutation Tool

    Permute palette entries using output-to-input ordering and report the inverse remapping for existing indexed pixels.

  • Palette Adjacent Repeat Audit

    Audit adjacent exact RGBA palette repeats, excluding RGB-only matches whose alpha differs; caller ordering is preserved.

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies