Capture Product Screenshots

You can capture screenshots from supported product experiences to use in user-facing documentation. Keeping screenshots current helps your documentation reflect what users actually see in the product.

Overview

Screenshot capture is part of Atloria’s visual documentation workflow. Use it when you need current images for a user guide, help center article, or other documentation created from your product’s screens.

You can manage screenshots from the enterprise screenshot area or from a specific project version. The project-version view is useful when documentation must match a particular released version, while the enterprise view helps you manage screenshots across broader documentation work.

The available actions support both first-time captures and updates. Use Capture to create a screenshot, use Recapture to replace an existing screenshot, and use 3. Bulk Recapture when several existing screenshots need to be refreshed.

📷 Screenshot pending: The User Docs area showing the Manage Screenshots action.

Prerequisites

Before you begin, make sure you have the following:

• Access to User Docs and the Manage Screenshots → action.
• Access to the enterprise screenshot area or to the appropriate project and version.
• A supported product experience available for capture.
• The correct product state prepared before capture, including the page, data, and user permissions you want the screenshot to show.
• A decision about whether you need a new image (Capture) or an updated replacement (Recapture).
• Any required documentation context, such as the relevant User Flow or user guide topic.

Step-by-Step Instructions

1. Open User Docs.

2. Select Manage Screenshots →.

3. Open the screenshot area for the documentation scope you need.

   You can work at the enterprise level when you are managing screenshots broadly, or from a specific project version when the image must match that version of the product.

4. Select Capture.

   Use Capture when you need to create a new screenshot from a supported product experience.

5. Navigate through the supported product experience until the screen you want to document is displayed.

   Prepare the screen carefully before capturing it. For example, show the correct user state, page content, and visible controls that the documentation needs to explain.

6. Complete the capture from the capture experience.

   Keep the captured screen focused on the task the reader must perform. Avoid capturing unrelated navigation, temporary messages, or data that does not support the documentation step.

📷 Screenshot pending: The screenshot capture experience with the Capture action and a supported product screen ready to capture.

7. Return to the screenshot management area after completing the capture.

8. Review the captured screenshot in the context of the documentation work it supports.

   Confirm that the image shows the expected product state and that it can be used with the relevant user-facing instructions.

9. Select Recapture when an existing screenshot is no longer accurate.

   Use this action when the same documentation image needs to reflect a changed product screen, updated wording, or a different product state.

10. Select 3. Bulk Recapture when multiple screenshots need to be updated.

    Use bulk recapture for a coordinated refresh, such as after a product interface update affects several screenshots in the same documentation area.

11. Continue with Generate Documentation → when your screenshots are ready to be included in generated documentation.

Tips and Best Practices

• Use Capture for new documentation images and Recapture for replacements. This distinction helps you avoid treating an update as an unrelated new capture.

• Capture screenshots from the correct documentation scope. When documentation is tied to a particular project version, manage the screenshot from that version so the image remains aligned with the intended release.

• Prepare the screen before you capture it. A screenshot should show the exact state a reader needs, such as the relevant page, visible action, and expected content.

• Keep screenshots task-focused. If an instruction tells users to select Capture, make sure the Capture action is visible in the accompanying image when practical.

• Use 3. Bulk Recapture for planned updates affecting multiple images. This is more appropriate than refreshing screenshots one at a time when a shared interface change affects a group of documentation pages.

• Review screenshots before generating documentation. An outdated image can make otherwise accurate instructions difficult to follow.

• Coordinate screenshot updates with documentation updates. If a product change affects labels, visible steps, or a User Flow, update both the text and the related screenshots together.

Related Pages

• User Guides
• User Flow
• Generate Documentation
• Export Documentation
• Documentation Templates
• User Manuals

Troubleshooting

You cannot find the screenshot management area

Open User Docs and look for Manage Screenshots →. If the action is not available, verify that you have access to the relevant documentation area, project, or version.

The screenshot does not match the product screen you intended to document

Use Recapture to replace the existing image. Before recapturing, return the supported product experience to the exact page and state that the documentation describes.

Several screenshots are outdated after a product update

Use 3. Bulk Recapture to refresh multiple affected images. Review the related user guide steps after the refresh to ensure the written instructions still match the updated screens.