Version: 2019.1 (switch to 2019.2b or 2018.4)
Windows General
Windows Debugging
Other Versions

Windows standalone Player build binaries

When you build a Unity project to the Windows standalone platform Unity produces the following files (where ‘ProjectName’ is the name of your project):

  • ProjectName.exe - The project executable. This contains the program entry point which calls into the Unity engine when launched.

  • UnityPlayer.dll - this DLL contains all the native Unity engine code. It is also signed using the Unity Technologies certificate, allowing easy verification that the engine was not tampered with.

  • *.pdb files - Symbol files for debugging. Unity copies these to the build directory if you enable Copy PDB files in the Build Settings window.

  • WinPixEventRuntime.dll - This DLL enables Windows PIX profiler support. Unity only creates this file if you check the Development BuildA development build includes debug symbols and enables the Profiler. More info
    See in Glossary
    checkbox in the Build Settings window.

  • ProjectName_Data folder - This folder contains all the data needed to run your project.

Rebuilding the game executable

Unity creates the source code for ProjectName.exe in this folder: Editor\Data\PlaybackEngines\WindowsStandaloneSupport\Source\WindowsPlayer.

To modify the executable, or ship code which you built yourself (if you want to sign it, for example), you must rebuild the executable and place it in your built game directory.

To build your executable outside of Unity, you need Visual Studio 2015 or 2017 with ‘Common Tools for Visual C++’’ and Windows support for C++ installed.

  • 2017–07–19 Page published with limited editorial review

  • Windows standalone Player build binaries changed in 2017.2 NewIn20172

  • Windows XP support in Standalone Player removed in 2018.1

Did you find this page useful? Please give it a rating:

Windows General
Windows Debugging