Audit your project's assets

Over a project's life, unused assets, leftover redirectors, and naming drift accumulate. This guide produces a prioritized audit report with tidy_assets — and it's read-only, so running it can't change your project.

Before you start

• Your AI client is connected.
• Recommended: the UE connector is installed in the project, so your client can export the inventory itself.

Export the asset inventory

tidy_assets works from an inventory file — a JSONL export of your project's asset registry.

With the connector: just ask — your client calls the connector's asset-inventory tool in the editor:

Export an asset inventory of my project, then audit it with tidy_assets.

The inventory lands at Saved/spaghetti_inventory.jsonl and the audit runs on it.

Without the connector: ask anyway — your client gives you a short script to run in the editor's Python console (Tools → Execute Python Script) that writes the same file, then continues with the audit.

Read the report

The report is grouped by reclaimable impact:

• Unused assets — no referencers anywhere in the project, with the disk space each would reclaim. Biggest wins first.
• Redirectors — old names still redirecting; a fix-up pass consolidates them.
• Naming violations — assets breaking the convention, listed with the expected name.
• LOD problems — oversized assets and meshes without LODs.

A downloadable CSV of the full report is included (link valid 24 hours).

Act on the findings

The audit never modifies anything. To fix what it found, generate a reviewed cleanup script — see Generate an editor script. Deleting assets is best done by you in the editor; a generated script can prepare and verify, but destructive steps stay commented out until you apply them by hand.

Verify

• The report appeared in your chat with stats and prioritized findings.
• The CSV link downloads the full report.

Next steps

• tidy_assets reference — inputs, outputs, and limits
• Generate an editor script