I work on SpriteShip. I tried the built-in sample pack: the table puts pulse_1, pulse_2 and pulse_10 in natural order, and selecting pulse gives an 18 × 16 canvas for the three differently sized source frames. One UI suggestion: distinguish source-name collisions from output-name collisions. The two idle rows are flagged as name collisions, but their numbered output filenames are already distinct. A label such as “Source names normalize alike; exported names are unique” would make it clearer whether action is needed before downloading.
Thanks for trying the sample pack and for the helpful suggestion! I've updated the demo to distinguish source-name normalization notices from actual output-name conflicts. It now makes clear when source names normalize alike, but the numbered exported filenames are unique. The JSON and CSV reports make that distinction too. Thanks for helping make this clearer!