Choose the browser that matches the compatibility target you need to test: Chrome or Chromium for general-purpose automation, Firefox for Firefox-engine behavior, WebKit for Safari-oriented coverage, and Microsoft Edge when Edge is the deployment standard. Set the choice with Playwright MCP’s --browser option. Then decide whether you need a visible or headless session, a persistent or isolated profile, or a connection to an existing Chromium-family browser.
Choose by the browser behavior you need to verify
A browser choice is first a compatibility decision, not a ranking of which browser is best. Playwright MCP supports chrome, firefox, webkit, and msedge. If you do not have a specific browser target, Chrome or Chromium is the practical starting point for general web automation. Use the engine or branded channel that corresponds to the users, platform, or deployment environment your work must support.
| Choice | Use it when | Important distinction |
|---|---|---|
chrome or Chromium |
You need a general-purpose starting point or Chromium-based compatibility coverage. | Playwright can use its bundled Chromium engine; branded Chrome can also be reached through a supported channel or CDP connection. |
firefox |
Firefox engine behavior is part of the acceptance target. | Playwright uses its supported patched Firefox build, not the branded Firefox application. |
webkit |
You need Safari-oriented coverage. | Playwright WebKit is not branded Safari. Its behavior can vary with operating system; macOS is the closest Safari-like environment, particularly for video or codec-sensitive tasks. |
msedge |
Your users, enterprise policies, or deployment standard specifically target Microsoft Edge. | Edge is a branded Chromium channel and may also be accessed through CDP. |
Chrome or Chromium for broad automation
Start with Chrome or Chromium when a particular browser engine is not the reason for the task. This gives you a Chromium-based target for ordinary automation and compatibility work. Choose branded Chrome when the installed browser identity or an existing Chrome session matters; otherwise, Playwright’s bundled Chromium is an option.
Firefox for Firefox-engine compatibility
Select firefox when you need to catch behavior specific to Firefox’s engine. Do not treat this MCP target as a way to automate the separately branded Firefox application: Playwright’s Firefox support depends on patches in its supported build.
#1 Best Overall
WebKit for Safari-oriented coverage
Select webkit when the acceptance question is whether a site behaves in a Safari-like engine. WebKit is derived from WebKit main-branch sources, not packaged as Safari. For the closest Safari experience, run the WebKit target on macOS. Media codecs and other platform-sensitive behavior should be checked in the operating-system environment that matters to your users.
Edge for Edge-specific requirements
Choose msedge when Edge itself is required—for example, because your users run Edge, an enterprise environment standardizes on it, or your deployment is validated against it. Although Edge is Chromium-based, the branded channel can matter for browser identity, policy, and deployment-specific checks.
Set the browser in the MCP configuration
The MCP server accepts the browser as a command-line argument. For example, to start the supported Firefox target, use this server entry in your MCP configuration:
{
"mcpServers": {
"playwright": {
"command": "npx",
"args": ["@playwright/mcp@latest", "--browser=firefox"]
}
}
}Change the value after --browser= to chrome, webkit, or msedge to select another documented target. The browser selection can also be supplied through a config file or the PLAYWRIGHT_MCP_BROWSER environment variable. If more than one configuration mechanism is in use, make sure the effective setting is the one you intend; otherwise you may troubleshoot the wrong browser.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Choose headed or headless mode
Playwright MCP runs headed by default, so the browser window is visible while the agent works. This is useful when you want to watch navigation, inspect state, or intervene in visible interactive work. For an automation workflow that does not need a visible window, add --headless to the server arguments.
Choose whether browser state persists
A persistent profile preserves login state and cookies by default, which can be useful for repeated work in the same authenticated environment. Use --isolated when you need a fresh session instead. Isolation is useful for repeatable checks or when you do not want prior cookies and login state to influence the current task. Decide deliberately: a test that expects a logged-in account will behave differently in a fresh profile.
Connect to an existing Chrome or Edge session when needed
If the work must use an already-running Chromium-family browser rather than starting a separate browser session, connect through a channel or a CDP endpoint. This is the appropriate path when the existing browser’s session is important. Supported channel names include chrome, chrome-beta, chrome-dev, chrome-canary, msedge, msedge-beta, msedge-dev, and msedge-canary.
CDP applies to Chromium-family browsers; it is not the method to use for Firefox or WebKit. Pick the channel that reflects the installed branded browser you need, or use the CDP endpoint for the existing browser connection. When choosing between a fresh MCP-launched session and an existing one, weigh repeatability against the need to retain that browser’s current state.
Rank #3
Make the choice reproducible
For a dependable browser decision, record the target engine or channel together with the environment and session mode. A useful selection note answers these questions:
- Compatibility target: Is the requirement Chromium/Chrome, Firefox, Safari-like WebKit, or Edge?
- Browser identity: Is Playwright’s bundled engine sufficient, or is a branded Chrome or Edge installation required?
- Operating system: Is the test especially sensitive to WebKit platform differences or media codecs?
- Session model: Should the run reuse a persistent profile, start isolated, or connect to an existing Chromium-family browser?
- Execution mode: Do you need a visible headed session, or should it run headless?
Keep those choices aligned with the actual question being tested. A WebKit run on one operating system does not establish identical behavior on another, and a successful run in Playwright’s Firefox target does not by itself validate the separately branded Firefox application.
Troubleshoot common browser-selection problems
The server starts in the wrong browser
Check the MCP server arguments for the exact --browser= value, and check whether a config file or PLAYWRIGHT_MCP_BROWSER setting is also supplying a browser choice. Use one deliberate effective selection, then restart the MCP server so the updated configuration is used.
The browser window is not visible
Headed mode is the default. If the browser is not visible, check whether --headless is present in the server arguments. Remove it when you need to watch or interact with the visible browser; retain it when the workflow is intended to run headlessly.
Recommended Free Tools
A login or cookie state disappeared
Check whether the session was started with --isolated. An isolated session starts fresh rather than relying on a persistent profile. For work that needs retained login state and cookies, use the persistent-profile behavior instead.
Branded Firefox or Safari does not behave as expected
Playwright’s Firefox target is its patched supported build, not branded Firefox. Likewise, the WebKit target is not Safari. For Safari-like checks, use WebKit and run it on macOS when the closest Safari experience is important; treat video and codec-sensitive behavior as platform-dependent.
An existing browser session is not being used
A standard browser choice may launch a separate session. If you need an already-running Chrome or Edge session, use a supported Chromium-family channel or CDP connection. CDP is not applicable to Firefox or WebKit.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Performance, reliability, and cost considerations
There is no single browser choice that is fastest or most reliable for every task established here. The engine, operating system, whether the session is headed, and whether it reuses state all affect what the run represents. For compatibility work, select the engine that matches the target rather than substituting one based on an assumed speed advantage. For reproducible checks, keep the browser, OS, session mode, and profile behavior consistent.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallThe documented browser-selection facts do not establish a Playwright MCP service price, a cross-browser performance benchmark, or a universal reliability ranking. Treat those as environment- or deployment-specific rather than assuming that one engine is inherently cheaper or more dependable.
Or skip the browser setup
If you need a screenshot or PDF rather than an interactive browser session, ScreenshotNeo provides a one-request API. It is not a substitute for choosing an engine when you must test browser-specific behavior, but it can avoid setting up browser automation for a capture task. 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.webpScreenshotNeo accepts and removes cookie or consent banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for AI agents. The Free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Frequently Asked Questions
Can Playwright MCP control Safari itself?
No. Its Safari-oriented target is Playwright WebKit, not the branded Safari application.
Does choosing Edge mean the same thing as choosing Chromium?
Edge is Chromium-based, but select the msedge channel when Edge’s branded browser or deployment identity is the requirement.
Can I change browser targets between MCP runs?
Yes. Set the desired browser with the MCP browser argument, config file, or PLAYWRIGHT_MCP_BROWSER environment variable for the run.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors
