Viewport
2 crOne screen, exactly as a visitor first sees it. Pick any width and height.
How it works
One call, one render, one link.
Snapshot exists because an agent can read HTML but cannot see a page. Layout, whether the banner covers the button, whether the hero image loaded at all — none of it survives a fetch. A render does.
- 01
You name a page and a shape
A URL — scheme optional — plus the mode you want back and the viewport to render at. Anything you leave out gets a sensible default: 1440 × 900, cookie banners hidden, no extra settle time.
- 02
A real browser loads it
Not a fetch. A headless Chrome navigates, runs the JavaScript, waits for the network to go quiet, and lays the page out at exactly the width you asked for. Ads are blocked and consent overlays are removed before the shutter.
- 03
The capture is re-hosted
The bytes are pulled straight out of the render and stored under our own private prefix. Nothing you get back points at a third party, and the link is signed fresh each time you ask for it.
- 04
Credits settle — or come back
The reserve was taken before the render. If bytes exist, it settles. If the page refused to load, timed out, or came back empty, the exact pools are refunded and the ledger stays untouched.
What you can ask for
Four modes, one endpoint. The mode decides the artifact.
Full page
3 crThe entire scroll height stitched into one tall image, header to footer.
The browser's own print render — real pages, selectable text, ready to attach.
Page text
2 crThe rendered DOM as clean text, after JavaScript has run. No pixels, just words.
The knobs that matter
- width · height
- 320–3840 px, honoured exactly. A responsive site is a genuinely different page at 390 than at 1440, so this is the input that decides what you are looking at.
- deviceScale
- 1 or 2. Two doubles the pixels for a retina-sharp image — worth it when a human will read the capture, wasteful when a model will.
- waitMs
- 0–8s of extra settle time after load. Reach for it when a page animates in, lazy-loads below the fold, or hydrates late.
- darkMode
- Best effort. Nothing inside a page can change the OS colour-scheme preference, so we set the class, attribute and storage keys modern sites read, then let the site's own theme code respond. Sites that key only off the media query stay light.
- blockCookieBanners
- On by default. Removes the consent overlays the major platforms ship and undoes the scroll lock they set, so the capture shows the page rather than the dialog.
What a capture costs you
Credits are reserved before the render and settled only once bytes exist.
- Whole credits
1 credit = 1¢, drawn from the one Ounie wallet every app shares.
- Reads are free
Listing captures, re-opening a result and downloading never bill again.
- Refused, not overdrawn
An empty wallet gets a 402 with the exact shortfall — no capture runs.