One of the biggest challenges in Android development is ensuring your app looks great on different screen sizes and densities. Android runs on thousands of devices — each with unique resolutions, DPIs, and aspect ratios — so understanding how to support multiple screens is essential for delivering a consistent user experience.
Understanding Screen Density
Screen density is the number of pixels within a physical area of the screen — measured as dots per inch (dpi).
It helps determine how UI elements and images scale across devices.
Note: Android measures screen size diagonally, i.e., from the bottom-left to the top-right corner of the display.
When you use density-independent pixels (dp) instead of pixels (px), Android automatically adjusts the size of your UI elements at runtime based on the device’s screen density.
Screen Density Categories and Conversion Ratios
Android groups devices into standard density buckets. Here’s how dp maps to px for each category:
| Density | DPI | Conversion Formula | Ratio | Example (base 160) |
|---|---|---|---|---|
| ldpi | 120 | 120 / 160 = 0.75x | 3 | 0.75 × dp = px |
| mdpi | 160 | 160 / 160 = 1x | 4 | 1 × dp = px |
| hdpi | 240 | 240 / 160 = 1.5x | 6 | 1.5 × dp = px |
| xhdpi | 320 | 320 / 160 = 2x | 8 | 2 × dp = px |
| xxhdpi | 480 | 480 / 160 = 3x | 12 | 3 × dp = px |
| xxxhdpi | 640 | 640 / 160 = 4x | 16 | 4 × dp = px |
The ratio between densities roughly becomes 0.75 : 1 : 1.5 : 2 : 3 : 4,
or when multiplied by 4 → 3 : 4 : 6 : 8 : 12 : 16.
Example: sw720dp Devices
sw720dpmeans a screen whose smallest width (in dp) is at least 720dp.- It’s often used for tablets and large-screen devices.
For example, you can create a layout specifically for tablets under:
res/layout-sw720dp/
Key Concepts to Remember
1. Use dp Instead of px
- Always define sizes using density-independent pixels (dp).
- This ensures your layout scales properly on devices with different screen densities.
1 dp = dpi / 160 pixelsFor mdpi (160 dpi) screens:
→1 dp = 1 px
2. Provide Alternative Resources
To make your app adaptive:
- Provide multiple versions of layouts, drawables, and values for different densities.
- Use the
res/directory qualifiers:res/drawable-ldpi/ res/drawable-mdpi/ res/drawable-hdpi/ res/drawable-xhdpi/ res/drawable-xxhdpi/ res/drawable-xxxhdpi/
Android will automatically pick the best matching resource folder based on the device configuration.
3. Let Android Handle Auto-Scaling
If density-specific images are missing, Android will auto-scale the available images to match the required density.
However, this can sometimes result in blurry or distorted images — so always prefer supplying proper density assets.
4. Use 9-Patch Images for Stretchable UI
Instead of providing multiple background images for different resolutions, use 9-patch drawables (.9.png files).
They scale intelligently while maintaining corners and edges.
Example use case:
- Buttons
- Dialog backgrounds
- Cards and panels
✅ Example: Button background that stretches only in non-text areas.
5. Drawable Ratios for Common Icons
| Density | Example Icon Size |
|---|---|
| ldpi | 36×36 px |
| mdpi | 48×48 px |
| hdpi | 72×72 px |
| xhdpi | 96×96 px |
| xxhdpi | 144×144 px |
| xxxhdpi | 192×192 px |
Reference
Official Android Developer Guide:
Supporting Multiple Screens
Summary
| Concept | Description |
|---|---|
| Screen Density | Number of pixels per inch (dpi) |
| dp (Density-independent pixel) | Logical pixel unit that scales with screen density |
| swdp qualifier | Used for layouts based on smallest screen width |
| 9-patch images | Scalable assets maintaining shape and corners |
| Multiple drawables | Helps maintain visual quality across devices |
Key Takeaway
“Design for dp, not px** — and let Android handle the scaling magic.”
By following these best practices, your app will look beautiful and consistent across all Android devices — from small phones to large tablets.