Android viewport sizes in CSS pixels: Pixel and Galaxy
A phone’s display resolution tells you how many physical pixels it has. CSS works with a logical viewport, and Android display settings can change that logical size. Use a sourced reference, then measure the browser involved in the bug.
Updated 12 November 2026
Pixel and Galaxy reference sizes
Checked 12 November 2026. These are published portrait references, not a claim that every owner gets the same dimensions. Rows marked browser use a browser viewport from the cited dataset. The screen row is a whole-screen CSS reference, before browser controls take space.
| Phone | CSS px: W × H | DPR | Reference |
|---|---|---|---|
| Pixel 10 | 360 × 732 | 3 | Playwright, browser [1] |
| Pixel 10 Pro | 427 × 876 | 3 | Playwright, browser [1] |
| Pixel 10 Pro XL | 448 × 921 | 3 | Playwright, browser [1] |
| Galaxy S26 | 360 × 639 | 3 | Effective Viewport, browser [2] |
| Galaxy S25 | 360 × 780 | 3 | Panescope, screen [3] |
Playwright publishes its testing profiles as source data, including separate screen and viewport fields for the Pixel models. Effective Viewport reports the S26 with Chrome’s controls expanded; it also publishes a taller 360 × 695 layout with controls collapsed. Choose the state relevant to your test.
References can disagree without describing the same configuration. Panescope’s Pixel 10 screen reference is 412 × 924 at DPR 2.625, while the Playwright browser profile above uses DPR 3. Keep a source’s dimensions and DPR together. Record a real device’s settings when reporting a discrepancy.
Android tablet reference sizes
These portrait sizes cover an established tablet, a newer large Galaxy Tab and a budget model. Two rows use whole-screen CSS references; the Tab S9 row follows Playwright’s browser profile. Source labels make that distinction explicit.
| Tablet | CSS px: W × H | DPR | Reference |
|---|---|---|---|
| Galaxy Tab S9 | 640 × 1024 | 2.5 | Playwright, browser [1] |
| Galaxy Tab S11 Ultra | 924 × 1480 | 2 | doesitfit, screen [4] |
| Galaxy Tab A9+ | 800 × 1280 | 1.5 | doesitfit, screen [4] |
Landscape and split-screen windows deserve their own checks. A tablet held in landscape can show a wide desktop-style navigation while still being operated with fingers. A narrow app window can cross back into your phone layout. Write down the viewport of the window you actually tested.
Measure CSS width and DPR on your page
On a development page, add a temporary readout using this function and call it again after rotation or a window resize:
function viewportReading() {
return {
width: window.innerWidth,
height: window.innerHeight,
dpr: window.devicePixelRatio,
visibleHeight: window.visualViewport?.height
};
}
Keep the responsive viewport meta tag in the document head: <meta name="viewport" content="width=device-width, initial-scale=1">. That lets a responsive page use the device’s logical width. A legacy wide viewport can otherwise make your measurements look like a desktop page.
DPR describes the relationship between CSS pixels and physical pixels. It helps choose sharp raster images. Physical pixels per inch, usually advertised as PPI, describe the panel and are a different quantity. Dividing the resolution by PPI gives inches; it does not give a browser viewport.
Common Android breakpoint checks
Android has no universal CSS breakpoint list. Start with your content and use familiar widths as checkpoints. At 360 px, check that navigation and cards fit. At 412–448 px, check longer lines and multi-button rows. Use the CSS breakpoint checks for tablet transitions around 768 and 1024 px, then wider layouts around 1280 px.
For each breakpoint in your own stylesheet, check immediately below it and at it. For example, a 768 px minimum-width rule needs 767 and 768 px reviews. Check the intermediate widths too: a fixed-width card can fail between two otherwise tidy presets.
Use fluid grids, flexible images and wrapping text so nearby widths work as well. Treat hover behaviour separately from width. A wide Android tablet may still need a tap to open its navigation menu. Forms and sticky controls also need a review with the keyboard visible.
Check Android sizes from an iPhone or iPad
- Open the URL in ViewPortal and choose the Pixel 10 (412 × 923) or Galaxy S26 (384 × 832) preset, or enter a custom width and height from the reference table.
- Read the selected dimensions to confirm the width and height you are checking.
- Compare wrapping, columns and navigation, then rotate the preview to check another orientation.
- Capture and annotate the result. In Pro, put several widths together using the side-by-side workflow.
ViewPortal uses your iPhone or iPad’s WebKit engine at the selected Android dimensions. Use those views to check layout and breakpoints in WebKit, and include Android Chrome or Samsung Internet in your final browser checks. Pro dev tools let you inspect element dimensions, padding, fonts and colours, measure gaps, read console errors and find horizontal overflow.
Turn a width check into useful feedback
ViewPortal is free to download for iPhone and iPad, including public-URL previews, custom sizes, rotation, capture and annotation. ViewPortal Pro adds multi-view, localhost/LAN development servers and dev tools for a one-time £4.99, with three free multi-view sessions first. There is no subscription, and the app has no accounts, analytics or tracking.
ViewPortal on the App StoreQuestions people ask
Why do Android viewport references disagree?
What does an Android size show in ViewPortal?
Sources and references
Sources checked 12 November 2026. Dimensions are published reference values; browser and display settings are described above.
- [1] Microsoft Playwright: device profiles, viewport and deviceScaleFactor
- [2] Effective Viewport: Galaxy S26, Chrome controls expanded and collapsed
- [3] Panescope: published screen-sized CSS references and DPR
- [4] doesitfit: Galaxy Tab screen-sized references and DPR
- MDN: devicePixelRatio
- web.dev: viewport settings and responsive layout