Export

Scene Insight can write the current bake to four formats from the Export dropdown in the toolbar. Each export includes the map name and every cluster's metrics and composite score.

Format	Extension	Best for
CSV	.csv	Spreadsheets, pivot tables, custom charts
JSON	.json	Tooling, dashboards, programmatic processing
Markdown	.md	Pull-request summaries, design docs, wikis
HTML	.html	A self-contained, shareable report

CSV

One row per cluster with every metric as a column. Drop it into Excel or Google Sheets to sort, chart or pivot. Ideal when an artist or producer wants the numbers without opening the editor.

JSON

The full structured dataset — every cluster, every metric, the score and the map name. Use it to feed an internal dashboard, diff builds programmatically, or run custom checks in CI.

Markdown

A formatted report table that pastes cleanly into a GitHub/GitLab pull request, a Notion page or a design doc. Great for "here's where the level stands this milestone" write-ups.

HTML

A single self-contained .html file you can open in any browser and send to someone who doesn't have the project — no editor, no plugin needed. The most shareable format for stakeholders.

Using exports in CI

Because JSON and CSV are plain text and the bake is fully static, you can drive Scene Insight from an automated process:

1. Open the level and bake.
2. Export JSON.
3. Have your pipeline flag any cluster whose composite score exceeds your threshold.

Pair this with snapshots to fail a build when a zone regresses past its baseline.

tip

Export HTML for humans and JSON for machines. The HTML report is the one to attach to a milestone review; the JSON is the one your CI parses.