SnagitPro is an independent publication. I write the Snagit guides on this site under the name Adrian Foster, and this page explains the standard every one of them is held to. If a guide here ever falls short of it, that is a mistake to report, not the policy.
What gets covered
Topics come from one place: the questions documentation writers, support reps, educators, and everyday Snagit users actually ask. That means scrolling capture that stops halfway, an editor that will not open, the real difference between Snagit and the Windows Snipping Tool, what a license actually costs this year. I do not publish a guide to chase a keyword if I have nothing useful to add to it.
Tested before it publishes
Every technique, capture profile, or output chain on this site is built inside a live Snagit session before the guide goes out — on a current Windows and macOS setup running the latest stable Snagit release. Full detail is on the How We Test page. I do not write up a workflow I have not run myself, and I do not pass off a feature list as hands-on experience.
Versions and freshness
Snagit changes, prices change, and Windows and macOS shift under it. Guides are anchored to a named Snagit version and the platform they were tested on. Pages that cover pricing, licensing, or version-specific behavior carry a Last checked date and the sources I verified against, and I re-check them on a rolling 30-to-45-day cycle. If a date looks stale to you, it is fair to assume the page is due — and to tell me.
Sourcing and quotes
When a guide cites a real-world result — a bug, a workaround, a performance complaint — it comes from a named, locatable source: a forum thread, a Reddit post, a support ticket, or direct reader email. I do not invent reader quotes or attribute opinions to people who never said them. Where I synthesize what users report into a general observation, I say that is what I am doing.
Independence
SnagitPro is not affiliated with, endorsed by, or sponsored by TechSmith Corporation, the maker of Snagit. No developer or vendor sees a draft before it publishes, and no product moves up a comparison because of a review copy, discount code, or affiliate arrangement. How the site earns money is set out plainly in the affiliate disclosure.
Getting it wrong
I will get things wrong — a price that moved, a menu that relocated in an update, a step that broke on a platform I did not retest. The corrections policy covers how to flag an error and what I do about it. Accuracy here is a maintenance job, not a launch-day claim.
Last reviewed: June 2026. Questions about anything on this page: contact.