Who owns Puppeteer?
Puppeteer sits under Google's ownership, but its code is built in the open by a worldwide contributor base.
Understanding that split — corporate stewardship plus community authorship — helps you judge how the project is governed and where to follow its progress.
Google ownership, community development
Google is the owner of Puppeteer. The library was created and first released in 2017 by the Chrome DevTools team, and its ongoing work is hosted on GitHub. It is released as an open-source project, so people outside Google can read, use, and improve it.
That openness does not mean Google has stepped away. The project remains under Google's umbrella, which is the practical distinction to keep in mind: stewardship and ownership rest with Google, while much of the day-to-day coding comes from independent contributors around the world.
What the contributor agreement means in practice
Most individual contributors are not affiliated with Google. Before their first contribution, they sign a one-time Contributor License Agreement. That agreement is the formal bridge between an outside developer and a Google-stewarded open-source project — it clarifies the terms under which their work can be included.
For teams evaluating Puppeteer, the checklist is simple: confirm the project is still actively maintained on GitHub, note who the current maintainers are, and check the contribution terms if your own developers plan to submit changes. Those three checks tell you more about the project's health than the ownership label alone.
Where to go next
If you are new to the tool, start with what Puppeteer is and why teams use it, then compare it with alternatives such as Playwright if you are choosing a browser-automation library. For hands-on work, practical topics like waiting for pages to load, finding elements by CSS selector or XPath, saving cookies, and taking screenshots are the skills that turn ownership background into working code.
Frequently asked questions
Who owns Puppeteer?
Google owns Puppeteer. It began with the Chrome DevTools team in 2017, and development now happens on GitHub. Anyone contributing is asked to sign a one-time Contributor License Agreement first, even though many individual contributors are not Google employees.
If Google owns it, who actually writes the code?
Ownership and day-to-day authorship are different things here: Google provides the project home, while outside developers supply much of the code. That mix is why the project can be both Google-owned and genuinely community-built.
Where should I verify current Puppeteer development?
Check the project repository on GitHub for current maintainers, recent releases, and contribution requirements before adopting it for a long-lived scraping or testing workflow.