Mobile Viewer Free browser extension

iPhone SE Screen size & website preview

Catch a menu that runs out of room. Preview your website at the compact iPhone SE size and compare it with a larger phone in Mobile Viewer.

Built-in preset

Install extensionChrome Web StoreFree

Free browser extension · No account required · Runs on your computer

Works with
  • Chrome
  • Edge
  • Opera
  • Brave
  • 375 × 667 CSS px
  • Side-by-side comparison
  • Selected-device PNG
iPhone SE product range pictured in Apple specifications
Device image: Apple ↗

This guide uses the 2020 second-generation iPhone SE as its hardware reference. Match the 375 × 667 preset dimensions: the first-generation 2016 SE has a smaller 4-inch display and is represented by the separate iPhone 5/SE configuration at 320 × 568. The iPhone SE has a 4.7-inch display with a 750 × 1334-pixel physical resolution in portrait order. For a website layout check, start with the 375 × 667 CSS-pixel configuration below. Keep screen pixels and CSS layout space separate, then use the practical test to inspect your own page.

Website configuration
375 × 667 CSS pxBuilt-in preset
Physical display
4.7 inches750 × 1334 hardware pixels
Preset density
2×DPR, separate from layout width

iPhone SE dimensions at a glance

Hardware specifications below come from the manufacturer. The CSS dimensions and DPR identify the current Mobile Viewer preset. They do not describe every browser state on the phone.

iPhone SE: distinguish the units
MeasurementValueUse it for
Display diagonal4.7 inchesPhysical screen comparison
Physical screen resolution750 × 1334 pixelsManufacturer hardware reference
Portrait website configuration375 × 667 CSS pxResponsive layout checks
Preset DPR2Density configuration, separate from CSS width
Landscape rectangle667 × 375 CSS pxA wider, shorter layout check
Mobile Viewer setupBuilt-in presetChoose iPhone SE in the device catalogue
iPhone SE portrait CSS rectangle 375 × 667, separately labeled from 750 × 1334 physical screen pixels
Reference diagram, not an extension screenshot. CSS layout space and physical display pixels use different units; the shape is illustrative.

What the iPhone SE screen resolution means for CSS

At a 2× preset scale, divide each physical dimension by 2 to obtain 375 × 667. This is a useful CSS starting rectangle. A 1 px CSS border is not necessarily a single physical display pixel.

Safari controls and the on-screen keyboard can change the visible viewport. The full screen rectangle is therefore different from the space a visitor sees at every moment. Check shorter heights as well, and verify Safari-specific behavior on an actual iPhone or an appropriate testing service.

Copy-ready website code for the iPhone SE format

Start with the 375 CSS-pixel configuration as a test case, then choose breakpoints where your content needs them. These examples describe layout conditions; they do not identify a unique iPhone SE. Expand the example you need and copy its code.

The placeholder image files and component classes below belong to your own project. Replace them before use. Keep zoom enabled and test the result above and below the selected width.

HTML · start with the CSS viewport

Let the browser use its device width for layout. Add viewport-fit=cover only when you also handle edge-to-edge safe areas.

<meta name="viewport" content="width=device-width, initial-scale=1">
CSS · inspect the layout at 375 px and below

An example content breakpoint for stacked product actions. Other devices and resized desktop windows can match the same condition.

@media (max-width: 375px) {
  .product-actions {
    display: grid;
    grid-template-columns: minmax(0, 1fr);
    gap: 0.75rem;
  }
}
JavaScript · record the actual browser state

Read these values in the target browser when reproducing a finding. Visual viewport height may change when the browser UI or keyboard changes.

const viewport = {
  layoutWidth: document.documentElement.clientWidth,
  layoutHeight: document.documentElement.clientHeight,
  visualWidth: window.visualViewport?.width,
  visualHeight: window.visualViewport?.height,
  devicePixelRatio: window.devicePixelRatio,
};
console.table(viewport);
CSS · a density condition, not a phone detector

This condition matches environments at or above 2 dppx. The threshold uses the preset DPR. Use responsive image selection for photographs; a density query alone does not guarantee an appropriate image size.

@media (min-resolution: 2dppx) {
  .brand-mark {
    /* Use a vector asset or a suitable high-density source. */
    background-image: url("/images/brand-mark.svg");
  }
}
HTML · let the browser choose a sharper product image

The sizes rule describes the rendered image width, while srcset provides source widths. Replace the example sizes and files to match your real component.

<img
  src="/images/product-480.jpg"
  srcset="/images/product-480.jpg 480w,
          /images/product-960.jpg 960w,
          /images/product-1440.jpg 1440w"
  sizes="(max-width: 375px) calc(100vw - 32px), 480px"
  width="480" height="600"
  alt="Describe the product and relevant visual details">
Tailwind CSS v4 · an optional 375 px checkpoint

At the default 16 px root size, 23.4375rem corresponds to 375px. Keep custom breakpoints in rem alongside Tailwind’s default units. This illustrative checkpoint is not a requirement to name a breakpoint after every device.

@import "tailwindcss";

@theme {
  --breakpoint-phone-check: 23.4375rem;
}

/* Example markup: */
/* <div class="grid grid-cols-1 phone-check:grid-cols-2">…</div> */

Safe areas, browser controls and fixed actions

The iPhone SE preset records no display cutout and inset hints of 20 px at the top and 0 px at the bottom. These are extension configuration values, not a measured promise about every browser state on the physical device.

For an edge-to-edge page, protect important content on every side and give a fixed bottom action its own padding. Keep ordinary spacing when the environment inset is zero. A drawn notch is not evidence that your real browser will expose a particular env() value.

HTML + CSS · keep an edge-to-edge action inside the safe area

