How to Capture a Mobile Website Screenshot at 393 Pixel Width in India
Set a 393 CSS pixel viewport in Chrome DevTools, capture the visible page or full document, and check India-specific page state before saving.
To capture a mobile website screenshot at 393 pixels wide in India, use Chrome DevTools on a desktop: open the page, turn on Device Toolbar, choose Responsive, enter 393 for the viewport width, set a height, then choose More options → Capture screenshot. Choose Capture a full size screenshot for the whole document. The 393 value is a CSS viewport width; the saved image’s physical pixel width also depends on device pixel ratio (DPR). Chrome documents Device Mode, viewport controls, DPR, and screenshot capture.
Capture a 393 CSS pixel viewport in Chrome
- Open the target webpage in desktop Chrome.
- Open DevTools: use F12 or Ctrl+Shift+I on Windows/Linux; on macOS use Command+Option+I.
- Click Toggle device toolbar in the DevTools action bar, or use Ctrl+Shift+M (Windows/Linux) or Command+Shift+M (macOS).
- In the device toolbar, select Responsive. Enter
393in the width field. Enter the height you need as well; the requested width does not determine the height. - Load or reload the target URL while the responsive viewport is active. Wait for the page to settle, then inspect it at that size.
- Open the Device Toolbar’s More options menu and choose Capture screenshot for the visible viewport, or Capture a full size screenshot to include content below the fold.
Chrome downloads the capture. The viewport controls can be adjusted before capture if you need another height or a different DPR. Menu placement and labels can vary slightly across Chrome versions.
Set the right region and output dimensions
Make the page represent India
The 393-pixel procedure does not automatically make a page India-specific. Before saving, verify the exact state the screenshot should show: the selected country or region, language, currency, login state, and any location-dependent content. If location is relevant, DevTools Sensors can override geolocation. That override alone does not guarantee a site will change its language, currency, or other regional rules; the page may use account settings, cookies, IP location, or its own region selector.
Understand CSS pixels and bitmap pixels
The width field sets the responsive viewport in CSS pixels. DPR describes the relationship between a CSS pixel and the screen pixels used to draw it. A 393 CSS-pixel viewport therefore does not necessarily produce a 393-pixel-wide image when DPR is above 1. If exact bitmap dimensions matter, set or record DPR separately and inspect the downloaded image dimensions. See Chrome’s explanation of DPR and device emulation.
Choose viewport or full-page capture
- Capture screenshot: saves what is visible in the emulated viewport. Use this for a mobile screen mockup or above-the-fold review.
- Capture a full size screenshot: captures the page beyond the current viewport. Use this for a complete page review. Very long pages may create large image files and may expose lazy-loading or sticky-element behavior that differs from normal scrolling.
Validate the result on a real phone when needed
Chrome Device Mode approximates mobile usage from a desktop; it does not execute the page on a physical phone. It is useful for responsive layout checks, but hardware, browser behavior, touch interaction, and some device-specific behavior can differ. If the screenshot must match an actual handset, capture on that phone or validate the page there as well.
On Android, take a screenshot with Power + Volume Down, or use the Screenshot option in the Power menu where available. Scrolling screenshots are supported on Android 12 and later on most screens that allow scrolling. On iPhone, press and release the Side button + Volume Up; on iPhones with a Home button, press Home + Side button. Tap the thumbnail and choose Full Page for supported content such as a Safari webpage. These phone methods capture the phone’s actual display, but they do not provide a way to specify an exact 393 CSS-pixel viewport. Sources: Android screenshot help and Apple iPhone screenshot instructions.
Common problems and fixes
| Problem | Likely cause | Fix |
|---|---|---|
| The output is not 393 pixels wide | 393 was set as the CSS viewport, while DPR controls physical output pixels. | Check the output image dimensions and set DPR separately if the bitmap width must be exact. |
| The page still looks desktop-sized | The Device Toolbar was not enabled, the width field did not take effect, or the page did not respond to the viewport change. | Confirm Responsive mode shows width 393, reload, and inspect the page’s layout. A site can have a fixed-width design that does not adapt as expected. |
| The capture shows the wrong language or currency | The website’s region state is controlled by a setting other than viewport width or geolocation. | Set the site’s region and language directly, check account and cookie state, then reload before capture. |
| Images or content are missing | The page may still be loading, lazy-load content only after scrolling, or depend on blocked or failed requests. | Wait for loading to finish; for content below the fold, scroll through the page before a full-page capture and retry. |
| A full-page screenshot is unexpectedly tall or incomplete | Long pages, lazy-loaded sections, and fixed or sticky elements can complicate full-page capture. | Scroll through the page first to trigger lazy content. If the page is very long, capture sections or validate the result against the live page. |
| The emulated view differs from a phone | Device Mode is an approximation and does not run on phone hardware. | Use the phone’s native screenshot or test on the target device for device-specific behavior. |
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server for developers. One GET request can capture an image or PDF, with options including viewport dimensions, device presets, DPR, full-page capture, and region-related settings such as geolocation. See the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);Replace the example target URL with the page you need. Pass viewport width 393 using the API’s documented viewport parameters. Cookie banners, newsletter popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. 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.
FAQ
Does 393 pixels mean a common phone’s exact screen width?
In this workflow it means a 393 CSS-pixel responsive viewport. It is a useful target width, but it does not identify a particular phone model or guarantee identical rendering on every device.
Should I set a specific viewport height?
Yes. Set the height to match the screen area you want to review. The title specifies width only, so choose height based on the task.
Does changing geolocation make every site show its India version?
No. A site may use its own region selector, account, cookies, or other signals. Verify the rendered page state before saving.
Can I use this method for automated recurring captures?
DevTools is convenient for a one-off manual screenshot. For repeated captures, use an automation workflow or a screenshot API and explicitly set the viewport and page state each time.
