While I was working on my first Android app, I found 9-patch (aka 9.png) to be confusing and poorly documented. After a little while, I finally picked up on how it works and decided to throw together something to help others figure it out.
Basically, 9-patch uses png transparency to do an advanced form of 9-slice or scale9. The guides are straight, 1-pixel black lines drawn on the edge of your image that define the scaling and fill of your image. By naming your image file name.9.png, Android will recognize the 9.png format and use the black guides to scale and fill your bitmaps.
Here’s a basic guide map:
As you can see, you have guides on each side of your image. The TOP and LEFT guides are for scaling your image (i.e. 9-slice), while the RIGHT and BOTTOM guides define the fill area.
The black guide lines are cut-off/removed from your image – they won’t show in the app. Guides must only be one pixel wide, so if you want a 48×48 button, your png will actually be 50×50. Anything thicker than one pixel will remain part of your image. (My examples have 4-pixel wide guides for better visibility. They should really be only 1-pixel).
Your guides must be solid black (#000000). Even a slight difference in color (#000001) or alpha will cause it to fail and stretch normally. This failure won’t be obvious either*, it fails silently! Yes. Really. Now you know.
Also you should keep in mind that remaining area of the one-pixel outline must be completely transparent. This includes the four corners of the image – those should always be clear. This can be a bigger problem than you realize. For example, if you scale an image in Photoshop it will add anti-aliased pixels which may include almost-invisible pixels which will also cause it to fail*. If you must scale in Photoshop, use the Nearest Neighbor setting in the Resample Image pulldown menu (at the bottom of the Image Size pop-up menu) to keep sharp edges on your guides.
*(updated 1/2012) This is actually a “fix” in the latest dev kit. Previously it would manifest itself as all of your other images and resources suddenly breaking, not the actually broken 9-patch image.

The TOP and LEFT guides are used to define the scalable portion of your image – LEFT for scaling height, TOP for scaling width. Using a button image as an example, this means the button can stretch horizontally and vertically within the black portion and everything else, such as the corners, will remain the same size. The allows you to have buttons that can scale to any size and maintain a uniform look.
It’s important to note that 9-patch images don’t scale down – they only scale up. So it’s best to start as small as possible.
Also, you can leave out portions in the middle of the scale line. So for example, if you have a button with a sharp glossy edge across the middle, you can leave out a few pixels in the middle of the LEFT guide. The center horizontal axis of your image won’t scale, just the parts above and below it, so your sharp gloss won’t get anti-aliased or fuzzy.

Fill area guides are optional and provide a way define the area for stuff like your text label. Fill determines how much room there is within your image to place text, or an icon, or other things. 9-patch isn’t just for buttons, it works for background images as well.
The above button & label example is exaggerated simply to explain the idea of fill – the label isn’t completely accurate. To be honest, I haven’t experienced how Android does multi-line labels, but there’s a good explanation of how to do them on Stack Overflow. Usually, a button label is usually a single row of text.
Finally, here’s a good demonstration of how scale and fill guides can vary, such as a LinearLayout with a background image & fully rounded sides:

With this example, the LEFT guide isn’t used but we’re still required to have a guide. The background image don’t scale vertically; it just scales horizontally (based on the TOP guide). Looking at the fill guides, the RIGHT and BOTTOM guides extend beyond where they meet the image’s curved edges. This allows me to place my round buttons close to the edges of the background for a tight, fitted look.
So that’s it. 9-patch is super easy, once you get it. It’s not a perfect way to do scaling, but the fill-area and multi-line scale-guides does offer more flexibility than traditional 9-slice and scale9. Give it a try and you’ll figure it out quickly.
For more useful tips, follow me on Twitter.

One other thing that I don’t think is documented on the official page, is that you can actually have more than one “stretchable” region on each side. There are a few .9.png files in the SDK that use this.
So imagine you have an icon in the middle of a button that you don’t want to stretch, but you do want the space either side of the icon to stretch… Your top black line would be in 2 parts, either side of the icon.
Very useful ! Thank you !
Very helpful! Thanks so much for your article.
Question: Normally Android recommends that you provide multiple versions of each image to account for different screen sizes/resolutions. Is that still required when you use a 9 Patch image? If you only need a single 9 Patch image for all resolutions, which baseline resolution do you pick?
Thanks so much.
There’s about a 30% size difference between mdpi & hdpi so I always do 2x screen images; I do mdpi & hdpi and ignore ldpi. By my understanding, mdpi is the standard baseline for dp scaling: layouts match mdpi and scale from there to hdpi.
Great article!
However, there’s something I don’t understand: if I don’t use the LEFT guide (because I don’t want the image to be stretched vertically), I get this error message: “No marked region found along edge. – Found along left edge”.
I think I must be missing something, but I can’t figure out what’s wrong.
Thanks a lot!
Nice catch. I checked out my actual working assets and turns out I did use a left guide, even though I’m not scaling vertically.
I’ve updated the graphic and post. Thanks for catching that =)
Thank you for the article.
I have posted a link on my blog: http://android9patch.blogspot.com
Richard.
How to use 9 patch image in a android? Where 9 patch tools in Eclipse?
When i use 9 patch image it gave error No resource found?
Plz give proper guideliness.
In adv Thanks.
radley,
Your blog reader and yourself are invited to come grab some free 9 patch PNG on my blog: http://android9patch.blogspot.com
I have a link back to your article here since I really like.
Keep on the good work!
Cheers!
Richard.
Awesome post! Easy to understand – thumbs up.
This is a fantastic explanation of 9 patch. Thank you for taking the time to create it.
You rock! Finally I understood, the android documentation is terrible, thanks for putting this out.
THANK YOU! I finally understand.
LoL
thnks a lot
Great write-up. Thank you.
ho God, thanks for the write up!!
its well explained
[...] Installation Script Syntax's – xda-developers [GUIDE] Want to learn how to theme? – xda-developers A simple guide to 9-patch for Android UI | @radley Enjoy GA_googleFillSlot("PhanForum_1stPostSig_300x250"); __________________ [ROM] CTMod [...]
[...] 比较为大众采用一种解决方案是NinePatch。可以毫不夸张得说,9 patch是Android中解决自适应问题的利器。介绍和使用你可以看看这里还有这里。 [...]
Nice post! Very easy to understand – thanks.
[...] liegt der absturz auch daran, weil es sich um 9-files handelt… Draw 9-patch | Android Developers A simple guide to 9-patch for Android UI | @radley Android 9 [...]