Skip to content

Add curated topic definition for headless-browser #5370

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
yinnho wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add curated topic definition for headless-browser #5370

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions topics/headless-browser/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
---
display_name: Headless Browser
topic: headless-browser
aliases: headless-browsers, headless
related: browser-automation, web-scraping, puppeteer, playwright, chromium
short_description: A headless browser runs a full web engine without a visible window for automation, scraping, and server-side rendering.
---
Headless browsers run a complete browser engine — HTML parsing, CSS layout, JavaScript execution, and rendering — without a graphical interface. They power server-side web scraping, automated testing, screenshot generation, and agent tools that read and act on the web.

Headless operation trades a visible window for the ability to run many browser instances cheaply in containers and CI pipelines, often driving them over protocols such as CDP, WebDriver, or MCP.
Loading