An advanced sprite packing tool. Currently a work in progress.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Starbeamrainbowlabs 28e3fcbfe5 Add usage information to README. 4 years ago
SpritePacker Correct short git commit hash in version string to be at the beginning of the full hash, not the end 4 years ago
.gitignore Polish CLI and add Utilities class. 4 years ago
LICENSE initial commit 4 years ago Add usage information to README. 4 years ago
SpritePacker.sln Polish CLI and add Utilities class. 4 years ago


An advanced sprite packing tool. Currently a work in progress.


  • Either the Microsoft .NET framework on Windows, or the Mono runtime on other platforms.
  • If you want to build SpritePacker from source, you’ll need git installed and in your PATH.

Getting Started

Prebuilt binaries

I provide prebuilt binaries, just in case you can’t get SpritePacker to build yourself.

Link: SpritePacker.exe (Direct Link)

From source

  • Clone or download this repo, and build the included solution.
    • Windows GUI: Open the solution in Visual Studio and hit build (CTRL + SHIFT + B).
    • Windows Command Line: Run msbuild from the root of this repo (I assume).
    • Linux GUI: Open the solution in MonoDevelop and hit build (F8)
    • Linux Command Line: Run xbuild from the root of this repo.


SpritePacker is currently a command line tool (Requests for a GUI are welcome), and intended to be easy to automate and integrate into your existing workflow. Despite that, it’s still easy to use. Here’s an example of how you would pack 3 different images into the same file:

SpritePacker.exe /path/to/output.png picture1.png textureB.jpeg anotherimage.gif

Your next latest and greatest project will probably have a lot mroe than just 3 images, making specifying them all one by one a pain in the neck. Thankfully, SpritePacker supports (recursive!) directories of images:

SpritePacker.exe /path/to/output.png /path/to/image/directory

Packing sprites is all very well, but your program needs to be able to tell where each individual sprite was placed in the final image. SpritePacker tells you by outputting some nice, easy to read text, but this isn’t particularly machine-friendly. Alternatively, you can add the --csv flag when you call SpritePacker. This will cause SpritePacker to output some nice, (hopefully) well-formatted CSV for your program to consume:

SpritePacker.exe /path/to/output.png /path/to/image/directory --csv

Note that any other text besides the CSV will be ouputted via stderr, so you can pipe the raw stdout to a file and have your program understand it.

SpritePacker.exe /path/to/output.png /path/to/image/directory --csv >SpriteLocations.csv

Additonal help can be found by running SpritePacker.exe --help.


This project is a work in progress. If you encounter any issues, please open an issue on the issue tracker if you have an account, otherwise please send an email to bugs at

Once SpritePacker is somewhat stable, it will be moving to GitHub. I still intend to host a mirror at this address though, so you can bookmark this address.

If you would like to contribute (before the move to GitHub sometime in the future), please an email to the aforementioned address and I’ll create you an account with which you can contribute.


This tool is licensed under the Mozilla Public License version 2.0. You can view the full license text in the LICENSE file in this repo. Alternatively, tl;dr legal has a summary of this license.