Browsers and device profiles
Saved Playwright tests support Chromium, Firefox, and WebKit through project configurations. In New run, choose a basic Device profile or expand Advanced configurations to choose specific files.
Supplied Playwright profiles
New projects include these configuration files under Configurations/:
| Profile | Browser engine | Viewport |
|---|---|---|
Desktop-Chrome (Default.config.js) | Chromium | 1920 × 1080 |
| Desktop-Firefox | Firefox | 1920 × 1080 |
| Desktop-Safari | WebKit | 1920 × 1080 |
| Tablet-iPad | WebKit | 834 × 1194 |
| Mobile-iPhone | WebKit | 393 × 852 |
| Mobile-Android | Chromium | 412 × 915 |
The table describes the current project template. Existing projects can have different or customized configurations. Settings → Playwright shows the files in your project.
WebKit is the engine used for Safari-oriented testing; an emulated iPhone or iPad profile is not a test on physical iOS hardware. A viewport alone does not reproduce every device characteristic.
Other execution modes
Assistant runs offer Desktop, Tablet, and Mobile profiles for their browser session. They do not execute your saved Playwright configuration files.
Browser-VU load tests always launch Chromium. They read one selected configuration for supported context settings, including viewport, base URL, HTTP credentials, permissions, geolocation, and reduced motion. They do not switch to Firefox or WebKit based on that file, and selecting a profile does not run a multi-browser matrix. HTTP load tests do not render a browser.
See configurations and load testing.