About SnagitPro

Learn what SnagitPro covers, how its editorial byline and research work, what testing labels mean, and where to find disclosures or report a factual error.

SnagitPro publishes independent guides to Snagit, screenshots, screen recording, image editing, and documentation workflows. The site is not affiliated with, endorsed by, or sponsored by TechSmith Corporation.

Who writes the guides

Adrian Foster is the editorial byline used on SnagitPro. It identifies the publication's content; it does not establish professional credentials or prove that an individual personally tested a product. Questions about a guide can be sent through the SnagitPro contact page.

AI-assisted research, drafting, and editing are part of the site's workflow. Product claims require traceable evidence. Generated text, a byline, or a polished illustration cannot substitute for that evidence.

What the site covers

The guides are for people who create instructions, answer support questions, teach, or need a clear screenshot for everyday work. Topics include capture setup, annotation and redaction, text extraction, recording problems, permissions, storage, backups, licensing, and comparisons with other capture tools.

If you are learning the app, start with the Snagit Editor guide. For an existing problem, use the troubleshooting directory to find the matching symptom.

How claims are checked

Our editorial standard requires research into the reader's task, current primary sources for product facts, and a separate check of the saved page. Prices, supported systems, license terms, version numbers, and menu paths need their own evidence. Search results help identify questions; the source behind a claim must support the answer.

Community reports can identify a problem worth investigating. They need a findable source and must be distinguished from official product behavior. The standard does not permit invented quotes, test environments, benchmarks, or personal experience.

These are requirements for the publication, not a guarantee that every older page has already completed the current review process. If an article lacks support for a claim or gives a step that does not match your version, report the specific passage.

Documentation review and hands-on testing

Documentation checked means the stated claim or procedure was compared with primary or authoritative sources. It does not mean the procedure was performed on a physical Windows or Mac computer.

A hands-on tested claim must identify the app version, operating system, relevant equipment or settings, test date, and observed result. Read the article's stated scope before applying a result to another setup. The research and verification method explains these distinctions.

Visual policy

Some visuals are illustrations or reconstructed interface views that explain a choice or workflow. Treat them as teaching aids, not proof of a performed test or an exact copy of your installed interface. The written steps and cited product documentation should identify the applicable platform and version.

Independence and commercial relationships

The site may earn a commission from a qualifying purchase through an affiliate link. The affiliate disclosure describes that relationship. The editorial standard requires recommendations to follow product evidence and the reader's needs; payment must not buy a favorable verdict or an undisclosed placement.

Report an error

Use the corrections process and include the page URL, app and operating-system versions, and the exact claim or step that differs. Do not send passwords, license keys, activation codes, or screenshots containing private customer information.

SnagitPro cannot manage a TechSmith account, issue a software refund, or recover a license. Send those requests to TechSmith Support. The independence and trademark notice explains the site's relationship to the products it covers.

Last reviewed: September 12, 2026.