Yeah, I like Pixelorama too; I’ve tried it out, and it’s feature-rich and very stable. I discovered Pixelorama while looking for an MIT-licensed open-source alternative on AlternativeTo.net, and I really like it—especially since it’s built with Godot, making it lighter than other pixel art editors like Aseprite (which is written in C++). That’s actually why I created the .pxo format for Fossprite, since so many people love Pixelorama as well. (This reply is based on my personal opinion and was written entirely using Google Translate.)

That’s what I humanized using AI, OK, I’m using Google Translate, I’m not very good at English.

Because “browser-based” and “online” aren’t the same thing at all. The browser is just where Fossprite runs, and it doesn’t need an internet connection. Download the single HTML file, turn off your internet, open it locally, and it works. I went with the browser because pretty much everyone already has one, on any operating system, so there’s nothing extra to install. The trade off is that some browser limitations still apply.

Fair point, tbh. Putting everything in one file, plus the AI assisted development, has left me with code that’s hard to read and maintain. Some parts still use minified style names, and that’s on me. I went with a single file so people could download it and run it offline, no build step and no dependencies. fwiw, that’s a reason, not an excuse for code that’s hard to follow. What I still need to do is split it into clearer modules, rename things properly, and document where the original, adapted, and third-party code begin and end. If you have specific suggestions for making it easier to debug or contribute to, lmk.