Alexander Schnebel about how he uses ScreenshotOne in Productglowup
I had a great chat with Alexander Schnebel, the fullstack software engineer behind Productglowup.
- Written by
- Dmytro Krasun
- Published on
- •
- 1 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
I had a great chat with Alexander Schnebel, the fullstack software engineer behind Productglowup.
I am thrilled to announce an exciting update for the ScreenshotOne users – the much-anticipated integration of ScreenshotOne with Zapier. This powerful combination is here to enhance your automation journey and expand your workflow capabilities to new heights.
Enter the ScreenshotOne API – a revolutionary tool designed to change the face of web archiving.
The article examines how you can take screenshots of any URL with C# (.NET) by using PuppeteerSharp, or screenshot API as a service.
It is not the first time that one of the ScreenshotOne users asked how to render screenshots in Google Sheets. I wrote a simple but complete tutorial once and for all.
Let's talk about the optimizeForSpeed parameter introduced in Chrome DevTools Protocol which will soon be supported by Puppeteer or even supported now at the time when you are reading the post.
Let's talk about the fromSurface parameter introduced in Chrome DevTools Protocol which will soon be supported by Puppeteer or even supported now at the time when you are reading the post.
Nowadays, you have various options to generate PDFs from HTML or any given URL: generating PDF in the browser, on the server-side (Node.js), or even using a modern and friendly API to generate PDF.
Let's talk about the captureBeyondViewport parameter introduced in Chrome DevTools Protocol which will soon be supported by Puppeteer or even supported now at the time when you are reading the post.
With Python, you can take website screenshots in multiple ways. But the best way to do it depends solely on your needs and your use case. Let's quickly examine all the options.
Let's examine what Ruby proposes for us to render HTML or URL as a screenshot dynamically.
Record video in Puppeteer with page.screencast() or puppeteer-screen-recorder. Compare MP4, WebM, and GIF output, crop, fps, streaming, and when to use each.
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.