As someone once said, a picture is worth a thousand words. Therefore, whenever you need to illustrate operations performed on the UI, use a screenshot to convey the information visually.

Follow these basic principles when you place screenshots in your content:

  • Do not overuse screenshots and limit visual noise.
  • Do not use directional indicators such as "above" and "below" to refer to screenshots. Instead, include a brief introduction before each screenshot that describes its purpose and any necessary details.
  • Do not include the mouse pointer in your screenshots, unless it shows a function related to the content.
  • Do not include unnecessary elements, such as the browser toolbar. Include only elements that are relevant for the given content.

For details on how to format screenshots and their elements in Kyma documents, see the particular document sections.

Alternative text

Always add an alternative (alt) text that concisely describes the content or function of the image you are referring to. The alt text:

  • Helps to maintain accessibility for every visitor, including people with vision impairments.
  • Appears in place of an image if it fails to load.
  • Improves the SEO of the website by enabling crawlers to index the image contents better.

    ⛔️ ![](/assets/community/guidelines/content-guidelines/assets/create-bucket.png)
    ![Create a bucket](/assets/community/guidelines/content-guidelines/assets/create-bucket.png)


Adjust or capture your screenshots using any tool that outputs high quality images, such as Snagit, Lightshot, or Monosnap. The desired image format is SVG, but PNG and JPG formats are also acceptable. Use an online tool such as TinyPNG to compress images and limit the size of each image to 1MB, or smaller. If you want to control the size of the image relative to the screen size, use one of these standard percentages: 100%, 75%, 50%, or 25%.

NOTE: The images keep their original aspect ratio on both the Console UI and the website. However, the maximum width on the website is 860px. Any image that exceeds that limit is resized to the maximum width.

Name the file as {screenshot-name} and save it under the corresponding assets directory.


Use grey (HEX: #D2D5D9) 1pt border for the screenshot.


If necessary, mark multiple areas or steps on the screenshot using blue (HEX: #0A6ED1) round stamps with white numbers. Explain the steps under the screenshot with the ordered list.


To highlight a certain area of your screenshot, use red (HEX: #EF2727) 10pt for arrows or boxes.

NOTE: Use arrows and boxes sparingly, only to point to an exceptionally important area of the screenshot. Do not use more than one indicator in one screenshot to avoid visual noise.

Simplified User Interfaces (SUI)

Wherever possible, present screenshots as simplified user interfaces (SUI). Basically, this means blurring or covering all UI elements that aren't essential for the task at hand. Snagit supports SUI with some specialized tools.

Use circles to cover icons, and rectangles with pointed corners to cover texts.

  • Light gray (#F2F2F2)​ for texts on a white background​
  • Dark gray (#D9D9D9)​ for headlines on a white background​

Don't cover: The logo, the sandwich icon, the search icon, expand buttons, close buttons.

For more information, see tcworld: Simplified graphics and screenshots in software documentation


See the exemplary screenshots for reference:

  • Example


  • Example SUI

Example SUI