Browser engine upgraded

We upgraded the browser engine behind ScreenshotOne to the latest stable version and ran regression tests to verify rendering behavior.

Changelog 1 min read

Written by

Dmytro Krasun

Published on

Upgrading the browser is part of the job

We upgraded the browser engine that powers ScreenshotOne to the latest stable version.

This kind of work is easy to underestimate, but it matters. New browser versions bring rendering fixes, web platform updates, performance improvements, and compatibility changes that can affect screenshot results.

You do not need to worry about this

One of the nice parts of using ScreenshotOne is that you do not need to spend time on this maintenance yourself.

You do not need to track browser releases, rebuild your screenshot infrastructure, check for regressions, or deal with edge cases after upgrades. We handle that work for you so you can focus on your product instead of browser operations.

Regression testing

As part of the rollout, we ran regression tests to verify that core rendering and screenshot flows still work as expected.

If you notice anything unusual after the upgrade, please, contact us at support@screenshotone.com and we will investigate it as quickly as possible.

Read more product updates

New features, bug fixes, and optimizations...

View all product updates
ScreenshotOne can now return screenshots and HTML in one request

ScreenshotOne can now return screenshots and HTML in one request

Starting from today ScreenshotOne can return both a website screenshot and the content in one simple API request.

Read more

1 min read

Using AI to block banners

Using AI to block banners

First successful attempts to block banners on websites using AI before rendering screenshots.

Read more

1 min read

Improving performance and stability by consolidating validation and access check logic in the API gateway

Improving performance and stability by consolidating validation and access check logic in the API gateway

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.

Read more

2 min read

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.