Editorial and review methodology

Two review types

Researched overview. We read the vendor's official pricing page and documentation and record what they say. We have not used the tool. These pages say nothing about output quality or ease of use.

Hands-on review. Used only when we have actually tested the tool and can show dated evidence, such as what we did and what happened. A page cannot be labelled hands-on without evidence entries in its data file, and the build fails if that rule is broken.

Tests so far. None. Every entry is a researched overview. We have written the procedures for four small evaluations (product photos, meeting summaries, coding help and presentations) but have not run them, so no page claims a tested result.

Pricing

What we do not do

How featured tools and picks are chosen

Selected categories have a headline editorial pick that answers a stated need, such as the most free video time on a pricing page, with the reason taken from published plan details. The category pages list further recommendations for other needs. Picks are not ratings, and we do not rank tools by popularity because we have no usage data. We start with categories where readers make real purchasing decisions, then include tools with official documentation; unchecked paid pricing is labelled clearly. A draft or unfinished entry is never featured or recommended as an alternative. Tools with no affiliate program are included on the same terms as tools with one. Affiliate status is stored in a separate file and is not used when we write recommendations.

Keeping pages current

Each tool page shows when pricing was checked and, per source, what each source covered and when. “Recently checked” sorts by the pricing verification date; “Recently added” sorts by listing date. Prices change, so treat dates older than a few months with caution and confirm on the vendor's site.