What exports do
An export is the final processing step for a project. It takes the current project state, source assets, editor layers, vector features, terrain edits, modifiers, target game, and relevant collections, then creates downloadable output files.
Exports are not the same as source data processing. Source processing prepares inputs for editing. Export processing packages the edited project into the format expected by the selected target.
When export is available
Export is available when the project is ready enough for the selected target. The project must have the source assets and editor state the target requires, and the selected export target must match the project game.
Farming Simulator 25 projects use FS25 export targets. Minecraft projects use Minecraft export targets and require choosing Java or Bedrock Edition in the export dialog.
Export processing
Exports run as background jobs. A queued export waits for processing capacity, a running export is being generated, a retrying export is being attempted again after an error, and a completed export exposes download links on the export detail page.
The export worker can read layer metadata such as mapping collection IDs, vector bounds, terrain source information, modifiers, and collection data. This is how editor choices become game-specific output instead of a generic archive.
Downloads and retention
Completed exports are saved against the project so you can open the export detail page and download the artifact. Download links are generated when you open the detail page and may expire, so reopening the page can create a fresh link.
The number of saved exports and the number of exports you can start per hour are limited by team tier. Older output files may also be purged after a retention period, so download important results when they are ready.
Export artifacts as assets
A completed export can expose its output artifact as an asset. That keeps exports connected to the same storage and download system used by source data assets.
If an export fails, open the export detail page to read the error message. The project state and source assets remain available, so you can fix the cause and queue another export when limits allow.