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
- •
- 2 min read
With more than a decade of experience in software engineering, I share the best practices and solutions you can apply to your problems in the space of headless browsers. You can also find me on Twitter and LinkedIn
How and why BugSmash uses ScreenshotOne for critical screenshot rendering tasks.
It is a good milestone to make a compact snapshot of the insights that (maybe?) led to it.
Learn how to render screenshots with different emoji styles in Puppeteer using emoji-js in a few lines of code.
OpenAI 4o image generation is a really good model that can change the way you automate marketing
How and why "Magic Pages" used ScreenshotOne to showcase how their customers use their product.
I tried many ways to monitor and detect website changes. But I was always disappointed by the results. I want to share a few tips that might help you to get better results, if you plan to do the same.
We just launched a new full-page screenshot Chrome extension that allows you to take full page screenshots of any websites and annotate them in a few clicks.
How and why "Make a Directory" used ScreenshotOne to automate screenshots for directory websites.
How and why "Directify" used ScreenshotOne to automate screenshots for directory websites.
A funny game built on top of ScreenshotOne API.
If you are interested in diving deeper into the Branding 5 use case and discover if ScreenshotOne might be useful for you, too, keep reading.
Check out how ScreenshotOne relies on Cloudflare Workers as an API gateway to enhance performance, reliability, and cost-efficiency.
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.