The plan. FastExport resolves the whole export - every target, every filename, every collision - once, then caches it. Pressing Export is only the writing. It also means you get to read the plan before committing to it.

Your choice of Ask or Skip, plus duplicate detection across the planned set. There is also a late collision recheck: Ask confirms only the paths you actually reviewed, so a file that appears between the review and the write is not overwritten.

No, deliberately. GLB is always a single binary file. Separate .gltf output turns one asset into several loose files that are easy to deliver incompletely, so it is not offered.

Only temporarily. In Object scope a selected Empty acts as the move-to-origin pivot for its hierarchy. Selection and transforms are restored after success, after failure, and after cancellation.

Yes. Presets exclude output paths by design, so a shared preset cannot point someone else's export at your folder. Unknown forward-compatible format settings are preserved when a preset is updated or exported, so a colleague on a newer build does not lose settings by round-tripping one.

{name}, {object}, {collection}, {scene}, {blend}, {format} and {preset}. Unavailable tokens, path traversal, unsafe names and duplicate destinations are rejected before the run, not discovered during it.

No. FastExport makes no network requests.

Manually, and it is small: prefix/suffix becomes {prefix}{name}{suffix}, old skip-existing maps to Skip, old collection maps to Scene Collections. Both add-ons can remain enabled - they use independent namespaces.