Screenshot API for product previews, listings, and launch assets
Turn public product pages, launch notes, and listing URLs into repeatable preview images. Scrnpix renders the URL, captures the viewport you choose, and returns PNG or JPEG bytes your app can store or publish.
Good fit
- Creating product-card, marketplace-listing, changelog, and launch-page previews from public URLs.
- Refreshing preview images after product copy, pricing, or layout changes go live.
- Adding a hosted capture step to CMS, catalog, or marketing automation without running headless browsers.
Not a fit
- Private product dashboards, admin screens, or launch rooms that require a logged-in browser session.
- A template engine for composing custom OG images, badges, overlays, or social graphics from scratch.
- A visual-review platform with approvals, diff history, and collaboration built around each preview.
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%2Fproducts%2Flaunch-kit&width=1200&height=630&format=jpeg&full_page=false" \ -H "X-KEY: your-api-key" \ -o product-preview.jpeg
Supported parameters
url
https://example.com/products/launch-kitThe public product, launch, or listing URL to capture.
width
1200Viewport width in pixels for the generated preview.
height
630Viewport height in pixels for a card-style preview.
format
jpegUse `jpeg` for smaller preview files or `png` for lossless output.
full_page
falseKeep this `false` for fixed preview cards. Set it to `true` only when you need the full scrollable page.
Sample output
- Returns image bytes directly as `image/png` or `image/jpeg` so your app can save the preview where it already stores media.
- A 1200x630 viewport works well for many product preview cards; adjust `width` and `height` for your destination.
- Each screenshot costs 1 credit. The `X-Credit-Cost` response header confirms the exact cost for every capture.
Known boundaries
- Scrnpix captures public URLs only. Private product areas still need your own authenticated browser flow.
- Cookie banners, chat widgets, dynamic inventory messages, and public overlays appear exactly as a regular visitor would see them.
- Scrnpix does not compose branded templates. If you need a custom OG layout, render that layout at a public URL and capture it.
- You trigger one API request per URL; catalog crawling, approval queues, and media-library management stay in your application.
Pricing examples
Scrnpix charges in credits. Screenshots cost 1 credit. Animations cost 1 credit per second of GIF duration (minimum 1).
Free
Validate the preview size, output format, and public-URL fit before wiring it into your product flow.
Basic
Good for lightweight preview refreshes across docs, small catalogs, and launch pages.
Growth
Designed for recurring product-preview generation across more listings, releases, and marketing workflows.
Related workflows
Use these tools and recipes to test the capture shape before you automate it inside your own product flow.
OG Image Preview Tool
Test a public product page at 1200x630 or Twitter card dimensions before automating the API call.
Bulk Screenshot Tool
Try a small set of public product URLs and download the captured previews as a ZIP.
Basic Screenshot Recipe
See the smallest screenshot request shape and adapt it for product preview capture.
Full-Page Capture Recipe
Use this when a long product story or landing page needs more than the initial preview viewport.
Frequently asked questions
Can I create product listing thumbnails with Scrnpix?
Yes, when each listing or product page is available at a public URL. Choose a fixed viewport, call the screenshot endpoint, and store the returned image in your own media workflow.
Can I capture staging or launch-preview URLs?
Only if the URL is publicly reachable without a login, VPN, or private network access. Scrnpix is designed for public-URL capture.
Is this the same as an OG image generator?
No. Scrnpix captures rendered pages. If you need custom text, badges, or brand artwork, build that as a public page or template first, then capture the rendered result.
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.