If a personalized pixel message loses letters after upload, save the original before editing or sending it again. Compare the editable design, the exported file and the device display to find the first place the ending disappears. A missing word alone does not establish a broken display or a failed connection.
If the ending is already absent in the file, repair a copy before uploading. If the file is complete but the app preview crops it, check the destination canvas and placement. If only the device differs, confirm the selected design and playback before escalating. Keep an updating device powered as its instructions require; do not reset it simply to recover missing letters.
Save the Message and Locate the First Missing Letter
Start with a record of what should appear: the complete message, including the recipient's name, punctuation and final word. Save the editable project under a new name and keep the file that produced the faulty upload. This preserves a comparison instead of replacing the evidence with another revision.
Then inspect the same message at each stage. For moving text, watch a complete pass rather than judging a single moment when the last letters have not yet entered the screen. Use this route to select the next check:
- The project is incomplete: restore the wording in a copy. Check the name against your intended text before changing its layout.
- The project is complete but the exported file is incomplete: inspect the export dimensions and, for animation, the exported frame selection.
- The file is complete but the app preview is incomplete: compare the selected destination, visible canvas and import placement.
- The preview is complete but the device differs: keep that file unchanged and check the active device and design.
Record the first differing stage and the last visible character. A repeatable cutoff at the same letter is more useful to support than “some text vanished.” If the panel also shows an unrelated damaged area or other content fails there, stop treating this as a lettering-only problem and document that separate symptom.
Check the Actual Grid and the File You Sent
A message must be assessed against its intended display area, not the apparent size of the phone preview. Identify the device model and hardware version, then select the manual for your actual display. A familiar product name is not enough to assume that another model or revision uses the same canvas or controls.
For example, the original Pixoo 64 manual specifies a 64×64 pixel LED display. Use that fact only for the documented model. Confirm the receiving area in the current app too, particularly when a template contains other visual elements; the physical panel and an individual text region need not be treated as interchangeable.
Open the exact exported file independently of the editable project. Check whether its final letter is present and whether the file dimensions match the layout you prepared. In Aseprite, export options can change the output scale. A correct-looking project therefore does not establish that you selected the intended export.
If the message was designed on a larger canvas, avoid stretching it into a smaller square merely to match the outline. Decide whether to recompose the words, use an available text feature, or prepare a supported animation. To work through that separate design task, distinguish resizing from cropping before rebuilding the layout. The goal is a complete message at the destination, not just a file with the expected dimensions.
Repair a Copy at the First Failing Stage
Work on the earliest version that actually loses content. If the exported file already cuts off the ending, uploading it again cannot supply the missing wording. If the exported file is complete, leave it as your control while adjusting the import or destination that first changes it.
- Restore the full wording. Compare the copy with your saved text. Keep the full name and important punctuation; do not silently shorten a dedication to make it fit.
- Review the visible bounds. Move or recompose the lettering within the intended area. Check both edges and the top and bottom of the letters, including accents. Avoid shrinking until a name is technically present but impossible to recognize.
- Inspect the output. Export the revised copy, reopen it and inspect the ending independently. Give it a distinguishable filename so that the next send uses this revision.
- Preview the receiving layout. Select the intended device and inspect any placement or crop controls actually available. Change one relevant option, then compare again; do not assume every app version exposes identical controls.
Canvas bounds and artwork size are different editing decisions. Aseprite documents the canvas as the visible area of a sprite. Use that distinction when checking where the ending is lost; enlarging the visible area of a working copy is not the same operation as making its letters smaller.
When you intentionally choose moving text, first verify that the complete wording enters and leaves the preview. Only after the ending is present should you adjust scrolling text for readable playback. Speed and contrast are a later viewing task; neither replaces letters missing from the source.
This branch is complete when the revised file and receiving preview both contain the intended message. If the preview still differs from a complete file, save screenshots of the mismatch rather than changing unrelated settings or redrawing the entire gift.
Send the Correct Revision and Verify the Whole Message
With a complete file and preview, follow the creation or upload workflow available for your actual device. The app's labels can vary by version and model, so follow the custom-art upload workflow for your device rather than looking for an assumed universal button. Confirm the selected device before sending.
Check which design is actually playing. A previously saved message, another channel or another version can make the new upload appear unchanged. Identify the revision by its actual wording or artwork; do not overwrite your only original merely to distinguish copies. If the device reports an update, follow its instructions and wait before ordinary troubleshooting.
On the real display, read the name, the middle of the message and the final word. For animation, observe the complete sequence and its return to the beginning. Then view it from the position where the recipient will normally read it. A complete but illegible message needs a layout or playback adjustment, while a complete preview that repeatedly becomes incomplete on the device needs a documented mismatch report.
Keep the corrected source and the exact successful output together with a note identifying the destination. Recovery means the intended wording is present on the actual display and can be read in its intended use. A phone preview alone is insufficient acceptance.
Stop Repeating the Upload When the Evidence Stops Changing
If a complete file and preview still produce the same missing ending on the correct device, contact Divoom support with the model, hardware version if available, app version and the stage where the text first differs. Include the file dimensions, a preview screenshot and a photo or short recording showing the whole playback. State whether unrelated designs have the same affected area.
Use a nonsensitive substitute message when sharing examples, and remove personal details from screenshots. Ask whether that model, format and selected feature have a documented limit or known issue. Do not claim an undocumented character limit from one failed message, and do not assume a factory or network reset is a lettering repair.
Keep the original and the last clear comparison while waiting. Resume editing when you have a specific layout change or model-specific instruction to apply. If ordinary content also fails in a fixed panel area, report that separate symptom rather than compensating by moving every future message around it.
Questions About Missing Message Endings
Could an export leave out the frames containing my message ending?
Yes, if those frames were excluded from the export. Aseprite allows a single frame or selected frames to be exported. Compare the output sequence with the frames containing your final word, then export the intended selection again. This checks a specific omission before upload; it does not establish that the receiving device discarded any frames.
What if the ending appears in the wrong order rather than disappearing?
Inspect the exported animation before calling the wording missing. Aseprite offers Forward, Backward and Ping-Pong export directions. Compare the file with the intended reading order and inspect that export option if the sequence reverses. This is an Aseprite-specific check for an animated message, not a claim that every device has the same playback setting.
Which original should I keep while repairing a cut-off gift message?
Keep the editable source as well as the exact output you sent. In Aseprite, saving an .aseprite project preserves full work information, while exporting creates an output such as a GIF or PNG sequence. Make the correction from a separately named working copy; do not treat the sent output as your only editable original. These file roles help preserve the complete message while you compare revisions.
Conclusion
Recover a cut-off personalized pixel message by finding the first version that loses its ending, then repairing a copy at that stage. Keep the original, confirm the exact output and receiving layout, and check the complete wording on the actual display. Treat the message as restored only when the intended name and final word are present and readable. If a complete file and preview still produce the same device-only mismatch, preserve that comparison and ask support about the actual model and feature.
