iPhone SE vs Galaxy A15: screen size and viewport
The iPhone SE lays web pages out at 375 × 667 CSS px with a pixel ratio of 2; the Galaxy A15 at 384 × 832 with 2.813. The Galaxy A15 is 9 px wider and 165 px taller.
The two screens side by side
Specs compared
| Spec | iPhone SE | Galaxy A15 | Difference |
|---|---|---|---|
| Viewport, portrait (CSS px) | 375 × 667 | 384 × 832 | −9 px wide, −165 px tall |
| Device pixel ratio | 2 | 2.813 | −0.813 for the iPhone SE |
| Physical resolution | 750 × 1334 | 1080 × 2340 | Galaxy A15: 153% more pixels |
| Aspect ratio | 16:9 | 19.5:9 | Galaxy A15 is taller |
| Visible height, portrait, with browser bars | ~559 px | ~736 px | −177 px for the iPhone SE |
| Landscape width (CSS px) | 667 px | 832 px | −165 px for the iPhone SE |
| Visible height, landscape | ~325 px | ~304 px | +21 px for the iPhone SE |
| First released | 2020 | 2024 | 4 years apart |
| Engine in MobileCheck | WebKit (Safari) | Chromium (Chrome) | different engines |
CSS px are the units media queries see. Visible heights subtract the status bar and the Safari on iOS and Chrome on Android bars as set in our device profiles; real bar heights vary with settings and scrolling. The release year is that of the first model with each screen.
What this means for your layout
How the width difference affects your layout
The Galaxy A15 is 9 CSS px wider (384 vs 375, 2% more). No common breakpoint falls between 375 and 384 px, so with typical media queries both get the same layout and the extra 9 pixels only stretch fluid columns, text lines and images.
In a 2-column card grid with 16 px page padding and 16 px gaps, each card is 168 px wide on the Galaxy A15 and 163 px on the iPhone SE. Check that buttons, prices and long words still fit in the narrower one.
Pixel density and image sizes
The Galaxy A15 has the denser screen: 2.813× against 2×. A full-width image (sizes="100vw") needs about 1080 px on the Galaxy A15 and 750 px on the iPhone SE to look sharp.
With a srcset such as 640w, 828w, 1080w, 1290w, 1440w, 1640w, 2048w, the browser would normally pick the 828w file on the iPhone SE and the 1080w file on the Galaxy A15. Leave out the 1080w candidate and the Galaxy A15 upscales a smaller file.
The Galaxy A15's ratio of 2.813 is fractional: one CSS pixel isn't a whole number of device pixels, so 1 px borders and hairlines can be rounded unevenly. Check thin lines on that screen rather than assuming they match.
How much fits above the fold
On first load about 736 px of the page is visible on the Galaxy A15 and 559 px on the iPhone SE: 177 px less (32%) on the iPhone SE, roughly 7 lines of 16 px body text at a 1.5 line height.
If your main button sits just above the fold on the Galaxy A15, it can end up below it on the iPhone SE. Keep the headline and the main action within the first 559 px, and size full-screen sections with 100svh rather than 100vh — see the 100vh problem on mobile.
Relative to its width, the Galaxy A15 has the taller screen (16:9 vs 19.5:9), so the same content is laid out narrower but more of its length fits at once.
In landscape
Turned sideways, the iPhone SE is 667 px wide and the Galaxy A15 832 px; (min-width: 768px) matches only the Galaxy A15 in landscape. The visible height drops to about 325 and 304 px, so a 64 px sticky header covers 20% and 21% of the screen — under the 25% at which MobileCheck flags fixed bars covering the page.
Different browser engines
The iPhone SE renders with WebKit (Safari's engine) and the Galaxy A15 with Chromium (Chrome's), so fonts, form controls and some CSS can differ on top of the size difference. Chrome DevTools draws every emulated device with Chromium, which hides WebKit-only problems — see how to test on an iPhone and on Android.
More about these devices
- iPhone SE viewport size — one screen for the iPhone SE (2nd/3rd gen) / 7 / 8
- Galaxy A15 viewport size — one screen for the Samsung Galaxy S24 / S25 Ultra / A15 / A54 / A55
Or open the free check with the iPhone SE and the Galaxy A15 preselected: full-page screenshots in WebKit and Chromium, with problems such as small text and crowded buttons highlighted.
Related comparisons
- iPhone 16 Pro vs Galaxy S24 Ultra — 402 vs 384 px wide, 3× vs 2.813×
- iPhone 16 Pro Max vs Galaxy S24 Ultra — 440 vs 384 px wide, 3× vs 2.813×
- iPhone 15 Pro Max vs Galaxy S24 Ultra — 430 vs 384 px wide, 3× vs 2.813×
- iPhone 14 vs Galaxy A54 — 390 vs 384 px wide, 3× vs 2.813×
- iPhone SE vs iPhone 16e — 375 vs 390 px wide, 2× vs 3×
- iPhone SE vs iPhone 13 mini — both 375 px wide, 667 vs 812 px tall
Compare other devices → · All mobile viewport sizes →
Frequently asked questions
Is the iPhone SE screen bigger than the Galaxy A15?
In CSS pixels, which decide how much of a page fits, the Galaxy A15 is larger: 384 × 832 against 375 × 667. The Galaxy A15 has more physical pixels (1080 × 2340), which makes it sharper rather than roomier.
Do I need different CSS for the iPhone SE and the Galaxy A15?
Usually not. No common breakpoint falls between their widths (375 and 384 px), so a fluid layout gets the same rules on both and only stretches by 9 px.
How much of a web page is visible on the iPhone SE vs the Galaxy A15?
About 375 × 559 CSS px on the iPhone SE and 384 × 736 on the Galaxy A15 when a page first opens in portrait, after the status bar and the browser's bars. Bar heights are our device profiles' estimates.