Snagit guides go stale in specific, predictable ways: a price changes, a feature moves in an update, a step that worked on Windows breaks on a Mac. When something here is wrong, I want to know and fix it. This page is how that works.
How to report an error
Use the contact page. The most useful reports include the page URL, the exact line or step that is wrong, and — if you have it — what you saw instead (a screenshot helps, but is not required). "The price on the pricing page is out of date" is enough to act on; "something seemed off" is harder to chase.
What I do with it
- Verify. I re-check the claim against the current Snagit version and the original sources — TechSmith's store and support pages for pricing and licensing, the live interface for menu and hotkey changes.
- Fix. If the report holds up, I correct the page.
- Date it. Pages that cover fast-moving facts carry a "Last checked" date, which moves when the page is updated, so you can see how current the information is.
Substantive corrections
Fixing a typo is not a correction worth flagging on the page. Changing a factual claim that a reader may have acted on — a price, a license term, a "this feature does X" statement — is. When that happens, the update is reflected in the page's revised date rather than quietly overwritten.
Response time
This is an independent, one-person publication, so I cannot promise a same-day turnaround. I read every correction report and aim to verify and act on substantive ones quickly, prioritizing pages that could cost a reader money or time — pricing, licensing, and anything labeled a fix.
Last reviewed: June 2026. How guides are produced and tested in the first place: editorial policy and how we test.