How I Picked a Screenshot API (Developer Notes)

I spent weeks evaluating screenshot APIs before deciding to build my own. These are the notes I kept during that process. It's not a feature matrix, just observations from actually using each service.

If you want the full comparison with pricing tables, feature breakdowns, and rankings, I wrote a detailed screenshot API comparison that covers eight providers side by side. This post is the informal version.

What I was looking for

My project needed screenshots of other people's websites, not my own pages, not controlled environments. That ruled out anything that struggled with cookie banners, lazy loading, or JavaScript-heavy SPAs. I also needed PDF export, which eliminated some options immediately.

What I tried

ScreenshotOne impressed me with documentation quality. Seven SDKs, clear examples, a responsive founder. The rendering was solid. The price was the sticking point. $79/month for 10,000 screenshots wasn't what I wanted to spend at the prototyping stage, and the free tier (100/month) ran out during initial testing.

ApiFlash was fast. Sub-second responses on simple pages. But no webhooks, no PDF, and SPA rendering was inconsistent. Great for quick URL-to-PNG jobs, less so for anything complex.

I ended up building screenshotrun because I wanted webhook support, PDF export, and reliable SPA rendering at a price point that made sense for indie projects. The free tier comparison page shows where each service lands on volume and features.

What actually matters when choosing

After going through the process, three things mattered more than the feature list: rendering quality on real-world pages (not demo URLs), how the free tier holds up during integration testing, and whether async processing (webhooks) is supported. Everything else is secondary.

For the full breakdown with tables and pricing math, see the best screenshot API comparison. For head-to-head details, see screenshotrun vs ScreenshotOne and screenshotrun vs ApiFlash.