The fastest way to check your iPad screen resolution is to open an in-browser tool such as Screen Resolution Checker in Mobile Safari, which reads the labeled CSS screen width, available area, current viewport, outer window dimensions, device pixel ratio, and an estimated device-pixel multiplication that the page can display and copy. The iPad Settings app identifies the model but not the raw pixel count, so a live browser readout is the most direct way to see what Safari actually exposes about the panel today.
The numbers the tool shows are not the same thing as the marketed resolution on Apple's spec sheet. They come from standard browser objects, are affected by zoom, orientation, multitasking, and any Sidecar or external display situation, and are explicitly labeled as CSS coordinates rather than physical inches or a guaranteed native pixel count. Treating the readout as the truth about Safari's coordinate space, and as a strong hint about the backing store when the multiplication is honest, is the right frame, while treating it as a substitute for the panel's true advertised resolution is not.
What the iPad Settings App Shows About Resolution
On a current iPad running iPadOS 18, the Settings app does not display a "Resolution" field anywhere in the Display or General sections. What Settings does show is the model name (for example "iPad Pro 13-inch (M4)") and, on some models, a hardware summary that includes the chip and storage tier. From the model name you can map to Apple's published spec sheet, which lists the resolution in pixels and the pixel density in pixels per inch, but Settings itself does not say "2732 × 2048" anywhere you can find by tapping through menus.
That gap is why many readers land on a search for "screen resolution on iPad" in the first place: the obvious place to look does not show the value. A few additional places expose partial information without using a third-party tool. The About panel shows the model identifier and the iPadOS version. The Accessibility → Display & Text Size panel shows whether Reduce White Point, Bold Text, or Smart Invert are on, but not pixel counts. Apple's specifications page for the identified iPad model is the authoritative source for the marketed resolution; everything reported on-device is a derived, situational, or browser-mediated number.
Why Safari Reports Different Numbers Than the Spec Sheet
Mobile Safari exposes coordinates through standard web APIs. For the iPad, screen.width and screen.height describe the coordinate space that web content sees, and they are typically reported in CSS pixels rather than physical panel pixels. devicePixelRatio then tells Safari how many physical pixels correspond to one CSS pixel for the current view. On common iPad models, devicePixelRatio is 2; on iPad Pro models with a higher-density Liquid Retina XDR or Ultra Retina XDR panel, the ratio can be 2 or 3 depending on configuration and display zoom setting.
A few other values appear on the same page and they are not interchangeable. screen.availWidth and screen.availHeight may exclude system interface areas. window.innerWidth and window.innerHeight describe the page layout viewport inside Safari and account for the address bar, tab bar, and any reader-mode or fullscreen adjustments. window.outerWidth and window.outerHeight describe the entire browser window when Safari exposes them; otherwise the page falls back to the viewport. Each of these is a snapshot of a specific coordinate environment, and none of them by itself is the panel's advertised resolution.
Read the iPad Resolution in Mobile Safari
- Wake the iPad, unlock it, and orient the device in the position you want to measure (portrait or landscape). The readout will follow what Safari reports at that moment.
- Open Safari and navigate directly to the Screen Resolution Checker page, then let it load fully before rotating or scrolling.
- Wait until the labeled fields on the page settle to a stable set of numbers, then read the CSS screen width and height first; these are the coordinate space Safari exposes to web content.
- Read the available area, viewport, and outer window values beneath the screen fields so you can see how much space Safari chrome is occupying relative to the full screen.
- Read devicePixelRatio and the estimated device-pixel multiplication that the page displays in the same panel, and treat the multiplication as a labeled estimate rather than a guarantee of native panel pixels.
- Note whether the orientation label on the page reads Portrait, Landscape, or Square; that label only compares the two reported CSS numbers and is not an accelerometer reading.
If a particular reading is what you actually need (for example a CSS screen width for laying out a responsive design, or an estimated device-pixel value for picking an asset size), write it down at this moment rather than after rotating the device, because rotating will change several values at once.
What Each Field on the Screen Means
The page presents its values with explicit labels so the reader can match each one back to the browser object it comes from. The relationship between the field, its source, and what it represents is summarized below.
| Field | Browser source | What it represents |
|---|---|---|
| Screen width and height | screen.width, screen.height | The CSS coordinate space exposed to web content, not the panel's marketed or native pixel count. |
| Available width and height | screen.availWidth, screen.availHeight | Screen area excluding operating-system interfaces such as the iPadOS status bar region or task switcher overlay. |
| Viewport width and height | window.innerWidth, window.innerHeight | The layout viewport that the page can fill, smaller than the screen whenever Safari chrome is visible. |
| Outer window width and height | window.outerWidth, window.outerHeight | The full browser window when iPadOS exposes a positive outer value; falls back to the viewport when not available. |
| Device pixel ratio | window.devicePixelRatio | The ratio the browser uses to convert CSS pixels into backing-store pixels for the current view. |
| Estimated device pixels | Calculated as round(CSS screen × ratio) | A deliberately labeled estimate, useful as a backing-store hint but not a guarantee of native panel pixels. |
| Orientation label | Comparison of reported CSS width and height | Portrait if height is greater, Landscape if width is greater, Square if equal; no accelerometer is read. |
The fields are refreshable and re-readable: rotating the iPad, toggling Safari into fullscreen reader mode, sliding Split View, or attaching an external display will change at least one of the values. Resize the browser by rotating the device or by tapping the page-zoom indicator in the URL bar to refresh the displayed numbers without reloading the page.
Copy a Report and Re-Measure After Resizing
The same page includes a Copy report control that places the visible fields in plain text on the clipboard. That makes it possible to capture a snapshot of Safari's coordinate environment and paste it into a note, a bug report, or a message to a designer without taking a screenshot. To produce a useful before-and-after record, copy the readout twice in a row: once before a change, and once after it.
A change worth documenting with a copy is the change of any single condition you actually care about. Examples include changing Safari's Page Zoom from 100% to a higher value, rotating the iPad between portrait and landscape, entering Safari's fullscreen reader mode, moving the page into Split View with another app, connecting a Sidecar display and dragging the Safari window onto it, and changing the iPadOS display zoom between Standard and Larger Text in Accessibility settings. Each change will move at least one of the visible fields, and recording the exact values before and after is the tool's recommended way to build a troubleshooting report.
For a single concrete worked example, when Safari reports a CSS screen width of 1440 with devicePixelRatio equal to 2, the page computes the estimated device-pixel multiplication as 1440 × 2 = 2880, then rounds to 2880. That calculation is openly displayed on the page, and the Copy report text contains exactly that value alongside the other fields.
The tool does not save any of this history. Reload the page, switch tabs, or close Safari and the previous values are gone. If you need to compare values across sessions, paste each report into a note or a document immediately after copying.
Pair the Readout With a Before-and-After Check
A live readout on its own only describes one moment. To make it useful for a real task, capture the same set of values under two different conditions and compare them. The difference is the signal; either side by itself is only a snapshot. Common pairs include the same page in portrait versus landscape, in regular Safari versus Safari's fullscreen reader mode, and on the iPad display alone versus the same Safari window on a Sidecar-attached external display.
When the two reports match field-for-field, the change you made did not move any coordinate the browser exposed. When they differ, look first at viewport and outer window because those are the layers Safari controls, then at screen width and height, then at the multiplication result. The orientation label changes whenever width and height swap magnitude, and that single line is often the fastest sanity check that the device actually rotated from the browser's point of view.
For a wider set of conditions and a step-by-step walkthrough for desktop browsers, the related guide on checking screen resolution in any browser covers the same fields from a different angle, and the guide on getting screen resolution back to normal is the right next read when the value on the iPad is not what you expected and you want to reset it.