Contact
A question, a bug, or a feature that would unblock your project. A real person reads every message.
Send a message
All fields requiredSix kinds of message
One person reads all of this, so the channel matters less than what is in the message. Some of these still have a faster route than mail.
Something is broken
Form or email, with the template below
Export produced the wrong file, the splitter cut in the wrong place, a tool stopped responding. Worth reporting even when it looks obvious, because a bug that survives a release usually survived it silently.
A format does not import
Email, and attach the file
Atlas formats disagree in the details, and a single real file settles an argument a description cannot. Attach the sheet and its data file, or a cut-down version with two frames.
A feature is missing
Form, described as a problem
Say what you were trying to ship and where the tool stopped you. Padding, trimming, and onion skinning all arrived that way, each from someone describing a job rather than naming a button.
A guide is wrong
Email, with the URL
Engine dialogs move between versions and a guide written against one release can quietly age. Corrections get applied and the page date changes with them.
Gallery takedown or account data
Email, so there is a record
Removal of something you uploaded, a copyright claim on someone elses upload, or a request to delete an account and its saved projects. Use mail rather than the form so the thread is traceable on both sides.
Just asking how to do something
FAQ, guides, or Discord
A question with a known answer gets answered fastest by the page that already covers it. Discord is the place for a question that needs three messages back and forth.
Five lines is enough
A report that says what you expected next to what happened can usually be reproduced on the first try. Without those two lines it takes a round of questions, which costs a day for something that might have been a five minute fix.
The browser matters more than it should. Canvas behaviour, GIF encoding speed, and file dialogs differ between Chrome, Firefox, and Safari, so name yours. If a specific file is involved, attach two frames that reproduce the problem rather than describing forty that do not.
What I did: dropped 12 PNGs, set 4 columns, exported JSON atlas
What I expected: 12 frames in the atlas
What happened: 3 frames missing from the JSON, PNG looks correct
Browser / OS: Firefox 141 on Windows 11
File: attached (the 12 source PNGs, zipped)Direct channels
Donate
Spritesheet generator is free to use. If it saves you an afternoon, consider supporting it with a donation.
Ko-fi
Bitcoin (BTC)
Litecoin (LTC)
Ethereum (ETH)
Thank you for your support!
Before you write
Check the FAQ
Most questions are already answered on the FAQ page.
Bug reports
Browser, OS, and repro steps. Screenshots are gold.
Feature requests
Describe the problem first. The feature usually follows.
Answered before you ask
What to expect
After you send it
There is no support team. One developer reads the inbox around the work that pays for it, so a reply can take a few days and a quiet week happens. A bug with clear repro steps is often fixed before it is answered, so the reply may be a changelog link.
The message itself
The form stores what you type and the contact detail you give, so a reply is possible. Nothing else is collected, and nothing is sold. Send mail instead if you want no database record, and ask for a message and its reply to be deleted afterwards if you want them gone.
The editor never uploads your art, so a sheet specific bug cannot be investigated from your session. Attaching the file is the only way to reproduce it. Terms and privacy cover the rest.
Feature requests get an honest answer, including no. The about page lists the four things this tool deliberately will not do.