---
title: "Adding Screenshots to Your Buuk Pages"
url: "/help/buuk/adding-screenshots-to-your-buuk-pages"
updated: "2026-11-13T13:32:01.912Z"
---
# Adding Screenshots to Your Buuk Pages

Screenshots make a step obvious when a sentence alone would leave readers guessing. In the Buuk editor, you can upload images directly, or let Buuk capture screens from your product automatically while drafting an article. Either way, nothing reaches your live help center until you publish.

## Adding an image yourself

Use this method any time you have a screenshot ready to drop into an article — including on pages like your "How it works" overview.

1. Open the article in the editor.
2. On a new line, press `/` to open the insert menu.
3. Choose **Image**, then select a PNG, JPG, WebP, or GIF file from the picker.
4. Before uploading, give the file a descriptive name — it becomes the image's alt text and the caption readers see underneath it on the public page. `export-settings.png` is more useful than `image-3.png`.
5. Publish the article when the copy and images are ready.

Every upload lands in your draft first. Customers won't see the image — or the rest of the article — until you publish.

### Image limits and compression

Buuk compresses images in your browser before they upload, so pages stay fast:

- Images wider than 1,920 px are scaled down.
- Most JPEG and WebP files are re-encoded at high quality when the smaller version saves space.
- Files already under about 400 KB upload as-is.
- GIF files are never re-encoded, so animated GIFs stay animated.
- A single image can be up to 24 MB. Larger files are rejected with a message asking you to try a smaller one.

### Annotating an image

Select an image already placed in the editor and choose **Annotate** to blur sensitive details, crop the frame, or draw arrows pointing at the part of the screen you're describing. Saving the annotation uploads a new PNG and swaps it into the article — the original file you uploaded stays untouched.

### How images appear to readers

On the public page, images load in place and open in a lightbox when clicked, giving readers an enlarged view with a magnifier cursor and a close button to return to the article.

## Letting Buuk capture screenshots automatically

Instead of taking screenshots yourself, you can have Buuk capture them from your product while it drafts or updates an article.

1. During onboarding, or later in **Settings → General**, make sure your product website is set. Buuk uses this domain for research and as a fallback URL for public-page captures.
2. Open **Automations** and add **Product screenshots**.
3. Set **App URL** to a page Buuk can open in a browser — for example, `https://app.yourproduct.com`.
4. If the screens you need sit behind a login, write numbered steps for a dedicated demo account. These steps are stored encrypted. Skip this if the pages you want captured are already public.
5. In the dashboard, open **Ask Buuk** (`⌘J`) and ask it to draft an article — for example, "Draft an article about how our dashboard works." You can also accept a suggested update from **Suggestions**.
6. Open the resulting draft. Screenshots appear under the headings they illustrate — up to three per draft.
7. Replace, crop, annotate, or delete anything that doesn't look right, then publish only when the page is ready.

Automated capture is best-effort. A missed screenshot still leaves you with a complete draft you can finish by hand using the manual upload steps above.

### A note on login

Prefer a dedicated screenshot user with a viewer role rather than an admin account. Simple email-and-password login generally works; SSO, MFA, or unusual sign-in flows often won't. If a capture fails for this reason, upload the screenshot yourself.

### If your product is a mobile app

Automated capture runs in a browser, so it cannot open iOS or Android apps directly. Point **Automations → Product screenshots** at a page Buuk can load instead — your web app, marketing site, or app store listing — if you want anything captured automatically.

For screens that only exist inside the native app, capture them from a simulator or device, or export from App Store Connect or Play Console. Then press `/` in the editor, choose **Image**, and upload the file manually.

If you don't have a web app, leave the automation off or leave **App URL** empty. Your product website set in Settings → General is still used for research even without automated screenshots.

## Troubleshooting

**The capture didn't match my heading.**

Automated screenshots are best-effort. Open the draft, delete the mismatched image, and upload the correct one manually with `/` → **Image**.

**My image won't upload.**

Check the file type (PNG, JPG, WebP, or GIF) and size — files over 24 MB are rejected. Try exporting a smaller or recompressed version.

**Login-protected screens aren't being captured.**

Confirm the demo account steps are correct and that the login page uses simple email-and-password authentication. SSO and MFA are not supported by the capture automation.

**Images look fine in the editor but aren't visible to customers.**

Images only appear on the public page once the article itself is published. Check **Preview in help center** to confirm layout, then publish.

## FAQ

**Do screenshots publish automatically once Buuk captures them?**

No. Captured screenshots land inside a draft, the same as AI-written copy. A person reviews, edits, and publishes.

**Can I mix manual uploads and automated captures in the same article?**

Yes. You can upload images yourself anywhere in the editor and still use automated captures for other sections.

**Will annotating an image affect the original file?**

No. Annotating saves a new, separate PNG and swaps it into the article in place of the original.