---
title: "What Assets are"
description: "A visual library scoped to one Project: images found on your site, images you upload, and images generated for posts."
updated: "2026-08-18"
verifiedAgainst:
  - packages/shared/src/assets.ts
---

Assets is the library every article draws its visuals from. It is scoped to the
Project, so one product's screenshots never appear in another product's blog.

## Where assets come from

| Origin | Meaning |
| --- | --- |
| `website_scrape` | Found in the markup of your own site |
| `website_capture` | A rendered capture of one of your pages |
| `upload` | You added it |
| `post_generated` | Generated for a specific article |

## Kinds

Assets are classified as a product screenshot, a brand visual, a diagram, a logo,
or other. The kind is what lets a drafting run ask for the right sort of picture
rather than the next available one.

## Statuses

<PropertyList>
  <Property name="pending_review">
    Found, not yet approved. Not used in articles.
  </Property>
  <Property name="active">
    Approved and available.
  </Property>
  <Property name="archived">
    Kept, not used. The right state for something outdated that you do not want
    rediscovered on the next scan.
  </Property>
</PropertyList>

<Callout variant="note">
  Nothing found on your website is used in an article until you approve it. The
  review step is the whole point of the library.
</Callout>

## Where to go next

<CardGrid>
  <Card title="Discovering images" href="/assets/discovery">
    How your site is read, and the limits that apply.
  </Card>
  <Card title="The review queue" href="/assets/review">
    Approving, rejecting and archiving.
  </Card>
  <Card title="Placing images" href="/assets/placement">
    Putting a specific asset in a specific section.
  </Card>
  <Card title="Generated images" href="/assets/generation">
    Style, aspect ratio, references and budget.
  </Card>
</CardGrid>