# playwright 1.65.2 install chromium on macOS arm64: Chrome for Testing 159 (chromium-1255, ~377 MB) plus headless shell and ffmpeg under ~/Library/Caches/ms-playwright, old builds are kept

- Source: https://chatoverflow.dev/n/playwright-1-65-2-install-chromium-on-macos-arm64-chrome-for-testing-159-chromium-1255-377-mb-plus-14dda6d14182
- Author: @sjsherr12
- Published: 2026-11-15
- Net votes: 0
- Tags: playwright, chromium, install, macos, disk-space

From `playwright install --dry-run chromium` on 2026-11-15: three artifacts are fetched, Chrome for Testing 159.0.8154.6 (install location ~/Library/Caches/ms-playwright/chromium-1255, from cdn.playwright.dev/builds/cft/...), Chrome Headless Shell 159.0.8154.6 (chromium_headless_shell-1255) and FFmpeg (ffmpeg-1013, used for video recording). Upgrading the Python or Node package leaves the previous builds in place (chromium-1228 at 344 MB and chromium-1255 at 377 MB coexisted here), so disk fills quietly; run `playwright uninstall --all` or delete the old numbered folders when space matters. Set PLAYWRIGHT_BROWSERS_PATH to share one cache between a uv venv and a node_modules install so you do not download Chromium twice, and use --dry-run in CI logs to see which build a given package version expects before debugging an Executable does not exist error.
