The Pricing Table Everyone Wants
I pulled pricing from every major screenshot API and normalized it to monthly cost at each volume tier. These are list prices from each provider's public pricing page, checked August 2026.
| Monthly Volume |
SnapRender |
ScreenshotOne |
ApiFlash |
CaptureKit |
Urlbox |
ScrapingBee |
| 200 |
$0 (free) |
$0 (100/mo) |
$0 (free, 100/mo) |
$0 (free, 100 credits) |
N/A (7-day trial) |
N/A (trial credits) |
| 2,000 |
$9 |
$17 |
$35 (10K plan) |
$29 (10K plan) |
$19 |
$49+ |
| 5,000 |
$29 (10K plan) |
$79 (10K plan) |
$35 (10K plan) |
$29 (10K plan) |
$49 |
$49+ |
| 10,000 |
$29 |
$79 |
$35 |
$29 |
$99 (15K plan) |
$49+ |
| 25,000 |
$79 (50K plan) |
$259 (50K plan) |
$180 (100K plan) |
$89 (50K plan) |
$495 base + $3/1K |
Credit-based |
| 50,000 |
$79 |
$259 |
$180 (100K plan) |
$89 |
$495 base + $3/1K |
Credit-based |
| 100,000 |
$199 (200K plan) |
Custom |
$180 |
Custom |
Custom |
Credit-based |
| 200,000 |
$199 |
Custom |
Custom |
Custom |
Custom |
Custom |
SnapRender is the cheapest option at the 2K tier ($9 vs $17+ from every competitor). At 5K and 10K, it ties with CaptureKit at $29 while ScreenshotOne charges $79. At 25K and above, SnapRender is the cheapest again. At 100K, ApiFlash is slightly cheaper ($180 vs $199), but SnapRender's plan includes 200K screenshots. For a more detailed feature-by-feature comparison, see Screenshot API Pricing Compared.
Here's what it takes to capture a screenshot with SnapRender:
curl "https://app.snap-render.com/v1/screenshot?url=https://example.com&format=png" \
-H "X-API-Key: YOUR_API_KEY" \
-o screenshot.png
One request, one screenshot. Ad blocking, device emulation, dark mode, PDF export, full-page capture: add the parameter and it works. No tier restrictions.
Effective Cost Per Screenshot
The sticker price matters less than what each screenshot actually costs you. Here's the per-screenshot math (plans and volumes verified August 2026):
| Provider |
Plan |
Volume |
Monthly Cost |
Cost Per Screenshot |
| SnapRender |
Free |
200 |
$0 |
$0.000 |
| SnapRender |
Starter |
2,000 |
$9 |
$0.0045 |
| SnapRender |
Growth |
10,000 |
$29 |
$0.0029 |
| SnapRender |
Business |
50,000 |
$79 |
$0.0016 |
| SnapRender |
Scale |
200,000 |
$199 |
$0.0010 |
| ScreenshotOne |
Basic |
2,000 |
$17 |
$0.0085 |
| ScreenshotOne |
Growth |
10,000 |
$79 |
$0.0079 |
| ScreenshotOne |
Scale |
50,000 |
$259 |
$0.0052 |
| ApiFlash |
Lite |
1,000 |
$7 |
$0.0070 |
| ApiFlash |
Medium |
10,000 |
$35 |
$0.0035 |
| CaptureKit |
Starter |
1,000 |
$7 |
$0.0070 |
| CaptureKit |
Pro |
10,000 |
$29 |
$0.0029 |
| Urlbox |
Lo-Fi |
2,000 |
$19 |
$0.0095 |
At the 2K tier, SnapRender is 47% cheaper than ScreenshotOne and 53% cheaper than Urlbox. At 10K, SnapRender and CaptureKit both cost $0.0029 per screenshot, while ScreenshotOne charges $0.0079 (nearly 3x more).
Per-Screenshot Cost at Scale
One thing that isn't obvious from the pricing tables: buying a larger plan than you need can actually save money. The per-screenshot cost drops so steeply on some APIs that upgrading a tier makes sense even if you're only using 60-70% of the quota.
Here's the math for SnapRender:
| Plan |
Quota |
Monthly Cost |
Cost/Screenshot (full usage) |
Cost/Screenshot (70% usage) |
Cost/Screenshot (50% usage) |
| Starter |
2,000 |
$9 |
$0.0045 |
$0.0064 |
$0.0090 |
| Growth |
10,000 |
$29 |
$0.0029 |
$0.0041 |
$0.0058 |
| Business |
50,000 |
$79 |
$0.0016 |
$0.0023 |
$0.0032 |
| Scale |
200,000 |
$199 |
$0.0010 |
$0.0014 |
$0.0020 |
Notice: even at 50% usage, the Business plan ($0.0032/screenshot) is cheaper per screenshot than the Starter plan at full capacity ($0.0045). If you're generating 3,500 screenshots a month, the Growth plan at $29 gives you 10,000 screenshots, which is a lower per-screenshot cost even though you're only using 35% of the quota.
The same logic applies to competitors, but the break-even points are less forgiving. ScreenshotOne's jump from $17 (2K) to $79 (10K) is a 4.6x price increase for a 5x volume increase. You need to actually use close to 10,000 screenshots before that upgrade pays off. SnapRender's Growth plan is only a 3.2x price increase for a 5x volume bump, which means you break even sooner.
The takeaway: run the numbers on your actual usage before picking a tier. Sometimes the plan that looks too big is the one that saves you the most per screenshot.
Free Tier Comparison
If you're starting with zero budget, here's what each free tier actually gives you. (For a deeper dive into free tiers specifically, see Free Screenshot API Comparison.)
| Provider |
Free Screenshots/Month |
Credit Card Required |
Features Included |
Rate Limit |
| SnapRender |
200 |
No |
All features |
10 req/min (30-200 on paid) |
| ScreenshotOne |
100 |
No |
Core features (geo/scrolling/video gated) |
Limited |
| ApiFlash |
100 |
No |
Ad + cookie blocking included |
Limited |
| CaptureKit |
100 credits |
No |
Basic |
No strict limits |
| Google PageSpeed |
Unlimited |
No |
Performance screenshots only |
Low |
| Screenshotlayer |
100 |
No |
Basic, older rendering |
Low |
SnapRender's free tier gives you 2x the volume of ScreenshotOne, ApiFlash, and CaptureKit, and includes every feature (device emulation, ad blocking, cookie banner removal, dark mode, full-page capture, PDF output). No surprise upgrades when you need a feature that turns out to be gated.
Start with the free tier. No credit card. 200 screenshots per month.
Why "Cheapest" Isn't Always the Lowest Sticker Price
The real cost of a screenshot API includes factors most pricing pages don't show:
Feature gating forces tier jumps. You pick a plan based on volume, then discover a feature you need requires a higher tier. With SnapRender, every feature is available on every plan including free, so your plan choice is purely about volume.
Cache billing varies. Some APIs count cached responses against your monthly quota. If 40% of your requests hit cache and those count, your effective volume is 40% less than what you paid for. SnapRender's cached responses (under 200ms) don't count against your quota.
Overage handling differs. When you exceed your monthly limit, some APIs charge per extra screenshot, others hard-stop. Surprise overage charges can blow your budget. Check the overage policy before committing.
Rate limits affect architecture. A low rate limit means you need a queue system to smooth burst traffic. SnapRender's paid plans run from 30 requests per minute (Starter) up to 200 (Scale), and the batch endpoint absorbs one-off spikes of up to 50 URLs per request.
Self-hosting is even more expensive. If you're comparing API pricing against running your own Puppeteer setup, the numbers aren't close once you include engineering time and infrastructure. See The Real Cost of Self-Hosting Screenshots for the full breakdown.
What About Overages?
What happens when you exceed your monthly limit is one of the most overlooked parts of API pricing (policies checked August 2026):
| Provider |
Overage Behavior |
Overage Cost |
Rollover? |
| SnapRender |
Hard stop (API returns 429), optional extra-credit packs |
N/A |
Extra credits valid 1 year |
| ScreenshotOne |
Per-screenshot overage billing on paid plans |
$0.009 (Basic) to $0.004 (Scale) per extra |
No |
| ApiFlash |
Hard stop |
N/A |
No |
| CaptureKit |
Hard stop |
N/A |
No |
| Urlbox |
Overage charges on Business ($3 per 1,000 renders) |
$3/1,000 |
No |
| ScrapingBee |
Credit-based |
Varies |
No |
There are two main models here, and each has trade-offs.
Hard stop means your API calls fail with a rate limit error once you hit your quota. Your app needs to handle this gracefully, but you'll never get a surprise bill. This is the safest model for budget predictability. SnapRender and ApiFlash both do this, and SnapRender sells optional extra-credit packs if you'd rather top up than upgrade.
Overage charges mean the API keeps working past your quota, but you pay per extra screenshot at a markup. ScreenshotOne and Urlbox use this model. The upside is your users don't experience failures. The downside is that a traffic spike or a retry-loop bug can rack up real money before anyone notices.
For most teams, the hard stop model is safer. You build in a usage check, show a "quota reached" message or queue requests for the next cycle, and your costs stay exactly where you planned them.
Real-World Cost Scenario
A typical SaaS app needs link preview thumbnails for user-submitted URLs. The requirements:
- 5,000 unique URLs per month
- Need ad blocking (clean screenshots)
- Need device emulation (mobile and desktop versions)
- Need WebP output (smaller files for CDN)
- Cache TTL of 7 days
With SnapRender Growth ($29/month): all of the above included, 5,000 well within the 10,000 quota. Total: $29/month.
With ScreenshotOne: 5,000 screenshots needs the Growth plan. Total: $79/month.
With CaptureKit Pro ($29/month): within quota, but device emulation is limited presets. Total: $29/month.
With Urlbox Hi-Fi ($49/month): 5,000 renders exactly at quota. Total: $49/month.
Over a year, that's $348 (SnapRender) vs $348 (CaptureKit) vs $588 (Urlbox) vs $948 (ScreenshotOne) for the same output. SnapRender and CaptureKit tie on price at this tier, but SnapRender includes dark mode, named device presets, and an MCP server for AI agents that CaptureKit doesn't offer.
Scenario 2: Competitor Price Monitoring
An e-commerce team captures 200 competitor product pages daily, mobile and desktop (12,000 screenshots/month), full-page, with 30-day retention.
With SnapRender Business ($79/month): 12,000 well within the 50,000 quota, full-page and device emulation included, room to scale without a plan change. Total: $79/month. Note: SnapRender does not offer geolocation rendering. If region-specific captures are required, pair with ScreenshotOne for those specific URLs.
With ScreenshotOne: 12,000 needs the Growth plan ($79/10K) plus overage, or Scale; geolocation needs Growth or higher anyway. Total: $79-259/month depending on requirements.
With CaptureKit: 12,000 requires the Ultimate plan ($89/50K). Total: $89/month.
Over 12 months: $948 (SnapRender) vs $1,068 (CaptureKit) vs $948-3,108 (ScreenshotOne). And on SnapRender you still have 38,000 unused screenshots in quota each month for other projects.
Cost Optimization Tips
Regardless of which API you choose, these techniques reduce your bill:
-
Use caching aggressively. If URLs don't change daily, set a long cache_ttl (86400 for 24 hours, 604800 for 7 days). On SnapRender, cached responses don't count against quota and return in under 200ms.
-
Choose WebP over PNG. WebP images are 25-35% smaller, meaning faster delivery and less bandwidth cost on your CDN.
-
Deduplicate client-side. If multiple users request the same URL within minutes, cache the result locally and avoid duplicate API calls.
-
Capture once, resize locally. Instead of capturing at multiple sizes, capture at your largest needed size and resize with Sharp or ImageMagick.
-
Right-size your captures. Use 1280x720 for thumbnails, not 1920x1080. Smaller viewports render faster and produce smaller files.
-
Batch during off-peak. Pre-generate screenshots for known URLs during low-traffic hours rather than capturing on-demand during peaks.
What $9/Month Gets You
At SnapRender's Starter tier ($9/month for 2,000 screenshots), you get every output format (PNG, JPEG, WebP, PDF), named device presets, ad blocking and cookie banner removal, dark mode, full-page capture to 32,768px, custom viewports, hide and click selectors, configurable cache TTL, custom headers and cookies, 30 requests per minute, Node.js, Python, and Go SDKs, the MCP server for AI agents, content extraction in six formats, batch screenshots, and webhooks.
At $9/month, no other screenshot API gives you this combination of features and volume. The next cheapest comparable option is ScreenshotOne at $17/month for 2,000 screenshots with its headline features gated.
The Bottom Line
For developers who care about cost, SnapRender is the strongest choice in 2026. It's the cheapest at the 2K entry tier ($9 vs $17+ from competitors), ties CaptureKit at 10K, and is the cheapest again at 25K and above. It has the most generous free tier (200/month, 2x what competitors offer, every feature included) and doesn't gate anything behind higher plans. Start with the free tier, test with your actual URLs, and upgrade when your volume demands it.
For a full comparison of API features beyond pricing, see Best Screenshot APIs in 2026. For per-screenshot math across nine providers, see Screenshot API Pricing Compared. To see how these API costs compare against running your own infrastructure, check The Complete Screenshot API Guide. Or skip the reading and try the free website screenshot tool right now.