How to Screenshot an Indian Travel Website at Samsung Galaxy A15 Size

To screenshot an Indian travel website at Samsung Galaxy A15 size, open it in Chrome, enable DevTools Device Mode, and set a responsive viewport to the CSS dimensions you want to inspect. Then choose Capture screenshot for the visible screen or Capture a full size screenshot for the whole page. Samsung lists the Galaxy A15 5G display as 1080 × 2340 physical pixels, but that does not establish one universal browser viewport in CSS pixels. For an exact device result, capture the site on the phone itself.

Choose the right capture method

Method	Best for	Record or check
Chrome DevTools responsive/custom device	A quick, repeatable image of a responsive layout	CSS viewport width and height, DPR, orientation, and whether the image is viewport-only or full-page
Actual Galaxy A15	Checking Samsung Internet, browser UI, touch interaction, or device-specific rendering	Browser, orientation, zoom/settings, and normal screenshot versus Scroll capture

Samsung Developer lists the Galaxy A15 5G with a 6.5-inch display and 1080 × 2340 resolution. Samsung Pakistan gives the same display figures for the SM-A155F. These are physical panel specifications, not a guaranteed browser viewport size. Device pixel ratio (DPR), browser chrome, zoom, and settings affect how physical pixels relate to CSS pixels. [Samsung Developer: Galaxy A15 5G; Samsung Pakistan: Galaxy A15 specifications]

Capture the site in Chrome DevTools

Open Chrome on your computer and navigate to the Indian travel website you want to capture.
Open DevTools: use the browser menu’s developer tools option or the keyboard shortcut for your operating system.
Turn on the device toolbar using the device toolbar control in DevTools.
Select Responsive, or open the device list’s edit/settings controls and add a custom device. Chrome’s custom device settings support a name, width, and height; DPR, user-agent string, and device type can also be set when the test calls for them. Choose and record the intended CSS viewport dimensions. Do not derive a CSS width from the A15’s 1080-pixel panel specification alone.
Use portrait orientation for a typical phone layout. Rotate to landscape if that is part of the check. Visit relevant responsive breakpoints if you need to assess how the page changes as the viewport narrows or widens.
Inspect the parts of the travel flow that matter: destination search, dates, passenger controls, price or availability cards, menus, and booking calls to action. These are useful inspection targets, not claims about any particular website.
To capture what is currently visible, select More options > Capture screenshot. To include below-the-fold content in one image, select Capture a full size screenshot.

Chrome documents both capture options and notes that device mode cannot reproduce every aspect of mobile hardware and behavior. Use a live phone when the result depends on the actual browser or device. [Chrome DevTools: Device Mode]

Set viewport dimensions and DPR deliberately

Viewport width and height are the dimensions the responsive page uses in CSS pixels. DPR describes the ratio between physical screen pixels and logical CSS pixels. They answer different questions: viewport dimensions determine layout breakpoints, while DPR affects pixel density in rendering. For a responsive-layout review, start with a chosen CSS viewport and do not add a DPR or user-agent override unless the behavior under test requires it. For device-specific rendering, document the values you used and compare against the phone.

Need a repeatable layout mockup: use a custom or responsive viewport and write down its width and height.
Need a particular pixel density: set DPR as part of the custom device configuration and include it in capture notes.
Need Samsung Internet behavior: test in Samsung Internet on the handset; a user-agent override alone does not reproduce the browser.
Need landscape: rotate the emulated viewport or the phone and capture that orientation separately.

Chrome’s documentation explains that DPR relates hardware-screen pixels to logical CSS pixels and cautions that emulation cannot simulate every mobile feature. Its device controls and menus can change over time, so follow the labels shown in your installed Chrome version. [Chrome DevTools: Device Mode]

Capture on the actual Galaxy A15

Open the travel website in the browser you need to validate and navigate to the page or state you want.
Hold the Side button and Volume Down buttons together briefly to take a screenshot.
For a long page, tap Scroll capture after the screenshot to extend the capture down the page, if the option is available.
Find saved captures in Gallery > Albums > Screenshots, or in My Files > Images.

Samsung also documents a palm-swipe capture gesture that can be enabled under Settings > Advanced features, though labels and availability can vary by model and software version. The button shortcut is the simplest starting point. Samsung describes Scroll capture as a way to capture lengthy content in one image. [Samsung Support: Take a screenshot]

