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

# HTML

> Standalone, styled HTML reports and pages Addison builds from your data, rendered in the app and downloadable as a single .html file.

An **HTML** artifact is a standalone, styled web page (`.html`) that [Addison](/features/addison) builds from your data — a data narrative, a one-page report, or a visual summary with charts and KPI cards. It's a *second-class* artifact: a file in your [project](/features/projects) rather than a native Summation document, but it renders in a full in-app viewer and downloads as a single self-contained `.html` file.

**Where each action lives in the UI** (for telling users where to click):

* **Opening an HTML artifact**: HTML files live in a [project](/features/projects). Open one from the project file list to render the page in the in-app **HTML viewer**.
* **Top bar**: a breadcrumb (project name / page title) at the center and a **⋯** menu at the top-right with **Rename**, **Share**, **Styles**, **Verification**, **Download as HTML**, **Versions**, and **Delete**.
* **Body**: the full styled page renders inline (hero, KPI stat cards, charts, and sections), exactly as it exports.
* **Verification and Ask / Edit with AI**: HTML pages are first-class **verification** subjects (`html_file`) — the viewer mounts a **verification badge** (shield) in the top bar that opens the **Verification Hub**, the same as [reports](/features/artifacts/reports#verify-a-report) and [decks](/features/artifacts/decks). In the preview you can also select a region to **Ask** or **Edit with AI** (gated by the `ui_html_ask_edit` feature flag).
* **Creation**: no public endpoint generates an HTML artifact. Addison builds it (an `html-template-*` or `workbook-report` skill), or a [playbook](/features/artifacts/playbooks) produces it. Because the result is a file, it is listed, downloaded, and deleted through the [Files API](/features/projects/files).

<Frame caption="An HTML report rendered in the in-app viewer, with the ⋯ menu showing Rename, Share, Download as HTML, Versions, and Delete">
  <img src="https://mintcdn.com/summation-676748f5/bD5B6OO2CVOWNhOR/images/features/artifacts/html/html-report.png?fit=max&auto=format&n=bD5B6OO2CVOWNhOR&q=85&s=5cc2213ec15d9118fd4dc20456ccf176" alt="A styled HTML report titled 'London 2012 at a Glance.html' rendered in Summation's in-app viewer under a 'My Project' breadcrumb. A dark hero reads 'The London Games at a glance.' above a row of KPI stat cards (Countries 205, Athletes 10,502, Sports 32, Events 302, Medals 1,941), followed by a 'The medal table.' section with a horizontal bar chart titled 'Top 10 nations by gold — 2012' comparing gold and total medals for the United States, Russia, Great Britain, China and other nations. The top-right toolbar shows a shield icon and a ⋯ menu button." width="2934" height="1866" data-path="images/features/artifacts/html/html-report.png" />
</Frame>

## What Addison builds

HTML artifacts are finished, presentation-ready pages:

* **Self-contained** — one `.html` file with its styling and charts inline, nothing external to load
* **Template-driven** — editorial, light, and dark themes via Addison's `html-template-*` skills
* **Optionally workbook-traced** — with the `workbook-report` skill, every number traces cell-by-cell to an auditable Excel workbook

## Create

<Tabs sync={false}>
  <Tab title="In the app">
    Ask [Addison](/features/addison) in a chat for the page or report you want, or produce one by running a [playbook](/features/artifacts/playbooks). Addison writes the `.html` into your project and opens it in the viewer.
  </Tab>

  <Tab title="Via the API">
    <Card title="Coming soon" icon="clock" horizontal>
      Generate an HTML artifact with Addison.
    </Card>
  </Tab>
</Tabs>

## Open and view

<Tabs sync={false}>
  <Tab title="In the app">
    Open the file to render the full styled page in the in-app viewer. It shows exactly what the downloaded `.html` contains.
  </Tab>

  <Tab title="Via the API">
    <Card title="GET /v1/projects/{projectId}/files/{fileId}/content" icon="code" href="/api-reference/files/download-file-content" horizontal>
      Download the page's HTML.
    </Card>

    <Card title="PUT /v1/projects/{projectId}/files/content" icon="code" href="/api-reference/files/write-file-content" horizontal>
      Create or overwrite the page's HTML.
    </Card>
  </Tab>
</Tabs>

## Versions

<Tabs sync={false}>
  <Tab title="In the app">
    Each save adds a version. Open **Versions** in the **⋯** menu to see and switch between earlier versions of the page.
  </Tab>

  <Tab title="Via the API">
    <Card title="Coming soon" icon="clock" horizontal>
      List and restore versions.
    </Card>
  </Tab>
</Tabs>

## Manage as a file

An HTML artifact is an ordinary file in your project, so every [file operation](/features/projects/files) applies — move it between folders, copy it to another project, duplicate it, or delete it.

<Tabs sync={false}>
  <Tab title="In the app">
    From the **⋯** menu in the top bar (or the file's row in the project file list): **Rename**, **Share**, **Styles**, **Verification**, **Download as HTML**, **Versions**, or **Delete**.
  </Tab>

  <Tab title="Via the API">
    <Card title="GET /v1/projects/{projectId}/files/{fileId}/content" icon="code" href="/api-reference/files/download-file-content" horizontal>
      Download the page.
    </Card>

    <Card title="DELETE /v1/projects/{projectId}/files/{fileId}" icon="code" href="/api-reference/files/delete-file" horizontal>
      Delete the page. Requires `confirm=true`.
    </Card>

    <Card title="Coming soon" icon="clock" horizontal>
      Rename, move, copy, and share.
    </Card>
  </Tab>
</Tabs>

## Promote to a first-class artifact

HTML pages already support verification on their own, but a common flow is still to start with an HTML page and then have Addison rebuild it as a first-class artifact — an interactive [dashboard](/features/artifacts/dashboards), a presentation [deck](/features/artifacts/decks), or a verified [report](/features/artifacts/reports). The native document gains full data citations and a dedicated home in the app.

<CardGroup cols={3}>
  <Card title="Dashboards" icon="chart-mixed" href="/features/artifacts/dashboards">
    Turn the page into interactive charts and KPIs.
  </Card>

  <Card title="Decks" icon="presentation-screen" href="/features/artifacts/decks">
    Turn the content into a presentation.
  </Card>

  <Card title="Reports" icon="file-lines" href="/features/artifacts/reports">
    Turn the narrative into a verified written report.
  </Card>
</CardGroup>