
Aseprite padding and edge extrusion solve different packaging needs. Padding adds space at defined locations; extrusion duplicates sprite edges by one pixel in a sheet export. Choose them according to the receiving renderer's requirements and inspect the result there rather than assuming either option universally prevents atlas bleeding.
Key Takeaways
- Border, shape and inner padding apply to different regions.
- Extrusion supplies duplicated edge pixels rather than merely more spacing.
- A correct-looking atlas still needs a receiving-renderer check.
Identify the region that needs protection
The Aseprite command-line reference distinguishes border-padding for the whole sheet, shape-padding between frames and inner-padding inside each frame. It defines extrude as duplicating all edges by one pixel for sheet exports.
Record the target renderer's atlas requirements before choosing values. Ask whether it expects empty separation, duplicated edge content or a particular layout. The cited Aseprite page defines exporter behavior; it does not prescribe sampling or mipmap rules for every game engine.
- Preserve the .aseprite source and current export configuration.
- Identify whether the unwanted contribution comes from a neighboring atlas region or another rendering issue.
- Choose the padding location relevant to the intended separation.
- Add extrusion only when duplicated edge content matches the receiving contract.
- Export a separately named image and matching metadata, then test the intended scale and movement.
Keep the options and output version together so the implementer can reproduce the candidate.
A hypothetical icon-atlas comparison
Imagine two brightly colored icons placed close together in an atlas. Prepare candidates that change only the relevant spacing or edge-content option. In the receiving interface, inspect the icon border at the scales actually used.
| Export decision | Evidence to inspect |
|---|---|
| Border padding | Space around the outside of the whole sheet |
| Shape padding | Separation between packed frames |
| Inner padding | Border inside each frame's exported area |
| Extrusion | One-pixel duplication along sprite edges |
The table describes documented option roles and proposed observations, not measured rendering results.
Keep pixel-art grid quality separate
The strict pixel-grid guide concerns block consistency and scaling of the artwork itself. An internally clean sprite can still need an appropriate atlas package. Conversely, extrusion cannot repair a soft or incorrectly drawn source silhouette.
Do not crop off an exported border without checking how the receiver interprets its rectangles. Keep image and data versions matched.
Accept when the intended renderer shows clean boundaries with the required layout and no unwanted neighboring content. If bleeding remains, inspect the receiver's texture sampling and atlas interpretation using its current documentation. Increasing every padding value blindly can waste space without identifying the actual cause.
Related tasks
- Is a Photo-to-Pixel-Art Effect the Same as a True Pixel-Perfect Image?
- Why Does ImageMagick Smush Ignore the Transparent Padding Around My Assets?
- Why Does My Transparent PNG Look Tiny Despite Its Large Pixel Dimensions?
Sources and scope
- Aseprite Command Line Interface: border-padding, shape-padding and inner-padding affect different regions; extrude duplicates all sprite edges by one pixel for sheet export.
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.