Exporting Data
After capturing profiler data, the plugin automatically exports it as CSV files.
Exported Files
FrameDoctor exports multiple CSV files to a local directory:
| File | Contents |
|---|---|
frame_timing.csv | Per-frame CPU/GPU timing data |
memory.csv | Memory usage and GC metrics per frame |
gc_allocations.csv | GC allocation details (if any) |
rendering.csv | Draw calls, batches, triangles per frame |
textures.csv | Texture asset inventory |
meshes.csv | Mesh asset inventory |
materials.csv | Material asset inventory |
audio.csv | Audio clip inventory |
shaders.csv | Shaders in use |
scene_objects.csv | GameObjects in scene |
cameras.csv | Camera settings |
lights.csv | Light settings |
summary.txt | Human-readable summary |
Export Location
By default, data is exported to Application.persistentDataPath/FrameDoctor. You can change this in Preferences > FrameDoctor > Export Path.
Click Open Export Folder in the FrameDoctor window to navigate directly to your exported files.
Using Your Data
The CSV files are standard comma-separated format and can be used with:
- Spreadsheet applications (Excel, Google Sheets)
- Data analysis tools (Python/pandas, R)
- Custom scripts or pipelines
Optional: AI-Powered Analysis
For automated performance analysis, you can upload your CSV files to the FrameDoctor web service (opens in a new tab):
- Go to framedoctor.dev/upload (opens in a new tab)
- Create a free account
- Drag and drop your exported CSV files
- Receive an AI-generated performance report
The web service is a separate product from the Unity plugin. See framedoctor.dev/pricing (opens in a new tab) for details.
File Size Considerations
- Typical exports are 1-10 MB depending on frame count
- Large captures (1000+ frames) may take longer to analyze
- Asset inventories scale with project size
Data Privacy
Your profiler data stays on your local machine unless you choose to upload it. The exported files contain only profiler metrics — no source code, game assets, or project files are captured.