
How BugSmash automates website screenshot rendering
How and why BugSmash uses ScreenshotOne for critical screenshot rendering tasks.
- Written by
- Nabil Kazi, Dmytro Krasun
- Published on
Automate Website Screenshots
Guides, Product Updates, and Helpful Resources from ScreenshotOne.
How and why BugSmash uses ScreenshotOne for critical screenshot rendering tasks.
Check out how to use the external identifier to improve tracking of webhook executions.
Check out how to get notified about rendering errors when using webhooks.
We added support of Slack notifications to ScreenshotOne. Now you can set up and get Slack notifications when you reach your quota limits.
We improve UI/UX of rendering numbers in the dashboard for better readability.
We added more algorithms for screenshots by selectors.
It is a good milestone to make a compact snapshot of the insights that (maybe?) led to it.
Improved code examples in the playground and added all official supported ScreenshotOne SDKs.
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.