SnapshotFlow - Screenshot & OG image API - no browser setup
byβ’
SnapshotFlow is a screenshot and OG image REST API for developers. Send a URL, get back a PNG or WebP - no Puppeteer setup, no headless browser infrastructure to manage. Handles JS-rendered pages, lazy-loaded content, cookie banners, geo-targeted capture, and full-page mode out of the box. Typed Node.js SDK, java SDK and MCP included. Works with Next.js, Vercel, Zapier, and any webhook-based stack.
Replies
Hi Product Hunt! π
If you've ever spent hours retaking screenshots after a UI change - updating docs, help centers, landing pages, or marketing materials - you know how quickly that work adds up.
We built SnapshotFlow to handle it automatically. It captures product screenshots via a REST API and keeps visual content in sync with the latest version of your product, without the manual update cycle.
β¨ What you can do with it:
Capture full-page or viewport screenshots of any URL - no browser setup required.
Generate dynamic OG images for Next.js, Vercel, and Jamstack apps.
Automate visual changelogs and keep documentation current after every release.
Connect to Zapier, Make, or any webhook-based stack without writing custom infrastructure.
We're launching today to get real feedback from the people most likely to use this. If you've hit this problem before, we'd love to hear how you're currently solving it - and what we should build next.
Thanks for checking out SnapshotFlow. We'll be around all day π
The fact that it handles cookie banners and geo-targeted capture out of the box is a really thoughtful touch, sounds like the team has been through the headless browser pain themselves.
how does geo-targeted capture actually work on your end β are you routing through residential proxies or using something like Bright Data, and is there a per-request cost bump for it?
@anl135651133311Β Yes β geo captures are routed at the IP level through in-country exit nodes, with genuine residential IPs on the premium tier. It's real network-level routing, not Accept-Language spoofing, so IP-based pricing, geo-blocks and redirects behave as they would for a local visitor. We work with multiple upstream providers rather than a single vendor, so we don't share specifics there.
And yes, there's a transparent cost bump. Cached repeats are free. As demand grows, we'll also be rolling out our own in-country exit infrastructure for the most-requested locations β which will bring the geo multiplier down for those regions over time.
the typed Node SDK is a nice touch, shows you actually thought about how this gets used in a real Next.js codebase instead of just shipping a generic REST endpoint and calling it a day.
Plugged it into a Next.js project over the weekend and the typed SDK made setup painless, the full-page captures even rendered my lazy-loaded sections without me babysitting viewport heights. The geo-targeted capture was a nice surprise since I didn't expect that at this price point.
Took it for a quick spin with a Next.js site and the full-page mode handled my lazy-loaded images without me tweaking anything, which was a nice surprise. The Typed SDK made it drop in cleanly with basically one import.
How does the geo-targeted capture actually work under the hood, and is that priced differently from regular captures?
Curious how pricing scales with traffic, is it pure request-based or do those geo capture options bump it up? Also wondering how the rendered output looks on pages heavy with custom fonts or canvas animations.
Weβve launched MCP support for SnapshotFlow.
You can now connect AI agents to SnapshotFlow and automate website monitoring workflows directly through MCP.
Learn more and get started: https://snapshotflow.com/mcp