Very elongated screen
With a ratio of 19.5:9, Samsung A50 displays a lot of height for little width. Sections designed in landscape become endless columns, and full-screen visuals are poorly cropped.
Samsung · Android 9.0 · Smartphone · 2019
Released in 2019, Samsung A50 features a CSS viewport of 412 x 892 pixels. Here are all its display characteristics and how to check the responsive rendering of your site on this model.
Test your site on Samsung A50 directly in your browser, without buying the device.
4.9/5 based on 5,100 reviews · 1,500,000 users · free
With a ratio of 19.5:9, Samsung A50 displays a lot of height for little width. Sections designed in landscape become endless columns, and full-screen visuals are poorly cropped.
With a density of 2.625x, Samsung A50 provides a useful benchmark to ensure your images remain sharp without serving unnecessarily large files.
The 412 x 892 pixels viewport of Samsung A50 rarely matches the round breakpoints of frameworks. It is precisely between these values that layouts break.
This resolution is what your stylesheet actually manipulates. It determines the applied breakpoint, the number of displayed columns, and the size of your images.
The height remains indicative: Safari, Chrome, and other mobile browsers reduce the visible area with their address bar, which folds on scroll.
Be cautious when analyzing your statistics: some tools only report the manufacturer resolution, never the CSS viewport presented here.
2.625
The device pixel ratio of Samsung A50 is 2.625.
Each CSS pixel is thus rendered by 2.625 physical pixels, making any image provided in simple resolution immediately visible.
This is the number of physical pixels on the screen, as announced by the manufacturer. Useful for preparing your image exports, useless for your media queries.
403 pixels per inch (ppi) · 6.4 inches diagonal, or 16.3 cm
These snippets are generated from the exact characteristics of Samsung A50. Copy them directly into your stylesheet or configuration.
Targets screens whose width matches that of Samsung A50 and models of the same format.
@media only screen and (min-width: 412px) and (max-width: 891px) {
/* Samsung A50 */
}Serves high-resolution images to screens of at least 2.625x.
@media only screen and (-webkit-min-device-pixel-ratio: 2.625),
only screen and (min-resolution: 252dpi) {
/* High-density images and icons */
}Adds a named breakpoint at the exact width of Samsung A50.
// tailwind.config.js
module.exports = {
theme: {
screens: {
'samsung-a50': '412px'
}
}
}Detects format and density client-side.
const isDeviceWidth = window.matchMedia('(min-width: 412px)').matches;
const isHighDensity = window.devicePixelRatio >= 2.625;Essential for Samsung A50 to use its CSS viewport and not a simulated width of 980 pixels.
<meta name="viewport" content="width=device-width, initial-scale=1">Mobile FIRST does not yet include Samsung A50, but a model with the same format is available. You can already validate your breakpoints and display density.
This is where the difference with Chrome DevTools' responsive mode is seen: DevTools resizes a window, the extension replicates the device's browser and allows exporting shareable screenshots and videos.
These 5 devices share exactly the viewport of 412 x 892 pixels and the 2.625x density of Samsung A50. Their CSS rendering is therefore exactly the same: what you validate on one is valid on all others.
The neighboring formats of Samsung A50 are the ones to test right after, as they reveal poorly placed breakpoints.
| Model | CSS Viewport | Pixel density | Manufacturer resolution |
|---|---|---|---|
| Samsung A50 | 412 x 892 | 2.625x | 1080 x 2340 |
| Samsung Galaxy Note20 Ultra | 412 x 883 | 3.5x | 1440 x 3088 |
| Samsung Galaxy A17 | 412 x 892 | 2.625x | 1082 x 2342 |
| Samsung Galaxy A30 | 412 x 892 | 2.625x | 1080 x 2340 |
| Apple iPhone 11 | 414 x 896 | 2x | 828 x 1792 |
| Apple iPhone 11 Pro Max | 414 x 896 | 3x | 1242 x 2688 |
| OnePlus Nord 2 | 412 x 915 | 2.625x | 1080 x 2400 |
The CSS viewport of Samsung A50 measures 412 pixels wide and 892 pixels high. This is the width to use for defining your media queries, not the manufacturer's resolution.
The device pixel ratio of Samsung A50 is 2.625. Each CSS pixel is thus displayed by 2.625 physical pixels, requiring you to provide your images in 2.625x to keep them sharp.
The panel of Samsung A50 displays 1080 x 2340 physical pixels. This is the value reported by most analytics tools, while your CSS works on a viewport of 412 x 892 pixels.
5 other models share exactly the viewport of 412 x 892 pixels and the 2.625x density of Samsung A50: OnePlus 6T, OnePlus 7, Samsung Galaxy A17, Samsung Galaxy A30, Samsung Galaxy A50s. A rendering validated on one is valid on all others.
Install the Mobile FIRST extension on Chrome, Firefox, or Edge, then select Samsung A50. Your page displays in a viewport of 412 x 892 pixels with the corresponding mobile User-Agent, in two clicks and for free.
DevTools resizes the window and applies partial emulation. Mobile FIRST additionally applies the User-Agent of Samsung A50, touch events, scroll behavior, and the actual appearance of the device, and allows capturing directly usable images and videos.
Yes. The extension works on any URL open in your browser, including localhost:3000, 127.0.0.1, or a password-protected pre-production environment.
No. The simulation covers the vast majority of development needs at no cost. A final test on a real device is still recommended before critical production deployment, but it's no longer necessary for each iteration.
A media query on the exact width targets Samsung A50: @media only screen and (min-width: 412px). Combine it with the pixel density to precisely target this model and those sharing its format.
Without buying a single phone, without creating an account.
Free installation in seconds · computer only