Back
ScreenshotOne

ScreenshotOne

#screenshotone

Render screenshots in one simple API call, instead of managing browser clusters, and handling all the corner cases.
Load previous page…
In case if there is an issue or timeout to open a new page in the browser, I launch a new instance of the browser to guarantee reliable rendering by #screenshotone as much as possible.
Improved graceful shutdown for the #screenshotone Kubernetes rendering services.
Upgraded Puppeteer to version 23.1.0 for #screenshotone.
Made the #screenshotone Kubernetes cluster autoscaling more aggressive.
Updated cookie blocking banners list with one more website for #screenshotone.
Improved error handling for #screenshotone. Enabled timeouts for asynchronous requests and fixed a few small issues that periodically made API requests hang.
Prototyped a simple analytics service for #screenshotone based on DuckDB in Go with Cursor.
Published a blog post on how I use Cloudflare Workers at #screenshotone 👉 screenshotone.com/blog/cloudf…
Announced a new feature in the #screenshotone blog.
Extended the #screenshotone API to return the host HTTP response with screenshots.
Switched the Vision API model to gpt-4o-mini in #screenshotone.
Adding all known #screenshotone API errors to the documentation, API responses and the log request history.
Publish an update about the recent improvements to #screenshotone blog—screenshotone.com/blog/introd….
Allow to report any click #screenshotone API request issue with a few clicks.
Moved all #screenshotone API request details to a side panel.
Closed the latest support tickets for #screenshotone and now go to sleep.
Posted about how spectate.net uses #screenshotone.
Add more logging in the #screenshotone API access management to catch corner cases.
Allow the #screenshotone customers to set longer delays before rendering screenshots.
Spent around 4 hours hunting a website rendering bug (#screenshotone) and finally fixed it 😌
Home
Search
Messages
Notifications
More