How to capture a website at Nothing Phone 2 screen resolution

The Nothing Phone (2) display is 1080 × 2412 pixels in portrait orientation (2412 × 1080 in landscape). To capture a webpage as it appears on the phone, open it and press Power + Volume Down at the same time. For a longer page, use Capture more if Android offers it. If a file must have exactly 1080 × 2412 pixels, inspect the saved image and crop or resize a copy: the display specification does not guarantee that every screenshot export has those dimensions.

Choose the kind of capture you need

Goal	Method	What to expect
Record the visible webpage as shown on the phone	Native screenshot: Power + Volume Down	Captures the current screen, including whatever browser and system interface is visible.
Include more of a scrollable page	Take a screenshot, then tap Capture more if offered	Extends the capture on compatible scrollable screens. Availability is not universal.
Deliver an image with exact portrait dimensions	Capture, inspect dimensions, then crop or resize a copy if needed	Target 1080 px wide × 2412 px tall. Exact output may require post-processing.
Show motion or a scrolling walkthrough	Use Android screen recording	Produces a video rather than a still image.

The Phone (2) screen specification is 1080 × 2412 pixels; Nothing’s product page writes the same portrait display dimensions as 2412 × 1080 pixels and lists 394 ppi. Those figures describe the display, not a universal guarantee for exported screenshot files. Nothing Support: Phone (2) screen resolution · Nothing Phone (2) product page.

Capture the visible website on Phone (2)

Open the webpage in your browser and wait for the content you want to appear.
Position the page, then press Power and Volume Down simultaneously.
Use the screenshot preview to review, edit, or share the image. You can also find it in the screenshot album in Google Photos.

This records the screen as displayed. Browser controls, the status bar, orientation, and the content’s current position affect what is in the image. To capture a specific web element or the page without browser chrome, use a browser-based capture workflow instead of assuming the native screenshot will isolate it.

The Phone (2) guide documents the button combination and screenshot album. Phone (2) user guide.

Capture more of a scrollable page

Take a normal screenshot with Power + Volume Down.
If Android displays Capture more, tap it.
Drag the crop guides to include the additional page area you need.
Save the expanded capture and review the result for missing or repeated content.

Scrolling capture is available on Android 12 and later on most screens that allow scrolling, according to Android Help. It may not appear for a particular webpage, browser state, or interface. If the control is missing, capture the visible screen and take additional screenshots while scrolling, or use a full-page browser capture tool. Android Help: take a screenshot or record your screen on an Android device.

Get an exact 1080 × 2412 image

For a portrait file with strict pixel dimensions, use 1080 px wide × 2412 px tall as the target. A native screenshot is useful when the goal is to preserve what the phone showed, but the display specification is not a promise about every saved image’s dimensions. Expanded captures are longer, and orientation or visible system and browser bars can also change the image bounds.

Capture the webpage using the native method or a browser capture workflow.
Open the saved image’s details or properties and check its pixel width and height.
If it is not 1080 × 2412, make a copy and crop or resize that copy to the required dimensions.
Check the result at the intended use size. Cropping removes content; resizing changes its scale and can affect sharpness.

If the source has a different aspect ratio, choose whether to crop, add empty space, or stretch it. Cropping preserves proportions but discards edges; stretching can distort the webpage. Keep the original if you may need to revisit that choice.

Capture from a computer at Phone (2) viewport dimensions

When you need a webpage image rather than a photograph of the actual phone display, a browser automation tool can set a 1080 × 2412 CSS-pixel viewport and save a screenshot. A desktop browser does not reproduce every Phone (2) hardware or Android-browser behavior, but it gives you control over the requested viewport dimensions.

Playwright with Node.js

Install Playwright and its Chromium browser, then save the following as capture.mjs:

npm install playwright
npx playwright install chromium

import { chromium } from 'playwright';

const url = process.argv[2] ?? 'https://example.com';
const browser = await chromium.launch({ headless: true });
const page = await browser.newPage({
  viewport: { width: 1080, height: 2412 },
  deviceScaleFactor: 1,
});

