How to Capture a Website Screenshot at Galaxy Z Fold Cover Screen Size
Set Chrome DevTools to a Galaxy Z Fold cover screen viewport, capture the visible page or full page, and learn when to verify on a real device.
To capture a website at Galaxy Z Fold cover screen size, open the page in Chrome, enable DevTools Device Mode, select Responsive, and enter the target width and height in CSS pixels. For a measured Galaxy Z Fold7 folded portrait example, use 411 × 814 CSS pixels with the browser interface expanded, or 411 × 870 CSS pixels with it collapsed. Set device type to Mobile. Then choose More options → Capture screenshot for the visible viewport, or Capture a full size screenshot for the entire page.
Those dimensions describe a particular Fold7, browser, and UI state—not every Galaxy Z Fold. Use the viewport that matches the model and condition you need to test, and check a physical device when device-specific behavior matters.
Set up the Fold cover viewport in Chrome
- Open the target page in Chrome and open DevTools.
- Toggle the device toolbar. In the device selector, choose Responsive.
- Enter the desired viewport width and height. For the Fold7 reference values, use 411 × 814 or 411 × 870 CSS pixels.
- Set the device type to Mobile. Set device pixel ratio separately if you need to approximate pixel density.
- Reload the page after changing the viewport if the site uses responsive breakpoints or only applies layout changes on load.
- Open the device toolbar’s More options menu. Choose Capture screenshot for the visible viewport or Capture a full size screenshot for the full page.
Chrome Device Mode approximates a mobile device; it does not run the page on a phone. See Google’s Device Mode documentation for the emulation controls and limitations.
Choose the right viewport dimensions
| Target | CSS viewport | Context |
|---|---|---|
| Galaxy Z Fold7 cover, portrait, smaller height | 411 × 814 | Measured with browser UI expanded |
| Galaxy Z Fold7 cover, portrait, larger height | 411 × 870 | Measured with browser UI collapsed |
| Original Galaxy Fold historical example | 320 × 519 | Samsung Developer’s 2020 guidance for a described worst-case configuration; not a current Fold7 size |
The Fold7 measurements are reported for Android 16 and Chrome 134.0.6998.135 by the Effective Viewport Fold7 measurement page. That source also lists a 412 × 960 device-size field and DPR 2.625. The device-size field is not the same thing as the measured browser layout viewport: browser controls and state affect the space available to the page.
For responsive layout work, enter the CSS viewport dimensions. CSS pixels are logical layout units. DPR is the ratio between physical screen pixels and CSS pixels; changing DPR affects density and raster output, not the meaning of the width and height fields. Avoid treating an advertised display resolution as the browser viewport.
Record the test conditions
When you share a screenshot or file a bug, note the Fold generation, orientation, viewport width and height, browser, browser UI state, DPR, and whether the capture is viewport-only or full-page. This makes the result reproducible and prevents a Fold7 measurement from being mistaken for a Fold6 or original Fold target.
Viewport capture versus full-page capture
Capture screenshot saves the content currently visible inside the emulated viewport. Use it to inspect the first screen, navigation, text wrapping, and controls at cover-screen width. Capture a full size screenshot captures the page beyond the viewport height. Use it to review long layouts and below-the-fold sections; it does not change the viewport width used to render the page.
A full-page capture can expose issues that a viewport capture misses, such as lazy-loaded images that have not appeared yet or sticky elements behaving differently during scrolling. Scroll through the page before capturing if its content loads on demand, then inspect the resulting image for missing sections or duplicated sticky elements.
Set DPR and device frame only when needed
Keep the viewport at the target CSS width and height. Change DPR only when testing density-sensitive behavior or when you need an output raster with a particular pixel density. The cited Fold7 reference uses DPR 2.625, but that is a measured configuration, not a required setting for every cover-screen screenshot.
Chrome may offer a device frame in device-specific emulation. If you need a framed presentation image, enable Show device frame before capture when available. A frame is decoration around the rendered page; it does not make the page rendering more representative of physical hardware.
When to verify on the actual phone
Use emulation for repeatable viewport checks, breakpoint debugging, and quick visual review. Verify on a physical Fold when the result depends on browser controls, fold posture, Android behavior, touch input, device-specific rendering, or the way a particular browser handles the cover display. Chrome describes Device Mode as an approximation, not a replacement for running the page on a mobile device.
Fold viewport sizes vary by model, browser, orientation, and interface state. Samsung’s 2020 first-generation Fold guidance described a 320 × 519 front-screen viewport under a specific configuration and warned that available height can vary with browser and navigation conditions. Do not reuse that historical number as a current Fold7 setting.
Or skip the browser setup
If you need a screenshot from a URL without configuring a browser, ScreenshotNeo is a website screenshot API and MCP server. Its options include custom viewport dimensions, device presets, full-page capture, and output as PNG, JPEG, WebP, or PDF. For a Fold cover viewport, use the custom viewport options described in the ScreenshotNeo docs.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpCookie and consent banners are accepted like a visitor and removed, along with supported newsletter popups and chat widgets, before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers say the page verdict and billing status. An MCP server gives AI agents tools to take screenshots, get page information, and capture PDFs. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.
Sign up for 1,000 free screenshots a month, with no card required.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| The page looks wider or narrower than the Fold cover | You entered a physical display size or selected a different device preset instead of the target CSS viewport. | Choose Responsive and enter the intended CSS width and height explicitly. |
| Content is cut off vertically | You captured only the visible viewport. | Use Capture a full size screenshot for the whole page, or scroll to the desired area before taking a viewport capture. |
| The page does not switch to its mobile layout | The device type is set to Desktop, or the page applies responsive logic only during load. | Set device type to Mobile, then reload the page at the target dimensions. |
| The screenshot’s pixel dimensions differ from the CSS dimensions | DPR scales the raster pixel output relative to CSS pixels. | Check the DPR setting. Keep CSS viewport dimensions and output pixel dimensions distinct. |
| The emulated image differs from a real Fold | Device Mode does not reproduce all hardware, browser, and operating-system behavior. | Record the emulation conditions and verify on the target phone for device-dependent issues. |
| Fold measurements from another guide do not match | The guide may cover another generation, browser, orientation, or browser UI state. | Match the model and state. Treat the 411 × 814 and 411 × 870 figures as Fold7 measurements in the cited environment. |
Performance and repeatability
- Reuse a named custom device profile for repeated checks, and record its width, height, device type, and DPR.
- Wait for the page’s important content before capturing. Network speed and client-side rendering can change what appears in an otherwise identical screenshot.
- For full-page captures, allow lazy content to load by scrolling through the page first when necessary.
- Keep capture type consistent across comparisons. Viewport and full-page screenshots answer different questions.
- Use a real phone for final checks that depend on device behavior; desktop emulation is useful for layout work but cannot establish hardware-specific fidelity.
The DevTools workflow does not require a paid screenshot service. An optional physical Fold is only needed when the test requires checking the actual device; it is not required to follow the emulation steps.
FAQ
What viewport size should I use for a Galaxy Z Fold cover screen?
For the cited Fold7 portrait measurements, start with 411 × 814 CSS pixels when browser UI is expanded or 411 × 870 when collapsed. Choose a different measured target for another model or state.
Is a phone’s screen resolution the same as its CSS viewport?
No. Resolution describes physical pixels; CSS viewport dimensions describe the logical layout area available to the webpage. DPR relates the two, while browser controls can further change the available viewport.
Can I capture a full-page screenshot in Chrome DevTools?
Yes. In the device toolbar’s More options menu, choose Capture a full size screenshot. For only the visible area, choose Capture screenshot.
Does DevTools prove the page works on a Galaxy Z Fold?
No. It approximates mobile conditions. Test on the actual phone when the result depends on hardware, browser controls, or device-specific behavior.
