In this post I'm going to try and share what I've learned about doing pixel art, the tools I use, the process I follow and some tips and tricks that sound simple but I find really useful. Bear in mind that I'm not a professional artist, but instead a programmer that has gotten into pixel art to try and do some art for his side projects. Anyway, I'm going to put an index at the beginning so you can find what you're interested into if you don't want to read the full article.
Also, for reference, when I talk about the knight I did I refer to this:
If you want to see it moving or see an early, kind of rough version just follow the links.
1 – A little backstory (my background & experience)
2 – Tools and references
3 – Creating an asset step by step
4 – Tips & tricks summary
As I mentioned in the introductory paragraph, I'm a programmer by trade. As many programmers that are also gamers, game development caught my attention. I've been lucky enough to get to work as game dev, but even then, I try my hand at hobby projects now and then. And then again, as many programmers that try making games as a hobby, I've been faced with the problem of having no art for the games I want to make.
As a natural consequence of that I've tried on several occasions to create some game art, normally leading to really ugly looking games and to frustration. I have tried doing things in MSPaint, and obviously found it severely lacking. I've tried Photoshop and Gimp, and found them really overwhelming, spending more time fighting the tools and trying to find out how to do what I wanted that actually drawing. And even when I managed to create some assets for my game they looked terrible and I wasn't happy with the result.
Luckily for me, another programmer friend of mine told me that he had been trying to do some pixel art, that he had found a great tool, and that things were looking promising. That of course got my attention, and with that we transition to the second point of this entry...
One key thing for me to get things working, and to get enough motivation to put the time required and actually finish some asset, was finding the right tool for what I wanted to do. That tool is Aseprite, and I can't recommend it enough. It's 15$, and it has a free trial, so you can check it out and see if it works for you.
What I love about it is that it has been designed with the specific purpose of doing 2D pixel art. Due to that it has everything I've needed so far, without being as overwhelming as some other tools I've tried. It also has a pretty good and straightforward documentation. And on top of that, the integrated tool for doing animations frame by frame is really nice and easy to use. This may seem stupid, but for me going from a still frame to something I could see move was a huge moral boost. I could go on and on and explain more features, but I think it is better to focus on other things on this post, and everything I may say is already on their website.
Another really important thing for me to get started was finding some good tutorials and initial guidelines and tips. With any luck this post can do that for you, but just in case, I also want to share a site that helped me a lot. Everything here is gold. I would recommend at least checking all of them once, but specifically the ones about Character Design, Fundamentals and the Top Down Run Cycle are really good things to keep in mind when starting a new drawing.
Now that I have shared the tool I use and some tutorials I followed, I'm going to try and give a step by step guide of what I do when creating a new asset. Keep in mind that this works for me, and may be wrong for you. If you feel like a step is a waste of time and want to skip it, or like you need to add any steps in between, please do so and share how it went in the comments.
Also, unfortunately I didn't document the process when doing the knight I shared recently, but I will try to remember with the next thing I do, so expect an updated post for this section with lots of screenshots at some point in the future :). Here we go:
Quite a bit of effor went into this, so I hope you find it useful, and please let me know if you have any more tips, or disagree with any of what I said.
And last but not least, a big shoutout to @svosse , who gave me the final push I needed to write the article.