
Deliver the Aseprite image together with slice metadata when a button needs a defined stretchable center or pivot. A PNG crop shows the pixels but does not by itself explain the nine-slice center and placement anchor. Verify that the receiving application reads the exported data using the same slice identity.
Key Takeaways
- Slice bounds, nine-slice center and pivot are separate properties.
- Exporting each slice as an image differs from exporting slice metadata.
- The receiver must explicitly support the intended data.
Specify the receiving contract first
Ask the implementer which image, metadata format and coordinate conventions their interface system expects. Do not assume that every engine imports Aseprite slice data automatically.
The Aseprite Slices manual documents slice bounds, an internal nine-slice rectangle and a pivot. Its export section describes JSON output. The command-line reference also illustrates slice bounds, center and pivot in metadata.
- Select the Slice tool with Shift+C and mark the intended button region.
- Double-click the slice to inspect its properties.
- Name it clearly and define the required bounds, internal center and pivot.
- Export the sprite-sheet image with JSON output enabled, or use the documented data-export workflow.
- Confirm that the image and metadata reach the receiver as one identified version.
Preserve the editable master so the stretchable region can be revised without reconstructing it from a flat export.
A hypothetical resizable-label check
Suppose a client needs the same button artwork at narrow and wide sizes. The center can be designed for stretching while the border treatment remains visually controlled. The pivot supplies a separate placement reference; it is not merely another name for the center rectangle.
Give the receiver two proposed test sizes and an agreed alignment point. Check corners, border thickness, lettering and anchor placement in the actual interface. These are acceptance scenarios, not claims that a particular renderer has been tested.
Inspect data independently from cropping
The Affinity slice-source guide explains why different slice creation methods can include different pixels. This handoff adds semantic slice information that remains necessary even when the crop is visually correct.
Compare the JSON's slice name, frame key, bounds and applicable center or pivot with the source properties. Do not use another version's metadata simply because the filenames look similar.
Accept when the receiver uses the intended pixels and honors the required stretch and anchor behavior. If it ignores those properties, agree on an importer or another supported handoff format. A successful PNG export cannot establish that the receiving application interprets nine-slice metadata.
Related tasks
- Why Does My Affinity Photo 2 Slice Export Leave Out the Background?
- What Is the Difference Between an Editable Artwork Master and a Flat PNG?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
Sources and scope
- Aseprite Slices: Slice bounds, internal nine-slice center, pivot, JSON output and separate slice-image export.
- Aseprite Command Line Interface: list-slices: Slice metadata example includes frame key, bounds, center and pivot.
Documentation-based guidance. Scenarios, worksheets and acceptance procedures are proposed or hypothetical; no hands-on test, benchmark, search-volume measurement or AI-citation ranking is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.