Hey everyone! I’ve been working with Puppeteer for web automation and I’m curious about something. Is there a way to make Puppeteer work with the Brave browser rather than the default Chromium it usually uses?
I know that Brave is built on top of Chromium, which is why I can use it with Selenium WebDriver without issues. But I’m not sure if the same flexibility exists with Puppeteer.
Has anyone here successfully configured Puppeteer to launch Brave instead of Chrome? If so, how did you set it up? I’d really appreciate any guidance or code examples you might have.
Works gr8! Just tried this last week. Point puppeteer to brave’s executable when launching - mine was /usr/bin/brave-browser on ubuntu but it’ll vary by OS. Heads up tho, brave’s shields might block things so disable them for testing.
Absolutely possible and pretty straightforward. I switched to Brave with Puppeteer six months ago for a client project and haven’t looked back. The key is finding the right executable path - check where Brave installed or run which brave-browser on Linux. Through trial and error, I found you’ll want to pass extra launch arguments to disable some of Brave’s default security features that mess with automation scripts. The --disable-web-security and --disable-features=VizDisplayCompositor flags have been lifesavers. Performance-wise, I’ve seen slightly better resource management than standard Chromium, though it depends on what you’re automating.
Been running Brave with Puppeteer for almost a year - works great. Just turn off auto-updates so your Brave version doesn’t break compatibility. One heads up: Brave’s fingerprint randomization will mess with your sessions, so you’ll probably need to disable it depending on what you’re automating.
Yes, you can definitely run Puppeteer with Brave. I’ve been doing it for months and it works great. Just specify the executable path when launching Puppeteer using the executablePath option in puppeteer.launch(). On Windows it’s usually ‘C:\Program Files\BraveSoftware\Brave-Browser\Application\brave.exe’, on Mac it’s ‘/Applications/Brave Browser.app/Contents/MacOS/Brave Browser’. Watch out for Brave’s built-in privacy features and ad blocking - they might mess with your automation. You may need to disable those or tweak your scripts. I’ve actually found Brave performs better than Chrome for some tasks, especially memory-heavy operations.
I hit this exact issue three months ago on a data scraping project. Client wanted Brave for privacy, and while the executablePath solutions here are right, there’s a nasty gotcha I learned the hard way. Brave’s version numbering doesn’t always match Chrome, so certain Puppeteer features break. Had to downgrade from the latest Puppeteer to match Brave’s Chromium base. Also, Brave’s auto-updates will randomly break your automation - the executable path changes or new privacy features turn on by default. I built a quick validation script that checks if Brave launches before running the main tasks. Saved me from random production failures.
Yeah, you can use Brave with Puppeteer, but there’s a way cleaner approach that’ll save you the headache.
I ditched all the executable path wrestling and security feature disabling when I moved my browser automation to Latenode. It handles browser management automatically - no more worrying about which browser or version you’re running.
Used to waste hours debugging path issues and shield conflicts switching between Chrome and Brave for different projects. Now I build the automation flow once in Latenode and it works consistently everywhere.
The visual workflow builder beats writing Puppeteer scripts hands down - you actually see what your automation’s doing. Built-in scheduling and error handling without extra code is a nice bonus too.
If you’re doing regular web automation, definitely worth a look: https://latenode.com