Java Desktop app to resize XXXHDPI (or lower) images and sort them into folders automatically.
The next iteration will be a node module which can be used as a standalone CLI tool or as a dependency for another node project, followed by an electron frontend. This project is unlikely to receive any further updates.
Created by Craig Currie
Artwork by Jan Putzan
AndroidResizer is a simple Java desktop app for automatically re-sizing android assets.
AR will downscale your assets and copy them into an android-style folder structure.
AR was a personal project to help speed up some of the tedious tasks when dealing with Android assets. With AR, you can scale down from XXXHDPI, which can be useful in a few ways. When creating new assets the benefits are obvious, simply create your XXXHDPI assets and scale them down straight into your project.
It can also be useful when adding new assets into a project. Instead of getting the new assets for each density and dragging them into each DPI folder, simply drag your XXXHDPI asset into it’s folder then run AndroidResizer again to re-scale the folder down.
NOTE: You may want to back up your assets before running this tool. In the unlikely event that all of your assets get rekt, I can not be held responsible.
Quick release since someone requested this in the project issues: - Added XXXHDPI support
I'll try to get another version out soon with some more features, and I've come up with an idea for 9-patch support which I'll be attempting to implement soon! Also hoping to get iOS support in the next release, along with the new GUI.
Been a bit lazy recently with this, but the project is progressing! You should find v1.3 in the releases tab, ready to go.
Android Image Resizing Asset Resizer Density Scale LDPI MDPI HDPI TVDPI XHDPI XXHDPI XXXHDPI DPI Resource Res
mdpi is the reference density -- that is, 1 px on an mdpi display is equal to 1 dip. The ratio for asset scaling is:
ldpi | mdpi | tvdpi | hdpi | xhdpi | xxhdpi | xxxhdpi --- | --- | --- | --- | --- | --- | --- | --- 0.75 | 1 | 1.33 | 1.5 | 2 | 3 | 4
Although you don't really need to worry about tvdpi unless you're developing specifically for Google TV or the original Nexus 7 -- but even Google recommends simply using hdpi assets.
What this means is if you're doing a 48dip image and plan to support up to xhdpi resolution, you should start with a 96px image (144px if you want native assets for xxhdpi) and make the following images for the densities:
ldpi | mdpi | tvdpi | hdpi | xhdpi | xxhdpi | xxxhdpi --- | --- | --- | --- | --- | --- | --- | --- 36 x 36 | 48 x 48 | 64 x 64 | 72 x 72 | 96 x 96 | 144 x 144 | 192 x 192
And these should display at roughly the same size on any device, provided you've placed these in density-specific folders (e.g. drawable-xhdpi, drawable-hdpi, etc.)
For reference, the pixel densities for these are:
ldpi | mdpi | tvdpi | hdpi | xhdpi | xxhdpi | xxxhdpi --- | --- | --- | --- | --- | --- | --- | --- 120 | 160 | 213 | 240 | 320 | 480 | 640
The MIT License (MIT)
Copyright (c) 2016 Craig Currie
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.