Use with an edge-to-edge layout. Reserve the actual height of your fixed action in the page content. Confirm env() values and keyboard interaction on the target browser; the example does not hardcode a model-specific inset.

<meta name="viewport"
      content="width=device-width, initial-scale=1, viewport-fit=cover">

<style>
  :root { --action-height: 5rem; } /* Match your actual control. */
  .page-content {
    padding-left: max(1rem, env(safe-area-inset-left, 0px));
    padding-right: max(1rem, env(safe-area-inset-right, 0px));
    padding-bottom: calc(var(--action-height) + env(safe-area-inset-bottom, 0px));
  }
  .fixed-action {
    position: fixed;
    inset-inline: 0;
    bottom: 0;
    padding: 1rem;
    padding-bottom: max(1rem, env(safe-area-inset-bottom, 0px));
  }
</style>

User-Agent: the preset fixture and the browser you are testing

The following string is stored in Mobile Viewer’s current preset. Its browser and OS versions are a fixture configuration; they are not a claim about the latest software running on every phone with this model name.

User-Agent strings can be reduced or changed, and iPhones do not reliably expose the exact hardware model through them. A mobile User-Agent also does not replace Chrome’s rendering engine with Safari. Prefer feature detection for application behavior and keep the browser/version with a reproducible issue report.

Current preset User-Agent · reference fixture

Useful as a configuration or log reference, not as a reliable device identity test.

Mozilla/5.0 (iPhone; CPU iPhone OS 13_2_3 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.3 Mobile/15E148 Safari/604.1

A short viewport and a long navigation menu

Open the longest menu at 375 × 667 and find its final link and close control. Then inspect the last required field and submit button in a form. A menu that fits at 390 × 844 can need its own scrolling area at the shorter SE height. Repeat the keyboard interaction on the target phone.

Use the same content and page state in each view. A longer title in one preview can otherwise look like a device difference. Zoom the device frames to fit your monitor without changing the chosen CSS dimensions.

Look

Inspect text wrapping, the main action and any content that reaches the right edge. Open the menu or dialog involved in your task.

Change one thing

Compare the neighboring width or rotate a preview. Keep the content fixed so the layout difference is easy to explain.

Keep evidence

Save a PNG of the selected device or a short recording. Include width, height, orientation and the steps that lead to the result.

Compare a shorter menu space with modern phone layouts. The actual iPhone SE 375 × 667 preview has the Margin menu open; iPhone 18 Pro and Xiaomi show the journal alongside it. Sync is off so each state can be inspected independently.

Mobile Viewer in use

Scroll the image to inspect the details.

Open full original

Compare nearby presets before calling the layout finished

These are actual Mobile Viewer configurations close to 375 CSS px, selected by width and then height. A nearby width can expose a breakpoint transition; the same width with a different height can expose an unreachable menu or dialog action.

No other current built-in preset shares all three values in this reference: width, height and DPR. Custom configurations can still reproduce the same CSS rectangle.

iPhone SE
375 × 667 CSS px
2× preset DPR
iPhone 17 Pro Max
440 × 956 CSS px
3× preset DPR

65 CSS px difference in width. Check whether your component changes between these sizes.

CSS rectangle diagrams at 1:5 scale. In Mobile Viewer, add these configurations beside your desktop page and repeat the task above. Use custom width and height for a configuration without a named preset.

Nearby built-in configurations, not traffic share
PresetPortrait CSS pxDPRWidth difference
Galaxy Z Flip 3384 × 9382.813+9 px
Galaxy S8360 × 7403-15 px
iPhone 13 Pro390 × 8443+15 px
Pixel 5393 × 8512.75+18 px

Set up this iPhone SE website preview

Install Mobile Viewer in desktop Chrome, open your HTTPS or localhost page and choose iPhone SE. Confirm the 375 × 667 preset, then add another useful size for comparison. The workspace supports up to five mobile previews beside desktop.

Follow the page task above, make the CSS change you need and repeat the same check. For a browser-specific fault, keep the desktop finding as a lead and confirm it in the target browser.

Frequently asked questions

What is the iPhone SE screen size?

The display diagonal is 4.7 inches; its physical resolution is 750 × 1334 pixels in portrait order. For this website check, use the separately labeled 375 × 667 CSS configuration.

Is iPhone SE a built-in Mobile Viewer preset?

Yes. The current catalogue includes iPhone SE with the configuration shown above. Confirm real-device behavior separately.

Does this preview test the real mobile browser?

The page renders in desktop Chrome. Use it to review layout and supported interactions at the chosen size; verify iOS Safari, browser controls and keyboard in a real device environment.

Which CSS media query targets the iPhone SE?

CSS queries test conditions such as width, height and resolution, not a unique phone identity. The 375 px example above helps inspect this layout format and narrower windows. Choose breakpoints from your content and test nearby widths too.

What does the 2× DPR value mean?

DPR describes a scale along each dimension; the configured preset value here is 2. At 2×, for example, a square CSS pixel can correspond to a 2 by 2 device-pixel region. Fractional DPR, browser zoom and rasterization add further details. DPR is different from physical pixels per inch and does not identify a unique model.

Why can the visible viewport height change while scrolling?

Browser controls can expand or collapse, and a software keyboard can change the visual viewport. Record both layout and visual viewport measurements when height is involved in an issue; the preset rectangle does not describe every real browser state.

Can I test a localhost development page at this size?

Yes. Open localhost or 127.0.0.1 in desktop Chrome and start Mobile Viewer. For a non-local site use HTTPS. Compare the same content in each view and keep the configuration with your finding.

Watch the Mobile Viewer product demo.

Try this size on your own website

Open your page at 375 × 667, compare one neighboring width and follow the action your visitors need. Start with the free Mobile Viewer Chrome extension.

Install extensionChrome Web StoreFree

Free browser extension · No account required · Runs on your computer