try {
  await page.goto(url, { waitUntil: 'networkidle', timeout: 60000 });
  await page.screenshot({ path: 'phone-2-viewport.png' });
} finally {
  await browser.close();
}

Run it with node capture.mjs https://example.com. This produces a viewport screenshot at the configured browser viewport, not necessarily a full-page capture and not a guarantee of matching the physical phone’s browser rendering. Set fullPage: true in page.screenshot to capture the full document; the resulting image will be taller than 2412 pixels when the page exceeds the viewport. Playwright documents viewport configuration and screenshot options in its screenshots guide.

A device scale factor of 1 requests one output pixel per CSS pixel. A higher factor creates a denser raster image, so its pixel dimensions differ from the viewport dimensions. If the deliverable must be exactly 1080 × 2412 pixels, keep the scale factor at 1 and inspect the resulting file.

Or skip the browser setup

ScreenshotNeo can capture a webpage with one API request. Its API accepts a URL and returns an image or PDF; the documentation is at ScreenshotNeo API docs.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://example.com"},
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);

These calls capture a webpage URL; they do not set a 1080 × 2412 viewport by themselves. See the API docs for supported parameters, including viewport settings. ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture; each cleanup step can be disabled. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers report the page verdict and billing status. Its MCP server lets AI agents use take_screenshot, get_page_info, and capture_pdf. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots.

Moving capture: screen recording

For a scrolling demonstration, use the Screen Record tile in Quick Settings. If it is not visible, open the Quick Settings edit control and add it. Nothing’s support instructions say recordings are available in Google Photos under Library > Movies. This creates a video, so use a screenshot when you need a still image. Nothing Support.

Troubleshooting

Symptom	Likely cause	What to do
Power + Volume Down does not capture	The buttons were not pressed together, or one button was held too long.	Press both briefly at the same time. If needed, try again after closing a transient system overlay.
Capture more is absent	The current screen or browser state does not support scrolling capture.	Use multiple screenshots while scrolling, or capture the page in a browser automation workflow.
The image is not 1080 × 2412	Display resolution does not guarantee screenshot-file dimensions; orientation, capture extent, and visible bars affect output.	Check file properties and crop or resize a copy to the required dimensions.
The webpage looks different from the phone	A desktop browser viewport is not the same environment as the Android browser on Phone (2).	Use a native screenshot for actual on-device appearance, or capture on the device when Android-specific rendering matters.
The browser automation capture hangs	The page may keep network connections open, preventing a network-idle condition.	Use a bounded timeout and consider waiting for `domcontentloaded` or a specific selector instead of network idle.
The screenshot is too tall	Full-page capture includes content below the viewport.	Disable full-page mode for a viewport image, or crop the saved copy to the target bounds.

Performance, reliability, and file handling

Wait for the content you need. A page can render its main content before images or client-side widgets finish. In automation, wait for a meaningful selector when the page has a clear readiness signal.
Keep the capture bounded. Full-page images of long pages consume more memory and may be awkward to share or process. Capture the viewport when that is all the deliverable needs.
Check pixel dimensions after capture. Viewport CSS dimensions, device scale factor, full-page mode, and post-processing determine output size.
Preserve the original. Crop and resize a duplicate so you can recover the full capture if the required framing changes.
Consider privacy. A screenshot can contain account details, notifications, or personal data. Review and crop it before sharing.

FAQ

Is the Nothing Phone (2) screen 1080 × 2412 or 2412 × 1080?

Both describe the same display in portrait versus landscape axis order. Portrait is 1080 pixels wide by 2412 pixels tall.

Does Capture more always work in a browser?

No. Android describes scrolling capture as available on most scrollable screens on Android 12 and later. The option can be unavailable on a particular screen.

Can a 1080 × 2412 browser viewport guarantee a Phone (2)-accurate screenshot?

It sets the requested CSS viewport dimensions, but it does not reproduce the phone’s physical display, Android interface, or every mobile browser behavior.

Where do Phone (2) screenshots go?

The Phone (2) guide points to the screenshot album in Google Photos.