Skip to main content

Solutions

Products

Recommended products

Questions? We are here to help.
Contact us

Purchase

Questions? We are here to help.

Resources

Content guidelines for Help and Support

Images

Help and Support is a text-first resource, but we also use design thinking to make content clearer and more engaging. When we understand what users need and where they get stuck, we can add images and videos to boost comprehension and improve the overall experience.

When to use images

We use images when they add clear instructional value. If they're purely decorative, we tend to avoid them. We typically add images:
  • In content aimed at new users (for example, setup or first-time tasks).
  • For new features or updates to existing interfaces.
  • When explaining UI that’s hard to describe with words (for example, unlabeled controls or uncommon UI elements).
  • To display product icons such as toolbar buttons.
  • To break up walls of text. However keep in mind each image adds 12 seconds of read time. We try to keep articles to 3 minutes or less.
  • In high-traffic or high-visibility articles, or when specifically requested by stakeholders or users.

How to incorporate images

  • Make sure the content makes sense without images. Images supplement; they do not replace steps or explanations.
  • Write steps and context first; place the image immediately after the relevant text.
  • For icons, write the button or control name first, followed by the icon image.
  • Add concise captions or callouts to highlight what matters in the image.
  • Provide alt text that conveys the instructional purpose of the image (not just “screenshot”).

Image quality and accessibility guidelines

  • Use PNG, JPEG, or SVG.
  • Use current UI for screenshots and update images when interfaces change. Review our Screenshots guidelines for more details on this.
  • Use consistent styling: crop to the relevant area, highlight focus elements, and remove sensitive data.
  • Standardize image dimensions and aspect ratios for consistency.
  • Make sure there's sufficient color contrast in annotations and callouts.
  • Provide meaningful alt text; describe the action or element users need to identify.

This article applies to:

Related Content