How to automate help center screenshots
Four ways teams keep help center screenshots current, from retaking them by hand to scripts and AI agents, with what each covers and where each breaks.
Daniel Nadasan, founder of Snapflow
6 min read
On this page
Every release moves something: a button gets a new name, a menu moves to the sidebar, a settings page gets a new section. The help center doesn't move with it. Across 487 Intercom help centers Snapflow audited in October and November 2026, 57% of 332,907 screenshots were more than a year old.
Nobody decides to let that happen. Retaking screenshots is slow, and it's never more urgent than the next ticket. So teams look for a way to automate it. This guide covers the four ways we've seen teams try, and where each one holds up.
What does automating help center screenshots involve?
It involves five jobs, and taking the screenshot is the easy one. Most tools only do that one:
- Find what's out of date. Which of your hundreds of screenshots no longer match the product?
- Get to the right screen. Sign in as the right kind of user, with tidy sample data, and click through to the exact state the article describes.
- Take it the way your help center does. The same size and crop, the same arrows and boxes, nothing private on screen: your screenshot style guide.
- Put it back. Replace the old image in the article, in every language it appears in.
- Do it again next release, and notice when it fails.
Keep that list in mind for the options below. A tool that makes step 3 faster still leaves you with steps 1, 2, 4 and 5.
How do teams keep screenshots current today?
Mostly by hand. In the teams we've talked to, it's one of two habits, or both.
After each release, by hand. Whoever shipped the change, or whoever in support hears about it first, updates the articles they remember. The articles nobody remembers stay as they were, and those are the ones customers find.
A sweep every few months. Someone goes through the help center article by article and retakes what's changed. It takes days, and the help center starts going out of date again the day it ends.
Plenty of teams do neither for long stretches. 65 of the 487 Intercom help centers we audited (13%) hadn't added a single screenshot in the six months before their audit. Across all of them, nearly half the screenshots date from before July 2025:
| Before Jul 2025 | 45.6% |
|---|---|
| Q3 2025 | 7.9% |
| Q4 2025 | 8.1% |
| Q1 2026 | 9.3% |
| Q2 2026 | 10.1% |
| Q3 2026 | 11.5% |
| Q4 2026 | 7.3% |
What are the ways to automate help center screenshots?
There are four: retake them by hand with a checklist, use a capture tool, write scripts, or use an AI agent. They differ in which of the five jobs they take off your hands.
1. Retake them by hand, with a checklist
Not automation, but it's the baseline everything else is measured against, and with a good checklist it can be enough for a small help center. The cost grows with every article and every release, and it depends on one person remembering which articles a change touched.
2. Capture tools: Scribe, Tango, Snagit
Scribe and Tango record you clicking through a process and turn each click into a step with a screenshot, so writing a new guide takes minutes. Snagit is a screen capture and annotation tool: it makes taking and marking up a single screenshot faster.
All three speed up step 3. None of them finds the screenshots that are out of date, and when the product changes, the guide is recorded again by hand. As of 13 November 2026, neither Scribe's nor Tango's site says their guides update when your product does. Scribe lists flagging outdated docs as "coming soon".
They also make their own guides. If your articles live in Intercom, Zendesk, HubSpot, Help Scout or Freshdesk, the screenshots in those articles still have to be replaced one by one. Each compared with Snapflow: Scribe, Tango, Snagit and Guidde.
3. Scripts: Playwright or Puppeteer
A developer writes a browser automation script for each screenshot: sign in, go to the page, set up the state, take the screenshot, upload it. Run it after each release and every screenshot comes back fresh. On paper it covers steps 2 to 5.
We've watched this play out at a tax-tech scaleup. A developer built the scripts, and the result was usable but mediocre. Every new scenario needed a fix: a new user role, a modal that only appears on some accounts, a screen that looked different with other data. The developer had a product to build, so fixes waited.
Then the automation broke, and nobody noticed for a while. A script that fails doesn't update anything, and an out-of-date screenshot looks just like a current one. By the time someone saw it, the help center had been drifting for weeks. The team couldn't keep pulling the developer off product work, and they found no other way to automate it, so they went back to retaking screenshots by hand.
That's the usual shape of it. Writing the scripts is a few days of work. Owning them is the real cost: every UI change that breaks a screenshot breaks a script too, so the work moves from support to engineering instead of going away. It holds up for a handful of stable screens and a developer whose job includes keeping it running.
4. An AI agent that retakes them
This is what we built Snapflow to do. Instead of a script per screenshot, it works from the article:
- It reads each article and works out what its screenshot is meant to show, from the text around it and the old screenshot.
- It signs in to your product as a demo account that fits (an admin, a member, a free plan) and clicks through to that screen the way a customer following the article would.
- It takes the screenshot, frames it on what the article talks about, and adds the arrows or boxes your style uses.
- Each screenshot has a permanent image address. You add it to the article once, and the picture behind it updates. Nothing is re-uploaded.
- It runs on a schedule, or after each release through the API on the Scale plan. Scheduled retakes wait for you to review them next to the old ones.
Because it finds the screen from what the article says rather than from a fixed path, a renamed button or a moved menu doesn't need anyone to fix code, the way it would with a script. LaunchBrightly also retakes help center screenshots, from a recorded recipe per screenshot; see Snapflow vs LaunchBrightly.
What it can't do yet, so you know before you try it:
- Single sign-on and two-factor sign-in. Snapflow signs in with a username and password, so the demo account needs a password and no second factor.
- Screens that only exist after creating something, like the confirmation after sending an invoice. That's planned, and will work by connecting Snapflow to your code so it can set up the data first.
- Anything irreversible. It never confirms a deletion, a payment, a plan change or a message to other people. It stops before the button and takes the screenshot there. That one is on purpose.
Pros and cons of each option
| Best for | Pros | Cons | |
|---|---|---|---|
| By hand | Small help centers that change rarely | Works for any screen. A person judges what matters. No setup. | Grows with every article and release. Relies on someone remembering which articles a change touched. |
| Capture tools | Writing new guides | New guides in minutes, with annotations. Easy for anyone on the team. | Doesn't find what's out of date. Every changed guide is recorded again by hand. Doesn't replace screenshots already in your help center. |
| Scripts | A few stable screens, with a developer who owns them | Fully automatic once working. Free apart from a developer's time. | Every new scenario needs code. Breaks quietly when the UI changes. Needs a developer for as long as you use it. |
| AI agent | Keeping a whole help center current after each release | Works out which screenshots need retaking. Finds each screen from the article, so a moved button needs no code fix. Updates screenshots in place, after your review. | No single sign-on or two-factor sign-in yet. Screens that need data created first are still to come. A subscription. |
Where should you start?
With step 1, whichever way you go: find out how much of your help center is out of date. Snapflow's free audit dates every screenshot in your help center and lists the articles that were edited after their screenshots were taken. It takes about five minutes and needs no account. If you want a number for what doing it by hand costs your team, the savings calculator works it out from the hours spent retaking screenshots and the tickets out-of-date ones cause.
Questions
Can I automate help center screenshots with Playwright or Puppeteer?
Yes, with a script per screenshot that signs in, opens the page and takes the screenshot. It works for a few stable screens. The cost is keeping it running: every UI change that breaks a screenshot breaks its script too, and a failed script leaves the old screenshot in place without anyone noticing.
Do Scribe or Tango update screenshots when the product changes?
As of 13 November 2026, neither says so on its site. Both record a process as you click through it, so a changed screen is recorded again. Scribe lists flagging outdated docs as coming soon.
What does Snapflow need to start?
Your help center's address and a demo account for your product that signs in with a username and password. Nothing is installed in your product or your help center.
See how old your help center's screenshots are
Free scan no account results in about five minutes
Summarize with AI
Founder of Snapflow
Daniel Nadasan is the founder of Snapflow. He has run the screenshots of more than 500 software help centers through Snapflow's audit, and writes here about what that shows: how fast screenshots fall behind the product, and what it takes to keep them current.
LinkedIn