> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryquibble.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Screenshots and page activity

> Choose the context attached to your feedback.

Attach a screenshot or page activity to a quibble, or leave them off. A quibble
always keeps your note, its page URL, and the selected element's context.

## Attach a screenshot

1. Place a comment. Quibble captures the visible viewport for the composer.
2. Choose **Add screenshot**.
3. Inspect the preview.
4. Save the comment.

A project can enable screenshots by default.

> [!WARNING]
>
> Check the preview for other sensitive information before saving.

## Remove a screenshot

1. In the composer, find the attached screenshot.
2. Choose **Remove**.

## Attach page activity

Page activity is recent console, error, and network-event context from the
project page.

1. Open Quibble on the project page, then place a comment.
2. Choose **Add page activity**.
3. Inspect the attached activity.
4. Save the comment.

Activity attaches automatically when something broke, such as an error or a
failed request. A project can also attach it to every quibble.

## Redact part of your page

Add the `data-quibble-redact` attribute to any element you want hidden in
screenshots. Password inputs are redacted automatically.

## What is and is not captured

* A screenshot covers only the visible viewport, not the full page.
* Quibble's overlay is hidden from the capture.
* The capture stays in the tab until you attach it. An unattached capture is not stored or uploaded.
* Password inputs and regions marked `data-quibble-redact` are redacted automatically.
* Page activity collection starts after you open Quibble on the page. It cannot recover activity from before that point.
* Collected activity is bounded and redacted for credentials and secrets.
* Unattached activity is not stored or uploaded.
* Page activity is not a session recording.

## Who can see evidence

Shared quibbles are available to members of their workspace. Creating an issue
can copy evidence or an evidence link to the selected tracker. A connected
coding agent can read the quibbles you can access.

See the [privacy policy](https://tryquibble.com/privacy) for the full data-handling
details.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.