Devices reference

A device preset sets several viewport properties with one id. It is the fastest way to get a realistic phone, tablet or laptop capture. This page lists all 15 devices, the size of the image each one produces, and what a device changes in the browser. It is part of the API documentation. For when to use a device and when a custom viewport is better, read the mobile screenshots guide.

Use a device

GET, with a flat query parameter:

curl -G https://api.renderscreenshot.com/v1/screenshot \
  -H "Authorization: Bearer $RS_API_KEY" \
  -d url=https://example.com \
  -d device=iphone_14 \
  -o phone.png

POST, with device at the top level of the body, next to url:

{
  "url": "https://example.com",
  "device": "iphone_14"
}

Keep device at the top level. In the current API version, a request that nests it as viewport.device passes validation but renders at the default 1280 x 800 desktop viewport.

With the Node.js and Python SDKs (client and TakeOptions as set up in the SDK docs):

// Node.js
const image = await client.take(TakeOptions.url('https://example.com').device('iphone_14'));

# Python
image = client.take(TakeOptions.url('https://example.com').device('iphone_14'))

All devices

The output size is the image you get from a viewport capture: CSS viewport times scale, rounded to whole pixels. We measured it by repeating the renderer's viewport step for each device in Chrome (see the method note below).

iphone_14 and iphone_13 share a viewport. They differ only in the iOS version in the user agent. GET /v1/devices returns this list from the API, and it is the list the API validates against. See list devices.

What a device sets, and what it does not

Override part of a device

Explicit viewport values win over the device. Everything you do not set still comes from the device. This request keeps the iPhone 14 scale, mobile mode and user agent, and turns the viewport to landscape:

{
  "url": "https://example.com",
  "device": "iphone_14",
  "viewport": { "width": 844, "height": 390 }
}

The same rule gives you a smaller file: add "scale": 1 to viewport to keep the phone layout at one third of the pixel width of a scale 3 device. The retina screenshots guide covers the cost of a high scale.

Unknown device ids

A device id that is not in the list fails before any rendering, so a typo never uses a credit:

{
  "error": {
    "type": "validation_error",
    "code": "invalid_device",
    "message": "Unknown device 'iphone_15'. Use GET /v1/devices to see available devices.",
    "param": "device",
    "retryable": false,
    "docs": "https://renderscreenshot.com/docs/errors/error-codes"
  },
  "request_id": "3f1c9a52-7d4e-4b8a-9e21-6c0d5b7a8f13"
}

The device record

Each entry from GET /v1/devices has this shape:

{
  "id": "pixel_7",
  "name": "Google Pixel 7",
  "viewport": {
    "width": 412,
    "height": 915,
    "device_scale_factor": 2.625,
    "is_mobile": true,
    "has_touch": true
  },
  "user_agent": "Mozilla/5.0 (Linux; Android 13; Pixel 7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Mobile Safari/537.36"
}

For a device that is not in the list, set viewport.width, viewport.height, viewport.scale and viewport.mobile, and send the device's user agent in browser.user_agent. The viewport parameters list the limits.

Method, 2026-10-15: we read the 15 device records from the API source and repeated the renderer's viewport step for each one (page.setViewport with width, height, scale and mobile, plus the device user agent) in Puppeteer 24.43.1 with Chrome Headless Shell, then captured https://example.com. The output column is the PNG size from that run. The touch result comes from matchMedia('(pointer: coarse)') in the same run. The override and viewport.device behaviour come from the API's parameter code with the same inputs. These are not API renders.

See also

• Mobile screenshots: when width alone is not enough
• Presets: the mobile and mobile_landscape presets, which also set format and cache
• List devices: the endpoint behind this table