What to include in a useful screenshot

Before sharing a capture, note the URL, date, browser, viewport width and height in CSS pixels, DPR if set, orientation, and capture type. This makes a later comparison meaningful and avoids implying that an emulated image is a pixel-exact record of every A15 configuration. If you are reviewing a booking flow, capture the relevant state without exposing personal details or booking information.

Or skip the browser setup

ScreenshotNeo can capture a page with one API request. Its API accepts a URL and returns an image or PDF. For a mobile layout, provide the relevant viewport settings using the documented API options; consult the ScreenshotNeo API documentation for parameter names and supported values. A server-side screenshot does not reproduce a live Galaxy A15 or Samsung Internet session, so use the phone when that fidelity matters.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://www.makemytrip.com/ \
  -o travel-site.webp

Python

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={
        "access_key": "YOUR_API_KEY",
        "url": "https://www.makemytrip.com/",
    },
    timeout=90,
)
r.raise_for_status()
with open("travel-site.webp", "wb") as image_file:
    image_file.write(r.content)

Node.js

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://www.makemytrip.com/',
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('travel-site.webp', image));

Replace the example URL with the page you are authorized to capture. Add viewport and other capture parameters from the API documentation. ScreenshotNeo removes cookie/consent banners, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server offers screenshot tools for Claude, Cursor, and other MCP clients.

The free plan includes 1,000 screenshots a month with no card. Paid plans start at $5 for 3,000 shots; every feature is on every plan. Create a free ScreenshotNeo account.

Troubleshooting

Symptom	Likely cause	What to do
The emulated layout does not match the A15	The chosen CSS viewport or DPR differs, or the site responds to browser/device behavior that emulation does not reproduce	Record the dimensions and DPR; compare in the actual phone browser for device-specific validation.
The screenshot is only the visible portion	You used viewport capture	Use DevTools’ full-size screenshot option or the phone’s Scroll capture where available.
Content appears cut off in a full-page capture	The page may load more content on scroll or rely on lazy loading	Scroll through the page first, wait for content to appear, then capture again; inspect sections separately if the page changes as it scrolls.
The custom device option is missing or labels differ	DevTools controls vary between Chrome versions	Use Responsive mode and set dimensions directly, or consult the current Device Mode documentation.
Screenshot button shortcut does not work	Button timing or software behavior can vary	Press Side and Volume Down briefly together. Check Settings for the palm-swipe option if preferred.
API response is an error or not an image	The key, URL, or request parameters may be invalid, or the page may fail to load	Check the API response and headers, verify the key and URL, and confirm parameter names in the docs. ScreenshotNeo responses identify page verdict and billing status.

Performance, reliability, and cost

DevTools is a convenient local option for a one-off responsive screenshot and does not require an API capture service. A real-phone capture is the appropriate check for browser-specific output but requires access to the handset and the relevant browser state. For repeatable captures in code or a workflow, an API can avoid maintaining browser automation setup; account for request timeouts and the target page’s load behavior. ScreenshotNeo’s requests can take up to the timeout you configure in your client, and its example integration uses a 90-second timeout. Check response status and save the returned bytes only after a successful request.

ScreenshotNeo bills clean shots; bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing. Inspect the response’s X-Page-Verdict and X-Billed headers when tracking usage. Plans are Free (1,000/month), Starter ($5 for 3,000), Growth ($15 for 15,000), Pro ($39 for 60,000), Scale ($99 for 250,000), and Business ($249 for 1,000,000); yearly billing gives two months free. Confirm current plan details on the product site before choosing a plan.

FAQ

Is 1080 × 2340 the right DevTools viewport for a Galaxy A15?

Those are the listed physical display pixels, not a universal CSS browser viewport. Set and report CSS dimensions for responsive testing; use the handset for an exact browser/device check.

Can DevTools prove how the site looks in Samsung Internet?

No. Emulation is useful for responsive layout checks but does not reproduce every real browser feature. Open the site in Samsung Internet on the phone when that behavior matters.

Should I use a normal screenshot or a full-page/scroll capture?

Use a normal viewport capture to document what a visitor sees at one moment. Use full-page or scroll capture when the below-the-fold content is part of the review.

Can I use ScreenshotNeo to capture the actual phone screen?

No. It captures a web page through its API; it does not capture the handset’s browser chrome or prove how a specific A15 renders the page.