Add website screenshots to your app with one API call (no headless Chrome)
说明与用途
CurlShot 通过 API 快速获取网页截图,免去管理 headless Chrome 的麻烦,解决内存、环境和扩展性问题。
问题
Teams need web page screenshots for Open Graph images, PDFs, thumbnails, or monitoring, but running headless Chrome (Puppeteer/Playwright) in production is heavy, error‑prone, and costly.
结果
CurlShot reduces ops overhead, eliminates Chrome‑related bugs, and provides a scalable, parameterized screenshot solution, saving teams time and resources.
工作流
- 1. Sign up for CurlShot and obtain an access key.
- 2. Make a GET request to https://curlshot.com/api/v1/screenshot?url=TARGET_URL&access_key=YOUR_KEY to get a PNG.
- 3. For advanced options, POST JSON to https://curlshot.com/api/v1/screenshot with headers X-Access-Key and content-type, including fields like full_page, block_ads, selector, format, viewport_device, dark_mode.
- 4. Save the returned image or PDF locally or use it in your application.
- 5. (Optional) Integrate with n8n via the community node or with AI agents via the MCP endpoint.
证据
Sooner or later a project needs a picture of a web page: an Open Graph image for social cards, a PDF receipt or report, a thumbnail of a user's site, a visual archive, or a monitoring diff.
The "obvious" answer — run Puppeteer or Playwright yourself — turns into a surprising amount of ops work once it hits production.
Chrome is heavy. Each render spins up a browser; memory spikes, and a few concurrent requests can OOM a small box.
A screenshot API does the Chrome-wrangling for you: send a URL, get back an image or PDF.
curl "https://curlshot.com/api/v1/screenshot?url=https://example.com&access_key=YOUR_KEY" -o shot.png
curl -X POST https://curlshot.com/api/v1/screenshot \
-H "X-Access-Key: YOUR_KEY" \
-H "content-type: application/json" \
-d '{ "url": "https://example.com", "full_page": true, "block_ads": true, "block_cookie_banners": true }' \
-o shot.png
- 记录日期: 2026-11-01T19:28:54.323Z