Snagit Step Capture takes screenshots as you click through a task and builds an editable numbered guide. Start in the Capture window with Presets > Step Capture, then review the result in Editor. The feature requires Snagit 2025 or newer on Windows or Mac. TechSmith’s feature page calls it Step Recorder; its release notes still use Step Capture.
Create a usable Step Capture in six steps
- Prepare a demo task with safe sample data, a consistent window size, notifications off and a visible success result.
- In the Snagit Capture window, choose Presets > Step Capture and start the capture. Some interfaces expose Steps under the Image selection options.
- Follow one successful path. Wait for each screen to load before clicking the next control, and use the capture toolbar to pause if needed.
- Finish from the floating capture toolbar and review the generated guide in Editor. Do not use Escape as a finish shortcut: on Windows it cancels Step Capture.
- Delete irrelevant steps, correct the instructions and add any missing action or confirmation image. Inspect every captured screen for private information.
- Save a separate SNAGX source, export the required delivery format and ask an authorised reader to follow the guide from the documented starting state.
TechSmith’s 2026 Step Capture video covers the recording toolbar and the editing controls. This guide also explains what to do when a click sequence misses information, why a Word export can arrive as one image, and how to choose an output your version supports.
Use Step Capture for the right kind of task
Step Capture fits a task with a visible starting state, a sequence of clicks and a result you can check: changing a display setting, creating a sample project or submitting a test request, for example. Record one route and document the exceptions separately.
Pick another format when the task depends on long text entry, precise drag movement, hover-only controls, exact timing, audio, or several decision branches. Manual screenshots give you tighter control over state, and a short Snagit screen recording can carry motion and timing. A decision tree may suit a procedure with several valid routes.
| Task | Starting format | What you still need to explain |
|---|---|---|
| Linear clicks | Step Capture | Values, prerequisites and confirmation |
| Ordered targets on one image | Step tool | Manually place numbered markers |
| Exact values or long text entry | Manual images plus text | What to enter, not just where to click |
| Drag, hover or timing | Short video or annotated stills | Movement and the completed state |
| Several valid routes | Decision tree with selected images | Which condition leads to each route |
A 20-click setup can be linear, while a four-step sign-in procedure can branch into password reset or administrator approval. Those numbers illustrate scope; they aren't limits on how many steps Snagit can capture.
Prepare the task before you record
Reset the app or website to a known state, then write down where the procedure begins and which visible result proves it worked. For example, start on an empty project list, create a sample project, and finish when its name appears in the list.
- Use safe sample data. Remove real customer details, credentials, tokens and private messages before capture.
- Keep the layout consistent. Use one window size and zoom level to reduce unnecessary layout changes.
- Remove interruptions. Close unrelated windows and pause notification previews.
- Write the expected path. Note the controls you will use and the confirmation you need at the end.
Use a separate demo account when the process touches billing, permissions, customer data, or production settings. A realistic sample is useful, but a real secret is not.
Start, pause and finish Step Capture
Open the Capture window, expand Presets and choose Step Capture, then start with the capture control. The Windows 2025 release notes and Mac 2025 release notes both document that preset. Some interfaces offer Steps under the Image selection options instead. If you can't find either, make sure you're in Capture rather than Editor, then check your installed version.
Use the floating toolbar to pause while you prepare the next part of the task, then resume. Before choosing a restart or cancel command, read its confirmation and decide whether you want to discard the current run. On Windows, Escape cancels Step Capture. It can't finish the capture and keep the guide.
Finish from the capture toolbar once you reach the result, then check that the guide includes the confirmation. If the last image only shows the button before it was clicked, add a separate capture of the completed state. Brief messages and hover states don't always appear automatically.
Do not treat a small detected capture area as a privacy boundary. Windows 2025.4 introduced a full-screen fallback for detected areas smaller than 200 × 200 pixels, so make sure everything visible in your workspace is safe to show, then check what ended up in the capture.
Treat the automatic sequence as a draft
Read the generated guide in Snagit Editor before you adjust the layout. Confirm that the order matches the task and that the text names the right controls. Automatic descriptions are only a starting point; it's still your job to check whether a new reader can complete the procedure.
- Remove noise. Delete accidental clicks, repeated states, empty loading frames, and navigation that does not help the reader.
- Add missing actions. Insert an image or sentence where the change depends on typing, a shortcut, a wait, an upload, drag movement, hover, or a choice.
- Write one action per step. Start with a direct verb such as Open, Select, Enter, Choose, or Confirm.
- Name the target. Use the visible label and location when similar controls exist. Avoid 'click here' and 'use the button above.'
- State the result. Tell the reader what changes after an important action so they can catch a wrong state early.
- Standardize the visual treatment. Use one callout style, one crop rule, and a consistent image width. Keep the target visible in its surrounding context.
You can edit and reorder the guide, remove unnecessary steps and add explanations. Captured cursors became movable or removable in Windows 2025.3 and Mac 2025.2, so you can move one that covers a label, as long as it stays tied to the action it represents. After you rearrange sections, check the whole sequence again.
Add what the clicks do not explain
Compare each pair of images and ask whether a reader can tell what changed and which action caused it. A captured click doesn't necessarily explain a typed value, a keyboard command or a background process, so write in the missing instruction instead of leaving the reader to guess.
Typing and exact values
Name the field and the type of value it accepts. For example: “Enter project-archive-2026 in Project name.” Mark sample values as examples, and never publish a working credential or imply that an account-specific value applies to everyone.
Keyboard shortcuts
Write out the exact key combination and say which platform it's for. If it opens a dialog or changes a hidden setting, include the state it leaves behind. When the procedure itself involves Snagit commands, check them against the Windows and Mac shortcut reference.
Waiting and background work
Name the completion signal: a progress bar disappears, a status changes or the new item appears. Avoid “wait five seconds” unless you have a reason specific to that procedure, because a slow connection could make the next instruction impossible to follow.
Uploads, drag actions, and hover states
Show the source file and the accepted end state without exposing a private filename. For drag or hover behavior, switch to a manual screenshot with a clear annotation, or a short video. A still frame can't prove motion.
Keep each step readable
A good step answers three questions: what do I do, where do I do it, and what should happen? Most steps need one short sentence and one focused image. Split a step when it contains two separate actions or two separate results.
Crop enough to make the target legible, but leave enough context for the reader to get oriented. When the same toolbar appears in ten images, keep the crop consistent, and if the target moves between the desktop and a modal window, make that change obvious.
Keep numbering in reading order, and add an arrow or label only when it helps the reader find a target or see what changed. For a single image with several targets, use the manual Step tool, which numbers an existing image instead of recording a workflow. The annotation guide covers these markings.
Put meaningful text beside every image. On its own, a numbered screenshot does little for a screen-reader user and is hard to scan on a small display, so the instruction has to hold up even when the image is unavailable.
Protect private data before export
Inspect the entire canvas, not just the main form. Browser tabs, bookmarks, menu bars, filenames, recent items, notifications, avatars, account names, and background windows can reveal more than the target field ever would.
- Prefer a clean capture made with demo data.
- Remove unnecessary captured states before preparing the delivery copy.
- If you cover sensitive pixels with an opaque shape, inspect a flattened delivery image. A movable shape in an editable source is not permanent redaction.
- For a public guide, check that its intended public link opens without signing in. For a private guide, check that an authorised recipient can open it and an unauthorised signed-out visitor cannot.
Be careful with native files sent to Camtasia Online. Windows 2026.3.1 and later and Mac 2026.3.2 and later send the original SNAGX, which keeps information such as cursors and text. Covering something on the canvas with an opaque annotation doesn't make a sensitive native source safe to send. Keep private originals in approved storage, and send only content you've checked for that destination.
Choose the output by audience and version
Use File > Save As to keep a separate SNAGX working source. TechSmith’s source graphics guidance separates editable objects from a flattened PNG or JPEG, and saving a PNG back as SNAGX won’t bring back the separate text and objects it once contained.
| Output | Documented minimum | Route or delivery detail |
|---|---|---|
| Word: separate images and editable text | Windows 2025.3; Mac 2025.1 | Share to Word. Earlier sharing could produce one flat image. |
| Pages: editable text and separate images | Mac 2025.2 | Choose Pages as the destination. |
| PowerPoint: editable step slides | Windows 2026.1; Mac 2026.0 | Includes a title slide and a slide per image. |
| Keynote: editable step slides | Mac 2026.0 | Mac presentation destination. |
| Markdown | Mac 2025.3 | File > Export > Markdown; keep the document and image files together. |
| Individual step images | Mac 2026.1 | File > Export > Step Capture images. Share to File gained a separate-images option in 2026.3. |
| HTML | Mac 2026.3 | File > Export > HTML; keep the HTML file with its images. |
| Camtasia handoff | Snagit 2026.3 on Windows and Mac | Camtasia Online or Camtasia Editor 2026.2.0 and newer. Mac 2027.0 adds Create a Video to the Move tool. |
The Windows 2026 history and Mac 2026 history document the newer destinations, while the 2025 histories linked above confirm Word, Pages and Markdown support. Windows release notes list neither HTML nor Markdown export, so for a Windows guide I’d deliver Word or PowerPoint, which both keep the step text editable.
A Camtasia handoff turns the steps into a video-editing workflow, which is different from recording a live screen video in Snagit. Review narration, timing and the final exported video in the destination. Moving still images into a video editor won't recreate motion that was never recorded.
When Step Capture or its export is not working
The Steps option is missing
Check the installed version and open Capture, not just Editor. Step Capture was introduced in 2025 and is a different feature from the older Step tool. Look under Presets and the Image selection options; an ordinary image preset won't produce an automatic guide.
Word contains one long image
Open the original Step Capture source rather than a flattened PNG. Check your version against the table, then use the Word share destination instead of copying the entire canvas as an image. Look at the result in Word: you should be able to edit the text separately. The version change added structured, editable output, but it wasn't the first way to put a Snagit image into Word.
An action or final result is missing
Add an explicit instruction and a separate capture of the missing state. Windows 2025.3.1 fixed cases where Step Capture missed cursor actions, but an update can't guarantee that every typed value or transient screen will be self-explanatory. Before you share the guide, compare it with the real procedure.
The output option is missing or images disappear
Check the platform, minimum version and exact export route in the table. Keep Markdown or HTML exports together with their images, since moving only the document can break image references. For a revised layout, keep the editable source and work through the Snagit templates workflow instead of rebuilding a guide from a flattened export.
Test the published guide like a new user
Give the exported guide to an authorized reader who didn't watch the recording, and ask them to follow it from a reset demo state without any verbal help. Note where they hesitate or get a different result, then fix that step.
- Start from the documented prerequisite state.
- Follow the instructions in order without verbal help.
- Record the first unclear action, missing value, wrong label, or unexpected result.
- Check every link, download, permission request, and success message.
- Repeat on the supported platform or interface variant that your audience uses.
- Correct the source, export again, and retest the affected path.
For a web guide, check it at desktop and phone widths and confirm that the images load, labels stay readable and wide tables can scroll. Follow the links with the permissions your audience will have. None of these checks requires sharing private files or making a private guide public.
Plan for the next interface change
Store the editable source, final exports, owner, product version, and last verification date together, and name the documented start and success states in the file or project notes. The next reviewer shouldn't have to depend on your memory.
Review the guide when the documented app changes a relevant label, layout, permission or result. Edit the affected source, export a fresh delivery copy and retest the surrounding steps. Keep the original publication date separate from the date you last verified the procedure.
For a formal procedure with an owner, prerequisites and approval requirements, use the broader SOP with screenshots workflow. Step Capture supplies the visual sequence; your organization’s rules, and who’s allowed to perform the task, are still your call.
Snagit Step Capture FAQ
What is Snagit Step Capture?
Snagit Step Capture takes screenshots as you click through a task and builds an editable numbered guide. It was introduced in Snagit 2025 on Windows and Mac. TechSmith’s feature page calls it Step Recorder, while release notes use Step Capture.
How do I start Step Capture in Snagit?
In the Capture window, choose Presets > Step Capture and start the capture. Some interfaces show Steps under the Image selection options. Follow the task, finish from the capture toolbar and review the guide in Editor. On Windows, Escape cancels rather than finishes Step Capture.
Does Step Capture record typing and keyboard shortcuts?
Do not assume that the generated guide fully explains typing, shortcuts, waits, uploads or hover states. Compare each transition with the real task and add explicit instructions or a separate capture wherever the action or result is missing.
What is the difference between Step Capture and the Step tool?
Step Capture takes screenshots during a sequence of actions and builds a guide. The Step tool manually adds numbered markers to an image already open in Snagit Editor. It does not record a multi-screen workflow.
Can I export a Snagit Step Capture to PowerPoint or Word?
Yes. Word output with separate images and editable text requires Windows 2025.3 or Mac 2025.1. Editable PowerPoint step slides require Windows 2026.1 or Mac 2026.0; Mac 2026.0 also supports Keynote. Older Word sharing could send one flat image instead.
Can I export a Step Capture as HTML?
Mac 2026.3 added File > Export > HTML, producing an HTML file and accompanying images. Keep those files together. Mac 2025.3 also supports Markdown export. Windows release notes list neither export, so on Windows I’d share to Word or PowerPoint instead.
Can Step Capture create a video?
Snagit 2026.3 can send Step Capture content to Camtasia Online or Camtasia Editor 2026.2.0 and newer for video creation and editing. On Mac 2027.0, the Move tool’s Create a Video option sends a selected Step Capture straight to Camtasia Online. This is different from recording live screen motion. Review the source for private information and check the final video in the destination.
This procedure belongs to the Snagit guides hub.