OnePlus 12 display and calculation reference
Use the official QHD+ display facts and a reproducible calculation to test a wide phone layout, without mistaking that scenario for a measured browser default.
Reference scope: OnePlus 12 global model (2024), excluding OnePlus 12R.
Two measurement layers
The native display values come from OnePlus. CSS dimensions are a normalized testing baseline and remain dependent on browser state.
| Field | Reference value | Evidence scope |
|---|---|---|
| Display diagonal | 6.82 inches | OnePlus specification, measured diagonally corner to corner. |
| Native pixel grid | 1440 × 3168 | OnePlus QHD+ specification reordered as portrait width × height. |
| Pixel density | 510 PPI | OnePlus-stated density: 510 PPI. |
| CSS viewport | 450 × 990 CSS px | Calculated full-panel scenario: native width and height divided by assumed DPR 3.2; browser space may be smaller. |
| Device pixel ratio | 3.2 | Chosen calculation input of 3.2; not a measured browser value or a verified default setting. |
| Record year | 2024 | Model-generation context; verify the exact configuration. |
| Reference CSS area | 445,500 CSS px² | Calculated from the normalized width and height; not physical screen area. |
Manufacturer-verified layer
OnePlus specifies a 19.8:9 QHD+ panel and an LTPO display with dynamic refresh from 1 to 120 Hz. The panel ratio describes native geometry; system scaling and browser controls determine the webpage space within it.
Browser-dependent layer
The calculation is 1440 ÷ 3.2 = 450 and 3168 ÷ 3.2 = 990. This replaces the old 1000-pixel profile height, which did not follow the same arithmetic. The chosen scale is a testing assumption and does not verify an actual device mode.
At DPR 3.2, the mapping uses 3.2 in each direction and 10.24 raster pixel units of area (DPR²). Browser zoom, OS scaling, and device downsampling can change the observed result.
Responsive testing decisions
The value of this record is its explicit calculation and model scope. It can reproduce a layout scenario without pretending to reproduce every OnePlus setting.
At 450 CSS pixels, check whether cards gain useful space or simply stretch text and buttons. Keep content-driven max widths when a wider phone makes a control unnecessarily broad.
Record the phone display settings and browser-reported screen, viewport and DPR values. Compare them to this calculation to establish which assumption differs.
Generate assets from the component’s measured CSS size and output requirements. A QHD+ panel does not mean every thumbnail or canvas must use the full 1440-pixel width.
Test a long form in the 990-pixel scenario, then reduce the available height to represent controls and the keyboard. Confirm the completion action remains reachable without requiring the original height.
Limits of a static record
A model name and portrait reference cannot reproduce every browser, accessibility, orientation, keyboard, or safe-area condition.
Evidence and provenance
OnePlus lists a 6.82-inch display, 1440 × 3168 native pixels and 510 PPI. The 450 × 990 CSS profile is calculated by dividing that grid by an assumed DPR of 3.2. It is an unmeasured full-panel QA scenario, not an observed OxygenOS or Chrome viewport. No real-device browser measurement was performed for this review.
Review method: AI-assisted desk review checked diagonal, native resolution, aspect ratio and stated density against OnePlus. The old 450 × 1000 profile was corrected to 450 × 990 so its explicitly assumed 3.2 scale is arithmetically consistent. Browser toolbars, display modes and actual DPR remain unmeasured.
Reviewed September 5, 2026 by ScreenMetricLab Editorial Team.
Frequently asked questions
No default browser claim is made. It is a calculated full-panel scenario using a chosen DPR of 3.2; actual Chrome and system settings were not measured in this review.
3168 native pixels divided by the scenario’s assumed 3.2 DPR is 990. The earlier height did not use the same arithmetic, so the revised profile makes its calculation reproducible.
Yes. Native pixels and CSS layout units serve different purposes. Use the browser’s measured width and DPR rather than substituting the panel specification into a breakpoint.
Include exact model, OS and browser versions, display and zoom settings, orientation and measured viewport values. First reproduce the reported dimensions, then test the real device behavior.
Continue testing
Related Android reference
Google Pixel 8a: 6.1-inch display, 1080 × 2400 pixels and 430 PPI, with a clearly labelled 412 × 915 CSS testing profile and live-check guidance.
View referenceRelated Android reference
Google Pixel 9 Pro XL has a 6.8-inch display and 1344 × 2992 native pixels. Review its sourced hardware facts, CSS profile, DPR limits and practical QA uses.
View referenceRelated Android reference
Samsung Galaxy S24 Ultra has a 6.8-inch display and 1440 × 3120 native pixels. Review its sourced hardware facts, CSS profile, DPR limits and practical QA uses.
View referenceRelated Android reference
Samsung Galaxy A55 5G has a 6.6-inch display and 1080 × 2340 pixels. Compare its 360 × 780 CSS scenario, calculated PPI and official display evidence.
View referenceLive browser tool
Measure the current layout and visual viewport before recording a device-specific QA result.
Check viewportMobile layout guide
Keep controls clear of rounded corners, browser UI, and device safe-area boundaries.
Read guide