Mobile Viewer Free browser extension

Google Pixel 6 Pro Screen size & website preview

Keep your form usable at Pixel sizes. Preview your website with the Pixel 6 Pro preset in Mobile Viewer and compare labels, errors and the final action.

Built-in preset

Install extensionChrome Web StoreFree

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

Works with
  • Chrome
  • Edge
  • Opera
  • Brave
  • 412 × 892 CSS px
  • Side-by-side comparison
  • Selected-device PNG
Actual Pixel 6 Pro 412 by 892 preview of the Northline travel form beside desktop
Actual Mobile Viewer workspace

The Google Pixel 6 Pro has a 6.7-inch display with a 1440 × 3120-pixel physical resolution in portrait order. For a website layout check, start with the 412 × 892 CSS-pixel configuration below. Keep screen pixels and CSS layout space separate, then use the practical test to inspect your own page.

Website configuration
412 × 892 CSS pxBuilt-in preset
Physical display
6.7 inches1440 × 3120 hardware pixels
Preset density
3.5×DPR, separate from layout width

Google Pixel 6 Pro 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.

Google Pixel 6 Pro: distinguish the units
MeasurementValueUse it for
Display diagonal6.7 inchesPhysical screen comparison
Physical screen resolution1440 × 3120 pixelsManufacturer hardware reference
Portrait website configuration412 × 892 CSS pxResponsive layout checks
Preset DPR3.5Density configuration, separate from CSS width
Landscape rectangle892 × 412 CSS pxA wider, shorter layout check
Mobile Viewer setupBuilt-in presetChoose Pixel 6 Pro in the device catalogue
Google Pixel 6 Pro portrait CSS rectangle 412 × 892, separately labeled from 1440 × 3120 physical screen pixels
Reference diagram, not an extension screenshot. CSS layout space and physical display pixels use different units; the shape is illustrative.

Why a Google Pixel 6 Pro viewport can vary

The 412 × 892 configuration uses DPR 3.5 in Mobile Viewer. It should not be multiplied back into the maximum 1440 × 3120 physical display resolution as though the two described the same display setting. Android display size and resolution preferences can produce different effective CSS widths.

Measure your target phone if the issue depends on an exact browser state. Record its settings, browser, viewport and DPR, then use a custom width and height to reproduce the layout. A desktop preview cannot establish that all Android configurations behave identically.

Copy-ready website code for the Google Pixel 6 Pro format

Start with the 412 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 Google Pixel 6 Pro. 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 412 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: 412px) {
  .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 3.5 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: 3.5dppx) {
  .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: 412px) calc(100vw - 32px), 480px"
  width="480" height="600"
  alt="Describe the product and relevant visual details">
Tailwind CSS v4 · an optional 412 px checkpoint

At the default 16 px root size, 25.75rem corresponds to 412px. 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: 25.75rem;
}

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

Safe areas, browser controls and fixed actions

The Google Pixel 6 Pro preset records a punch center cutout and inset hints of 36 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 (Linux; Android 13; Pixel 6 Pro Build/TQ2A.230305.008.C1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Mobile Safari/537.36

A Pixel form at a different density from a same-width Galaxy

Compare the Pixel 6 Pro at 412 × 892 with Galaxy S24 Ultra at 412 × 918. Their default CSS widths match, while height and DPR differ. Check the last form action and responsive image selection; a width-only media query cannot distinguish these devices. Record the real Pixel display settings when reproducing a reported issue.

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.

The actual Pixel 6 Pro preset on our local Northline travel demo. Compare field labels and the final action with another 412 px configuration; no booking is sent.

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 412 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.

Google Pixel 6 Pro
412 × 892 CSS px
3.5× preset DPR
Galaxy S24 Ultra
412 × 918 CSS px
2.625× preset DPR

Same CSS width; 26 CSS px difference in height. Compare density and the actual page state too.

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 A17412 × 8912.6250 px
Galaxy S22 Ultra412 × 9152.6250 px
Galaxy S24 Ultra412 × 9182.6250 px
Galaxy Note 5412 × 7323.50 px

Set up this Google Pixel 6 Pro website preview

Install Mobile Viewer in desktop Chrome, open your HTTPS or localhost page and choose Pixel 6 Pro. Confirm the 412 × 892 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 Google Pixel 6 Pro screen size?

The display diagonal is 6.7 inches; its physical resolution is 1440 × 3120 pixels in portrait order. For this website check, use the separately labeled 412 × 892 CSS configuration.

Is Google Pixel 6 Pro a built-in Mobile Viewer preset?

Yes. The current catalogue includes Pixel 6 Pro 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 the target Android browser, display settings and keyboard in a real device environment.

Which CSS media query targets the Google Pixel 6 Pro?

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

What does the 3.5× DPR value mean?

DPR describes a scale along each dimension; the configured preset value here is 3.5. 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 412 × 892, 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