Every guide on SnagitPro is built and verified in a live Snagit session before it publishes. This page is the long version of what that means, so you can judge the work instead of taking "tested" on faith. It is a solo publication — when I say "I tested this," one person ran it on real hardware, not a team signing off on a spec sheet.
The hardware
Guides are tested on two machines kept on current operating systems: a current-generation Windows workstation and a macOS workstation. Testing runs at display resolutions up to 4K, because high-DPI scaling is exactly where capture tools misbehave — blurry exports, wrong-sized regions, scroll capture that drifts. Clean single-monitor setups hide those problems; I look for them on purpose.
The Snagit version
Each guide is run against the latest stable Snagit release at the time of writing, and the version is named in the guide. When TechSmith ships an update that changes a menu path, a hotkey, or a capture behavior I have documented, that page goes on the re-test list. A guide tied to an old version with no note is a bug — flag it.
What "tested" covers
- Real interfaces, not demos. Test projects use live application windows and real screen content, with both system-level and application-level capture modes active — not pre-staged sample images.
- The full chain. Capture, edit, annotate, and the output step. A scrolling capture that grabs the page but exports a broken image has not passed.
- Both platforms, where it matters. Windows and macOS handle permissions, hotkeys, and recording differently. When a step diverges, the guide says so for each platform rather than assuming Windows behavior holds on a Mac.
- Exact specifications. If a result depends on a specific display-scaling setting or an export resolution, I give the number instead of waving at "your settings."
Third-party and alternative tools
When a guide covers an alternative to Snagit — ShareX, Greenshot, Shottr, CleanShot X, OBS, the Windows Snipping Tool — I test it the same way, on a licensed or genuinely free copy. I do not review from trial limitations, watermarked output, or a competitor's marketing page.
Performance claims
Where a guide describes how a tool behaves under load — capture lag, recording stability, export time — those are observations from these test conditions and from real user reports, not TechSmith-supplied benchmark figures run in a controlled demo. If a number would not survive a normal documentation workflow, it does not belong in a guide.
What I will not do
- Publish a technique I have not personally run in the current Snagit version.
- Quote vendor performance numbers as if they were hands-on results.
- Move a tool up a comparison because of a review copy or a discount code.
- Write as though I have documented a workflow I have not.
Last reviewed: June 2026. The short version of who I am and why this site exists is on the about page.