How Snapflow decides which screenshots to take
What the audit looks at, and how the Depth setting controls how many screenshots are planned.
Written by Daniel Nadasan
Updated 1 min read
On this page
Snapflow reads every article and plans a screenshot wherever one would help a reader follow it. Each planned screenshot gets a rating for how much the article needs it, and you choose how far down that list to go.
This step is called the audit. It doesn't take any screenshots and doesn't use any captures.
What the audit looks at
For each article, Snapflow works out:
- Which existing screenshots to take again, because they show your product.
- Where a screenshot is missing, such as a step that's hard to follow from text alone.
- Which images to leave alone: logos, avatars, badges and screenshots of other products.
Each planned screenshot says what it will show and why the article needs it. Open one on the Help center page to read both.
Choose how many to take
The Depth menu on the Help center page sets how many of the planned screenshots count:
| Depth | What it includes |
|---|---|
| Critical | Screenshots the articles can't be followed without. |
| Recommended | Those, plus the ones that remove real doubt about a step. |
| Everything | Every screenshot Snapflow suggested, down to confirmations. |
The menu shows how many screenshots each depth means for your help center. Changing it changes what the page shows as planned and how many the Take screenshots button takes.
If there are more than your plan includes
Snapflow takes the ones your articles need most first. The rest stay planned, and you can take them later.
When to run the audit again
Run a new audit when your articles or demo accounts change, not when your product does. Check for changes, re-take or run a new audit explains which one to use.
Did this answer your question?
Still stuck?
Email daniel@usesnapflow.com and you'll hear back from Daniel, who built Snapflow.