Managing Zendesk help center images is one of those problems that feels completely manageable, until one day it suddenly isn’t.
At 20 articles, a loose approach to managing screenshots is fine.
But with 200+ articles and a product UI that changes every few weeks, managing help center images suddenly becomes one of the most time-consuming and error-prone maintenance tasks in your entire knowledge base.
If you could visit a help center doctor, the symptoms they’d check for would be consistent:
- Outdated screenshots that no longer match your product.
- The same image uploaded a dozen times under slightly different filenames.
- No reliable way to know which articles are affected when something changes.
When that’s your reality, one product update can quietly cascade into dozens of broken or misleading screenshots across your help center.
In many cases, support teams only discover the full extent of the issue when a customer complains or an agent spots something embarrassingly outdated in a customer-facing article.
This post covers how to get ahead of this problem: the right mental model, what Zendesk’s Media Library actually gives you (and where it falls short), and the practical habits and tooling that keep things from spiraling at scale.
Why Help Center Image Management Breaks Down in Zendesk
The root issue that makes help center image management a problem is how most teams think about screenshots: as per-article uploads rather than shared, reusable assets.
When someone writes a new article, they take a screenshot, upload it, and move on. If another article needs the same image, they do it again.
Over time, the same screenshot might exist as five or six separate files in five or six different articles, each with a slightly different filename and no connection to the others.
When your product UI changes, every one of those images needs to be updated manually — and there’s no reliable way to find them all.
This came up recently in a discussion in the Support Driven Slack community. A customer support manager described running into this exact problem: duplicate images scattered across articles, no centralized image library, and constant manual work whenever the product changed.
Unfortunately, the response from other Zendesk practitioners wasn’t providing an obvious solution — it was more like “yeah, this is genuinely hard in Zendesk and most teams don’t have a great answer.“
Josh Peacock, COO of LaunchBrightly — a screenshot automation platform built specifically for help centers — put it well: “This one sneaks up on you — totally manageable at small scale then suddenly you’ve got hundreds of articles and constant UI updates.”
Josh also pointed out a key underlying factor that leads to this issue: duplication is as much a process problem as a storage problem.
Even if you build a great system for managing screenshots and help center images, it won’t help if your team doesn’t have the discipline to follow a consistent process of checking to see if images already exist before uploading new ones.
Other process-related steps — like consistent naming conventions — also are critical to solving this for good.
Bottom line: the tooling matters, but it must be paired with the right habits in order to work.
The Mental Model Shift: Treat Images as Reusable Assets
Before getting into tooling, it’s critical to frame this problem right, because the teams that manage Zendesk help center images well at scale tend to think about it differently than the ones that struggle.
One mental model that resonates with a lot of Zendesk admins (and support leaders in general) is COPE: Change Once, Publish Everywhere.
The idea is straightforward: every image in your help center should have one canonical version, stored in one place. When that canonical version is updated, the change propagates to every article that references it automatically, without you needing to hunt down and replace each instance individually.
Jason Schulke, Principal Solutions Architect at Prep Work, wrote about the COPE framework in his Product Education newsletter.
The post includes a few recommendations of digital asset management tools that can help with implementing COPE — tools like Dash, Canto, and Frontify.
LaunchBrightly (mentioned above) is also a tool worth keeping in mind. Because it’s helpdesk agnostic and automates the actual capture and sync of screenshots (recording the steps to capture a specific UI state, applying consistent styling and annotations, and syncing updated screenshots directly to your help center when the product changes).
It’s a specialist tool for teams where screenshot maintenance is a significant, recurring cost.
While dedicated tool investments like these can help, plenty of support teams aren’t at the scale or budget where full screenshot automation makes sense.
For those Zendesk teams, the question is: how do we get closer to COPE using what we have, plus the right supporting tooling?
Zendesk’s Media Library: What It Does Well and Where It Falls Short
Zendesk’s native ability to manage help center images has improved meaningfully over the years. The Zendesk Media Library is the primary native way to manage images across your knowledge base, and it’s worth understanding in detail.
What works well:
The most significant feature related to this issue of managing images at scale is the Replace Media feature. When you replace an image in the Media Library, the new image propagates to every article and content block where the old image was used — and critically, the URL stays the same, so no links break.
This is the closest thing to COPE within Zendesk natively, and it’s really useful once you’re working from a clean, deduplicated state.
The Share to all feature lets agents share uploaded images with their whole team, making images available across content writers and agents (rather than siloed to the person who uploaded them).
That’s also critical, because now there’s a way for agents to see what everyone else has uploaded, helping prevent duplication. It also makes it easier for Zendesk Knowledge admins to audit and clean up images when needed.
Where it falls short:
While those things help, the limitations of the Zendesk Media Library are real:
- Duplicate cleanup is still manual and slow. Improved visibility across images helps, but it’s still manual and painfully slow. If you want to consolidate ten copies of the same screenshot, you’re doing it one by one.
- No staging environment. Replacing an image updates every published article immediately. If you’re prepping KB articles ahead of a major product release and want to have screenshots ready to go, there’s no way to stage the change.
- Reuse is still optional. If someone uploads the same screenshot twice — which happens all the time — Zendesk creates two separate assets with no nudge to consolidate them.
Media Library’s ability to replace an image and propagate it across all articles where the image is already used is really valuable, but actually keeping your images clean and unduplicated across your help center still primarily relies on your team’s behaviors.
The moment a duplicate image is uploaded, you’re back to managing two separate image assets and the cycle starts all over.
Better Visibility Across Your Image Library
One of the things the Support Driven discussion surfaced is that most teams are missing article-level tracking — knowing not just that an image exists, but exactly which articles it’s used in.
Without that visibility, you can’t be confident that an update actually propagated everywhere it should have.
This is where Swifteq’s Help Center Manager fills a meaningful gap for Zendesk teams.
Its Media Page gives you a centralized view of every image and video across your published and draft articles — searchable by filename or alt text, sortable, and with each image’s source article linked directly.
Even if you’re relying on manual audits and changes, this alone dramatically changes what that process looks like: instead of opening articles one by one to check what’s in them, you have the full picture in one place.
A few specific things it enables that Zendesk’s native Media Library doesn’t:
- Spotting likely duplicates — you can search by filename or alt text to find images that appear across multiple articles as separate uploads, which is the first step toward consolidating them.
- Finding and fixing broken media — broken images in published articles show up clearly, so you can address them before customers hit them.
- Alt text management at scale — you can identify every image missing alt text across your entire help center, generate alt text with AI, and push it to Zendesk without opening individual articles. This is a huge time saver for teams with large content libraries.
It’s not a full solution to managing help center images at scale, but it makes the process significantly less painful at an incredibly low price.
The Practical Habits That Keep Things from Spiraling
Tooling is really important, but like I mentioned above, it has to be paired with the right habits and behaviors to really work well. Here’s what tends to make the biggest difference:
Audit before anything else
Before putting any new systems or naming conventions in place, figure out what you’re working with.
If you have dozens or hundreds of duplicate images across your help center, you need to work towards a single source of truth for each part of your product UI. Without that canonical version of each key image, nothing else works.
Make naming conventions non-negotiable
A predictable naming pattern is a gamechanger and should be a requirement for everyone who uploads images to your help center. Josh recommends something like product-area-feature-state.png (e.g. settings-billing-upgrade-modal.png) as a good format to use.
The reason it matters so much is that once your naming is consistent, you’re able to use a tool like Help Center Manager to easily search for those images — and you can actually trust the search results. If your images are all named things like “screenshot_04122026”, that’s impossible.
Make “does this already exist?” a reflex
This is a process gate, not a technical one. Before anyone uploads a new screenshot, they should spend 30 seconds checking whether it’s already in the library.
Pair this with your consistent naming convention and you’ve already made a messy problem far easier to deal with.
Assign area ownership
For larger teams, assigning someone accountability for the images in each product area goes a long way. Without ownership, consistency drifts over time (we’re all busy, it’s inevitable).
With ownership and accountability, you have someone whose job includes periodic audits and keeping their assigned area clean.
Add timestamps where you can
Zendesk’s Media Library doesn’t surface upload dates, but if you’re tracking images externally (in a spreadsheet, Figma, or a tool like Help Center Manager), adding a date column makes audits dramatically easier.
You can quickly identify images that haven’t been touched in 18 months and prioritize them for review.
Managing Zendesk Help Center Images at Scale Is Possible
There’s no single tool or process that solves managing Zendesk help center images entirely — it’s a layered problem that requires a layered approach:
- COPE as the mental model: one canonical version of every image, with changes propagating automatically.
- Zendesk’s Media Library for replace-and-propagate within the platform. It’s particularly useful once you’re working from a clean state.
- Naming conventions and consistent process as the backbone that prevents duplicates from accumulating in the first place.
- Swifteq’s Help Center Manager for centralized visibility, auditing, duplicate spotting, broken image detection, and alt text management across your full Zendesk Help Center.
- LaunchBrightly for larger help centers where screenshot capture and sync needs to be automated end-to-end.
The teams that stay on top of managing Zendesk help center images aren’t necessarily using more sophisticated tooling — they’ve just stopped treating screenshots as throwaway, per-article uploads and started treating them as centralized assets with a lifecycle.
That shift in thinking, combined with the right visibility into what’s actually in your library, is what makes the difference between a help center that compounds in quality over time and one that slowly becomes a maintenance burden.
If your images are a mess or you’re not sure where they stand, a good place to start is running an audit in Help Center Manager — there’s even a 45-day pass option so you can give it a try and run a full audit to get your knowledge base cleaned up.
Written by Larry Barker
Larry has spent over a decade leading CX teams at tech companies of various sizes. He also currently operates Supported Content, a niche content marketing company that helps CX brands attract and retain customers.
