> ## 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.

# Core concepts

> The building blocks of BenchCanvas: projects, canvas, flows, frames, screens, and connections.

A few terms show up throughout BenchCanvas. Understanding them makes everything else easier.

## Project

A **project** is your workspace for one piece of analysis. It holds a single canvas and everything on it. Each project has a name (usually based on the captured site), a status while it is being captured, and an optional share link.

You manage projects from the dashboard at [app.benchcanvas.app/app](https://app.benchcanvas.app/app).

## Canvas

The **canvas** is the infinite, Figma-style board where your work lives. You pan, zoom, and arrange everything on it. A project always has exactly one canvas. Learn more in [Canvas overview](/canvas/overview).

## Flow and frame

A **flow** is a logical user journey, for example a signup flow or a checkout flow. On the canvas, each flow lives inside a labeled **frame**. Frames keep multiple flows organized and make it easy to compare different URLs side by side in the same project. See [Flows and frames](/canvas/flows-and-frames).

## Screen

A **screen** is a single node on the canvas representing one page or state. Each screen has a screenshot, a URL, a title, and a **page type** (auto-detected labels like homepage, pricing, or signup, plus project-scoped custom types). See [Screens](/canvas/screens).

## Connection

A **connection** is a directional link between two screens that shows how a user navigates from one to the other. BenchCanvas detects connections automatically during a capture, and you can add or remove them manually. See [Connections](/canvas/connections).

## Capture

A **capture** is the automated process that discovers pages, takes screenshots, and detects navigation. Capturing from a URL is the core workflow, but you can also import from a PDF or screen recording, add screens manually, or start from a template. See [Capture overview](/capture/overview).

## How they fit together

```mermaid theme={null}
flowchart TD
  Project --> Canvas
  Canvas --> Frame1["Frame (flow)"]
  Canvas --> Frame2["Frame (flow)"]
  Frame1 --> ScreenA[Screen]
  Frame1 --> ScreenB[Screen]
  ScreenA -->|connection| ScreenB
```

## Other terms you will see

| Term             | Meaning                                                                      |
| ---------------- | ---------------------------------------------------------------------------- |
| Page type        | Auto-assigned label for a screen, such as homepage, pricing, or checkout     |
| Flow size        | How many screens and how deep a capture goes: Quick, Standard, or Deep       |
| Template         | A published flow you can copy into your own workspace                        |
| Share link       | A public, read-only URL to a canvas                                          |
| Connect AI (MCP) | Hook Claude Code, Cursor, Codex, or another MCP client into a shared project |
| AI report        | A structured analysis of a single screen                                     |
| Flow chat        | The AI assistant that has context about your whole flow                      |
| Credits          | Usage currency for AI and capture actions (rolling out in beta)              |

<Card title="Ready to capture?" icon="camera" href="/capture/overview">
  Head to the Capture overview to start mapping a product.
</Card>