Pixelorama Problems & Issues
Real user-reported problems, complaints, and limitations for Pixelorama. Based on analysis of 12 signals.
Overall score: 72/100
Issues by Category
Pixelorama crashes while saving large projects and leaves a 0 byte file
A user reported a crash during save that left the project and its autosave backups at 0 bytes. Developers called it a known issue with large projects and ZSTD compression and suggested unticking compression in the save dialog.
Pixelorama GIF export fails, stalls at 0% or saves no file
GitHub issues describe GIF export reporting completion with no file, progress stuck at 0%, and a currently open 'Cannot export as gif' report. Several users say older versions worked.
Pixelorama crashes or freezes on certain tools and window actions
GitHub issues include bucket fill freezing with an active selection, and crashes when resizing images or dragging the window on Apple Silicon. Most were fixed in later releases.
Pixelorama export error 12 or error 1 when exporting PNG
Windows users hit error codes on export, which the docs attribute to antivirus folder protection; error 1 is a generic failure often caused by permissions or illegal characters in the path.
Pixelorama tools or effects stop working after an update
The docs attribute breakage after updates to conflicting extensions. Disabling the extension does not help; you must update or uninstall it. Layout files from before 1.0 are also incompatible.
Pixelorama is less polished than Aseprite for professional workflows
Comparison lists treat Pixelorama as the strongest free alternative but describe Aseprite as more polished and widely used, with a larger tutorial ecosystem.
Pixelorama saves .pxo instead of PNG
New users are surprised that Save writes Pixelorama's own project format. Image files come from File > Export.
Pixelorama drawing tablet pen pressure not working on Windows
Reports describe pressure stuck at 0 or 1 in Wintab mode and no drawing in Windows Ink mode. Official docs say to match the driver under Preferences > Drivers, and a community patch exists; the tablet layer comes from Godot.
Pixelorama says macOS app is damaged and will not open
The app is not signed or notarized, so recent macOS versions block it. The docs point to a Gatekeeper workaround, and an open GitHub issue reports the app won't open on macOS.
Windows Defender warns about Pixelorama
Because builds are unsigned, Windows Defender and other antivirus tools sometimes flag the download. The docs say this is not a virus when downloaded from official sources, but it puts some users off.
Pixelorama slow with many layers or large canvases
Official troubleshooting covers poor performance and suggests an FPS limit under Preferences > Performance and Passthrough blend mode on group layers. Heavy projects are also where save crashes appear.
Pixelorama documentation is incomplete and support is community-only
The project's own page admits documentation has missing pages. Help comes via GitHub issues, itch.io comments and Discord from a small volunteer team funded by Patreon.
Regret Patterns
Common reasons users regret choosing Pixelorama.
Lost work from a save crash
Large projects with ZSTD compression can crash during save and leave 0 byte files.
Expecting PNG from Save
Users save .pxo and think the export is done.
Tablet pressure not working
Pen setup requires choosing the right driver.
macOS refuses to open the app
Unsigned build is blocked by Gatekeeper.
Extensions break after an update
Old extensions conflict with new versions.
When Pixelorama Breaks Down
Specific scenarios where Pixelorama fails or underperforms.
Very large canvases with many layers
Slowdowns and risk of save failures.
Windows with strict antivirus
Export error 12 and Defender warnings.
Pen tablet on Windows
Pressure stuck or pen cannot draw until driver is changed.
Long GIF animations
Export can stall or produce no file in some versions.
Apple Silicon Macs
Launch and window-resize problems reported.