Headless Browsers: What, How and Why
summary
Headless browsers are full browser engines running without a visible window; the talk compares concrete tools and tradeoffs such as Puppeteer/Chrome DevTools Protocol versus older PhantomJS and Selenium and shows a one‑page PDF rendering code example. It demonstrates practical features like network interception, session isolation, and virtual timers, and outlines limits and pitfalls — no audio/video or extensions, cross‑platform rendering differences, header‑order fingerprinting, memory leaks and the pragmatic fix of restarting processes.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:18What headless browsers are
- 5:13Why use headless browsers
- 8:05Headless browser tools
- 15:27PDF generation with Puppeteer
- 21:41Chrome headless architecture
- 26:48Chrome DevTools Protocol
- 30:42Virtual timers use cases
- 34:59Intercepting network requests
- 37:50Rendering issues across platforms
- 40:01Bypassing blocks and limits
- 42:15Unavailable headless features
- 44:45Future of headless browsers
- 47:40Q&A
- 50:43Q&A Unusual use cases
- 51:48Q&A Real browser compatibility
- 53:21Q&A Memory monitoring
- 54:46Q&A Rendering and GPU
- 56:31Q&A Bypassing blocks and headers
related talks
28mRethinking Browser Automation: Unleashing the Power of Puppeteer and Playwright
19mDevTools and Headless Chrome - The Automation Power-Couple
32mDevTools and Headless Chrome - The Automation Power Couple
30mModern Web Testing and Automation with Puppeteer
28mRethinking Browser Automation: Unleashing the Power of Puppeteer and Playwright
01h 02mModern web testing and automation with Puppeteer
13mUsing Headless Browsers to ship reliable and performant apps
31mSelenium Hacks