Project Export
Project export turns a project into a self-contained build that runs without the editor. It gathers the transformed assets of the project, the engine's Base data, the data of every enabled package, and the binaries the game needs (the Player, renderers, runtime plugins and the project's own C++ plugin), and writes them into one folder. For Android it goes on to compile the shader cache and build an APK or App Bundle.
The Build & Export Dialog
Open Project > Export Project.... The Build & Export dialog has two steps, Configure and Export.

Platform
The cards along the top list the target platforms of the project's asset profiles. Only platforms the computer you are working on can export are shown:
| Host | Platforms offered |
|---|---|
| Windows | Windows, Linux (through WSL), Android |
| Linux | Linux, Android |
| macOS | macOS, Android |
A card that needs a toolchain (Linux, Android) shows Checking toolchain ... while the editor looks for it, then whether the toolchain is usable. The Profile dropdown picks which asset profile of that platform the export uses. The export always uses the active asset profile, so picking a card switches it.
When a project opened on a Mac has no macOS asset profile, the editor adds one (target platform OSX). See macOS.
Tabs
| Tab | What it holds |
|---|---|
| Build | Configuration (Development, Debug or Shipping), Compile C++ plugin (builds the project's game plugin first; disabled when the project has none) and Transform all assets (re-transforms every asset before packaging). |
| Content | Scenes in build: tick the scenes to package and pick one as the LAUNCH scene. Project data and the platform's export filters are applied automatically. |
| Android app | Only for Android: app identity, icon, launch splash, build output, signing, asset packs and the device. See Android App Settings. |
| Runtime | The Startup section (RuntimeConfigs/Startup.ddl): Startup scene, Preload collection, Start position, Fallback scene menu and the splash screens, plus Startup & Boot Flow... and Platform Services.... Desktop platforms also get the Window section (RuntimeConfigs/Window.ddl): Resolution, Mode and Title. |
| Advanced | Asset profile overrides: the profile values the export uses, with Asset Profiles... to edit them. Profile changes are saved immediately and affect later asset transforms. |
The Configuration chooses which engine binaries ship. The export takes them from Binaries/<Platform>_<Configuration> and expects the project's and every package's plugins for the same configuration. It fails instead of mixing configurations. Build the Player (and the project's game target) for that configuration first. The C++ plugin step does this for the project's plugin when it differs from the editor's configuration.
Preflight
The column on the right summarises the export (target, profile, configuration, scenes, startup scene, output folder) and lists the Preflight checks. Errors block the export; warnings do not. On every platform the checks include the toolchain state and Destination writable. Android adds a long list of its own; see Preflight checks.
Destination
Pick the output folder under Output. The export empties the folder first. If it is not empty, the dialog says so. To protect your files, the export refuses:
- a relative path or a drive root,
- a folder that contains or is inside the project folder,
- a folder that contains or is inside the engine folder (exports below the engine's
Outputfolder are allowed).
Exporting
Click the export button. Its label tells you what happens: Export Windows Build, Export macOS Build, or for Android Build APK, Build & Install, Build, Install & Run, Build App Bundle or Build Bundle & Install. The Export step shows each stage (compile C++ plugin, transform assets, export data, then for Android compile shaders, build APK, install, run) with its log. Cancel Export stops after the current stage. Open Folder opens the result.
What a Desktop Export Contains
<destination>/
Bin/ Player and every library it loads, the project plugin, package plugins
Data/Base/ engine data
Data/project/ the project's transformed assets, RuntimeConfigs, data directory config
Data/<package>/ data of each enabled package
Content/ content manifest and chunks (see Shipping Builds)
There are no launch scripts. Start Bin/Player (Bin/Player.exe on Windows): it finds Data/project on its own and runs the startup flow of RuntimeConfigs/Startup.ddl, which the LAUNCH scene selection writes. To test a different scene, pass -scene on the command line (see Player).
On Windows and macOS the export reads the import tables of the Player, the runtime plugins and the renderers and ships exactly the libraries they need. On macOS, executables have no file extension, so nothing ships by default and only that dependency walk decides. Linux exports rely on the export filters.
Every desktop export ends by writing a content manifest (Content/Manifest.plContent) that tools can verify the build against and rebuild it from. See Shipping Builds.
Configuring Project Export
When you export a project for the first time, these files are added to the project directory:
ProjectBinaries.plExportFilterProjectData.plExportFilter
The first file decides which binaries are included. The second decides which data files are included. By default they #include the engine's predefined filters:
Data/Base/CommonData.plExportFilterData/Base/CommonBinaries.plExportFilter
You can extend them in your project files, or remove the #include and define your own rules.
A filter file has two sections, [EXCLUDE] and [INCLUDE]. Without any filter, every file is included. To leave out files, add a pattern to [EXCLUDE]. To include one file that an exclusion would otherwise remove, add it to [INCLUDE].
Each line is one file path pattern:
- If it starts with a
*, it matches paths that end with this pattern. - If it ends with a
*, it matches paths that start with this pattern. - If it starts and ends with a
*, it matches paths that contain this pattern. - At any other location,
*is not allowed. - All paths are relative to their data directory.
For examples, see Data/Base/CommonData.plExportFilter and Data/Base/CommonBinaries.plExportFilter.
Exporting from the Command Line
The EditorProcessor runs the same export without a window. This is useful for build machines:
EditorProcessor -project <project folder> -exportProject <asset profile> -exportTarget <folder> -exportConfiguration Shipping
| Option | Description |
|---|---|
-exportProject <profile> | Runs Build & Export for this asset profile: the C++ plugin, the asset transform, the data export and, for Android, the shader cache and the package. |
-exportTarget <folder> | The folder that is emptied and exported into. Required. |
-exportConfiguration | Development (default), Debug or Shipping. |
The process returns exit code 6 when the export fails. For Android options (-androidInstall, -androidRun and others), see Device Runs.
To stage only the data, as the dialog does before packaging, combine -transform <profile> with -exportData <folder> (exit code 5 on failure).
Troubleshooting
| Problem | Cause and fix |
|---|---|
| A platform is missing from the cards | This computer cannot export it (see the host table), or the project has no asset profile for it. Add one in Project > Project Settings > Asset Profiles.... |
| Export requires an existing runtime executable in a named build configuration | The Player for the selected configuration was never built. Build Player for that platform and configuration, then export again. |
| Shipping export requires 'vcruntime140.dll' beside the selected binaries | Windows Shipping exports need the x64 Visual C++ runtime (msvcp140.dll, vcruntime140.dll, vcruntime140_1.dll) next to the Shipping binaries. Copy them into Binaries/Windows_Shipping. |
| Refusing to export into ... | The destination is a drive root, or overlaps the project or engine folder. Choose a dedicated folder elsewhere. |
| A package or the project plugin is reported missing | It has no binaries for the selected configuration. Build it for that configuration, or pick the configuration it was built for. |