Having documentation and code examples is great, but not enough to allow developers to quickly integrate the API and assess all available features of the ScreenshotOne API.
Written by
Dmytro KrasunPublished on
That’s why ScreenshotOne’s playground was upgraded to support the most often used product use cases.
You can render static, scrolling screenshots, videos, and PDFs right from the playground from today and just copy and paste working code examples.
There are many more use cases. But let’s start with these ones and add more on the go.
Enjoy!
Read more product updates
Interviews, tips, guides, industry best practices, and news.
Fail rendering if the content contains a string
There is a set of use cases when you want to fail screenshot rendering and retry it if the content of the page contains a string.
I migrated to Google Cloud
Google Cloud gives $300 in credits for 3 months for experimenting. And I decided to give it a try, but not because of the free credits.
ScreenshotOne API supports GPU Rendering
From today ScreenshotOne supports GPU rendering for both regular and animated website screenshots. The API now leverages the latest in graphics processing technology to bring your screenshot needs to a whole new level.
Automate website screenshots
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.