Screenshotlayer vs Shoof Aflam

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Screenshotlayer vs Shoof Aflam: common questions

Which is more reliable, Screenshotlayer or Shoof Aflam?

On our scheduled checks, Shoof Aflam leads on measured uptime — Screenshotlayer at —% versus Shoof Aflam at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Screenshotlayer and Shoof Aflam need an API key?

Neither needs a paid key — Screenshotlayer is callable with no signup, and Shoof Aflam is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Screenshotlayer and Shoof Aflam from the browser?

Neither sends browser-friendly CORS headers reliably, so call Screenshotlayer and Shoof Aflam from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Screenshotlayer and Shoof Aflam free for commercial use?

Screenshotlayer has unclear commercial terms, and Shoof Aflam has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.