Google’s Chrome Browser Automation team maintains Puppeteer. Puppeteer is an open-source JavaScript library in the public puppeteer/puppeteer repository, so “Google maintains Puppeteer” is more accurate than saying Google owns every line of code. Contributors keep copyright in their own contributions while granting the project permission to use and redistribute them under the project’s Contributor License Agreement (CLA).
That distinction answers the common follow-up questions too: Puppeteer is not a physical Chrome product, the npm package is the distribution of a Google-led open-source project, and the browser-automation code is developed publicly rather than held as a closed Google-only codebase.
Who maintains Puppeteer today?
The current official Puppeteer FAQ identifies the Chrome Browser Automation team as the library’s maintainer. That is the clearest current description of responsibility for the project’s direction, releases, issue triage and engineering work.
Older official FAQ copies use the name Chrome DevTools team. The wording changed, but both names point to Google’s Chrome and DevTools organization rather than to an unrelated company or an independent commercial vendor. When you see the older phrase in documentation, it is describing the same long-running Google stewardship in earlier terminology.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
“The Chrome Browser Automation team maintains the library, but we’d love your help and expertise on the project!”
The invitation to contribute is significant: maintenance is Google-led, but participation is open to the wider software community.
Does Google own Puppeteer?
Google is the project’s maintainer and primary steward, but that does not mean Google owns the copyright to every change ever made. Puppeteer is developed as open source in the public puppeteer/puppeteer repository. People outside Google can submit code, documentation and other changes through the project’s contribution process.
In practical terms, “Google owns Puppeteer” can mean several different things:
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems| What someone might mean | Accurate answer |
|---|---|
| Who leads development and maintenance? | Google’s Chrome Browser Automation team. |
| Is the source code public? | Yes. The canonical public repository is puppeteer/puppeteer on GitHub. |
| Does Google hold every contributor’s copyright? | No. The contribution terms say contributors retain copyright in their own contributions. |
| Can the project use and redistribute contributions? | Yes. The CLA grants the project permission to use and redistribute a contribution. |
| Is Puppeteer itself a Chrome browser? | No. It is a JavaScript automation library that controls supported browsers. |
Therefore, the short answer is “Google maintains Puppeteer,” while the legally and technically careful answer is “Puppeteer is a Google-led open-source project with contributions handled through a CLA.”
Rank #2
What exactly is Puppeteer?
Puppeteer is a JavaScript library that provides a high-level API for controlling Chrome or Firefox. The project’s README describes support for the Chrome DevTools Protocol and WebDriver BiDi. Those protocols let your program perform browser actions such as opening pages, interacting with elements and collecting output.
Puppeteer is distributed through npm. During installation it can download compatible browsers, depending on the installation configuration you choose. That behavior does not turn Puppeteer into Chrome or Firefox; the library is the automation layer, while the browser is the program being automated.
Library, browser and repository are different things
- Puppeteer: the JavaScript API and supporting project code.
- Chrome or Firefox: the browser process Puppeteer controls.
- DevTools Protocol or WebDriver BiDi: communication protocols used to automate the browser.
puppeteer/puppeteer: the public source repository where the project is developed.- npm: the package distribution channel developers use to install the library.
Keeping these layers separate prevents a common error: assuming that because Google maintains Puppeteer, Puppeteer is a proprietary component of the Chrome browser. It is better understood as an open-source automation project maintained by a Google engineering team.
Who owns code submitted by contributors?
The project’s contributing guide requires a Contributor License Agreement. Under that arrangement, a contributor retains copyright in the contribution while giving the project permission to use and redistribute it.
This is different from silently transferring all rights to Google. A contributor’s copyright remains with that contributor, but the project receives the permissions it needs to combine the change with Puppeteer, publish releases and redistribute the resulting software.
What the CLA means for readers
- Google-led stewardship: the Chrome Browser Automation team decides and maintains the project as the primary engineering group.
- Community ownership of contributions: contributors do not automatically surrender copyright in their own work.
- Project-wide reuse: the CLA gives Puppeteer permission to use and redistribute accepted contributions.
- Public development: source, discussions and contributions occur in the public repository rather than in a closed internal codebase.
The CLA explains contribution rights; it should not be read as a complete summary of every legal term that may apply to a particular release. For a specific compliance decision, review the current project documents and the version you plan to deploy.
Who maintains the Puppeteer npm package?
The npm package is the installable distribution of the Puppeteer project maintained by Google’s Chrome Browser Automation team. In other words, npm is where developers obtain the package; it is not a separate owner or an independent competing implementation.
When you install Puppeteer, you are consuming the project’s published JavaScript library and, where configured, its compatible browser downloads. The repository, project documentation and contribution process remain the useful places to understand stewardship and source changes.
Why this matters when you select a dependency
- Track the project, not only the package name: important maintenance information lives in the public repository and official documentation.
- Separate browser updates from library updates: a Puppeteer release and the browser binary it controls are related, but they are not the same artifact.
- Check your deployment policy: installations that download browsers may need network access, cached artifacts or an approved internal mirror.
- Preserve reproducibility: record the Puppeteer version and browser setup used by your build so a future change can be investigated.
These are operational consequences of using a library that can install compatible browsers; they do not change who maintains the project.
Is Puppeteer part of Chrome or Chromium?
No. Puppeteer is a separate open-source JavaScript library. It can automate Chrome and Firefox through the Chrome DevTools Protocol or WebDriver BiDi, but it is not the browser engine, the Chrome desktop application or a Chromium distribution.
Google’s role is therefore easiest to describe in organizational terms: a Google team maintains the automation library, while the library communicates with browser software through supported automation protocols. A project can be closely associated with Chrome engineering without being a component that ships as the Chrome browser itself.
Recommended Free Tools
What does Google-led open source mean in practice?
Google provides the core stewardship
The Chrome Browser Automation team supplies the primary maintainership named by the official FAQ. That gives Puppeteer a clear home inside Google’s browser-automation organization and explains why Chrome-related protocols and browser downloads are central to the project.
The community can still shape the code
The official wording explicitly asks for outside help and expertise. Because the source is public and contributions are governed by a CLA, developers who are not Google employees can propose improvements and documentation changes through the project’s contribution process.
Stewardship is not the same as exclusive authorship
Maintainers review and integrate changes, but integrated code can originate with many contributors. The CLA’s copyright terms are designed to let the project distribute that combined work without pretending that every contributor’s copyright disappeared.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common ownership misconceptions
“Google maintains it, so it must be closed source.”
Maintenance and source visibility are separate questions. Puppeteer’s source is publicly developed in puppeteer/puppeteer, and the project accepts community contributions under its documented process.
Free tools Windows power users keep installed
One-click scans. No signup required.
Best Value
- Used Book in Good Condition
“The npm package belongs to npm.”
npm is the package registry and installation route. It does not replace the Puppeteer project’s maintainers or determine who stewards the source.
“Puppeteer is the same thing as Chromium.”
Puppeteer controls browsers; it is not itself a browser. Its README identifies Chrome and Firefox as targets and names the protocols used to communicate with them.
“Every line in the repository is Google copyright.”
The contribution guide says contributors retain copyright in their contributions. The project receives permission to use and redistribute those contributions through the CLA.
When should you use a screenshot service instead of owning browser infrastructure?
If your objective is to automate a complete browser workflow, Puppeteer gives you a JavaScript API and direct control over the browser process. If the objective is simply to obtain reliable website screenshots or PDFs, operating browsers, consent dialogs and failure handling yourself may be unnecessary infrastructure.
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 reinstallScreenshotNeo is the first screenshot API to try because it removes cookie-consent banners, newsletter popups and chat widgets before capture, and it bills only clean shots rather than failed loads.
What ScreenshotNeo handles
- A single GET request returns a PNG, JPEG, WebP or PDF.
- Cookie and consent banners are accepted like a visitor, and more than 60 known consent platforms, newsletter popups and chat widgets can be removed; each cleanup step can be disabled.
- Bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits cost nothing. Response headers identify the page verdict and whether the request was billed.
- An MCP server provides
take_screenshot,get_page_infoandcapture_pdftools for Claude, Cursor and other MCP clients.
A one-call example
See the ScreenshotNeo API documentation for all options. This cURL request saves a WebP screenshot:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpThe service also supports full-page captures with lazy images loaded, CSS-selector element captures, dark mode, device presets, arbitrary viewports, retina scale, PDF paper settings and page ranges, custom CSS and JavaScript, clicks before capture, hidden selectors, waits for selectors or network idle, blocked ads and trackers, custom headers, cookies, user agents, authorization, timezone and geolocation, transparent backgrounds, resizing, chosen cache TTLs, signed image links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, a usage API and an OpenAPI specification. Parameter names used by other screenshot APIs also work, which can simplify migration.
Pricing and sign-up
The Free plan includes 1,000 screenshots per month with no card. Paid plans are Starter ($5 for 3,000), Growth ($15 for 15,000), Pro ($39 for 60,000), Scale ($99 for 250,000) and Business ($249 for 1,000,000); yearly billing gives two months free, and every feature is available on every plan.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Create a free ScreenshotNeo account to use the 1,000 monthly screenshots without adding a card.
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.
