ScreenshotOne now renders HTTP-only websites more reliably by avoiding browser HTTPS-upgrade redirect loops.
We improved rendering for websites that are still served over HTTP.
Some browser versions can automatically try to upgrade http:// pages to https://. For HTTP-only websites, or websites that redirect back to HTTP, that browser behavior could cause a redirect loop before ScreenshotOne captured the page.
ScreenshotOne now preserves the requested HTTP URL unless the website itself redirects it. HTTPS URLs and normal server-side redirects continue to work as expected.
New features, bug fixes, and optimizations...
Shops.Gallery uses ScreenshotOne to render consistent storefront previews for design inspiration.
1 min read
A new ScreenshotOne tool to capture what users see before the first scroll.
1 min read
For the past few days, I have been working on improving the stability and performance of the ScreenshotOne API. I started from low-hanging fruits—moving validations and access key management from rendering services to ScreenshotOne's API gateway. The API will be more stable and performant as a result. If you are curious why, please continue reading.
2 min read
Exhaustive documentation, ready SDKs, no-code tools, and other automation to help you render website screenshots and outsource all the boring work related to that to us.