Scrnpix
Phase 1 Money Page

Full-page screenshot API for long pages, audits, and visual verification

Use Scrnpix when you need a single full-page capture from a public URL and you do not want to stitch images or run browser infrastructure yourself.

Get API KeyTry in Playground

Good fit

  • Monitoring public pages over time with a consistent capture surface.
  • Capturing docs, release pages, and landing pages that extend far below the first viewport.
  • Using Scrnpix as the capture layer in CI, preview, and verification workflows.

Not a fit

  • A full visual-review platform with diffs, approvals, and collaboration built in.
  • Authenticated dashboards or portals behind login.
  • Broad cross-browser test coverage where you need full local browser control rather than a hosted capture layer.

Code example

The integration surface stays small on purpose: one endpoint, one key header, and a few predictable parameters.

curl "https://api.scrnpix.com/screenshot?url=https%3A%2F%2Fexample.com&width=1280&height=720&full_page=true&format=png" \
  -H "X-KEY: your-api-key" \
  -o full-page-screenshot.png

Supported parameters

url

https://example.com

The public URL to capture from top to bottom.

full_page

true

Tells Scrnpix to capture the full scrollable document height.

width

1280

Viewport width used before the full-page capture is taken.

height

720

Initial viewport height before the full-page render expands.

format

png

Use PNG for archival quality, or JPEG where file size matters more.

Sample output

  • Returns one full-page image instead of a stitched client-side artifact.
  • Works with the same screenshot endpoint and authentication model as the standard screenshot API.
  • Each screenshot costs 1 credit. The `X-Credit-Cost` response header confirms the exact cost.

Known boundaries

  • Very long pages can take longer to render and produce larger files.
  • Sticky headers, public consent banners, and delayed client-side widgets still appear if they render for normal visitors.
  • Scrnpix gives you the capture. Diffing, review, and approval still belong in the rest of your workflow.

Pricing examples

Scrnpix charges in credits. Screenshots cost 1 credit. Animations cost 1 credit per second of GIF duration (minimum 1).

Free

Enough for test captures and validating long-page rendering on public URLs.

Basic

Good for recurring documentation captures and lightweight monitoring checks.

Growth

Designed for teams that need recurring capture jobs in product, QA, or ops workflows.

No automatic overage billing is exposed in the current product. When you outgrow a monthly credit bucket, move up to the next plan instead of relying on surprise overage charges.

Frequently asked questions

Is this meant to replace a visual regression platform?

No. Scrnpix is the capture layer. You can feed the returned images into your own diffing or approval workflow, but Scrnpix does not try to be the full review platform.

When should I use full_page=true?

Use it when the important content extends beyond the first viewport and you need a single long capture rather than just the visible fold.

Can I use this in CI or deploy-preview workflows?

Yes. That is one of the clearest fits: capture the public page in a stable hosted environment and let your CI pipeline handle the rest of the workflow.

Get an API key and test the flow end to end

Start with the free tier, verify the capture shape you need, then move up when the workflow becomes recurring.

Get API KeyReview Pricing