If you're using Helpscout Docs for your knowledge base, you know the drill. You write a great article, add screenshots, publish it, and then your product changes. Now you need to find that article, take new screenshots, upload them, and check if the text still makes sense.

For one article, that's fine. For sixty? That's your afternoon.

How Helpscout Docs handles screenshots and images

When you add a screenshot to a Helpscout article, it gets uploaded to Helpscout's own hosting. The image becomes part of that specific article. Use the same screenshot in three articles, and you upload it three times. Update it, and you update it three times.

There's no built-in image library across your Docs site. No overview of all screenshots, no way to flag an image as outdated, no notification when your UI changes.

This isn't a shortcoming: screenshot management simply isn't what a knowledge base platform is built for. But it's important to understand, because it explains why managing screenshots in Helpscout becomes harder as your help center grows.

What Helpscout does offer is flexibility. The editor supports HTML blocks, which means you can embed images from external URLs instead of uploading them directly. That's the key to a more scalable workflow.

When the manual Helpscout screenshot workflow breaks down

The manual workflow is straightforward: after each release, compare your articles to the current product and replace outdated screenshots one by one.

This stops working under four conditions:

  • More than thirty articles with screenshots. The review alone takes a significant chunk of time; you're auditing a body of content, not scanning a handful of pages.
  • Releases more often than monthly. Biweekly releases mean biweekly screenshot reviews, and that rhythm is hard to maintain alongside everything else.
  • The same screenshot in multiple articles. That dashboard screenshot in your onboarding guide, FAQ, and two feature articles? One UI change means four separate updates.
  • Multiple people working on documentation. Without a central overview, coordinating who checked what is its own task.

The manual workflow works until it doesn't. And by the time you realize it doesn't, you're already behind.

How to use embed codes for reusable Helpscout screenshots

Instead of uploading screenshots directly to Helpscout, you can embed them via an external URL using an HTML block. Update the image at that URL, and it changes in every article where it's embedded.

The concept: host your screenshot outside of Helpscout. In your article, use an HTML block with an image tag pointing to that URL. When you update the source image, every article reflects the change automatically.

SnapSteward is built for exactly this workflow. It imports all your existing Helpscout screenshots automatically. One click, and every screenshot from your Docs site is in SnapSteward, organized by article. Each screenshot gets a unique embed URL. Place it once in your Helpscout article, and from then on, all updates happen centrally.

The advantage over self-hosting: you get a complete overview of every screenshot, organized by project and product. You can see which articles use each screenshot, mark screenshots as outdated, and assign ownership for updates.

A recommended screenshot workflow for Helpscout teams

At every release:

Check what changed in the UI, talk to your dev team or read the release notes. Then review the affected articles. For each outdated screenshot, take a new one with a consistent approach: same browser width, same zoom level, same demo data.

Upload the new screenshot to your central location. If you're using embed codes, the articles update automatically. If uploading directly to Helpscout, update each article individually.

Finally, and this is easy to forget, check the text around each updated screenshot. A new screenshot might show a renamed button or restructured menu that makes the existing instructions confusing.

At a major redesign:

Plan a dedicated block of two to four hours. Prioritize the ten to fifteen most-visited articles; your Helpscout analytics show which get the most traffic. Consider delegating: with a central overview, someone else on your team can take over the update process.

The best workflow is one your team can follow every sprint. Not once, not when someone remembers. Every sprint.

Making Helpscout and SnapSteward work together

Helpscout is a strong knowledge base platform. SnapSteward adds the screenshot management layer it doesn't have: a central overview, per-project organization, and embed-once-update-everywhere.

Import your existing Helpscout screenshots in one click, manage them centrally, and let updates flow to every article automatically. Try SnapSteward free for 30 days.