Screenshot API, in your language.

A screenshot API turns any public URL into a PNG, JPEG or WebP image over one HTTPS request — the browsers run on our side, so nothing headless ships in your deployment. Each guide below carries runnable code for one language: capturing pages, generating Open Graph images from templates, signing URLs you can embed in public HTML, and handling errors.

Pick your language

• Pythonrequests, not Selenium or Playwright
• Node.jsOne fetch call, no Puppeteer
• PHPThe cURL extension you already have
• RubyStdlib net/http, nothing in your Gemfile
• GoStandard library only, no chromedp or CGO
• JavaBuilt-in HttpClient, no WebDriver matrix
• cURLShell scripts and CI runners with no browser

Workflow integrations

• n8nCommunity node with three operations — screenshots, OG images and locally-computed signed URLs.

What every guide covers

• Screenshots of any public URL — viewport control, PNG/JPEG/WebP, full-page capture up to 20,000px of scroll height.
• OG images from templates — typed parameters into one of five built-in designs, a finished 1200×630 card out.
• Signed URLs — HMAC-signed image links safe to print into public HTML, with the encoding details that differ by language spelled out.
• Error handling — RFC 9457 problem+json with stable type fields; failed renders are never billed.

The complete contract — auth, every parameter, the full error table, rate limits and billing semantics — lives in the API reference. Sign-up is GitHub OAuth and includes 100 free render credits, no card; plans start at $15/month on pricing.