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

# Troubleshooting captures

> What to do when a capture is blocked, thin, or not what you expected.

Most captures just work, but the open web is messy. Here is how to handle the common cases.

## The capture returned very few screens

This usually means the site was hard to crawl by following links.

* BenchCanvas may automatically use the [sitemap fallback](/capture/sitemap-fallback) to recover more pages.
* Increase the [flow size](/capture/options) to explore more deeply.
* [Expand the flow](/capture/expand-flow) from a key screen to add detail.
* [Add screens manually](/capture/add-screens) to fill specific gaps.

## The site blocked the capture

Some sites detect and block automated browsers with bot challenges or CAPTCHAs. When this happens, BenchCanvas surfaces an error explaining what went wrong.

Options when a site blocks crawling:

<CardGroup cols={2}>
  <Card title="Use the Chrome extension" icon="chrome" href="/extension/capture-from-browser">
    Capture from your own browser session, which behaves like a normal visitor.
  </Card>

  <Card title="Record a video" icon="video" href="/capture/video-to-flow">
    Record the flow yourself and import it. (Beta)
  </Card>

  <Card title="Import a PDF" icon="file-pdf" href="/capture/pdf-to-flow">
    Upload a deck or exported walkthrough and turn each page into a screen.
  </Card>
</CardGroup>

## The flow needs a login

Public crawling cannot get past authentication. To capture logged-in pages, [record an authenticated flow](/extension/record-authenticated-flows) with the Chrome extension and import it.

## Screenshots do not look right

* Try a different [screenshot variant](/canvas/screenshots): desktop or mobile, viewport or full page.
* [Replace a screenshot](/canvas/screenshots) on a single screen to recapture it.

## Crawl errors

BenchCanvas shows specific error messages when a capture fails, so you can tell whether the issue was a block, a timeout, or an unreachable URL. Read the message, adjust your approach, and try again.

<Note>
  Still stuck? Send a note through [in-app feedback](/account/roadmap-and-feedback) with the URL you were trying to capture.
</Note>