How Screencast guides are tested and maintained

What Screencast publishes

Our guides explain the recorder, the browser APIs it depends on, and the practical limits users may encounter.

We publish a page when it answers a distinct user question. We do not set a target article length, split one answer into several pages to create more URLs, or publish a browser claim only because it appears on another screen-recording site.

Product claims are limited to behavior that exists in the public recorder. Browser and operating-system claims are qualified because capture options can vary by browser version, device policy, hardware, operating system, and the surface selected in the share picker.

How product claims are checked

We compare each claim with the current Screencast implementation and the relevant browser or platform documentation.

Implementation checks confirm what the public code actually requests from the browser, what it stores locally, and which settings it passes to recording and export APIs. A guide should not promise a bitrate, resolution, frame rate, audio source, or conversion time that the implementation does not control.

Platform checks use primary documentation such as MDN Web API references, web standards, and browser-vendor documentation. When support depends on the environment, the guide says so and recommends a short test recording rather than presenting a browser capability as universal.

Hands-on results are identified as tests only when the exact browser, operating system, device, settings, and test date were recorded. Otherwise, the page describes implementation behavior and documented platform support, not a benchmark.

Review dates and changing browser behavior

Every guide shows a publication date and a last-reviewed date so readers can judge how current the information is.

Browser recording behavior changes. A browser update can add a capture option, remove an encoder, or change the labels in a share picker without any change to Screencast. We review compatibility content after meaningful recorder changes and when browser documentation changes.

A last-reviewed date means the text was checked against the code and sources listed on the page. It does not guarantee that every browser and hardware combination was physically tested on that date.

Corrections and reproducible reports

If a guide does not match what you see, send the page URL and enough environment details for us to reproduce it.

Useful reports include the browser name and version, operating system version, recording mode, selected share surface, audio options, export format, and the exact result. Do not send a private recording unless you have removed confidential information.

Email support@onlinescreencast.com with the subject "Guide correction". We update inaccurate claims and change the last-reviewed date when the correction is published.

Advertising and editorial independence

Advertising does not determine the conclusion of a guide, and an ad placement is not presented as a recommendation.

If advertising is enabled, ads are visually separated from recorder controls and editorial content. We do not accept payment to change a compatibility result or describe an unsupported feature as available.

Comparisons avoid time-sensitive competitor pricing and plan details unless they are checked against the provider's current documentation and dated. Readers should verify another product's current terms before making a purchase decision.