Support

Contact

Bug reports, format problems, feature requests, and gallery takedowns. Messages go to the maintainer, not a support queue.

Send a message

All fields required
Where to send what

Six kinds of message

Everything lands with the same person, so what you put in the message matters more than the channel. A few kinds 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. Report it even when it looks obvious. Nobody else may have.

  • 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 make and where the tool stopped you. A described job is easier to build for than a named button, and sometimes the tool already does it another way.

  • A guide is wrong

    Email, with the URL

    Engine menus move between versions, so a guide written against one release goes stale. When a correction goes in, the updated date on the guide changes too.

  • 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.

Bug report template

Five lines is enough

With what you expected next to what happened, a bug can usually be reproduced on the first try. Without those two lines it takes a round of questions, and a five minute fix waits a day.

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

Support

Donate

Spritesheet Generator is free. If it saved you an afternoon, a donation helps pay for hosting.

Ko-fi

Buy Me a Coffee at ko-fi.com

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 the steps to reproduce it. A screenshot helps.

  • Feature requests

    Describe the problem, not the button you want.

Answered before you ask

What to expect

After you send it

There is no support team. One developer reads the inbox around other work, so a reply can take a few days, sometimes longer. If a bug report has clear steps, the reply may simply be a link to the changelog entry that fixed it.

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.