Sub-second rendering. Every time.
Edge-optimized infrastructure with pre-warmed browsers. Most screenshots render in under 800ms. No cold starts, no spin-up delays.
Real capture
Captured in under a second
This screenshot of stripe.com was captured by our API — including full page render, ad blocking, and WebP encoding.
How it works
Request to screenshot in three steps
Request comes in
API receives the URL and rendering options. Routed to the nearest edge node automatically.
Browser renders
Pre-warmed Chromium instance renders the page. No cold start penalty — browsers are always running.
Response in milliseconds
Screenshot is captured, optimized, and returned. Median response time: 650ms.
Numbers
Performance you can measure
API response
render_time_ms in every response
Every screenshot response includes render_time_ms so you can monitor performance programmatically.
Track render times in your dashboards, set alerts on P95 latency, or use it to optimize which pages you cache.
{
"id": "sc_abc123",
"url": "https://stripe.com",
"status": "completed",
"render_time_ms": 420,
"metadata": {
"width": 1280,
"height": 800,
"format": "webp",
"size_bytes": 84200,
"cached": false
}
}Architecture
Why it's fast
Pre-warmed browsers
Browser instances are always running. Zero spin-up time, zero cold starts. Your request hits a warm browser immediately.
Edge routing
Requests are routed to the nearest node. Lower latency, faster DNS resolution, less time on the wire.
Smart caching
Identical requests are served from cache in under 100ms. Cache keys include all rendering parameters.
Optimized pipeline
Custom Chromium flags, connection pooling, and parallel processing for maximum throughput.
Speed you can measure
Every response includes render_time_ms. See for yourself.