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

# Captures & Storage

Figranium automatically captures visual evidence and intercepted files from your automation runs. This is crucial for debugging, auditing, and ensuring quality.

## **Screenshots**

By default, every successful task execution (in `agent` or `scrape` mode) captures a final screenshot of the page.

* **Format**: PNG
* **Location**: `public/captures/<run_id>_screenshot.png`
* **Accessibility**: View in **Captures** tab or via API.

### **Custom Screenshots**

You can trigger additional screenshots during an `agent` task using the `screenshot` action block.

* **Filename**: `<run_id>_<timestamp>_<custom_suffix>.png`
* **Full Page**: (Optional) Capture the entire scrollable area.

## **Video Recordings**

Figranium can record full session videos (WebM format).

* **Enable**: Set `disableRecording` to `false` in the task editor.
* **Location**: `public/captures/<run_id>.webm`
* **Playback**: View directly in the **Captures** tab.

**Note**: Recording consumes more disk space and CPU. Disable it for high-volume scraping.

## **File Downloads**

Figranium automatically intercepts files downloaded during an automation run. For more details on how to manage and access these files, see the [File Downloads](/docs/file-downloads) documentation.

## **Cookie Persistence**

Figranium stores cookies and browser session state in persistent profile directories on disk — one per execution mode:

* `data/browser-profile` — agent mode
* `data/browser-profile-scrape` — scrape mode
* `data/browser-profile-headful` — headful/VNC mode

Each mode has its own isolated profile. Cookies from a headful login are bridged to agent and scrape runs automatically via `data/headful-storage-state.json` — headful writes this file every 30 seconds and on session close; agent and scrape inject it at startup (skipped for stateless runs).

* **Persistence**: Cookies persist across browser restarts and task executions (unless `statelessExecution` is enabled).
* **Management**: View, copy, and delete individual cookies in **Settings > Data**. Click the **Copy** button next to any cookie to copy its value to your clipboard.
* **Clear All**: Use the "Clear Storage" button in Settings to wipe all session data.

### **Upgrading from v0.9.6 or Earlier**

If you are upgrading from a version that used `storage_state.json`, Figranium will automatically migrate your existing cookies into all three profile directories on first startup. The `storage_state.json` file is then deleted. No manual action is required.

### **Stateless Execution**

If you enable `statelessExecution` in a task, it will launch a fully ephemeral in-memory browser session (no cookies, no disk profile written) and discard any changes upon completion. This is ideal for testing login flows or anonymous scraping.

## **Storage Management**

### **File Cleanup**

Screenshots, videos, and downloaded files accumulate in `public/captures`. Video recordings are stored separately in `data/recordings`. You can delete or download them:

1. **Download**: Click the download icon on any capture card to save the file to your device.
2. **Single delete**: Click the delete icon on a capture card in the **Captures** tab, or remove it from the **Results** drawer.
3. **Clear all**: Click the trash icon in the **Captures** tab header to delete every screenshot and recording at once. You can also clear all captures from **Settings > Data**.
4. **API**: Use `DELETE /api/data/captures/:name` to remove individual files programmatically.

When you clear captures — whether from the **Captures** tab or from **Settings > Data** — both screenshots in `public/captures` and video recordings in `data/recordings` are deleted.

### **Execution Logs**

Execution metadata is stored in `data/executions.json`. Browser session profiles are stored separately in `data/browser-profile*` directories and are not affected by execution log rotation. This file grows over time. Figranium automatically rotates logs (configurable via `MAX_EXECUTIONS` in `server/constants.js`, default 500) to prevent unlimited growth.