ScreenshotOne supports PDF rendering for a long time but it was used till recently by a small group of customers. Growing demand in PDF rendering required updating the API. And today, we introduce new options for PDF customization.
We have added a possibility to render the website as a page PDF, it is essentially the equivalent of the full-page screenshot, but as a PDF with one page only. Use the pdf_fit_one_page option to achieve that.
And you can force our PDF API (now we call it so) to render graphics, which is not enabled by default. Most of our current customers use PDF rendering without graphics. Use the pdf_print_background option to achieve that.
Happy to share the updates and more soon to come!
New features, bug fixes, and optimizations...
First successful attempts to block banners on websites using AI before rendering screenshots.
1 min read
Add multiple dedicated email recipients for usage limit notifications.
1 min read
For the past few days, I have been working on improving the stability and performance of the ScreenshotOne API. I started from low-hanging fruits—moving validations and access key management from rendering services to ScreenshotOne's API gateway. The API will be more stable and performant as a result. If you are curious why, please continue reading.
2 min read
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.