Export only from the approved sceneRevision + snapshotId and under an approved output root.
Existing files require action-bound overwrite authorization.
In auto_with_budget, export.file may write a new file in an allowed format under the
session's approved root, using the current committed snapshot, without another user prompt.
review_only rejects export even with a claim. Following user takeover, inspect again and create
a new transaction/snapshot; old approvals must not be reused.
Call export.file; verify existence, non-zero size, SHA-256, format, and receipt schema. Model
formats require isolated re-import validation; images and MP4 require media probing. Distinguish
local export success from any downstream rendering system.
Use export.extended for EXR, USD/USDC and Alembic and preserve its receiptVersion 2.0.0 instead
of rewriting it as the legacy receipt. For a long EXPORT or RENDER_STILL, use
blender-background-jobs; export.file itself remains synchronous. Do not promise that
pause interrupts an already-running synchronous export.
When to Use
Use when an approved Blender snapshot needs to produce local artifacts such as models, images, videos, EXR, USD, or Alembic. Do not export when the scene is still being modified or only a preview is needed.
Prerequisites
- Exact
sceneRevision + snapshotId, format, filename, output root directory, and overwrite authorization. - Confirm format capabilities, dependency packaging strategy, coordinate/unit requirements, and downstream compatibility targets.
Workflow
Step 1. Check that the snapshot is still the approved version, resolve and validate the normalized output path.
Step 2. Select synchronous export, extended export, or background job based on format; silent format downgrade is prohibited.
Step 3. Write to a temporary target, complete format validation, then atomically deliver to the final path.
Step 4. Isolate and re-import models, probe media, and reopen .blend in an independent directory.
Step 5. Generate a receipt containing SHA-256, size, format, snapshot, and validation results.
Validation and Delivery Evidence
At minimum, prove that files exist and are non-empty, hashes, format signatures, and the corresponding reopen/re-import/media probe pass. Extended formats retain receiptVersion 2.0.0.
Rules and Capability Boundaries (Not Applicable Scenarios)
Local export does not equal publishing or downstream platform compatibility; do not overwrite unauthorized files, do not reuse pre-takeover approvals, and do not claim that synchronous export can be paused.
Gotchas (Common Issues and Recovery)
- File already exists: stop and request overwrite authorization for that action.
- Re-import failed: retain the source snapshot and logs; success cannot be determined solely by the file being non-empty.
- Missing dependencies: check packaging and relative paths, and re-validate opening in an independent directory.