I run SnagitPro as an independent publication covering Snagit workflows: hands-on capture builds, annotation and markup breakdowns, video recording sessions, output and sharing pipeline tests, and honest notes about where Snagit's interface gets in the way of the work.
Who I am
I write the Snagit guides on this site under the name Adrian Foster. The work is deliberately practical: open a blank capture profile, build the workflow from scratch, stress-test the annotation stack, push the video recording pipeline, and write down what broke. I do not use TechSmith-supplied benchmark numbers or YouTube tutorial folklore passed off as professional technique.
Born: March 24, 1990, Los Angeles, California.
Education
B.S. in Visual Communication Design, California State University Los Angeles, College of Arts & Letters, 2012. Concentration in digital media production and information design. Followed by a professional certificate in Technical Communication & Documentation from the Society for Technical Communication (STC) Seminar Series, completed 2016, covering structured documentation workflows, UX writing standards, and visual instruction design.
Work history
2012–2016 — Junior Technical Writer & Media Specialist, Clarity Systems Group (software consulting firm), Los Angeles. Produced user documentation, onboarding materials, and internal knowledge bases for enterprise SaaS clients, using Snagit as the primary screen capture and annotation tool from day one. First systematic exposure to the gap between what a screen capture tool can do in a controlled demo and what actually survives a cross-platform documentation cycle with real client assets.
2016–2020 — Senior Technical Communicator & Visual Documentation Lead, Bridgeline Digital, Los Angeles. Delivered finished documentation packages, video walkthrough libraries, and training materials for software rollouts across healthcare, finance, and education sector clients. Migrated the team's entire visual documentation pipeline from a mixed legacy toolset to a Snagit-centred workflow in 2018 following a four-month evaluation against the existing process. Responsible for training three junior writers on Snagit's capture profiles, template system, and batch output architecture.
2020–2024 — Freelance Technical Communicator, Documentation Consultant & Educator. Clients included SaaS startups, corporate L&D departments, a Los Angeles–area UX consultancy, and two online course platforms where he developed and delivered Snagit-focused curriculum. Began publishing workflow notes publicly in 2022 as a response to the volume of tutorial content he found imprecise, untestable, or built around outdated Snagit versions.
2024–present — Full-time writer and publisher. SnagitPro launched as an independent publication in January 2025.
What I do here
SnagitPro is an independent publication covering Snagit workflows for technical communicators, documentation teams, educators, and anyone who captures screens professionally. The guides cover still capture, video recording, annotation and markup, templates and themes, and output pipelines — every workflow area Snagit touches — against a single consistent standard: tested in a live Snagit session before publication.
The testing method
Every technique, capture profile, or output chain covered on this site is built inside a live Snagit session on a current-generation Windows and macOS workstation running the latest stable Snagit release. Test projects use real application interfaces and live screen content — not pre-staged demo environments — at display resolutions up to 4K, with both system-level and application-level capture modes active to surface issues that clean single-monitor setups hide.
Where a guide covers a third-party integration, template pack, or companion tool, I own a licensed copy. I do not review tools from trial versions or watermarked outputs. If a technique requires a specific display scaling setting, or a capture profile that only exports cleanly at a certain output resolution, I say so with the exact specification.
How I make money
SnagitPro runs on a combination of reader support and affiliate links. Some pages carry affiliate links — if you purchase a tool, course, or piece of software through one, I receive a commission. What does not change either way: guide content and recommendations are finalised independently of any commercial relationship. No developer sees a draft. No product has moved position in a roundup because of a sponsorship arrangement. If that changes, it will be disclosed on this page before it appears anywhere else on the site.
What I will not do
- Publish a guide on a technique I have not personally tested in the current Snagit version.
- Quote TechSmith-supplied performance figures. Those are controlled conditions, not production documentation conditions.
- Move a template pack or integration up a roundup because the developer offered a review copy or discount code.
- Fabricate reader results. Every quoted outcome on this site comes from a real forum thread, Reddit post, or direct email, and the source is named or easy to locate.
- Write as though I have documented workflows I have not.