A project's videos record on the desktop unless you say otherwise. Choose a device and the same guide is recorded as that phone or tablet: Chrome's device emulation gives the app a touch screen, a mobile browser and the device's exact size, so it shows its mobile layout, its menu button and its stacked forms. Nothing about the guide, the login, the effects or the credits changes.
Choosing a device
Under the project's Video tab, pick a Device. Every run of the project records as that device unless the record button's own device menu says otherwise. One run is one device and one video: for a desktop version and a phone version of the same guide, start two runs.
| Device | Screen |
|---|---|
| iPhone 17 Pro | 402 × 874 |
| iPhone 17 Pro Max | 440 × 956 |
| Pixel 10 | 412 × 924 |
| Pixel 10 Pro XL | 413 × 920 |
| iPad | 1180 × 820, sideways |
| iPad Pro 11 | 1210 × 834, sideways |
| Galaxy Tab S10+ | 1400 × 876, sideways |
The list is short on purpose and always the current models; a new model replaces the old one. Phones are recorded upright, tablets sideways.
Video format
A phone run is delivered in one of three formats:
| Format | What you get | For |
|---|---|---|
| Vertical 9:16 (default) | 1080 × 1920, the phone in a frame on a backdrop | Reels, TikTok, Shorts, app-store style previews, vertical embeds |
| Widescreen 16:9 | 1920 × 1080, the phone upright and centred on a backdrop | YouTube, 16:9 help centres, slides |
| Full screen | the phone's screen alone, 1080 wide, no frame | when you frame it yourself |
Tablets offer widescreen or full screen. 4K doubles every canvas.
The backdrop behind the frame is a neutral warm grey, or the colour of your brand kit when the project has one. The frame itself is a generic phone body: rounded corners, a thin rim, no maker's likeness.
Writing a guide for a phone
The same guide usually works. Two things differ on a touch screen:
- There is no pointer, so a hover step does nothing; the recorder skips it and says so in the run's activity. Write the click that opens the menu instead.
- Navigation sits behind a menu button. When the thing you name is in that hidden menu, the recorder taps the menu button itself and then your link; you can also name the button ("the menu button", "Menu") and open it in your own words.
Keep zoom factors at 1.4 or below; on a phone a 1.6 zoom shows a quarter of the screen. The pointer effect becomes a fingertip landing on the target.
From an agent or the API
create_project and update_project take device, frame and backdrop as the project's
defaults; start_run takes the same three as overrides for one video; get_run reports the run's
output. On the REST API, pass them in config_overrides when starting a run.
{ "project_id": "01K…", "config_overrides": { "device": "iphone", "frame": "landscape" } }
What it costs
The same as a desktop video at the same settings. A phone version of a guide is its own run.
What it is not
Chrome's emulation shows the app the way a phone browser lays it out; it does not run Safari or Chrome for Android, so a native date picker or the software keyboard look like Chrome's. Native apps, iOS or Android, are not recorded; a web app opened in a browser is.