Screenshots are most useful when they are prepared for the exact slide that needs them. In the hosted flow, the preview rail is the source of truth for where each screenshot belongs.

Recommended approach

• refresh the preview after structural YAML changes
• read the preview row before uploading anything
• attach one screenshot to one matching row
• keep the screenshot focused on the content that matters for that slide

Common problems

• uploading before refreshing the preview
• attaching the same image to several different rows
• using screenshots that are too dense, too cropped, or unrelated to the row

What good alignment looks like

Good screenshot preparation means the preview rail, upload panel, and draft content still refer to the same slide. When those three stay aligned, the generated deck is easier to read and easier to review.

When not to upload

If the current draft does not call for an image-bearing slide, do not add screenshots just to fill space. The upload step should follow the draft, not override it.