shipapis
StarSubmit an APISubmit API

Screenshotlayer vs Simkl

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

APIScreenshotlayerNEW—SimklNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedSimkl terms — user-contributed data
Free tierFree — limits not publishedFree read routes; client_id for search
Rate limitUnpublished1 req/s documented
In directory since2026-07-052026-07-05
operationalpartialdownno data

Screenshotlayer vs Simkl: common questions

Which is more reliable, Screenshotlayer or Simkl?

On our scheduled checks, Simkl leads on measured uptime — Screenshotlayer at —% versus Simkl 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 Simkl need an API key?

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

Can I call Screenshotlayer and Simkl from the browser?

Only Simkl is browser-friendly — it returns CORS headers over HTTPS. Screenshotlayer needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Screenshotlayer and Simkl free for commercial use?

Screenshotlayer has unclear commercial terms, and Simkl 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.