I can't reproduce the glitchy first row problem
As for the adding comments, I couldn't think of a good way of importing sprites where I differentiate between data, code, maps, sprites, etc, so it just takes anything A-F and 0-1 and assumes it is the next nibble.
I'm also considering adding the option to specify the picture variable it uses.

Still can't reproduce it.  Perhaps I fixed it a while ago and don't remember.

Okidoki, here's version two, with the bugs fixed and the requested features added.  Here's a breakdown of the new features in this version:
-Import/Export Black & White Sprite Sheets
-Specify a Pic variable to export as
-On import, if it finds that sprites are being stored to a Pic variable, it will set that one as the default

These features address the following:
Black and White:

I wish there was a black-and-white mode

Pic variable features:

If you change the picture pointer in the program, it doesn't automatically change it back to Pic1

If anyone wants any more features, post it up.  Also, bug reports would be nice.  One known bug is that occasionally, when importing a black and white sprite sheet, some of them will glitch up.

It's either all b/w or all grayscale.

*bump* anyone want more features?  Anyone still even use this?

Well the issue is that you are competing with about 100 other Axe/BASIC/ASM sprite editors on Omnimaga, so inevitably the amount of responses to new ones will be sparse.

That's true.  I think mine uniquely offers the ability to import/export pre-formatted Axe programs with the sprite sheets.

Yeah true. Actually I think Squidgetx's did too (although it was more a memory viewer), but yeah at one point there was a new sprite editor ccoming out every week or so, so I almost imitated Ticalc.org's 2011 April fools joke with quadratic solver folders (Not implying that sprite editors are useless, but there were so many )

Nice, that would have been a good one.  I still enjoy mine the most, and think that it rises to the top of the crop for it's inclusion of Axe-specific features.

Haha yeah, mine was more like a mem editor with the option to edit the data as sprites instead of bytes.

This is pretty cool, and I would use it except that I already have my own regular sprite editors that I keep as source in archive, then compile when I need them. Exec-only files are hard to find on my calc, as my RAM clears so often and I already have my custom-tailored one for A:P
Still, I think I would back your claim that it's the best gen. purpose sprite editor out there...

Thanks!  I appreciate it.  And I do write a lot of custom tools for each program I make - you should see how much extra software I've written to compile KnightOS.