Skip to content
ScreenMetricLab

Cookie settings

Manage your preferences

Essential features

Required for security, page delivery, and remembering this privacy choice.

Always on

Advertising

ScreenMetricLab does not currently serve ads. Advertising consent controls will be added before ads are enabled.

Not in use

Compact 2021 iPhone reference

iPhone 13 mini Screen Size, Resolution and Compact Viewport

A compact-phone reference for crowded navigation, form controls and short-screen interactions, with a separate explanation of native pixels and the CSS profile.

Reference scope: iPhone 13 mini (2021), excluding iPhone 13 and iPhone 12 mini.

iPhone 13 mini screen reference diagram Display outline showing a 375 by 812 CSS pixel reference and 1080 by 2340 native pixel grid for this phone record. 375 × 812 CSS pixel reference 1080 × 2340 native pixel grid 5.4 in · 476 PPI DPR 3 reference
Reference diagram, not a product rendering. Rounded corners, browser controls, safe areas, and the live visual viewport reduce or reshape usable content space.

Two measurement layers

Hardware specifications and browser reference

The native display values come from Apple. CSS dimensions are a normalized testing baseline and remain dependent on browser state.

Screen and viewport specifications for iPhone 13 mini
FieldReference valueEvidence scope
Display diagonal5.4 inchesApple specification: 5.4-inch class, 5.42-inch standard rectangle; actual viewable area is less.
Native pixel grid1080 × 2340Apple specification in portrait width × height order; not CSS width multiplied by DPR.
Pixel density476 PPIApple-stated hardware density: 476 PPI.
CSS viewport375 × 812 CSS pxRetained compact-phone QA profile; no live Safari measurement in this review.
Device pixel ratio3QA profile assumption; it does not establish native panel dimensions.
Record year2021Model-generation context; verify the exact configuration.
Reference CSS area304,500 CSS px²Calculated from the normalized width and height; not physical screen area.

Manufacturer-verified layer

What the hardware values establish

This page covers the 2021 mini model. Apple distinguishes the marketed 5.4-inch display from a 5.42-inch standard rectangular measurement; rounded corners reduce the actual visible area. Neither measurement describes the phone body or a browser content box.

Browser-dependent layer

How to use the CSS reference

At 375 CSS pixels, the profile is 18 pixels narrower than the iPhone 14 Pro reference. Use that modest reduction to stress long names, segmented controls and two-button rows rather than assuming a compact phone requires different navigation.

At DPR 3, the mapping uses 3 in each direction and 9 raster pixel units of area (DPR²). Browser zoom, OS scaling, and device downsampling can change the observed result.

Responsive testing decisions

Use the mini profile to find controls that are too crowded

A useful compact test keeps the same content and task as the larger-phone version, then checks what breaks when horizontal space shrinks.

Two-action rows

Test cancel-and-confirm or quantity-and-cart controls at 375 pixels with long translated labels. Allow wrapping or stacking before labels become clipped.

Keyboard-constrained forms

Focus the final field in a multi-step form and check that instructions, validation and the next action remain reachable when the visible height contracts.

Dense navigation

Use real section names and signed-in account text in the header. Count actual wrapping and overflow rather than judging an empty navigation mockup.

Screenshot interpretation

A 375-pixel-wide test rendered at DPR 3 would imply a 1125-pixel buffer, while Apple lists a 1080-pixel panel width. Record capture method and dimensions rather than treating these as interchangeable.

Limits of a static record

Verify the state that users actually experience

A model name and portrait reference cannot reproduce every browser, accessibility, orientation, keyboard, or safe-area condition.

  • Keep the 2021 iPhone 13 mini identity in bug reports; a shared CSS width does not make an iPhone SE or another mini generation the same device.
  • Test the 375-pixel profile with increased text size and long content before making buttons or text smaller to fit.
  • Do not use 1080 native pixels as the mobile media-query width, or infer screen inches from a screenshot.
  • Check portrait and landscape safe areas on the target browser. This source review supplies no measured notch or home-indicator inset.

Evidence and provenance

One source, two clearly labelled scopes

Apple lists a 5.4-inch OLED display, 1080 × 2340 native pixels and 476 PPI. The 375 × 812 CSS profile at DPR 3 is a retained browser-testing reference, not an Apple specification. No real-device browser measurement was performed for this review; CSS dimensions multiplied by DPR must not be presented as this model’s native grid.

Review method: AI-assisted desk review of Apple Support checked the model year, display diagonal, native resolution and stated PPI. The existing CSS profile was retained as an unmeasured QA scenario; the review explicitly checked and documented its mismatch with a simple native-pixel multiplication.

Reviewed September 5, 2026 by ScreenMetricLab Editorial Team.

Frequently asked questions

Questions about the iPhone 13 mini display reference

Is iPhone 13 mini a 5.4-inch or 5.42-inch display?

Apple uses 5.4 inches as the display class and 5.42 inches for the standard rectangular diagonal. Rounded corners make the viewable area smaller than that rectangle.

Can I calculate its native resolution as 375 × 812 times three?

No. That gives 1125 × 2436, while Apple lists 1080 × 2340. The retained CSS profile and a native panel specification must be recorded separately.

Is the 375-pixel width a verified Safari measurement?

No real-device measurement was performed in this review. Use it as a compact QA scenario and record the actual layout and visual viewport on your test phone.

Can a layout that works on a larger iPhone still fail here?

Yes. A small reduction in width can wrap one label, enlarge a card or push a control below the visible area. Use long content and keyboard-open states in the compact test.