# Why does packaging my project result in 2 builds?

**URL:** <https://forums.unrealengine.com/t/why-does-packaging-my-project-result-in-2-builds/2230088>\
**Category:** Getting Started & Setup\
**Tags:** unreal-engine, question\
**Created:** [December 18, 2024, 10:08am UTC](https://forums.unrealengine.com/t/why-does-packaging-my-project-result-in-2-builds/2230088 "2024-12-18T10:08:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![BRGEzeHulton](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@BRGEzeHulton](https://forums.unrealengine.com/u/BRGEzeHulton)\
**Post date:** [February 26, 2025, 1:50pm UTC](https://forums.unrealengine.com/t/why-does-packaging-my-project-result-in-2-builds/2230088/2 "2025-02-26T13:50:05Z")

</div>

Hello, CoolJosh. I can explain why. When you package your Unreal Engine project, you might notice that two executable files are generated:

1. Bootstrap Executable:  
Located at `WindowsNoEditor\YourProjectName.exe`, This small launcher conducts initial system checks and ensures that necessary prerequisites are installed before launching the main game.

2. Main Game Executable:  
Found at `WindowsNoEditor\YourProjectName\Binaries\Win64\YourProjectName.exe`, this is the primary executable containing your game’s core functionality.

This structure is intentional, as the bootstrap executable enables a smoother user experience by managing setup tasks before launching the main game.

If you would like more information, I can provide you with the link regarding Packaging Unreal Engine Projects.

> **[Packaging Unreal Engine Projects | Unreal Engine 5.5 Documentation | Epic...](https://dev.epicgames.com/documentation/en-us/unreal-engine/packaging-unreal-engine-projects)**
>
> Packaging Unreal game projects for distribution.

---

_[View the full topic](https://forums.unrealengine.com/t/why-does-packaging-my-project-result-in-2-builds/2230088)._