Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      


Updated on January 21, 2021

Use a screenshot to support an article, but do not rely only on screenshots or other visual media to document a procedure.

Refer to screenshots as figures. For more information, see figure.

Screenshot purpose

Add screenshots in the following circumstances:

  • To illustrate complicated steps.
  • To summarize a series of steps.
  • To identify the main elements of a complex window.
  • To show the location of a single control that is difficult to find.
  • To present process steps in a series of screenshots.
Note: Do not replace steps with screenshots.

Screenshot settings

When you capture screenshots, apply the following guidelines:

  • Capture an entire window, a dialog box, or a UI section.
  • Use different dots per inch settings depending on what you want to capture:
    • Full screen window: 235 dots per inch
    • Medium window or part of a window: 150 dots per inch
    • Icon or button: 96 dots per inch

As a best practice, to eliminate unnecessary information from screenshots for optimal clarity, hide the explorer pane in Dev Studio, Admin Studio, orApp Studio, resize the browser window, or layer multiple screenshots.

For more information about capturing and formatting screenshots, see Using Snagit

For example: The following screenshots show the proper way to capture a sample UI section.
Sample screenshot showing a UI section
Sample screenshot showing a UI section

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us