Save the editable project and reopen the exported copy before changing the display or repainting the artwork. Compare both on the same screen at a useful inspection zoom. If the export already differs, focus on export settings; if it matches, keep the file fixed and investigate the receiving app or physical output separately.
Palette conversion, transparent pixels and scaling can each change a pixel design in a different way. Work through those checks with a separate export copy and record the settings. The goal is to locate the first changed version, preserve deliberate pixel choices and avoid compensating in the source for a problem introduced later.
Find the first version that looks different
Use this check when the editor looks right but the exported result does not. Keep the saved project, reopened export and final viewing copy clearly named. Do not compare a new export with an old cached preview without first confirming the filename and destination.
Open the export in a viewer that supports its format. Inspect the same border, color patch or character edge in both versions. Distinguish changed pixel content from a viewer's enlarged presentation: a soft preview may not mean the file itself has been resampled.
Aseprite separates the editable project from exported copies. Retain the project for corrections and use the export as the item under inspection. An exported file that happens to look correct is not proof that all editable layers or frames have been preserved.
If the difference is already visible in the reopened export, continue with palette, alpha and dimensions. If the export matches, stop changing those settings and inspect the next stage. This boundary prevents repeated exports from becoming an unstructured search for a device-side correction.
Check the palette and color mode
Use this branch when shapes remain intact but hues or tonal steps change. Note the project's color mode and the chosen export format. Keep the screen and background constant for the first comparison so the file conversion is the variable you are testing.
In Aseprite, RGB and indexed modes store color differently. RGBA pixels carry their own color and alpha components; indexed pixels refer to entries in a palette. Changing a palette entry changes the appearance of pixels using that entry. Check an unintended palette change before repainting individual areas.
The Aseprite FAQ discusses color changes when exporting GIF files. A format conversion may require color choices that differ from the working project. Inspect the converted file against the intended palette instead of assuming that every animation format preserves every source color identically.
Make a small swatch test using the colors that matter to the artwork, export it through the same settings and reopen it. If the swatches change at this stage, adjust the conversion or choose a supported format better suited to the required result. If they remain correct, investigate the later viewing stage without changing the original palette.
Check transparency against an explicit background
Use this branch when outlines disappear, pale fringes appear or the background becomes unexpectedly solid. First identify whether the source uses opaque background pixels or transparent layers. An editor's checkerboard is a viewing aid, not necessarily part of the artwork.
Aseprite's color-mode documentation describes alpha as opacity information and notes that its background layer is opaque. Indexed transparency uses a designated transparent index. These details help explain why changing mode, layer type or background assumptions can alter an edge even when its basic color seems unchanged.
- Inspect the exported copy against both a light and a dark viewing background where the viewer permits it.
- Check whether the questionable edge pixels are opaque, partly transparent or fully transparent in the source.
- Create a separate opaque-background export if the final use needs a fixed background.
- Reopen that copy and compare the same edges before sending it through the receiving workflow.
If the opaque comparison resolves an appearance difference, decide whether that background fits the intended delivery. Do not flatten the only editable original. If the problem remains with fully opaque pixels, return to palette or scaling instead of treating every pale edge as transparency.
Check dimensions, scaling and pixel shape
Use this branch when borders look uneven, fine lines become soft or the composition no longer fits. Read the exported width and height, then compare them with the project and the receiving target. A zoom percentage in a viewer does not establish the file's dimensions.
Aseprite's export settings include a resize option and an option to apply a special pixel aspect ratio. Check both when a copy becomes larger or changes shape unexpectedly. Keep social-sharing enlargements separate from the version intended for a small physical grid.
If resizing is necessary, choose the output dimensions deliberately. Aseprite documents resizing a sprite through Sprite Size; inspect the resulting pixels instead of assuming that resizing preserves every hard edge. Check whether the actual method you selected introduces blended colors or changes narrow features.
Use a border and a simple alternating pattern as a comparison aid. If their spacing changes in the export, correct the dimensions or resize choice first. If they are intact in the file but look different only in one viewer, check that viewer's scaling before editing the art. A larger export cannot recover detail that was absent in the source.
For a dedication or small portrait, check which details survive resizing before approving the target-sized export.
Repeat the export from a saved preset
Use this stage after identifying a correction. Record format, dimensions, frame range, background treatment and relevant palette settings. Aseprite remembers export options, which is convenient but also makes it worth checking whether an earlier social-media enlargement or selected-frame export carried into this task.
Export again to a clearly named copy and reopen it without relying on the editor's export dialog preview. Compare the specific features that previously changed. For animation, inspect the full sequence as well as the single frame used for color and geometry checks.
Then send the approved copy through the intended supported route. Keep target compatibility separate from export fidelity: a file can faithfully represent the project and still need a different supported receiving route.
The correction is repeatable when the same saved settings produce the intended reopened file and the receiving route shows the approved content. If only the final output differs, preserve this known-good export as the control for the next investigation.
Only move to a physical pixel display after the reopened export preserves the intended colors, background and geometry. The Divoom Pixoo-64Ⅱ pixel art display provides a documented 64×64 LED target for that next comparison. Adapt a separate output copy to the actual target rather than resizing the editable master in place. The current model is an example of an output surface; it does not repair palette conversion or restore transparency information already lost in a file.
Divoom Pixoo-64Ⅱ WiFi 64x64 Pixel Art LED-display & Sociale mediateller Divoom Pixoo-64 WiFi pixel art display with 64x64 LED panel. Social media counter, custom animations, clocks, and community art. App controlled frame. €137,95 EUR Buy now
Compare pixel art displays when choosing an output grid, after deciding which details the verified export must retain.
Escalate only the stage that still changes the file
If the editor consistently exports an unexpected result, prepare a minimal project showing the relevant colors, alpha or resize behavior. Include the editor version and exact export settings when asking its support channel. Remove private artwork or recipient information that is unnecessary to reproduce the issue.
If the file is correct but the receiving app changes it, keep both copies and describe that boundary. If the app preview is correct and only the physical output differs, record the device model and viewing conditions. Assigning the first divergence is more useful than saying that the artwork changes “somewhere after saving.”
Frequently Asked Questions
Should I switch to JPEG for a smaller pixel-art file?
First check the receiving requirements and the features you need to retain, including transparency or animation. A smaller file is not the only criterion. Export a comparison copy and inspect edges and colors before replacing the approved delivery format.
Why did the export contain only one frame?
Check the export frame range. Aseprite allows selected-frame export, so a still result can reflect the chosen range rather than lost source frames. Inspect the project timeline before rebuilding an animation that may still be intact.
Can an enlarged preview be used to judge exact pixel spacing?
Use a viewing mode that lets you inspect the actual pixel grid and verify file dimensions independently. A viewer's presentation can enlarge or soften an image. The document's stored dimensions and pixel content are the comparison you need for diagnosing an export change.
Conclusion
Locate the first changed copy, then check palette, transparency and scaling with the original preserved. Keep a known-good reopened export as the control. Once that file is correct, direct further troubleshooting toward the receiving stage instead of repeatedly changing the artwork.
