Design

Webpage Screenshot

Capture any page top to bottom in a real headless Chrome, with JavaScript executed and lazy content loaded — desktop or mobile, exported as PNG, WebP, or JPEG.

POST/screenshot2 crDocs

Running it here is free and never spends credits — the page calls the same production endpoint your integration would.

✦ What you get

Everything the endpoint returns

The playground above shows the same fields the API responds with — nothing is held back for the paid tier.

Genuinely full page

We scroll the document to trigger lazy-loaded content, then capture top to bottom — not just the fold.

Real headless Chrome

JavaScript executes and web fonts load before the shot, so you get the page a visitor would see.

Desktop or mobile

A 1440px desktop viewport, or an iPhone-sized retina viewport for the mobile rendering.

PNG, WebP, or JPEG

Lossless when you need fidelity, WebP when you need it small, JPEG when you need it smaller.

Pre-warmed instances

Browsers stay resident, so a capture returns without waiting on a cold boot.

Preview then download

The result appears inline first. Download it in the format you picked when it looks right.

✦ How it works

Three steps, no signup

01

Enter a URL

Any publicly reachable page. Local and private network addresses are blocked for safety.

02

Pick viewport and format

Desktop or mobile, then PNG, WebP, or JPEG depending on what the image is for.

03

Download the capture

Preview it inline, then save. Images are deleted from our side a few minutes later.

✦ Who it's for

Built for

Designers

Pull reference captures of live sites without stitching scrolls together by hand.

QA engineers

Attach a full-page render to a bug report so the layout issue is undeniable.

Marketers

Generate clean visuals of landing pages for decks, changelogs, and case studies.

Agencies

Archive a client's site as it looked before the redesign shipped.

Developers

Automate visual snapshots of a deploy through the same endpoint this page calls.

✦ Questions

Frequently asked

Ready to run this on a schedule?

The same endpoint, called from your code, billed in credits.